[docs] feat: add cherrypick policy for release branches - #3739
Merged
Conversation
Document what may land on Megatron-LM and Megatron-Bridge release branches between branch cut and release. Defines two phases (code-freeze with fixes-only on in-scope code, absolute freeze with QA/automation-recommended only) and clarifies that only the automation team can waive cherrypicks. Cross-link from docs/releases/README.md and the Code-Freeze section of release-process.md. Signed-off-by: oliver könig <okoenig@nvidia.com>
Contributor
ReviewLGTM — clean docs-only PR. The new cherrypick policy is well-structured, internally consistent, and the cross-links from
Suggested test casesNo perf tests impacted. |
Frame the cherrypick waiver as an abstract "waiving authority" role held today by the automation team, so the policy survives an ownership handoff without rewording. Updates the Two Phases, Phase 2, and Quick Reference sections to use the role-then-holder phrasing. Signed-off-by: oliver könig <okoenig@nvidia.com>
Signed-off-by: oliver könig <okoenig@nvidia.com>
Signed-off-by: oliver könig <okoenig@nvidia.com>
Signed-off-by: oliver könig <okoenig@nvidia.com>
Signed-off-by: oliver könig <okoenig@nvidia.com>
…IBUTING url Sphinx --fail-on-warning treats two findings as errors: - cherrypick-policy.md missing from any toctree. - ../../CONTRIBUTING.md resolved as a myst xref to a non-existent doc. Add the page to the Releases toctree in docs/index.md and switch the CONTRIBUTING link to the GitHub URL pattern other docs already use. Signed-off-by: oliver könig <okoenig@nvidia.com>
ko3n1g
enabled auto-merge (squash)
May 9, 2026 09:46
chtruong814
approved these changes
May 9, 2026
gautham-kollu
pushed a commit
that referenced
this pull request
May 12, 2026
Signed-off-by: oliver könig <okoenig@nvidia.com>
vasunvidia
pushed a commit
to vasunvidia/Megatron-Bridge
that referenced
this pull request
Jun 10, 2026
…3739) Signed-off-by: oliver könig <okoenig@nvidia.com> Signed-off-by: Vasudevan Rengasamy <vrengasamy@nvidia.com>
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.
Claude summary
What
Adds
docs/releases/cherrypick-policy.md— a single source of truth for what may land on the Megatron-LM and Megatron-Bridge release branches between branch cut and release. Cross-links the new doc fromdocs/releases/README.mdand theCode-Freezesection ofdocs/releases/release-process.md.Why
Today, decisions about what can be cherrypicked onto a release branch during code-freeze are made ad-hoc. The new doc:
Quick reference
Files
docs/releases/cherrypick-policy.md— new doc.docs/releases/README.md— index row + Quick Navigation entry.docs/releases/release-process.md— one-line cross-link in the Code-Freeze section.