Lines Matching full:release
5 - [Release Compatibility Matrix](#release-compatibility-matrix)
6 - [Release Cadence](#release-cadence)
9 - [Cutting a release branch preparations](#cutting-a-release-branch-preparations)
10 - [Cutting release branches](#cutting-release-branches)
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…
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)
22 …- [Preparing and Creating Final Release candidate](#preparing-and-creating-final-release-candidate)
24 - [Additional Steps to prepare for release day](#additional-steps-to-prepare-for-release-day)
25 - [Modify release matrix](#modify-release-matrix)
28 - [Patch Release Criteria](#patch-release-criteria)
29 - [Patch Release Process](#patch-release-process)
30 - [Patch Release Process Description](#patch-release-process-description)
33 - [Building a release schedule / cherry picking](#building-a-release-schedule--cherry-picking)
42 - [Updating submodules for a release](#updating-submodules-for-a-release)
43 - [Triton dependency for the release](#triton-dependency-for-the-release)
47 ## Release Compatibility Matrix
49 Following is the Release Compatibility Matrix for PyTorch releases:
62 ## Release Cadence
64 …release cadence for year 2023/2024. All dates below are tentative, for latest updates on the relea…
66 | Minor Version | Release branch cut | Release date | First patch release date | Second patch relea…
82 0. Cutting a release branch preparations
83 1. Cutting a release branch and making release branch specific changes
84 2. Drafting RCs (Release Candidates), and merging cherry picks
85 3. Preparing and Creating Final Release Candidate
86 4. Promoting Final RC to stable and performing release day tasks
90 * Q: What is release branch cut ?
91 …release engineer starts the release process of cutting the release branch by creating a new git br…
94 …release branch, utilizing git's built in [cherry-pick feature](https://git-scm.com/docs/git-cherry…
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 ``` python github_analyze.py --repo-path ~/local/pytorch --remote upstream --branch release/1.11 --…
102 …the PyTorch and domain libraries included in the release. Validate it against all dimensions of re…
108 ## Cutting release branches
112 Release branches are typically cut from the branch [`viable/strict`](https://github.com/pytorch/pyt…
114 There's a convenience script to create release branches from current `viable/strict`. Perform follo…
122 DRY_RUN=disabled scripts/release/cut-release-branch.sh
125 * `release/{MAJOR}.{MINOR}`
126 * `orig/release/{MAJOR}.{MINOR}`
130 …Release branches for individual domain libraries should be created after first release candidate b…
136 DRY_RUN=disabled GIT_BRANCH_TO_CUT_FROM=main RELEASE_VERSION=1.11 scripts/release/cut-release-branc…
139 ### Making release branch specific changes for PyTorch
141 These are examples of changes that should be made to release branches so that CI / tooling can func…
146 * A release branches should also be created in [`pytorch/xla`](https://github.com/pytorch/xla) and …
148 …actions from trunk to release (for example, can be done by running `for i in .github/workflows/*.y…
151 These are examples of changes that should be made to the *default* branch after a release branch is…
153 * Nightly versions should be updated in all version files to the next MINOR release (i.e. 0.9.0 -> …
156 ### Making release branch specific changes for domain libraries
168 1. Establish release POC's from each of the workstreams
170 3. Discuss possible release blockers
174 * Release Eng
176 * Release notes
179 …*: The meetings should start after the release branch is created and should continue until the wee…
181 ## Drafting RCs (Release Candidates) for PyTorch and domain libraries
185 The git tag for a release candidate must follow the following format:
197 git checkout release/1.12
200 * Perform tag and push it to github (this will trigger the binary release build)
206 Pushing a release candidate should trigger the `binary_builds` workflow within CircleCI using [`pyt…
210 To view the state of the release build, please navigate to [HUD](https://hud.pytorch.org/hud/pytorc…
211 ### Release Candidate Storage
213 Release candidates are currently stored in the following places:
221 ### Release Candidate health validation
223 Validate the release jobs for pytorch and domain libraries should be green. Validate this using fol…
224 * [Pytorch](https://hud.pytorch.org/hud/pytorch/pytorch/release%2F1.12)
225 * [TorchVision](https://hud.pytorch.org/hud/pytorch/vision/release%2F1.12)
226 * [TorchAudio](https://hud.pytorch.org/hud/pytorch/audio/release%2F1.12)
228 …cumentation build has completed and generated entry corresponding to the release in [docs reposit…
232 Typically, within a release cycle fixes are necessary for regressions, test fixes, etc.
234 For fixes that are to go into a release after the release branch has been cut we typically employ t…
239 …target to the PR/issue, especially if it needs to be considered for inclusion into the dot release.
250 {regression,critical,fixnewfeature,docs,release}
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)
257 -c {regression,critical,fixnewfeature,docs,release}
262 created a cherry pick PR [#121232](https://github.com/pytorch/pytorch/pull/121232) onto `release/2.…
264 and the cherry-picked PRs on the release tracker issue. Please note
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 …itted into the main branch prior to the branch cut, must be propagated into release branch as well.
275 ## Preparing and Creating Final Release candidate
277 The following requirements need to be met prior to creating final Release Candidate :
281 * Validate that all closed milestone PRs are present in the release branch. Confirm this by running:
282 ``` python github_analyze.py --repo-path ~/local/pytorch --remote upstream --branch release/2.2 --m…
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…
296 * Create validation issue for the release, see for example [Validations for 2.1.2 release](https://…
301 [`pytorch/builder:release/pypi/promote_pypi_to_staging.sh`](https://github.com/pytorch/builder/blob…
308 [`pytorch/builder:release/promote.sh`](https://github.com/pytorch/builder/blob/main/release/promote…
318 ## Additional Steps to prepare for release day
320 The following should be prepared for the release day
322 ### Modify release matrix
324 Need to modify release matrix for get started page. See following [PR](https://github.com/pytorch/t…
328 …release day and hence it should be absolutely free of any failures. To test this PR, open another …
332 This is normally done right after the release is completed. We would need to create Google Colab Is…
336 A patch release is a maintenance release of PyTorch that includes fixes for regressions found in a …
338 …h releases after every minor ones. Patch releases would only be published for latest minor release.
340 ## Patch Release Criteria
353 ## Patch Release Process
355 ### Patch Release Process Description
357 > Main POC: Patch Release Managers, Triage Reviewers
359 … these high-level phases. This process starts immediately after the previous release has completed.
360 Patch release process takes around 4-5 weeks to complete.
362 …ed, compared to Patch Release Criteria and added to Patch Release milestone. This process normally…
363 …g, PyTorch Core and Project Managers where potential issues triggering a release in milestones are…
364 * Should the new patch Release be created ?
365 * Timeline execution for the patch release
366 …release. At this point a new release tracker for the patch release is created, and an announcement…
367 …ting. After all cherry picks have been merged, Release Managers trigger new build and produce new …
374 1. Tag issues / pull requests that are candidates for a potential patch release with `triage review`
376 …ression / fix identified fits within above mentioned [Patch Release Criteria](#patch-release-crite…
377 …1.9.1`) if the regressions is found to be within the [Patch Release Criteria](#patch-release-crite…
382 For patch releases issue tracker needs to be created. For patch release, we require all cherry-pick…
388 3. Fixes to new features being introduced in this release
390 5. Release branch specific changes (e.g. blocking ci fixes, change version identifiers)
392 ### Building a release schedule / cherry picking
394 > Main POC: Patch Release Managers
396 …/ fixes have been triaged Patch Release Managers will work together and build /announce a schedule…
398 …tch Release Managers will work with the authors of the regressions / fixes to cherry pick their ch…
399 …release managers should notify authors of the regressions to post a cherry picks for their changes…
400 3. If cherry picking deadline is missed by cherry pick author, patch release managers will not acce…
404 > Main POC: Patch Release managers
406 1. Patch Release Managers will follow the process of [Drafting RCs (Release Candidates)](#drafting-…
407 2. Patch Release Managers will follow the process of [Promoting RCs to Stable](#promoting-rcs-to-st…
417 For each minor release independently, we only support patch releases as follows:
418 - If the latest patch release is a bugfix release, we only support this one.
447 …release feature must be submitted to the [pytorch/tutorials](https://github.com/pytorch/tutorials)…
451 ## Updating submodules for a release
456 * Get the dependencies maintainers to support a release branch for us
467 ## Triton dependency for the release
476 However for release we have following :
477 …onda.org/pytorch-test/torchtriton for test and https://anaconda.org/pytorch/torchtriton for release
478 …builds, depend only triton pypi package: https://pypi.org/project/triton/ for both test and release
479 …pytorch-triton-rocm/ for test and https://download.pytorch.org/whl/pytorch-triton-rocm/ for release
481 …release of https://pypi.org/project/triton/ needs to be requested from OpenAI once branch cut is c…