# PyTorch release 2.1.2 planning

**URL:** <https://dev-discuss.pytorch.org/t/pytorch-release-2-1-2-planning/1663>\
**Category:** Release Announcements\
**Created:** [November 17, 2023, 5:48pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-1-2-planning/1663 "2023-11-17T17:48:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![atalman](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/atalman/32/1857_2.png) [@atalman](https://dev-discuss.pytorch.org/u/atalman)\
**Post date:** [November 17, 2023, 5:48pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-1-2-planning/1663/1 "2023-11-17T17:48:05Z")

</div>

Dear Team

We will be creating patch PyTorch release 2.1.2.

Following are the tentative dates:

- 12/1 Cherry-pick post deadline (End of day 5PM PST)
- 12/6 All RC binaries are ready for testing
- 12/13 Release 2.1.2 General Availability

Please consider the criteria below and follow the cherry picking process. Only low-risk changes may be cherry-picked from main:

1. Fixes to regressions against the most recent release (e.g. 2.1.1 for 2.1.2 release; see [module: regression issue list](https://github.com/pytorch/pytorch/issues?q=is%3Aissue+is%3Aopen+label%3A%22module%3A+regression%22+))
2. Low risk critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
3. Fixes to new features being introduced in 2.1.0 release
4. Documentation improvements
5. Release branch specific changes (e.g. blocking ci fixes, change version identifiers)

Issue tracker for this release can be found [here](https://github.com/pytorch/pytorch/issues/113962)  
Issues that are targeted to be included in this release can be found [here](https://github.com/pytorch/pytorch/milestone/39)