frozenleaves/pytorch
1
0
Fork 0
mirror of https://github.com/pytorch/pytorch.git synced 2025-10-20 12:54:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Explicitly state that a test-infra branch cut is required (#150214)

Browse Source 
Pull Request resolved: https://github.com/pytorch/pytorch/pull/150214
Approved by: https://github.com/atalman
ghstack dependencies: #150210, #150211, #150213
This commit is contained in:
Zain Rizvi
2025-03-28 14:32:25 -05:00
committed by PyTorch MergeBot
parent 2b2286c4ec
commit 4271ebdbdc
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
RELEASE.md
View File

@ -141,8 +141,11 @@ DRY_RUN=disabled GIT_BRANCH_TO_CUT_FROM=main RELEASE_VERSION=1.11 scripts/releas
```
### Making release branch specific changes for PyTorch
First you should cut a release branch for pytorch/test-infra:
* Create a new branch using the naming convention `release/[major].[minor]`, e.g. `release/2.7`
* On that release branch, update branch pointers for any pytorch-managed reusable actions or workflows to point to the new release's branch ([example](https://github.com/pytorch/test-infra/commit/749b9e36afa23298ad5498c9f5bcd96f5467baff#diff-d41015f3ac6cfa64b00e366bec416bb9487ac27493de7ebe7778fdfc7518b003R39)).
These are examples of changes that should be made to release branches so that CI / tooling can function normally on
Here are examples of changes that should be made to the pytorch/pytorch release branches so that CI / tooling can function normally on
them:
* Update backwards compatibility tests to use RC binaries instead of nightlies