We are excited to announce the start of the PyTorch 2.15 release cycle and look forward to all the great contributions from our community.
For 2.15 we are keeping the branch-cut → release window at ~3 weeks: the release branch is cut on Oct 5, 2026 and GA is Oct 28, 2026. The full cadence table is maintained in RELEASE.md.
Key Dates
| Milestone | Description | Date |
|---|---|---|
| M1 | Release Announcement | 9/9/26 |
| M2 | All PRs landed / Feature Submission Closed | 2/10/26 |
| M3 | Release branch cut, create RC1 for PyTorch and Torchvision | week of 5/10/26 |
| M4 | Release branch finalized, announce final launch date, feature classifications published; final RC produced | week of 19/10/26 |
| M4.1 | Tutorial drafts submission deadline | 23/10/26 |
| M5 | External-Facing Content Finalized | 27/10/26 |
| M6 | Release Day | 28/10/26 |
Feature Submission & Tracking
As with recent releases, feature submissions are tracked as GitHub Issues. To include your work in the 2.15 release, create a new “New Feature for Release” issue (or tag an existing RFC) and set the targeted version to 2.15. Features mentioned this way are the ones considered for the release blogpost.
Features are classified as either Stable (API-Stable) or Unstable (API-Unstable) — the earlier Prototype/Beta/Stable labels are no longer used. The requirements for a feature to be considered stable remain the same.
Questions / Contacts
For any questions about the release, please reach out to the release managers:
Andrey Talman, Huy Do, Alban Desmaison
Cheers!
Team PyTorch
#oneteam