-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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.
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
[v.1.12.0] Release Tracker #78005
Comments
Link to landed master PR (if applicable):
Link to release branch PR: Criteria Category:
@seemethere: Merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category: @atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category: @atalman Merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman Merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
EDIT: Nevermind, please ignore |
Link to landed master PR:
Link to release branch PR: Criteria Category: @malfet: edited and merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@malfet merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
The regression described in #78549 IS present in the 1.12 release branch (https://github.com/pytorch/pytorch/commits/release/1.12/test/distributed/test_c10d_common.py). @ngimel advises we should fix it or at least allow a workaround in 1.12, and @azrael417 and I won't argue with that. cc @mrshenli See @mrshenli fix below: Link to landed master PR (if applicable): Link to release branch PR: Criteria Category: Critical fixes for: backwards compatibility. See #78549 @atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category: Documentation improvements cc: @anjali411 @atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category: @atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
cc: @anjali411 @atalman megred |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
CC @ptrblck @ngimel @pritamdamania87 @atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR:
Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@malfet: merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged it (athough I don't know if we need to track builder changes here) |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@malfet: merged |
Link to landed master PR: Link to release branch PR: Criteria Category:
@malfet: merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@malfet merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@malfet: merged after additional discussion assessing risks(low, as issue requires opt in to be accessed) |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@malfet merged |
Please note we are currently in Phase 2 (after 06/13): perform extended integration/stability/performance testing based on Release Candidate builds. Therefore, the only accepted changes are Release-blocking critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category: documentation improvements @malfet: merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
-- |
Link to landed master PR (if applicable):
@malfet merged |
Link to landed master PR (if applicable):
cc: @atalman |
Link to landed master PR (if applicable):
Link to release branch PR: Criteria Category: @atalman merged |
Link to landed master PR: Link to release branch PR: Criteria Category:
@malfet merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Release is completed, closing this |
We cut a release branch for the 1.12.0 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
1.12.0
The text was updated successfully, but these errors were encountered: