Lines Matching +full:- +full:- +full:branch
3 <!-- toc -->
5 - [Release Compatibility Matrix](#release-compatibility-matrix)
6 - [Release Cadence](#release-cadence)
7 - [General Overview](#general-overview)
8 - [Frequently Asked Questions](#frequently-asked-questions)
9 - [Cutting a release branch preparations](#cutting-a-release-branch-preparations)
10 - [Cutting release branches](#cutting-release-branches)
11 - [`pytorch/pytorch`](#pytorchpytorch)
12 - [`pytorch/builder` / PyTorch domain libraries](#pytorchbuilder--pytorch-domain-libraries)
13 …- [Making release branch specific changes for PyTorch](#making-release-branch-specific-changes-for…
14 …- [Making release branch specific changes for domain libraries](#making-release-branch-specific-ch…
15 - [Running Launch Execution team Core XFN sync](#running-launch-execution-team-core-xfn-sync)
16 …- [Drafting RCs (Release Candidates) for PyTorch and domain libraries](#drafting-rcs-release-candi…
17 - [Release Candidate Storage](#release-candidate-storage)
18 - [Release Candidate health validation](#release-candidate-health-validation)
19 - [Cherry Picking Fixes](#cherry-picking-fixes)
20 - [How to do Cherry Picking](#how-to-do-cherry-picking)
21 - [Cherry Picking Reverts](#cherry-picking-reverts)
22 …- [Preparing and Creating Final Release candidate](#preparing-and-creating-final-release-candidate)
23 - [Promoting RCs to Stable](#promoting-rcs-to-stable)
24 - [Additional Steps to prepare for release day](#additional-steps-to-prepare-for-release-day)
25 - [Modify release matrix](#modify-release-matrix)
26 - [Open Google Colab issue](#open-google-colab-issue)
27 - [Patch Releases](#patch-releases)
28 - [Patch Release Criteria](#patch-release-criteria)
29 - [Patch Release Process](#patch-release-process)
30 - [Patch Release Process Description](#patch-release-process-description)
31 - [Triage](#triage)
32 - [Issue Tracker for Patch releases](#issue-tracker-for-patch-releases)
33 - [Building a release schedule / cherry picking](#building-a-release-schedule--cherry-picking)
34 - [Building Binaries / Promotion to Stable](#building-binaries--promotion-to-stable)
35 - [Hardware / Software Support in Binary Build Matrix](#hardware--software-support-in-binary-build-…
36 - [Python](#python)
37 - [Accelerator Software](#accelerator-software)
38 - [Special support cases](#special-support-cases)
39 - [Operating Systems](#operating-systems)
40 - [Submitting Tutorials](#submitting-tutorials)
41 - [Special Topics](#special-topics)
42 - [Updating submodules for a release](#updating-submodules-for-a-release)
43 - [Triton dependency for the release](#triton-dependency-for-the-release)
45 <!-- tocstop -->
52 | --- | --- | --- | --- | --- | --- |
64 …the release scheduled please follow [dev discuss](https://dev-discuss.pytorch.org/c/release-announ…
66 | Minor Version | Release branch cut | Release date | First patch release date | Second patch relea…
67 | --- | --- | --- | --- | --- |
82 0. Cutting a release branch preparations
83 1. Cutting a release branch and making release branch specific changes
90 * Q: What is release branch cut ?
91 …branch, the primary release engineer starts the release process of cutting the release branch by c…
93 * Q: What is cherry-pick ?
94 …branch, utilizing git's built in [cherry-pick feature](https://git-scm.com/docs/git-cherry-pick). …
96 ## Cutting a release branch preparations
98 Following Requirements needs to be met prior to cutting a release branch:
100 …e executed from builder repo in order to validate the presence of the fixes in the release branch :
101 …ython github_analyze.py --repo-path ~/local/pytorch --remote upstream --branch release/1.11 --mile…
112 …rom the branch [`viable/strict`](https://github.com/pytorch/pytorch/tree/viable/strict) as to ensu…
122 DRY_RUN=disabled scripts/release/cut-release-branch.sh
130 …ease branch has been created). This is absolutely required to allow sufficient testing time for ea…
131 Builder branch cut should be performed at the same time as Pytorch core branch cut. Convenience scr…
136 …RUN=disabled GIT_BRANCH_TO_CUT_FROM=main RELEASE_VERSION=1.11 scripts/release/cut-release-branch.sh
139 ### Making release branch specific changes for PyTorch
148 …Update branch used in composite actions from trunk to release (for example, can be done by running…
151 These are examples of changes that should be made to the *default* branch after a release branch is…
153 …pdated in all version files to the next MINOR release (i.e. 0.9.0 -> 0.10.0) in the default branch:
156 ### Making release branch specific changes for domain libraries
158 Domain library branch cut is done a week after branch cut for the `pytorch/pytorch`. The branch cut…
159 After the branch cut is performed, the Pytorch Dev Infra member should be informed of the branch cu…
179 **NOTE**: The meetings should start after the release branch is created and should continue until t…
187 v{MAJOR}.{MINOR}.{PATCH}-rc{RC_NUMBER}
192 v1.12.0-rc1
198 git log --oneline
202 git tag -f v1.12.0-rc2
203 git push origin v1.12.0-rc2
206 …I using [`pytorch/pytorch-probot`](https://github.com/pytorch/pytorch-probot)'s [`trigger-circleci…
208 … is configured here: [`pytorch-circleci-labels.yml`](https://github.com/pytorch/pytorch/blob/main/…
216 * Conda: https://anaconda.org/pytorch-test
219 … stored in a non-public S3 bucket at [`s3://pytorch-backup`](https://s3.console.aws.amazon.com/s3/…
234 For fixes that are to go into a release after the release branch has been cut we typically employ t…
246 to the main branch using `@pytorchbot cherry-pick` command as follows.
249 usage: @pytorchbot cherry-pick --onto ONTO [--fixes FIXES] -c
252 Cherry pick a pull request onto a release branch for inclusion in a release
255 --onto ONTO Branch you would like to cherry pick onto (Example: release/2.2)
256 …--fixes FIXES Link to the issue that your PR fixes (i.e. https://github.com/pytorch/pytorc…
257 -c {regression,critical,fixnewfeature,docs,release}
258 A machine-friendly classification of the cherry-pick reason.
261 For example, [#120567](https://github.com/pytorch/pytorch/pull/120567#issuecomment-1978964376)
263 branch to fix a regression issue. You can then refer to the original
264 and the cherry-picked PRs on the release tracker issue. Please note
265 that the cherry-picked PR will still need to be reviewed by PyTorch
266 RelEng team before it can go into the release branch. This feature
271 If PR that has been cherry-picked into release branch has been reverted, its cherry-pick must be re…
273 …changes that was committed into the main branch prior to the branch cut, must be propagated into r…
279 …ps://github.com/pytorch/pytorch/milestone/39)). The issue should either be closed or de-milestoned.
281 * Validate that all closed milestone PRs are present in the release branch. Confirm this by running:
282 …ython github_analyze.py --repo-path ~/local/pytorch --remote upstream --branch release/2.2 --miles…
284 * No outstanding cherry-picks that need to be reviewed in the issue tracker: https://github.com/pyt…
286 * Perform [Release Candidate health validation](#release-candidate-health-validation). CI should ha…
290 * Perform [Release Candidate health validation](#release-candidate-health-validation). CI should ha…
292 …date Binaries](https://github.com/pytorch/builder/actions/workflows/validate-binaries.yml) workflo…
294 …y commenting on the issue: https://github.com/pytorch/pytorch/issues/113568#issuecomment-1851031064
324 …rix for get started page. See following [PR](https://github.com/pytorch/test-infra/pull/4611) as r…
326 The PR to update published_versions.json and quick-start-module.js is auto generated. See following…
328 …lease candidate location as above [Release Candidate Storage](RELEASE.md#release-candidate-storage)
359 Patch releases should follow these high-level phases. This process starts immediately after the pre…
360 Patch release process takes around 4-5 weeks to complete.
366 …icial channels [example announcement](https://dev-discuss.pytorch.org/t/pytorch-release-2-0-1-impo…
375 …adding triage review label](https://user-images.githubusercontent.com/1700823/132589089-a9210a14-6…
376 …sion / fix identified fits within above mentioned [Patch Release Criteria](#patch-release-criteria)
377 ….1`) if the regressions is found to be within the [Patch Release Criteria](#patch-release-criteria)
378 …* 
397 …* *NOTE*: Ideally this should be ~2-3 weeks after a regression has been identified to allow other …
398 …regressions / fixes to cherry pick their change into the related release branch (i.e. `release/1.9…
406 …cess of [Drafting RCs (Release Candidates)](#drafting-rcs-release-candidates-for-pytorch-and-domai…
407 2. Patch Release Managers will follow the process of [Promoting RCs to Stable](#promoting-rcs-to-st…
418 - If the latest patch release is a bugfix release, we only support this one.
419 - Otherwise, we support all the non-bugfix patch releases.
421 See https://github.com/pytorch/rfcs/blob/master/RFC-0038-cpython-support.md for details on the rule…
439 | --- | --- | --- |
440 …ylinux2014 compatible, i.e. they should be runnable on any Linux system with glibc-2.17 or above. |
443 | Windows | x86_64 | Builds are compatible with Windows-10 or newer. |
447 …release date to allow for editorial and technical review. There is no cherry-pick process for tuto…
456 * Get the dependencies maintainers to support a release branch for us
460 git config --file=.gitmodules -e
472 * Conda builds, depend on: https://anaconda.org/pytorch-nightly/torchtriton
473 * Wheel builds, depend on : https://download.pytorch.org/whl/nightly/pytorch-triton/
474 * Rocm wheel builds, depend on : https://download.pytorch.org/whl/nightly/pytorch-triton-rocm/
477 * Conda builds, depend on: https://anaconda.org/pytorch-test/torchtriton for test and https://anaco…
479 …//download.pytorch.org/whl/test/pytorch-triton-rocm/ for test and https://download.pytorch.org/whl…
481 … https://pypi.org/project/triton/ needs to be requested from OpenAI once branch cut is completed. …