Skip to end of banner
Go to start of banner

Release Checklist Template

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

PendingComplete


Event / TimelineCommentsWho
Communicate code freeze to projects2 weeks before code freeze happensrelease manager
Code freeze (stable branch lock)3 weeks before any release.LF IT
Pick RC and produce CSIT spreadsheetAll blocker bugs must be closed before picking the RC. This is tentative date.integration/test
Vet CSIT failuresMax 1 week after CSIT spreadsheet is shared.all projects
TSC votes the Managed release
TSC
Unlock stable branch
LF IT
Remind PTL to produce release notes (only for GA release)
release manager
Publish released artifacts to Nexus
LF IT
Communicate Managed release to Self Managed projects
release manager
Release All SM projects (including "official" distribution)Max 1 week after Managed release.All SM projects (including int/dist)
Update docsdocs team

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 labels