# PyTorch Release 2.9.0 | Key Dates

**URL:** <https://dev-discuss.pytorch.org/t/pytorch-release-2-9-0-key-dates/3178>\
**Category:** Release Announcements\
**Created:** [August 13, 2025, 4:28pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-9-0-key-dates/3178 "2025-08-13T16:28:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![anitakat](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/anitakat/32/2830_2.png) [@anitakat](https://dev-discuss.pytorch.org/u/anitakat)\
**Post date:** [August 13, 2025, 4:28pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-9-0-key-dates/3178/1 "2025-08-13T16:28:53Z")

</div>

Hi Team,

We are kicking off the PyTorch 2.9.0 release cycle and continue to be excited for all the great features from our PyTorch community!

**KEY DATES FOR THE PYTORCH 2.9.0 RELEASE**

- M1: Release Announcement - (today)
- M2: Land Target PRs in PyTorch repo - DEADLINE (09/05)
- M3.1: Release branch cut (09/08)
- M3.2: Release first RC1 Binary for PyTorch Core (09/10)
- M3.3: Ecosystem libraries cut RC Branch (09/11)
- M4: Release branch finalized, Announce final launch date, new features published (week of 09/29) - Final RC is produced.
- M4.1 Tutorial drafts submission deadline (10/08)
- M5: External-Facing Content Finalized (10/10)
- M6: Release Day (10/15)

**REMINDER OF CHANGES TO CLASSIFICATION & TRACKING**

As mentioned in [this RFC](https://github.com/pytorch/pytorch/issues/152134), beginning in release 2.8, there are changes to classification and tracking.

**Classification**

Feature submissions are now classified as either Stable (API-Stable) or Unstable (API-Unstable), and 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](https://github.com/pytorch/pytorch/issues/152134).

**Tracking**

_What’s changed?_

- All new features should create an RFC. Steps are: _New Issue \> Release highlight for Proposed Feature._ (see image below)

 ![|379.4681467181466x316.1917578786091](https://canada1.discourse-cdn.com/flex036/uploads/pytorch1/original/2X/4/4a6acbc50c73b49a5785c4ad5532f3d5f3e81a73.jpeg)

- These features will be tracked from inception (initial RFC) till they are stable, after which they will be untagged and no longer tracked. This will provide continuous visibility / up-to-date status on features that the majority of the community relies on.

_What’s not changed?_

All features continue to be welcome. If you would like a feature to be included in the release blogpost, please mention it in the _“Release highlight for Proposed Feature”_ issue that you create, and include the release version this is targeted to.

Please also read the [blog post for the 2.8 release](https://pytorch.org/blog/pytorch-2-7/) to get familiar with the marketing format.

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