We are excited to announce the start of the **PyTorch 2.14** release cycle and look forward to all the great contributions from our community.
For 2.14 we are shortening the **branch-cut → release** window to **~3 weeks** (branch cut moves one week later to Aug 10, 2026, while the GA date is held at Sept 2, 2026). See the schedule RFC: [RFC] Release 2.14 schedule — shorten branch-cut to release to 3 weeks (move branch cut Aug 3 -> Aug 10) · Issue #190359 · pytorch/pytorch · GitHub
## Key Dates
| Milestone | Description | Date |
|---|---|---|
| M1 | Release Announcement | 21/7/26 |
| M2 | All PRs landed / Feature Submission Closed | 7/8/26 |
| M3 | Release branch cut, create RC1 for PyTorch and Torchvision | week of 10/8/26 |
| M4 | Release branch finalized, announce final launch date, feature classifications published; final RC produced | week of 24/8/26 |
| M4.1 | Tutorial drafts submission deadline | 28/8/26 |
| M5 | External-Facing Content Finalized | 1/9/26 |
| M6 | Release Day | 2/9/26 |
## Feature Submission & Tracking
As with recent releases, feature submissions are tracked as GitHub Issues. To include your work in the 2.14 release, create a new “New Feature for Release” issue (or tag an existing RFC) and set the targeted version to 2.14. 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:
**Gregory Chanan, Alban Desmaison, Andrey Talman **
Cheers!
Team PyTorch
#oneteam