# PyTorch Release 2.0.1 Planning **URL:** \ **Category:** Release Announcements\ **Created:** [March 22, 2023, 12:15pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-0-1-planning/1149 "2023-03-22T12:15:58Z")\ **Posts on this page:** 3\ **Page:** 1
**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:** [March 22, 2023, 12:15pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-0-1-planning/1149/1 "2023-03-22T12:15:58Z")
We are starting to plan for 2.0.1 release, preemptively cutting a branch to solicit critical bugs to decide when/whether to proceed with 2.0.1 . Let us know by April 4, 2023 if issue should be included in 2.0.1 minor Release. You can do so by creating new issue under pytorch/pytorch and assigning it to [2.0.1 Milestone](https://github.com/pytorch/pytorch/milestone/36) Please note: since it’s a minor release, we are only considering critical fixes to be included in this release. Please see Cherry-Pick Criteria of [[v2.0.1] Release Tracker](https://github.com/pytorch/pytorch/issues/97272). Important: If you added an issue to a milestones: [2.0.1 Milestone · GitHub](https://github.com/pytorch/pytorch/milestone/36?closed=1) and there is already a fix for it that is landed, please post it as cherry pick into the [[v2.0.1] Release Tracker](https://github.com/pytorch/pytorch/issues/97272). There isn’t a current timeline for 2.0.1 release. We use release tracker to know what will be included in the release and to take the decision on when and if it will happen. The next milestone is April 4th where the Release team will meet and decide if we are triggering an RC. Our plan from this point from this point is roughly: - Phase 0 (April 4th): Review posted cherry-picks and decide if we are triggering RC - Phase 1 (until TBD): Release Candidate 1 - Phase 2 (until TBD): _Tentative General Availability_ Please contact OSS Releng team members if you have any questions/comments. ---
**Author:** ![jerrypark](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jerrypark](https://dev-discuss.pytorch.org/u/jerrypark)\ **Post date:** [April 4, 2023, 7:36pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-0-1-planning/1149/2 "2023-04-04T19:36:55Z")
> [@PyTorch Release 2.0.1 Important Information](https://dev-discuss.pytorch.org/t/pytorch-release-2-0-1-important-information/1176): > > Dear Team, Today (4/4/23) the PyTorch Release Team reviewed cherry-picks and have decided to proceed with PyTorch 2.0.1 release based on the following two must-have fixes: [Convolutions are broken for PyTorch-2.0 CUDA-11.8 wheel builds](https://github.com/pytorch/pytorch/issues/97041)[Add support for custom backend](https://github.com/pytorch/pytorch/pull/95072) This post specifies the target timeline, and the process to follow to be considered for inclusion of this release. What you need to do if you have a fix that you want to get into 2.0.1 If you added an issue to milestones :[https:…](https://github.com/pytorch/pytorch/milestone/36?closed=1) See the new post on 4/4/23 that updates deadlines and timelines for 2.0.1 release. ---
**Author:** ![jerrypark](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@jerrypark](https://dev-discuss.pytorch.org/u/jerrypark)\ **Post date:** [April 13, 2023, 5:11pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-0-1-planning/1149/3 "2023-04-13T17:11:43Z")
We (on 4/13/23) have decided to delay the release of PyTorch 2.0.1 by a week to conduct additional regression testing on newly released hardware. New dates are: - 4/21 (Friday): Cherry-pick post deadline (End of day 5PM PST) - 4/24 (Monday): All cherry-picks merged in the release branch - 4/25 (Tuesday): All RC binaries are ready for testing - 5/5 (Friday): Release 2.0.1 General Availability