Ensure quality Kubernetes releases
The charter defines the scope and governance of the Release Special Interest Group.
- Regular SIG Meeting: Mondays at 15:00 UTC (biweekly). Convert to your timezone.
The Chairs of the SIG run operations and processes governing the SIG.
- Caleb Miles (@calebamiles), Google
- Stephen Augustus (@justaugustus), VMware
- Tim Pepper (@tpepper), VMware
- Jaice Singer DuMars (@jdumars)
- Slack: #sig-release
- Mailing list
- Open Community Issues/PRs
- GitHub Teams:
- @kubernetes/kubernetes-milestone-maintainers - Milestone Maintainers
- @kubernetes/kubernetes-release-managers - Release Managers
- @kubernetes/sig-release - SIG Release Members
- @kubernetes/sig-release-admins - Admins for SIG Release repositories
The following subprojects are owned by sig-release:
- Owners:
The Licensing subproject is responsible for analyzing/reporting/remediating licensing concerns within the Kubernetes project orgs.
The Release Engineering subproject is responsible for the process/procedures and tools used to create/maintain Kubernetes release artifacts.
- Owners:
- https://raw.githubusercontent.com/kubernetes-sigs/k8s-container-image-promoter/master/OWNERS
- https://raw.githubusercontent.com/kubernetes-sigs/release-notes/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/publishing-bot/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/release/master/OWNERS
- https://raw.githubusercontent.com/kubernetes/sig-release/master/release-engineering/OWNERS
- Contact:
- Slack: #release-management
- Meetings:
- Regular SIG Meeting: Mondays at 15:00 UTC (biweekly). Convert to your timezone.
The Kubernetes Release Team is responsible for the day-to-day work required to successfully create releases of Kubernetes.
Documents and processes related to SIG Release
The canonical location for SIG Release information is k/sig-release.