Update the release process as of 1.52.0 #534
Merged
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
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.
This PR includes miscellaneous updates to the release process to reflect what I'm doing for the 1.52.0 release. The changes are:
T-in the release day schedule to better reflect how longpromote-releasetakes nowadays.bootstrapcfgs. The guidelines would've been really useful when I started doing releases, and I hope they'll be useful when we onboard new people to doing releases.Notably, commits for (1) and (2) were already included and reviewed in #517. Once this is merged I'll rebase #517 to only include things were we don't have consensus yet.
r? @Mark-Simulacrum