Kubernetes Release Managers: Roles, Responsibilities, and Contact Information

--- title: Release Managers type: docs --- "Release Managers" is an umbrella term that encompasses the set of Kubernetes contributors responsible for maintaining release branches and creating releases by using the tools SIG Release provides. The responsibilities of each role are described below. - [Contact](#contact) - [Security Embargo Policy](#security-embargo-policy) - [Handbooks](#handbooks) - [Release Managers](#release-managers) - [Becoming a Release Manager](#becoming-a-release-manager) - [Release Manager Associates](#release-manager-associates) - [Becoming a Release Manager Associate](#becoming-a-release-manager-associate) - [SIG Release Leads](#sig-release-leads) - [Chairs](#chairs) - [Technical Leads](#technical-leads) ## Contact | Mailing List | Slack | Visibility | Usage | Membership | | --- | --- | --- | --- | --- | | [release-managers@kubernetes.io](mailto:release-managers@kubernetes.io) | [#release-management](https://kubernetes.slack.com/messages/CJH2GBF7Y) (channel) / @release-managers (user group) | Public | Public discussion for Release Managers | All Release Managers (including Associates, and SIG Chairs) | | [release-managers-private@kubernetes.io](mailto:release-managers-private@kubernetes.io) | N/A | Private | Private discussion for privileged Release Managers | Release Managers, SIG Release leadership | | [security-release-team@kubernetes.io](mailto:security-release-team@kubernetes.io) | [#security-release-team](https://kubernetes.slack.com/archives/G0162T1RYHG) (channel) / @security-rel-team (user group) | Private | Security release coordination with the Security Response Committee | [security-discuss-private@kubernetes.io](mailto:security-discuss-private@kubernetes.io), [release-managers-private@kubernetes.io](mailto:release-managers-private@kubernetes.io) | ### Security Embargo Policy Some information about releases is subject to embargo and we have defined policy about how those embargoes are set. Please refer to the [Security Embargo Policy](https://github.com/kubernetes/committee-security-response/blob/main/private-distributors-list.md#embargo-policy) for more information. ## Handbooks **NOTE: The Patch Release Team and Branch Manager handbooks will be de-duplicated at a later date.** - [Patch Release Team][handbook-patch-release] - [Branch Managers][handbook-branch-mgmt] ## Release Managers **Note:** The documentation might refer to the Patch Release Team and the Branch Management role. Those two roles were consolidated into the Release Managers role. Minimum requirements for Release Managers and Release Manager Associates are: - Familiarity with basic Unix commands and able to debug shell scripts. - Familiarity with branched source code workflows via `git` and associated `git` command line invocations. - General knowledge of Google Cloud (Cloud Build and Cloud Storage). - Open to seeking help and communicating clearly. - Kubernetes Community [membership][community-membership] Release Managers are responsible for: - 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 section describes the roles and responsibilities of Kubernetes Release Managers and Release Manager Associates, who are responsible for maintaining release branches and creating releases. It includes contact information for communication and coordination, as well as minimum requirements for the roles. Release Managers coordinate and cut releases, maintain release branches, mentor associates, develop features, and support contributors. It also links to the Security Embargo Policy and handbooks for Patch Release Teams and Branch Managers.