Defining the Kubernetes release cadence

[justaugustus]

Enhancement Description

• One-line enhancement description (can be used as a release note): Defining the Kubernetes release cadence
• Kubernetes Enhancement Proposal: sig-release: Add release cadence KEP #2567
• Discussion Link: Discussing/modifying the kubernetes/kubernetes release cadence sig-release#1290
• Primary contact (assignee): @justaugustus
• Responsible SIG: SIG Release
• Participating SIGs: SIG Architecture, SIG Testing
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.22
  • Beta release target (x.y): 1.23
  • Stable release target (x.y): 1.25
• Alpha
  • KEP (k/enhancements) update PR(s): sig-release: Add release cadence KEP #2567
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

/milestone v1.21
/stage alpha

[spiffxp]

/sig architecture testing
participating sigs

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale