25.12 updated Maintainer Docs - Hotfix Process #716
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
✅ Deploy Preview for docs-rapids-ai ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
rockhowse
commented
Dec 10, 2025
Comment on lines
+89
to
+91
| 3. Review documentation to ensure version numbers (updating to `YY.MA.Y`) and instructions are correct | ||
| 4. Merge the developer's PR targeting `release/YY.MA` after approval | ||
| 5. Create a new PR from `release/YY.MA` targeting `main` |
Contributor
Author
There was a problem hiding this comment.
This is the main section I have questions about... after we cut the official release, are the hotfix PRs that are merged into the release/YY.MAI see a couple scenarios here but need some clarification
-
- hotfix gets merged back into
mainvia theforward merger
- hotfix gets merged back into
-
- cherry pick from
release/YY.MAback intomain
- cherry pick from
-
- separate forward-port (?) PR into
main
- separate forward-port (?) PR into
@AyodeAwe you are probably the best person to help answer this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 updates the Release Planning section
to bring it up to the current planning/release process post RSN-47
This focuses on using
CALVER (YY.MM.PP)instead and + an un-changingmaindevelopment branchxref: rapidsai/build-planning#224