-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add some more notes to the release workflow #1121
Add some more notes to the release workflow #1121
Conversation
#. If there have been release-specific commits, In GitHub, create a pull request that merges the version branch into | ||
``dev``. Proceed with the nominal review & merge process described in steps (10) and (11) in the :ref:`git & GitHub | ||
Workflow <git-and-github-workflow>` section. |
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.
I am not good with release. I tried to release last month to fix a bug and I think I had to merge PR before I create a new release
. I tried to see if I can find notes but I couldn't. Is that what you do also? If so, should this step be moved one above.
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.
Good point, I think you are right about the ordering. That is how I do it for sds_data_manager
, which usually requires some release-specific commits to update version numbers.
I updated the docs to reflect the correct order, and also added some more notes.
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 updating this!
This PR updates the Release Workflow docs to add some notes on the expected cadences of the releases, as well as make some minor updates based on how we have been making releases.