Updating documentation: Post 1.29 Enhancements Role Handbook Updates

[npolshakova]

Umbrella issue to improve the Enhancements Role Handbook to clarify some things that have been points of confusion in this (and previous) releases.

• Add a reference to clarify what “PRR Freeze” means to handbook
  - Link this email from PRR team in our Enhancements handbook (maybe in the outreach templates)
  - PRR freeze has always been a soft deadline due to a limited PRR reviewers handling multiple KEPs, making it tough to finish all reviews by the deadline
  - notify people in #prod-readiness about KEPs waiting for PRR reviews since the enhancement freeze is coming up next week with project board filter with KEPs missing PRR assignee
  - Clarified PRR freeze and exceptions.yaml in enhancements handbook #2518
• Add section to clarify test freeze in the enhancements handbook
  - What is the test freeze
  - Clarify code freeze checks
• Add clarification for KEPs with only bug fixes going into release are fine to mark as tracked for code freeze for the purposes of enhancements tracking.
• Add instructions to help Comms team compile the major themes to handbook
• Add guidelines for creating new Project Board from template in Github
  - If we need additional automation that’s more declarative, Mark started this PR a while back that we can revisit: WIP - Script to create new project baords marosset/sig-release#1
• Add instructions for enabling/disabling test-infra job that does enhancement collection based on lead-opted-in label
  - Enable periodic enhancements sync for v1.29 test-infra#30528
  - Disable enhancements project board job for 1.29 Enhancement Freeze test-infra#30965
• Clarify code freeze cut offs in handbook (PRs must at least be approved by SIG reviewers and in the merge queue)
• Add example for exceptions.yaml file in the handbook

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue 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.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.

[sreeram-venkitesh]

/reopen

[k8s-ci-robot]

@sreeram-venkitesh: Reopened this issue.

In response to this:

/reopen

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-sigs/prow repository.

[sreeram-venkitesh]

/remove-lifecycle rotten

[sreeram-venkitesh]

/assign

[npolshakova]

Some of these were addressed in:

• f8f8820
• 98514a3

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[sreeram-venkitesh]

/remove-lifecycle stale

[sreeram-venkitesh]

@tjons I was cleaning up issues assigned to me in GitHub and came across this again. Wanted to ping you here. Feel free to share this with your shadows if they're interested in picking these up after code freeze :)