| Due Date | Comments | Start of the Release | Initial Checkpoint | Version Bump | Middle checkpoint | Formal Release For Managed Projects | Release for Self Managed Projects | Updating Release docs | Updating Release docs ( downloads, etc) | Comments | Who | applies to SRs |
|---|
| Communicate code freeze to projects | 2 weeks before code freeze happens | release manager | yes |
| Code freeze (stable branch lock) | 3 weeks before any release. | LF IT | yes |
| Pick RC and produce CSIT spreadsheet | All blocker bugs must be closed before picking the RC. This is tentative date. | integration/test | yes |
| Vet CSIT failures | Max 1 week after CSIT spreadsheet is shared. | all projects | yes |
| TSC votes the Managed release |
| TSC | yes |
| Unlock stable branch |
| LF IT | yes |
| Remind PTL to produce release notes (only for GA release) |
| release manager | no |
| Publish released artifacts to Nexus |
| LF IT | yes |
| Communicate Managed release to Self Managed projects |
| release manager | yes |
| Release All SM projects (including "official" distribution) | Max 1 week after Managed release. | All SM projects (including int/dist) | yes |
| Update docs | | docs team | some |
Branch docs project | - on master branch bump versions to next release (conf.yaml)
- Clear per-project release notes in master to prep for next release
- on new stable/branch update links to stable/branch away from "latest" (conf.py)
| docs team | no |