Release Managers is an umbrella term that encompasses the set of Kubernetes contributors responsible for maintaining release branches, tagging releases, and building/packaging Kubernetes.
The responsibilities of each role are described below.
- Contact
- Handbooks
- Patch Release Team
- Branch Managers
- Associates
- Build Admins
- SIG Release Chairs
- GCP IAM Groups
| Mailing List | Slack | Visibility | Usage | Membership |
|---|---|---|---|---|
| release-managers@kubernetes.io | #release-management (channel) / @release-managers (user group) | Public | Public discussion for Release Managers | All Release Managers (Patch Release Team, Branch Managers, Associates, Build Admins, SIG Chairs) |
| release-managers-private@kubernetes.io | #release-private | Private | Private discussion for privileged Release Managers | Patch Release Team, Branch Managers, SIG Chairs |
| security-release-team@kubernetes.io | N/A | Private | Security release coordination with the Product Security Committee | security-discuss-private@kubernetes.io, release-managers-private@kubernetes.io |
The Patch Release Team is responsible for coordinating patch releases (x.y.z, where z > 0) of Kubernetes.
This team at times works in close conjunction with the Product Security Committee and therefore should abide by the guidelines set forth in the Security Release Process.
GitHub Access Controls: @kubernetes/release-managers
GitHub Mentions: @kubernetes/patch-release-team
- Aleksandra Malinowska (@aleksandra-malinowska)
- Doug MacEachern (@dougm)
- Hannes Hörl (@hoegaarden)
- Pengfei Ni (@feiskyer)
- Stephen Augustus (@justaugustus)
- Tim Pepper (@tpepper)
- Yang Li (@idealhack)
Branch Managers are responsible for minor releases (x.y.z, where z = 0) of Kubernetes, working with the Release Team through each release cycle.
This team at times works in close conjunction with the Product Security Committee and therefore should abide by the guidelines set forth in the Security Release Process.
- Carlos Panato (@cpanato)
- Sascha Grunert (@saschagrunert)
Release Manager Associates are apprentices to the Branch Managers, formerly referred to as Branch Manager shadows.
- Ace Eldeib (@alexeldeib)
- Kendrick Coleman (@kacole2)
- Seth McCombs (@sethmccombs)
- Marko Mudrinić (@xmudrii)
- Taylor Dolezal (@onlydole)
- Paul Bouwer (@paulbouwer)
- Jim Angel (@jimangel)
Build Admins are (currently) Google employees with the requisite access to Google build systems/tooling to publish deb/rpm packages on behalf of the Kubernetes project.
GitHub team: @kubernetes/build-admins
- Aleksandra Malinowska (@aleksandra-malinowska)
- Linus Arver (@listx)
- Premdeep Sharma (@ps882)
- Simon Yang (@simony-gke)
- Sumitran Raghunathan (@sumitranr)
SIG Release Chairs are responsible for the governance of SIG Release. They are mentioned explicitly here as they are owners of the various communications channels and permissions groups (GitHub teams, GCP access) for each role.
As such, they are highly privileged community members and privy to some private communications, which can at times relate to Kubernetes security disclosures.
GitHub team: @kubernetes/sig-release-admins
- Caleb Miles (@calebamiles)
- Stephen Augustus (@justaugustus)
- Tim Pepper (@tpepper)
The following kubernetes.io Google Groups exist to grant Release Managers access to k8s-infra GCP resources.
Mail to the groups below will be ignored. Please instead use the contact groups listed at the top of this document.
k8s-infra-release-adminsk8s-infra-release-editorsk8s-infra-release-viewers
Membership and permissions for each group is defined in kubernetes/k8s.io.
Past Branch Managers, can be found in the releases directory within release-x.y/release_team.md.
Example: 1.15 Release Team