-
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
[v2.0.1] Release Tracker #97272
Comments
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 |
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 pytorch/builder repo main:
Link to pytorch/builder repo release/2.0 @malfet: Builder cherry-picks are not needed as packages are build from |
torchtext wheel are missing for aarch64 for PyTorch 2.0.0 release Link to release branch PR: Criteria Category:
This fixes the issue: |
Link to landed master PR (not yet merged, but approved as part of the below release branch PR) Link to release branch PR: Criteria Category:
This fixes the issue @atalman this was not merged for release |
Link to landed master PR(under review) Link to release branch PR: Criteria Category:
This fixes the issue: |
Link to landed master PR (if applicable):
Link to release branch PR:
Criteria Category:
|
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to master PR:
Criteria Category: @atalman merged |
Link to landed master PR: Link to release branch PR: Criteria Category: Low risk critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks. @malfet: This PR does not meet the specified criteria, as it does not fix any of the abovementioned issues. |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR:
Criteria Category: Fixes to regressions against the most recent release @atalman merged |
Link to landed master PR: Link to release branch PR: Criteria Category: @atalman merged |
Link to landed master PR: Link to release branch PR: Criteria Category:
@atalman merged |
Linkt to landed master PR: Link to release branch PR: Criteria Category:
@malfet: Yes, it enables non-standard behavior, but it also fixes |
Link to landed master PR: Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed master PR: Link to release branch PR: Criteria Category: Critical fixes for torch dynamo related tests in FX2TRT (Test failures) @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 |
Hi all, will this get merged? This is a critical fix. The two test failures in the run are related to a missing "no_torchaudio" package, so unrelated to the change. @mlazos this is merged |
Link to landed master PR: Link to release branch PR: Criteria Category: Regression from the most recent release @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: Low risk critical fixes for AOTAutograd @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:
|
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category: |
closing this as finished |
This issue is for tracking cherry-picks to the release branch. Following is release branch for the 2.0.1 release.
Our plan from this point from this point is roughly:
Only issues that have ‘cherry-picks’ in this tracker will be considered for the release.
Cherry-Pick Criteria
Phase 1 (until 04/21):
The Releng team relies on the cherry pick process to manage risk to release quality, i.e. by porting a small set of commit from trunk that are "must-have" into the release branch, we limit the change to the minimal to address pressing issues. Thus, not everything a developer land into the trunk will make it into the release. So, please consider the criteria below and follow the cherry picking process. Only low-risk changes may be cherry-picked from master:
Any other change requires special dispensation from the release managers (currently @malfet, @atalman, @weiwangmeta , @izaitsevfb @osalpekar ). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
Phase 2 (after 04/21):
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.
See HUD 2.0
Versions
2.0.1
The text was updated successfully, but these errors were encountered: