Lines Matching +full:update +full:- +full:labels +full:- +full:in +full:- +full:s3
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…
67 | --- | --- | --- | --- | --- |
91 …in order to release a series of release candidates (RC). The activities in the release branch incl…
93 * Q: What is cherry-pick ?
94 …in [cherry-pick feature](https://git-scm.com/docs/git-cherry-pick). These commits are typically li…
100 …in the milestones(for example [1.11.0](https://github.com/pytorch/pytorch/milestone/28))before fir…
101 …` python github_analyze.py --repo-path ~/local/pytorch --remote upstream --branch release/1.11 --m…
102 * Validate that all new workflows have been created in the PyTorch and domain libraries included in…
122 DRY_RUN=disabled scripts/release/cut-release-branch.sh
130 …uld be created after first release candidate build of PyTorch is available in staging channels (wh…
133 > NOTE: RELEASE_VERSION only needs to be specified if version.txt is not available in root directory
136 DRY_RUN=disabled GIT_BRANCH_TO_CUT_FROM=main RELEASE_VERSION=1.11 scripts/release/cut-release-branc…
144 * Update backwards compatibility tests to use RC binaries instead of nightlies
146 …be created in [`pytorch/xla`](https://github.com/pytorch/xla) and [`pytorch/builder`](https://gith…
148 * Update branch used in composite actions from trunk to release (for example, can be done by runnin…
153 * Nightly versions should be updated in all version files to the next MINOR release (i.e. 0.9.0 -> …
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 … configured here: [`pytorch-circleci-labels.yml`](https://github.com/pytorch/pytorch/blob/main/.gi…
213 Release candidates are currently stored in the following places:
216 * Conda: https://anaconda.org/pytorch-test
219 … are stored in a non-public S3 bucket at [`s3://pytorch-backup`](https://s3.console.aws.amazon.com…
228 …ation build has completed and generated entry corresponding to the release in [docs repository](h…
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)
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
267 requires `pytorchbot`, so it's only available in PyTorch atm.
271 If PR that has been cherry-picked into release branch has been reverted, its cherry-pick must be re…
279 …in the milestone. There should be no open issues/PRs (for example [2.1.2](https://github.com/pytor…
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 --mi…
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
298 * Run performance tests in [benchmark repository](https://github.com/pytorch/benchmark). Make sure …
310 Users of that script should take care to update the versions necessary for the specific packages yo…
312 Promotion should occur in two steps:
313 * Promote S3 artifacts (wheels, libtorch) and Conda packages
314 * Promote S3 wheels to PyPI
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)
336 A patch release is a maintenance release of PyTorch that includes fixes for regressions found in a …
344 1. Does the regression break core functionality (stable / beta features) including functionality in…
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.
363 …orch Core and Project Managers where potential issues triggering a release in milestones are revie…
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 …* ](#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…
409 # Hardware / Software Support in Binary Build Matrix
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…
430 In some instances support for a particular version of software will continue if a need is found. Fo…
437 Supported OS flavors are summarized in the table below:
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 …in support of a release feature must be submitted to the [pytorch/tutorials](https://github.com/py…
453 In the event a submodule cannot be fast forwarded, and a patch must be applied we can take two diff…
460 git config --file=.gitmodules -e
469 In nightly builds for conda and wheels pytorch depend on Triton build by this workflow: https://hud…
471 In Nightly builds we have following configuration:
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 …m OpenAI once branch cut is completed. Please include the release PIN hash in the request: https:/…