From 7ffdd4fedc592c6a242098687433fd3b82bcf51c Mon Sep 17 00:00:00 2001 From: Andrey Talman Date: Thu, 18 May 2023 20:27:16 +0000 Subject: [PATCH] Update release related information (#101819) Update release related information. Features became more complex. Number of commits per releases have increased a lot. We had in average: 2.5k commits for releases 1.1.0-1.7.0, 3-3.5k commits for releases 1.8.0-1.12.0 4.5k-5k commits for releases 1.13.0, 2.0.0 Hence current target is 3 releases a year Pull Request resolved: https://github.com/pytorch/pytorch/pull/101819 Approved by: https://github.com/svekars, https://github.com/malfet --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 61c1ee5e9ff..404fcbd5318 100644 --- a/README.md +++ b/README.md @@ -434,14 +434,14 @@ Three-pointers to get you started: ## Releases and Contributing -PyTorch has a 90-day release cycle (major releases). Please let us know if you encounter a bug by [filing an issue](https://github.com/pytorch/pytorch/issues). +Typically, PyTorch has three major releases a year. Please let us know if you encounter a bug by [filing an issue](https://github.com/pytorch/pytorch/issues). We appreciate all contributions. If you are planning to contribute back bug-fixes, please do so without any further discussion. If you plan to contribute new features, utility functions, or extensions to the core, please first open an issue and discuss the feature with us. Sending a PR without discussion might end up resulting in a rejected PR because we might be taking the core in a different direction than you might be aware of. -To learn more about making a contribution to Pytorch, please see our [Contribution page](CONTRIBUTING.md). +To learn more about making a contribution to Pytorch, please see our [Contribution page](CONTRIBUTING.md). For more information about PyTorch releases, see [Release page](RELEASE.md). ## The Team