Skip to content

Document preferred PR process for backports #2222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 21, 2025
+11 −0
Merged

Document preferred PR process for backports #2222

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a1e8b0f
Initial plan
Copilot Oct 20, 2025
844705e
Document preferred PR process for backports
Copilot Oct 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions Guide/src/dev_guide/contrib/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,17 @@ To seek approval to include a change in a release branch, follow these steps:
Please reach out to the maintainers before staging that PR if you have any
doubts.

#### Backport PR Best Practices

When creating a backport PR to a `release/YYMM` branch:

* **Clean cherry-picks are strongly preferred.** A clean cherry-pick minimizes
reviewer effort and reduces the risk of introducing regressions.
* **If the backport is not a clean cherry-pick** (e.g., requires conflict
resolution or additional modifications), clearly indicate this in the PR
description. This signals to the reviewer that extra care is needed during
the review process.

## Existing Release Branches

| Release | Phase | Notes |
Expand Down