docs: clarify rancher/rancher branch targeting strategy in release guide#2459
Merged
Conversation
anmazzotti
reviewed
May 29, 2026
32d882c to
574db65
Compare
yiannistri
previously approved these changes
Jun 1, 2026
Contributor
yiannistri
left a comment
There was a problem hiding this comment.
Looks good to me, just a minor (non-blocking) suggestion that reads better, in my opinion.
92e0bc3 to
cd76b11
Compare
Signed-off-by: Furkat Gofurov <furkat.gofurov@suse.com>
cd76b11 to
e22a386
Compare
anmazzotti
approved these changes
Jun 1, 2026
Contributor
anmazzotti
left a comment
There was a problem hiding this comment.
Thank you for addressing this.
yiannistri
approved these changes
Jun 1, 2026
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
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 this PR does / why we need it:
Updates the release guide to clarify when to target
rancher/ranchermainvs a releasebranch when using automation to update Turtles version in
rancher/rancher. When cutting RCs for a new Turtles minorand the corresponding release branch doesn't exist yet,
mainshould be targeted untilthe Rancher team creates it.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #2249
Special notes for your reviewer:
Checklist: