Responsibilities of Release Managers, GitHub Access, Current Members, and How to Become One

- Coordinating and cutting Kubernetes releases: - Patch releases (`x.y.z`, where `z` > 0) - Minor releases (`x.y.z`, where `z` = 0) - Pre-releases (alpha, beta, and release candidates) - Working with the [Release Team][release-team] through each release cycle - Setting the [schedule and cadence for patch releases][patches] - Maintaining the release branches: - Reviewing cherry picks - Ensuring the release branch stays healthy and that no unintended patch gets merged - Mentoring the [Release Manager Associates](#release-manager-associates) group - Actively developing features and maintaining the code in k/release - Supporting Release Manager Associates and contributors through actively participating in the Buddy program - Check in monthly with Associates and delegate tasks, empower them to cut releases, and mentor - Being available to support Associates in onboarding new contributors e.g., answering questions and suggesting appropriate work for them to do This team at times works in close conjunction with the [Security Response Committee][src] and therefore should abide by the guidelines set forth in the [Security Release Process][security-release-process]. GitHub Access Controls: [@kubernetes/release-managers](https://github.com/orgs/kubernetes/teams/release-managers) GitHub Mentions: @kubernetes/release-engineering - Adolfo García Veytia ([@puerco](https://github.com/puerco)) - Cici Huang ([@cici37](https://github.com/cici37)) - Carlos Panato ([@cpanato](https://github.com/cpanato)) - Jeremy Rickard ([@jeremyrickard](https://github.com/jeremyrickard)) - Marko Mudrinić ([@xmudrii](https://github.com/xmudrii)) - Nabarun Pal ([@palnabarun](https://github.com/palnabarun)) - Sascha Grunert ([@saschagrunert](https://github.com/saschagrunert)) - Stephen Augustus ([@justaugustus](https://github.com/justaugustus)) - Verónica López ([@verolop](https://github.com/verolop)) ### Becoming a Release Manager To become a Release Manager, one must first serve as a Release Manager Associate. Associates graduate to Release Manager by actively working on releases over several cycles and: - demonstrating the willingness to lead - tag-teaming with Release Managers on patches, to eventually cut a release independently - because releases have a limiting function, we also consider substantial contributions to image promotion and other core Release Engineering tasks - questioning how Associates work, suggesting improvements, gathering feedback, and driving change - being reliable and responsive - leaning into advanced work that requires Release Manager-level access and privileges to complete ## Release Manager Associates Release Manager Associates are apprentices to the Release Managers, formerly referred to as Release Manager shadows. They are responsible for: - Patch release work, cherry pick review - Contributing to k/release: updating dependencies and getting used to the

This section details the responsibilities of Release Managers, including coordinating releases, maintaining release branches, mentoring associates, and developing features. It highlights collaboration with the Security Response Committee and adherence to the Security Release Process. It lists the current members of the Release Manager team with their GitHub handles and provides guidelines on how to become a Release Manager, emphasizing leadership, independent release cutting, suggesting improvements, reliability, and advanced work.