From c878ea2c4e05b1ed98664178fda2ca4d8c8d6a7a Mon Sep 17 00:00:00 2001 From: Sergii Dymchenko Date: Thu, 26 Sep 2024 18:45:45 +0000 Subject: [PATCH] Add info about "release tracker" label for cherry-picking bot (#136777) Pull Request resolved: https://github.com/pytorch/pytorch/pull/136777 Approved by: https://github.com/seemethere, https://github.com/atalman --- RELEASE.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index a5641d402f7aa6..a5bc02a482a25c 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -234,7 +234,7 @@ Typically, within a release cycle fixes are necessary for regressions, test fixe For fixes that are to go into a release after the release branch has been cut we typically employ the use of a cherry pick tracker. An example of this would look like: -* https://github.com/pytorch/pytorch/issues/51886 +* https://github.com/pytorch/pytorch/issues/128436 Please also make sure to add milestone target to the PR/issue, especially if it needs to be considered for inclusion into the dot release. @@ -243,7 +243,9 @@ Please also make sure to add milestone target to the PR/issue, especially if it #### How to do Cherry Picking You can now use `pytorchbot` to cherry pick a PyTorch PR that has been committed -to the main branch using `@pytorchbot cherry-pick` command as follows. +to the main branch using `@pytorchbot cherry-pick` command as follows (make sure +that the cherry-pick tracker issue for the target release labelled as "release tracker" - +this will allow the bot to find it and post comments). ``` usage: @pytorchbot cherry-pick --onto ONTO [--fixes FIXES] -c @@ -380,7 +382,7 @@ Patch release process takes around 4-5 weeks to complete. ### 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 +* https://github.com/pytorch/pytorch/issues/128436 Only following issues are accepted: 1. Fixes to regressions against previous major version (e.g. regressions introduced in 1.13.0 from 1.12.0 are pickable for 1.13.1)