[v.2.3.0] Release Tracker

[atalman]

🐛 Describe the bug

We cut a release branch for the 2.3.0 release.

Our plan from this point from this point is roughly:

• Phase 1 (until 4/1/24): work on finalizing the release branch
• Phase 2 (after 4/1/24): perform extended integration/stability/performance testing based on Release Candidate builds.

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:

1. Fixes to regressions against the most recent minor release (e.g. 2.2.x for this release; see module: regression issue list)
2. Critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
3. Critical fixes to new features introduced in the most recent minor release (e.g. 2.2.x for this release)
4. Test/CI fixes
5. Documentation improvements
6. Compilation fixes or ifdefs required for different versions of the compilers or third-party libraries
7. Release branch specific changes (e.g. change version identifiers)

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

1. Ensure your PR has landed in master. This does not apply for release-branch specific changes (see Phase 1 criteria).

2. Create (but do not land) a PR against the release branch.

   # Find the hash of the commit you want to cherry pick
   # (for example, abcdef12345)
   git log
   
   git fetch origin release/2.3
   git checkout release/2.3
   git cherry-pick -x abcdef12345
   
   # Submit a PR based against 'release/2.3' either:
   # via the GitHub UI
   git push my-fork
   
   # via the GitHub CLI
   gh pr create --base release/2.3

3. Make a request below with the following format:

Link to landed trunk PR (if applicable):
* 

Link to release branch PR:
* 

Criteria Category:
* 

1. Someone from the release team will reply with approved / denied or ask for more information.
2. If approved, someone from the release team will merge your PR once the tests pass. Do not land the release branch PR yourself.

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

[snadampal]

Link to main PR (if applicable):

• aarch64: cherrypick onednn pr#1768 to improve torch.compile perf builder#1716
• aarch64: apply the cherrypicked onednn PR-1768 builder#1717

Link to 2.3 release branch PR:

• aarch64: cherrypick onednn pr#1768 to improve torch.compile performance builder#1728
• aarch64: apply the cherrypicked onednn PR-1768 builder#1730

Criteria Category:
The PRs improve the torch.compile performance on aarch64 linux systems substantially.

---

@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

[atalman]

Link to landed trunk PR (if applicable):

• NA

Link to release branch PR:

• [RELEASE ONLY CHANGES] Apply release only changes Release 2.3 #121726
• [Release Only] Build triton using pinned version rather branch #121765
• [RELEASE ONLY CHANGES] Apply release only changes Release 2.3 #121813
• [RELEASE ONLY CHANGES] Increase timeout for linux binary jobs, fix workflow lint #121851
• [Release only] Release 2.3 start using triton package from pypi #123580

Criteria Category:

• Release only required changes

---

@atalman merged

[atalman]

Link to landed trunk PR (if applicable):

• CI: Specify libc and libstdcxx versions in conda environments #121556

Link to release branch PR:

• CI: Specify libc and libstdcxx versions in conda environments #121929

Criteria Category:

• Critical fix: Without this we get mismatches between the GLIBC and GLIBCXX ABI used by conda packages vs pytorch.

---

@atalman merged

[NmomoN]

Link to landed trunk PR (if applicable):

• Add 'profiler/python' to the package.' #121892

Link to release branch PR:

• Add 'profiler/python' to the package.' #122065

Criteria Category:

• Fixes to new features being introduced in 2.3.0 release.

@zdevito

---

@atalman Please provide some details on what issue you are trying to address and what is the associated feature

[shunting314]

Link to landed trunk PR (if applicable):
N/A

Link to release branch PR:

• necessary change to make torch2.3 work with triton2.2 #122139

Criteria Category:

• need this to make pytorch release work with the corresponding triton release

---

@atalman merged

[atalman]

Link to landed trunk PR (if applicable):

• N/A

Link to release branch PR:

• Revert "[Release Only] Build triton using pinned version rather branch" builder#1751
• Triton wheel build using 2.3.x branch #122403

Criteria Category:

• need this to make pytorch release work with the corresponding triton release

---

@atalman merged

[wz337]

Link to landed trunk PR (if applicable):

• Back out "[DeviceMesh] Add support for nD slicing (#119752)" #121763

Link to release branch PR:

• [CherryPick] Back out "[DeviceMesh] Add support for nD slicing (#119752)" (#121763) #122495

Criteria Category:

• Cherry-picking a revert. Bug fix.

---

@atalman merged

[SS-JIA]

Link to landed trunk PR (if applicable):

• [ET-VK] Enable Dynamic shape support via tensor virtual and physical resizing #121598

Link to release branch PR:

• [ET-VK] Enable Dynamic shape support via tensor virtual and physical resizing #122634

Criteria Category:

• This does not quite fit into any of the cherry pick criterias, however, it implements features required for ExecuTorch alpha release. It is also low risk as it only impacts the PyTorch-Vulkan backend. cc: @huydhn

[guangy10]

Link to landed trunk PR (if applicable):

• remove torchao dependency #122524

Link to release branch PR:

• remove torchao dependency #122635

Criteria Category:

A critical fix for ExecuTorch. Need to be merged so that ExecuTorch v0.2 can be compatible with PyTorch v2.3. cc: @huydhn

---

@huydh merged

[JacobSzwejbka]

Link to landed trunk PR (if applicable):

#122246

Link to release branch PR:

#122655

Criteria Category:

A critical fix for ExecuTorch: A new pass that ExecuTorch uses to allow mutable state with custom ops. Need to be merged so that ExecuTorch v0.2 can be compatible with PyTorch v2.3 cc: @huydhn

---

@huydhn merged

[JacobSzwejbka]

Link to landed trunk PR (if applicable):

#121990

Link to release branch PR:

#122654

Criteria Category:

A critical fix for ExecuTorch: Patching auto functionalized which ExecuTorch relies on for exporting llama. Need to be merged so that ExecuTorch v0.2 can be compatible with PyTorch v2.3 cc: @huydhn

---

@huydhn merged

[JacobSzwejbka]

Link to landed trunk PR (if applicable):

#122683

Link to release branch PR:

#122721

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