-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
[v1.7.0] Release Tracker #45592
Comments
Link to landed master PR (if applicable): n/a, release-specific change @seemethere: accepted |
Link to landed master PR (if applicable): #45546 -- |
Link to landed master PR: #45461 -- |
Link to landed master PR: #45586 @malfet: Binary size diff is less than 4Kb, merged. |
Link to landed master PR: #44920 -- |
Link to landed master PR (if applicable): #45587 and #45588 @malfet: resolved merged conflict, waiting for CI |
Link to landed master PR (if applicable): #45729 A user just reported seeing this #45769. It would be nice that we have this minor information printing bug be fixed in the release. -- |
Link to landed master PR: N/A Merged |
Link to landed master PR: #45651, #45677, #45798
-- |
Link to landed master PR (if applicable): #45889 This may improve the performance on Ampere GeForce 3080 and 3090, if pytorch is compiled with cuda 11.1. -- |
Once it's landed, probably #46028 (high priority bug fix, should apply to 1.7 as well) |
Link to landed master PR: N/A Merged |
Link to landed master PR: N/A merged |
Link to release branch PR: #46845 |
Hey everyone, 1.7.0 has been released so I'm going to close this. Thank you everyone for the work towards getting v1.7.0 out of the door! |
@seemethere If this PR was not merged, is there still a way to add it? |
We cut a release branch for the 1.7.0 release.
Our plan from this point is roughly:
This issue is for tracking cherry-picks to the release branch.
Cherry-Pick Criteria
Phase 1 (until 10/13):
Only low-risk changes may be cherry-picked from master:
Any other change requires special dispensation from the release managers (currently @malfet, @seemethere, @gchanan). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
Phase 2 (after 10/13):
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
This 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. Note that you should use the normal github workflow for this; ghstack does not support release branches.
Make a request below with the following template:
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. NOTE: do not land the release branch PR yourself. Our normal landing tools (ghimport, phabricator, etc.) do not work on the release branch.
The text was updated successfully, but these errors were encountered: