Kubernetes Release Cycle: Targeting Enhancements, Issues, and PRs

--- title: Kubernetes Release Cycle type: docs auto_generated: true ---  {{% pageinfo color="light" %}} This content is auto-generated and links may not function. The source of the document is located [here](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-release/release.md). {{% /pageinfo %}}  ## Targeting enhancements, Issues and PRs to Release Milestones This document is focused on Kubernetes developers and contributors who need to create an enhancement, issue, or pull request which targets a specific release milestone. - [TL;DR](#tldr) - [Normal Dev (Weeks 1-11)](#normal-dev-weeks-1-11) - [Code Freeze (Weeks 12-14)](#code-freeze-weeks-12-14) - [Post-Release (Weeks 14+)](#post-release-weeks-14+) - [Definitions](#definitions) - [The Release Cycle](#the-release-cycle) - [Removal Of Items From The Milestone](#removal-of-items-from-the-milestone) - [Adding An Item To The Milestone](#adding-an-item-to-the-milestone) - [Milestone Maintainers](#milestone-maintainers) - [Feature additions](#feature-additions) - [Issue additions](#issue-additions) - [PR Additions](#pr-additions) - [Other Required Labels](#other-required-labels) - [SIG Owner Label](#sig-owner-label) - [Priority Label](#priority-label) - [Issue/PR Kind Label](#issuepr-kind-label) The process for shepherding enhancements, issues, and pull requests into a Kubernetes release spans multiple stakeholders: - the enhancement, issue, and pull request owner(s) - SIG leadership - the [Release Team][release-team] Information on workflows and interactions are described below. As the owner of an enhancement, issue, or pull request (PR), it is your responsibility to ensure release milestone requirements are met. Automation and the Release Team will be in contact with you if updates are required, but inaction can result in your work being removed from the milestone. Additional requirements exist when the target milestone is a prior release (see [cherry pick process][cherry-picks] for more information). ## TL;DR If you want your PR to get merged, it needs the following required labels and milestones, represented here by the Prow /commands it would take to add them: ### Normal Dev (Weeks 1-11) - /sig {name} - /kind {type} - /lgtm - /approved ### [Code Freeze][code-freeze] (Weeks 12-14) - /milestone {v1.y} - /sig {name} - /kind {bug, failing-test} - /lgtm - /approved ### Post-Release (Weeks 14+) Return to 'Normal Dev' phase requirements: - /sig {name} - /kind {type} - /lgtm - /approved Merges into the 1.y branch are now [via cherry picks][cherry-picks], approved by [Release Managers][release-managers]. In the past, there was a requirement for a milestone-targeted pull requests to have an associated GitHub issue opened, but this is no longer the case. Features or enhancements are effectively GitHub issues or [KEPs][keps] which lead to subsequent PRs. The general labeling process should be consistent across artifact types. ## Definitions - *issue owners*: Creator, assignees, and user who moved the issue into a release milestone - *Release Team*: Each Kubernetes release has a team doing project management tasks described [here][release-team]. The contact info for the team associated with any given release can be found [here](https://git.k8s.io/sig-release/releases/). - *Y days*: Refers to business days - *enhancement*: see "[Is My Thing an Enhancement?](https://git.k8s.io/enhancements/README.md#is-my-thing-an-enhancement)" - *[Enhancements Freeze][enhancements-freeze]*: the deadline by which [KEPs][keps] have to be completed in order for enhancements to be part of the current release - *[Exception Request][exceptions]*: The process of requesting an extension on the deadline for a particular Enhancement - *[Code Freeze][code-freeze]*:

This document provides guidance for Kubernetes developers and contributors on how to target enhancements, issues, and pull requests to specific release milestones. It outlines the process for managing these items throughout the release cycle, including required labels, milestone maintainers, and the roles of different stakeholders like SIG leadership and the Release Team. The document also includes a TL;DR section summarizing the requirements for merging PRs during different phases of the release cycle (Normal Dev, Code Freeze, and Post-Release) and defines key terms related to the Kubernetes release process.