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.1.1] Release Tracker #110961
Comments
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman merged |
got request from Mosaic to include these two fixes: 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 |
A minor NCCL version dropped that has a bug fix. Should we open a PR onto 2.1 tree to update it?
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:
@malfet merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@huydhn: |
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 |
Comments from user:
Link to landed master PR (if applicable):
Link to release branch PR:
Criteria Category:
@malfet: Looks fine, need to do some manual testing before merging @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 |
#111703 is a good backport candidate and fixes a repeatable and problematic mem leak according to the issue.
Closed my PR for @tringwald's issue below |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@malfet: merged, as change is very localized, but we need to have better guidance to distinguish between large and small memory leaks going forward |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@atalman moving it to 2.1.2 release |
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 the landed main commit: Lint to release branch PR: Criteria Category:
@atalman merged |
Link to landed master 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:
@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:
@malfet merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@bdhirsh could you please take a look at the cherry pick, there are multiple failures |
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:
Alban: This is actually a regression where it used to be possible to have indices on the mps device and it is not possible anymore. @huydhn merged |
Link to landed master PR (if applicable): Link to release branch PR: Criteria Category:
@huydhn merged |
Link to the landed PR: Link to the release branch PR: Criteria Category:
@malfet merged |
Link to the landed PR: Link to the release branch PR: Criteria Category:
@huydhn merged. Learn from @malfet: We don't have separation of the Docker image from main and release branch on builder atm. So I shouldn't have merged the change into the release branch because it would override the correct image from main. @malfet fixes this by rebuilding the image in pytorch/builder@617327e |
Got request from MosaicML to include this 1 fix. Comments from users:
Link to the landed PR:
Link to the release branch PR:
Criteria Category:
@malfet: I think category is wrong, this feels like a feature work (adding new argument to the existing method), isn't it? |
Link to the landed PR:
Link to the release branch PR: Criteria Category:
@huydhn merged |
Link to the landed PR: Link to the release branch PR: Criteria Category:
@malfet: We never had release tags in builder repo, had we? And may be it's fine to start doing it going forward, but not sure why it needs to be cherry-picked into release branch for 2.1.1 release) |
Link to the landed trunk PR: Link to the release branch PR: Criteria Category:
@malfet: merged |
Link to the landed trunk PR: Link to the release branch PR: Criteria Category:
@malfet merged |
Link to the landed trunk PR: Link to the release branch PR: Criteria Category:
@huydhn merged |
Link to landed master 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:
@huydhn merged confirm that the issue on #112577 (reproducible on 2.1.0) is fixed |
Link to landed trunk PR:
Link to release branch PR: Criteria Category:
@malfet merged |
Closing and unpinning, as final RC is out |
🐛 Describe the bug
This issue is for tracking cherry-picks to the release branch. Following is release branch for the 2.1.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 11/3):
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 11/3):
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.1
Versions
2.1.1
The text was updated successfully, but these errors were encountered: