Release Team Roster

[JamesLaverack]

Enhancement Description

• One-line enhancement description (can be used as a release note): Refine the Kubernetes Release Team selection process to provide better steam stability.
• Kubernetes Enhancement Proposal: KEP-3344: Add Release Team Roster KEP #3347
• Discussion Link: Refine Release Team Selection Process sig-release#1714
• Primary contact (assignee): @JamesLaverack
• Responsible SIGs: SIG Release
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): N/A
  • Beta release target (x.y): N/A
  • Stable release target (x.y): 1.26
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-3344: Add Release Team Roster KEP #3347
  • Code (k/k) update PR(s): Not Applicable
  • 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.

/assign
/sig release
/kind kep
/priority important-soon
/cc @kubernetes/sig-release-leads

This is developed from a GitHub discussion, an in-person SIG Release meeting at the Contributor Summit at KubeCon Europe 2022, and a number of other discussions.

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[JamesLaverack]

After furter discussion and reflection, I don't think there's support for a stable roster in SIG Release or the wider community.

/close

[k8s-ci-robot]

@JamesLaverack: Closing this issue.

In response to this:

After furter discussion and reflection, I don't think there's support for a stable roster in SIG Release or the wider community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.