# PyTorch release 2.1.1 planning

**URL:** <https://dev-discuss.pytorch.org/t/pytorch-release-2-1-1-planning/1558>\
**Category:** Release Announcements\
**Created:** [October 10, 2023, 9:58pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-1-1-planning/1558 "2023-10-10T21:58:48Z")\
**Posts on this page:** 5\
**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:** [October 10, 2023, 9:58pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-1-1-planning/1558/1 "2023-10-10T21:58:48Z")

</div>

Dear Team

We will be creating patch PyTorch release 2.1.1.

Following are the tentative dates:

- 11/3 Cherry-pick post deadline (End of day 5PM PST)
- 11/6 All RC binaries are ready for testing
- 11/15 Release 2.1.1 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.0 for 2.1.1 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/110961)  
Issues that are targeted to be included in this release can be found [here](https://github.com/pytorch/pytorch/milestone/38)

---

<div class="post-metadata">

**Author:** ![roywei](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/roywei/32/887_2.png) [@roywei](https://dev-discuss.pytorch.org/u/roywei)\
**Post date:** [October 25, 2023, 7:44pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-1-1-planning/1558/2 "2023-10-25T19:44:20Z")

</div>

Hi team,

Do we expect domain library releases (visoin, audio, text, data, torchserve) to go along with this release as well?  
We are packaging PyTorch libraries in AWS Deep Learning Containers ([Start via Cloud Partners | PyTorch](https://pytorch.org/get-started/cloud-partners/)) and would like to know what will happen for torchserve and data

1. Will torchserve become a domain library and share the same release cycle as torch like vision and audio?
2. Torch data is deprecated, do we expect future updates, new tags, new releases?

This helps us plan ahead Thanks!

---

<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:** [October 26, 2023, 5:53pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-1-1-planning/1558/3 "2023-10-26T17:53:26Z")

</div>

HI @roywei

Yes we should release pytorch, vision, audio, data and text with this patch release. 2.1.1.  
For Question #1 let me ask torchserve team to comment. For Question #2 - please stay tuned for release 2.2 announcement. And consult [GitHub - pytorch/data: A PyTorch repo for data loading and utilities to be shared by the PyTorch domain libraries.](https://github.com/pytorch/data) readme.md for any changes.

Thank you,  
Andrey

---

<div class="post-metadata">

**Author:** ![agunapal](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/agunapal/32/810_2.png) [@agunapal](https://dev-discuss.pytorch.org/u/agunapal)\
**Post date:** [October 26, 2023, 7:23pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-1-1-planning/1558/4 "2023-10-26T19:23:06Z")

</div>

Hi @roywei

Sharing what we discussed in the call.

- TorchServe release won’t be tightly coupled with PyTorch Release
- TorchServe version is not tightly coupled with PyTorch version.
- We will continue to make a TorchServe release after a major PyTorch Release.
- We will not have a mandatory TorchServe release after every PyTorch minor release. We will do it only if its necessary.

---

<div class="post-metadata">

**Author:** ![roywei](https://yyz2.discourse-cdn.com/flex036/user_avatar/dev-discuss.pytorch.org/roywei/32/887_2.png) [@roywei](https://dev-discuss.pytorch.org/u/roywei)\
**Post date:** [October 26, 2023, 8:21pm UTC](https://dev-discuss.pytorch.org/t/pytorch-release-2-1-1-planning/1558/5 "2023-10-26T20:21:54Z")

</div>

Thank you guys for the clarification and all the help driving the releases!