OSSForks/pytorch
1
0
Fork 0
mirror of https://github.com/zebrajr/pytorch.git synced 2025-12-06 12:20:52 +01:00
Code Issues Actions 38 Packages Projects Releases Wiki Activity

[release] Add Launch Execution XFN meeting process to release runbook (#116701)

Browse Source 
Make sure we have this process documented in the runbook.

Pull Request resolved: https://github.com/pytorch/pytorch/pull/116701
Approved by: https://github.com/seemethere
This commit is contained in:
atalman 2024-01-03 17:16:18 +00:00 committed by PyTorch MergeBot
parent d2fc00d2cc
commit 2ae55e99fe
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
RELEASE.md
View File

@ -12,6 +12,7 @@
- [`pytorch/builder` / PyTorch domain libraries](#pytorchbuilder--pytorch-domain-libraries) - [`pytorch/builder` / PyTorch domain libraries](#pytorchbuilder--pytorch-domain-libraries)
- [Making release branch specific changes for PyTorch](#making-release-branch-specific-changes-for-pytorch) - [Making release branch specific changes for PyTorch](#making-release-branch-specific-changes-for-pytorch)
- [Making release branch specific changes for domain libraries](#making-release-branch-specific-changes-for-domain-libraries) - [Making release branch specific changes for domain libraries](#making-release-branch-specific-changes-for-domain-libraries)
- [Running Launch Execution team Core XFN sync](#running-launch-execution-team-core-xfn-sync)
- [Drafting RCs (Release Candidates) for PyTorch and domain libraries](#drafting-rcs-release-candidates-for-pytorch-and-domain-libraries) - [Drafting RCs (Release Candidates) for PyTorch and domain libraries](#drafting-rcs-release-candidates-for-pytorch-and-domain-libraries)
- [Release Candidate Storage](#release-candidate-storage) - [Release Candidate Storage](#release-candidate-storage)
- [Release Candidate health validation](#release-candidate-health-validation) - [Release Candidate health validation](#release-candidate-health-validation)
@ -153,6 +154,22 @@ Follow these examples of PR that updates the version and sets RC Candidate uploa
* torchvision : https://github.com/pytorch/vision/pull/5400 * torchvision : https://github.com/pytorch/vision/pull/5400
* torchaudio: https://github.com/pytorch/audio/pull/2210 * torchaudio: https://github.com/pytorch/audio/pull/2210
## Running Launch Execution team Core XFN sync
The series of meetings for Core XFN sync should be organized. The goal of these meetings are the following:
1. Establish release POC's from each of the workstreams
2. Cover the tactical phase of releasing minor releases to the market
3. Discuss possible release blockers
Following POC's should be assigned from each of the workstreams:
* Core/Marketing
* Release Eng
* Doc Eng
* Release notes
* Partner
**NOTE**: The meetings should start after the release branch is created and should continue until the week of the release.
## Drafting RCs (Release Candidates) for PyTorch and domain libraries ## Drafting RCs (Release Candidates) for PyTorch and domain libraries
To draft RCs, a user with the necessary permissions can push a git tag to the main `pytorch/pytorch` git repository. Please note: exactly same process is used for each of the domain library To draft RCs, a user with the necessary permissions can push a git tag to the main `pytorch/pytorch` git repository. Please note: exactly same process is used for each of the domain library