release process: Use release candidates #34051
Draft
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
A downside of repurposing the applier_version as the actual state version is that we can no longer determine what the actual version of the code was that made the change withought a serious investigation. Adding it to this string means it will be included in various places in state.
def-
force-pushed
the
pr-release-candidate2
branch
from
812f587 to
62f17dd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Based on #33983, so only look at the last commit.
The goal is to always release the .0 patch version, and have release candidates before that. For example:
v26.0.0-dev.0 -> v26.0.0-rc.1 -> v26.0.0-rc.2 -> v26.0.0 released.
Checklist
$T ⇔ Proto$Tmapping (possibly in a backwards-incompatible way), then it is tagged with aT-protolabel.