-
Notifications
You must be signed in to change notification settings - Fork 22.9k
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
[v.2.3.0] Release Tracker #121760
Comments
Link to main PR (if applicable):
Link to 2.3 release branch PR:
Criteria Category: @malfet: Please do not cherry-pick those changes, we should revert it on builder on trunk and coordinate with oneDNN team to get those changes into release branch and/or wait until the next release |
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 Please provide some details on what issue you are trying to address and what is the associated feature |
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:
|
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category: A critical fix for ExecuTorch: Makes dead code elimination pass not trash the output of capture_pre_autograd_graph if it contains kv cache mutation. Need to be merged so that ExecuTorch v0.2 can be compatible with PyTorch v2.3 cc: @huydhn @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: A critical fix for ExecuTorch. W/o this PR, PyTorch v2.3 will not be compatible with ExecuTorch, even the simples add module will fail. What this PR does is adding new ops to native_functions.yaml and they are covered by tests. It’s relatively low risk as these ops are not used by many component except for ExecuTorch. @atalman wrote: @guangy10 This is all looks like feature work. We normally accept only critical fixes at this point:
cc: @malfet @albanD@atalman I don't think it's a feature work. I would category this to the "critical fix: compatibility" because it does break the compatibility with ExecuTorch w/o this fix. @huydhn merged |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@atalman wrote: @SS-JIA For cherry-pick to be considered for a release it needs to have unit test with the cherry-pick @SS-JIA wrote: @atalman the `linux-vulkan-focal-py3.11-clang10 / test job tests PyTorch Vulkan and is passing on the PR. Is that sufficient? |
Link to landed trunk PR: Link to release branch PR: Criteria Category: @atalman wrote: Please provide some unit tests for 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 |
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:
edit: @mikaylagawarecki added cherry pick of #122800 per discussion on #123106 since we are cherry picking #122755 as a critical fix for wrapper tensor subclasses @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: @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:
|
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
|
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: Please note, at this point we already generated final RC. Is there an issue associated with this PR ? |
Link to landed trunk PR (if applicable):
Link to release branch PR: Criteria Category:
@atalman wrote: Hi @WeizhuoZhang-intel we already built final rc. this only affects torchbench suite. Is running this on nightly is possibility ? This cherry-pick does not fit the criteria for Critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks |
Link to landed trunk PR (if applicable): Link to release branch PR: Criteria Category:
@huydhn merged |
🐛 Describe the bug
We cut a release branch for the 2.3.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 4/1/24):
Only low-risk changes may be cherry-picked from main:
Any other change requires special dispensation from the release managers (currently @atalman, @osalpekar, @huydhn, @malfet). If this applies to your change please write "Special Dispensation" in the "Criteria Category:" template below and explain.
Phase 2 (after 4/1/24):
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.
Please note HUD Link with branch CI status and link to the HUD to be provided here.
HUD
Versions
2.3.0
The text was updated successfully, but these errors were encountered: