(docs) Document the special case of shipping point releases when new release branch already exists #46083
+2
−0
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
fullofcaffeine
requested review from
ajitbohra,
ryanwelcher,
juanmaguitar and
fabiankaegy
as code owners
|
|
fullofcaffeine
changed the title
…n a new release branch already exists If a new release branch exists, commits should be cherry-picked there, too, in order for the same changes to be available in the upcoming releases.
fullofcaffeine
force-pushed
the
document/point-release-update-with-new-rc-out
branch
from
8f27067 to
cd773d8
Compare
fabiankaegy
approved these changes
Nov 26, 2022
fabiankaegy
deleted the
document/point-release-update-with-new-rc-out
branch
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.
What?
Update release docs.
Why?
To document an edgy case scenario when releasing point releases for previous stable releases when a new stable release is still not out, but an RC is. If a new release branch exists, commits should be cherry-picked there, too, for the same changes to be available in the upcoming releases.
How?
By documenting it in the
release.mdfile.Testing Instructions
Screenshots or screencast