saymrwulf/pytorch
1
0
Fork 0
mirror of https://github.com/saymrwulf/pytorch.git synced 2026-05-14 20:57:59 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add statement about minor releases, in the release.md document (#89698)

Browse source 
* Add statement about minor releases

* Update RELEASE.md
This commit is contained in:
Andrey Talman 2022-11-28 10:36:40 -05:00 committed by GitHub
parent 6ba6b64a79
commit 8721448544
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
RELEASE.md
View file

@ -21,6 +21,7 @@
- [Patch Release Criteria](#patch-release-criteria)
- [Patch Release Process](#patch-release-process)
- [Triage](#triage)
- [Issue Tracker for Patch releases](#issue-tracker-for-patch-releases)
- [Building a release schedule / cherry picking](#building-a-release-schedule--cherry-picking)
- [Building Binaries / Promotion to Stable](#building-binaries--promotion-to-stable)
- [Hardware / Software Support in Binary Build Matrix](#hardware--software-support-in-binary-build-matrix)
@ -234,6 +235,20 @@ Patch releases should be considered if a regression meets the following criteria
3. Triage reviewers will then add the issue / pull request to the related milestone (i.e. `1.9.1`) if the regressions if found to be within the [Patch Release Criteria](#patch-release-criteria)
* ![adding to milestone](https://user-images.githubusercontent.com/1700823/131175980-148ff38d-44c3-4611-8a1f-cd2fd1f4c49d.png)
### Issue Tracker for Patch releases
For patch releases issue tracker needs to be created. For patch release, we require all cherry-pick changes to have links to either a high-priority Github issue or a CI failure from previous RC. An example of this would look like:
* https://github.com/pytorch/pytorch/issues/51886
Only following issues are accepted:
1. Fixes to regressions against previous major version
2. Critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
3. Fixes to new features being introduced in this release
4. Compilation fixes or ifdefs required for different versions of the compilers or third-party libraries
5. Test/CI fixes or improvements
6. Documentation improvements
7. Release branch specific changes (e.g. change version identifiers, remove/hide features that aren’t ready for release)
### Building a release schedule / cherry picking
> Main POC: Patch Release Managers