-
Notifications
You must be signed in to change notification settings - Fork 24.3k
[v.2.6.0] Release Tracker #142814
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
Comments
Closing this temporarily until new branch cut. |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: @kit1980: merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: @kit1980 merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: @kit1980 merged |
Link to landed trunk PR (if applicable):
Link to release branch PR: Criteria Category:
@kit1980 merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: Critical @kit1980 merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: Critical - fixes libtorch builds @kit1980 merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@kit1980: @XuehaiPan this changes the public API and BC-breaking, no? |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: Critical @malfet merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: Critical @atalman merged |
Link to landed trunk PR (if applicable):
Link to release branch PR:
Criteria Category: Critical @atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: Critical @atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: Critical @atalman merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@kit1980 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:
@kit1980 merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: @malfet: merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: @malfet: merged |
Link to landed trunk PRs:
Link to cherry-pick PR: Criteria category: RelEng? @kit1980 merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: @kit1980 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:
Merged by @malfet |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
|
Please note: We are no longer accepting cherry-pick requests after this point. |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: @kit1980 merged |
Uh oh!
There was an error while loading. Please reload this page.
We cut a release branch for the 2.6.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 1/13/25):
Only low-risk changes may be cherry-picked from main:
Any other change requires special dispensation from the release managers (currently @atalman, @malfet, @kit1980). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
Phase 2 (after 1/13/25):
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.
You can also use the
@pytorchbot cherry-pick
command to cherry-pick your PR. To do this, just add a comment in your merged PR. For example:(
-c docs
- is the category of your changes - adjust accordingly):For more information, see pytorchbot cherry-pick docs.
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
2.6.0
cc @seemethere @malfet @pytorch/pytorch-dev-infra
The text was updated successfully, but these errors were encountered: