-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update release process documentation #17461
Conversation
Goes along with galaxyproject/galaxy-release-util#8, so hopefully we will have 24.0.0 as a release both on github and uploaded to pypi. |
This issue is generated via `make release-issue` at the end of the process. | ||
The final result of the release process are | ||
- a new branch (release_YY.N) from which point releases are created | ||
- a tag pointing at the first commit of the branch (vYY.N) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if we still want this ? It doesn't hurt anything, but maybe we should let the first point release create the first tag ?
Co-authored-by: John Davis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for all this documentation @mvdbeek - this is very helpful!
Co-authored-by: John Davis <[email protected]>
This PR was merged without a "kind/" label, please correct. |
Documenting what we're doing now. I'll update the release issue script to reflect that as well.
How to test the changes?
(Select all options that apply)
License