README.md

Release Special Interest Group

Ensure quality Kubernetes releases

The charter defines the scope and governance of the Release Special Interest Group.

Meetings

• Regular SIG Meeting: Tuesdays at 14:30 UTC (biweekly). Convert to your timezone.
  • Meeting notes and Agenda.
  • Meeting recordings.

Leadership

Chairs

The Chairs of the SIG run operations and processes governing the SIG.

• Stephen Augustus (@justaugustus), VMware
• Sascha Grunert (@saschagrunert), Red Hat

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

• Daniel Mangum (@hasheddan), Upbound
• Jeremy Rickard (@jeremyrickard), Apple

Emeritus Leads

• Jorge Alarcon Ochoa (@alejandrox1)
• Caleb Miles (@calebamiles)
• Jaice Singer DuMars (@jdumars)
• Tim Pepper (@tpepper)

Contact

• Slack: #sig-release
• Mailing list
• Open Community Issues/PRs
• GitHub Teams:
  • @kubernetes/kubernetes-milestone-maintainers - Milestone Maintainers
  • @kubernetes/release-managers - Release Managers
  • @kubernetes/sig-release - SIG Release Members
  • @kubernetes/sig-release-admins - Admins for SIG Release repositories
• Steering Committee Liaison: Davanum Srinivas (@dims)

Subprojects

The following subprojects are owned by sig-release:

Release Engineering

The Release Engineering subproject is responsible for the process/procedures and tools used to create/maintain Kubernetes release artifacts.

• Owners:
  • kubernetes-sigs/downloadkubernetes
  • kubernetes-sigs/k8s-container-image-promoter
  • kubernetes-sigs/mdtoc
  • kubernetes-sigs/release-notes
  • kubernetes-sigs/release-sdk
  • kubernetes-sigs/release-utils
  • kubernetes-sigs/zeitgeist
  • kubernetes/publishing-bot
  • kubernetes/release
  • kubernetes/sig-release/release-engineering
• Contact:
  • Slack: #release-management
• Meetings:
  • Release Engineering: Tuesdays at 14:30 UTC (biweekly). Convert to your timezone.
    • Meeting notes and Agenda.
    • Meeting recordings.

Release Team

The Kubernetes Release Team is responsible for the day-to-day work required to successfully create releases of Kubernetes.

• Owners:
  • kubernetes/sig-release/release-team

SIG Release Process Documentation

Documents and processes related to SIG Release

• Owners:
  • kubernetes/sig-release

hyperkube

Best-effort maintaining of hyperkube until 1.18 goes EOL 2021-04-30.

• Owners:
  • kubernetes/kubernetes/cluster/images/hyperkube
  • kubernetes/release/images/build/debian-hyperkube-base

kubernetes/repo-infra

Creates and maintains tools and templates for Kubernetes org repositories. Includes bazel tooling for managing dependencies for kubernetes/kubernetes and kubernetes/test-infra.

• Owners:
  • kubernetes/repo-infra

---

The canonical location for SIG Release information is k/sig-release.