Conversation
hoffie
left a comment
hoffie
left a comment
There was a problem hiding this comment.
This is great, thanks for doing this! I have nothing to add :)
I guess this will also help shorten the release tracking checklist for the next iterations as we can just reference this document. :)
|
|
||
| ``` | ||
| $ git tag r3_7_0 | ||
| $ git push origin tag r3_7_0 |
There was a problem hiding this comment.
Have never seen or used this syntax, but seems correct based on git push --help.
There was a problem hiding this comment.
There may be other ways to achieve it via Github, but the above was what worked for me. It means the complete process can be achieved via the shell without visiting the website.
There was a problem hiding this comment.
Also needs
git tag latest
git push tags --force
to move latest to the latest release. (origin is redundant, in the above, I think.)
There was a problem hiding this comment.
Ah yes, but only if it’s a formal release, not a pre-release, of course. I’ll update soon.
In line 93 above, I think origin is required, because <repository> is required to precede a <refspec>, which is what tag r3_7_0 is.
There was a problem hiding this comment.
Reading the man page for git push, I think you meant git push --tags --force, but I think that could be slightly risky, and I would prefer the more specific git push --force origin tag latest
|
https://github.com/softins/jamulus/blob/release-process/RELEASE-PROCESS.md |
|
|
||
| ## If this is a proper release, move the `latest` tag | ||
|
|
||
| This needs the `--force` option to overwrite the existing `latest` tag and move it to the current commit: |
There was a problem hiding this comment.
You could also delete and re-apply the latest tag.
4 participants
Document the process for doing a pre-release or release.