11/07 UPDATE: Please note that the M2 to M4 dates below have changed, and release day will now be Jan 21st 2026.
Hi Team,
We are kicking off the PyTorch 2.10 release cycle and continue to be excited for all the great features from our PyTorch community!
WHEN ARE THE CRITICAL DATES FOR THE PYTORCH 2.10 RELEASE?
- M1: Release Announcement (11/6/25)
- M2: All PRs landed in PyTorch repo / Feature Submission Closed (12/3/25)
- M3.1: Release branch cut (12/5/25)
- M3.2: Release first RC1 Binary for PyTorch Core (12/8/25)
- M3.3: Domain libraries cut RC Branch (12/9/25)
- M4: Release branch finalized, Announce final launch date, Feature classifications published (week of 1/9/26) - Final RC is produced.
- M4.1: Tutorial drafts submission deadline (1/12/26)
- M5: External-Facing Content Finalized (1/16/26)
- M6: Release Day (1/21/26)
FEATURE TRACKING & CLASSIFICATION
As mentioned in this RFC, beginning in release 2.8, feature submissions for the release are tracked as GitHub Issues. You can either create a new issue or tag an existing RFC as to include it in the upcoming release. If you would like a feature to be included in the release blogpost, please mention it in the “New Feature for Release” issue that you create, and include the release version this is targeted to. Please also read the blog post for the 2.9 release to get familiar with the marketing format.
Also since 2.8 are updates to classification i.e. features are now either Stable (API-Stable) or Unstable (API-Unstable). The previous classifications of Prototype, Beta and Stable, will no longer be used. The requirements for a feature to be considered stable remain the same, and in the RFC we propose a suggested path to stable.
If you still have questions after reading the material –or at any time during the process–please don’t hesitate to contact one of us: Gregory Chanan, Alban Desmaison, Andrey Talman, Nikita Shulga, Hamid Shojanazeri, Eli Uriegas and myself.
Cheers,
Team PyTorch
#oneteam