From 872144854417cb03b4c5293755bfa4a4a1bc78ae Mon Sep 17 00:00:00 2001 From: Andrey Talman Date: Mon, 28 Nov 2022 10:36:40 -0500 Subject: [PATCH] Add statement about minor releases, in the release.md document (#89698) * Add statement about minor releases * Update RELEASE.md --- RELEASE.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/RELEASE.md b/RELEASE.md index d13ca5d11e1..58d938fafdd 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -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