# PyTorch Release 2.0.1 Planning

**URL:** https://dev-discuss.pytorch.org/t/pytorch-release-2-0-1-planning/1149
**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:** 1
**Showing post:** 2

<div class="post-metadata">

### 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")

</div>

> [@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.

---

_[View the full topic](https://dev-discuss.pytorch.org/t/pytorch-release-2-0-1-planning/1149)._
