You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes to new features introduced in the most recent minor release (e.g. 0.12 for 0.13 release)
Test/CI fixes
Documentation improvements
Compilation fixes or ifdefs required for different versions of the compilers or third-party libraries
Release branch specific changes (e.g. change version identifiers)
Any other change requires special dispensation from the release managers (currently @atalman, @seemethere ). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
Phase 2 (after 06/13/22):
Note that changes here require us to rebuild a Release Candidate and restart extended testing (likely delaying the release). Therefore, the only accepted changes are Release-blocking critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
Changes will likely require a discussion with the larger release team over VC or Slack.
Cherry-Pick Process
Ensure your PR has landed in master. This does not apply for release-branch specific changes (see Phase 1 criteria).
Create (but do not land) a PR against the release branch.
# Find the hash of the commit you want to cherry pick# (for example, abcdef12345)
git log
git fetch origin release/0.13
git checkout release/0.13
git cherry-pick abcdef12345
# Submit a PR based against 'release/0.13' either:# via the GitHub UI
git push my-fork
# via the GitHub CLI
gh pr create --base release/0.13
Make a request below with the following format:
Link to landed master PR (if applicable):
*
Link to release branch PR:
*
Criteria Category:
*
Someone from the release team will reply with approved / denied or ask for more information.
If approved, someone from the release team will merge your PR once the tests pass. Do not land the release branch PR yourself.
NOTE: Our normal tools (ghstack / ghimport, etc.) do not work on the release branch.
Please note HUD Link with branch CI status and link to the HUD to be provided here. HUD
Versions
0.13
The text was updated successfully, but these errors were encountered:
We cut a release branch for the 0.13 release.
Our plan from this point from this point is roughly:
This issue is for tracking cherry-picks to the release branch.
Cherry-Pick Criteria
Phase 1 (until 06/13/22):
Only low-risk changes may be cherry-picked from master:
Any other change requires special dispensation from the release managers (currently @atalman, @seemethere ). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
Phase 2 (after 06/13/22):
Note that changes here require us to rebuild a Release Candidate and restart extended testing (likely delaying the release). Therefore, the only accepted changes are Release-blocking critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
Changes will likely require a discussion with the larger release team over VC or Slack.
Cherry-Pick Process
Ensure your PR has landed in master. This does not apply for release-branch specific changes (see Phase 1 criteria).
Create (but do not land) a PR against the release branch.
Make a request below with the following format:
NOTE: Our normal tools (ghstack / ghimport, etc.) do not work on the release branch.
Please note HUD Link with branch CI status and link to the HUD to be provided here.
HUD
Versions
0.13
The text was updated successfully, but these errors were encountered: