docs: Update RELEASE_CHECKLIST.md to reflect state of operations #4841
Conversation
This file contains 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
The overall mechanisms haven't changed, but these are steps which have changed, process-wise in terms of how we do releases. Aside from setting the variables at each stage, it's basically copy-paste all the way down (but a lot of copy-paste). Concretely, the steps are no longer all grouped into one and no longer you to remember where to pick up, or require manual changes to do things like cut pre-releases. Instead, each have distinct sections which can either be done at separate times (and by separate people!) or just all at once.
|
@abernix, please consider creating a changeset entry in |
BrynCooke
approved these changes
Mar 25, 2024
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.
Wrote up these changes on Friday night and just wanted to push them up. The overall mechanisms haven't changed (e.g., a tag creates a release), but these are steps which have changed, process-wise in terms of how we do releases. Today, we've adopted the pattern of:
main, but stays as draft until it's ready to go final (step 4)devmoves forward.main.Concretely, the release checklist steps are no longer all grouped into one "big step" and no longer require you to remember where to pick up. Instead, each have distinct sections which can either be done at separate times (and by separate people!) or just all at once.
There are a lot of steps, but aside from setting the required variables at each stage, it's copy-paste all the way down (but a lot of copy-paste, admitedly).
There are some clear follow-up items still - all of them include automation - but I don't think we should wait for them.