TCW 22 update: moved creation of release branch to after step 14. #18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think this is exactly right. But we'll never know for sure till the next release.:-) Thanks @trishaoconnor. |
martindholmes
approved these changes
May 19, 2025
ebeshero
approved these changes
May 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Steps 5 and 6, which instruct release techs to create the
releasedbranch comes too early in the procedure and delayed the overall process on release day. I've added these steps to after step 14 "Make your release the default downloadable version from Sourceforge" and before step 15 "Update tags on GitHub".Had to reword Step 8 though as it mentioned the "released" branch specifically in the git push command, so I updated it as follows: