Intro: SIG Release
summary
SIG Release runs Kubernetes on a quarterly cadence with a concrete pipeline: a planning phase that narrows ~40–60 enhancements, an enhancements freeze at week 4, branch and code slush around week 7, and a code freeze at week 8, followed by publishing build artifacts and nine months of support. Releases take ~2,000 commits, use git cherry-pick to backport critical fixes, and rely on roles like CI signal, test infra, bug triage, branch and patch managers. Ongoing work includes signed artifacts, release engineering tooling, and an LTS working group.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:47What is SIG Release
- 4:16The Process
- 8:53Support
- 11:11Long Term Support
- 13:23Release Team
- 17:10Roles
- 21:38Role Handbooks
- 23:15Sub Projects
- 25:48QA
