554196a4f9
SIG Release Annual Report 2024 |
||
|---|---|---|
| .. | ||
| meeting-notes-archive | ||
| OWNERS | ||
| README.md | ||
| annual-report-2020.md | ||
| annual-report-2021.md | ||
| annual-report-2022.md | ||
| annual-report-2023.md | ||
| annual-report-2024.md | ||
| charter.md | ||
README.md
Release Special Interest Group
Ensure quality Kubernetes releases
The charter defines the scope and governance of the Release Special Interest Group.
Meetings
Joining the mailing list for the group will typically add invites for the following meetings to your calendar.
- Regular SIG Meeting APAC/EU Oriented Time: Tuesdays at 14:30 UTC (biweekly). Convert to your timezone.
- Regular SIG Meeting US Oriented Time: Tuesdays at 17:00 UTC (biweekly). Convert to your timezone.
Leadership
Chairs
The Chairs of the SIG run operations and processes governing the SIG.
- Jeremy Rickard (@jeremyrickard), Microsoft
- Stephen Augustus (@justaugustus), Bloomberg
- 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.
- Verónica López (@Verolop), AuthZed
- Carlos Tadeu Panato Jr. (@cpanato), Chainguard, Inc
- Adolfo García Veytia (@puerco), Stacklok
Emeritus Leads
- Jorge Alarcon Ochoa (@alejandrox1)
- Caleb Miles (@calebamiles)
- Daniel Mangum (@hasheddan)
- Jaice Singer DuMars (@jdumars)
- Tim Pepper (@tpepper)
Contact
- Slack: #sig-release
- Mailing list
- Open Community Issues/PRs
- GitHub Teams:
- @kubernetes/milestone-maintainers - Milestone Maintainers
- @kubernetes/sig-release - SIG Release Members
- @kubernetes/sig-release-admins - Admins for SIG Release repositories
- @kubernetes/sig-release-leads - Chairs, Technical Leads, and Program Managers for SIG Release
- Steering Committee Liaison: Sascha Grunert (@saschagrunert)
Working Groups
The following working groups are sponsored by sig-release:
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.
- Leads:
- Marko Mudrinić (@xmudrii), Kubermatic
- Owners:
- kubernetes-sigs/bom
- kubernetes-sigs/downloadkubernetes
- kubernetes-sigs/mdtoc
- kubernetes-sigs/obscli
- kubernetes-sigs/promo-tools
- kubernetes-sigs/release-actions
- kubernetes-sigs/release-notes
- kubernetes-sigs/release-sdk
- kubernetes-sigs/release-utils
- kubernetes-sigs/tejolote
- kubernetes-sigs/testgrid-json-exporter
- kubernetes-sigs/zeitgeist
- kubernetes/kubernetes/CHANGELOG
- kubernetes/kubernetes/build/build-image
- kubernetes/kubernetes/staging/publishing
- kubernetes/publishing-bot
- kubernetes/release
- kubernetes/repo-infra
- kubernetes/sig-release/release-engineering
- kubernetes/website/content/en/releases
- kubernetes/website/data/releases
- Contact:
Release Team
The Kubernetes Release Team is responsible for the day-to-day work required to successfully create releases of Kubernetes.
- Leads:
- Grace Nguyen (@gracenng), Notion
- Kat Cosgrove (@katcosgrove), Independent
- Owners:
- Contact:
- Mailing List
- GitHub Teams:
- @kubernetes/release-ci-signal
- @kubernetes/release-team - Members of the current Release Team and subproject owners
- @kubernetes/release-team-bug-triage
- @kubernetes/release-team-comms
- @kubernetes/release-team-docs
- @kubernetes/release-team-enhancements
- @kubernetes/release-team-leads - Release Team Leads for the current Kubernetes release cycle
- @kubernetes/release-team-release-notes
SIG Release Process Documentation
Documents and processes related to SIG Release
- Owners:
The canonical location for SIG Release information is kubernetes/sig-release.