-
Notifications
You must be signed in to change notification settings - Fork 21.7k
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.2.1] Release Tracker #119295
Comments
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@malfet: merged |
Link to master PR (if applicable): Link to 2.2 release branch PR: Criteria Category: @malfet: needs some discussion, as technically its not a 2.1->2.2 regression, but rather 2.0->2.2 one @malfet merged |
Link to landed trunk PR (if applicable):
Link to release branch PR:
Criteria Category:
@atalman merged |
Dtensor / device mesh is currently broken on 2.2 and has serious silent correctness errors. These were fixed by teh following PRs:
Related to distributed checkpointing: Related dtensor sync_module_states bug: These are all low-risk PRs and fix various issues, eg silent correctness. CC: @chauhang @mvpatel2000 could you please post cherry-picks to release/2.2 branch for these PRs ? Edit: skylion included PR below |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: @atalman merged |
Link to landed trunk 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 trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman merged |
Fixes sharded checkpoint bug which causes OOM on large GPU counts: Edit: skylion included PR below Edit: See #119295 (comment). #117799 was replaced by #118197 in main @atalman wrote: @mvpatel2000 I don't see this PR being included as a cherry-pick @atalman wrote: As discussion here: #119295 (comment) this PR is not required |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@Skylion007 @atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman wrote: @Skylion007 this cherry-pick is missing unit tests, we require unit tests for all cherry-picks. Also this one mentions #117799 do we need this cherry pick as well here ? @fegin wrote: @atalman @atalman merged |
Link to landed trunk PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable):
Link to release branch PR: Criteria Category:
@huydhn merged |
Link to landed trunk PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR:
Criteria Category:
@huydhn merged |
Link to landed trunk PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@huydhn merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@huydhn merged |
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: -- cc., @atalman @atalman wrote: @mvpatel2000 reverting this PR: #119995 . Will not be merging this cherry-pick |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
Please Note We don't accept cherry-picks anymore. We are currently in Phase 2 (after 2/14). |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@huydhn merged |
Closing this. Completed |
🐛 Describe the bug
This issue is for tracking cherry-picks to the release branch. Following is release branch for the 2.2.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 2/14):
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 @atalman, @huydhn, @osalpekar, @malfet). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
Phase 2 (after 2/14):
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.2
Versions
2.2.1
The text was updated successfully, but these errors were encountered: