Kubernetes Release: Adding Issues and PRs to Milestones and Required Labels

might be a large piece of work described in a [KEP][keps], with associated task issues in GitHub. When the plan has reached an implementable state and work is underway, the enhancement or parts thereof are targeted for an upcoming milestone by creating GitHub issues and marking them with the Prow "/milestone" command. For the first ~4 weeks into the release cycle, the Release Team's Enhancements Lead will interact with SIGs and feature owners via GitHub, Slack, and SIG meetings to capture all required planning artifacts. If you have an enhancement to target for an upcoming release milestone, begin a conversation with your SIG leadership and with that release's Enhancements Lead. ### Issue additions Issues are marked as targeting a milestone via the Prow "/milestone" command. The Release Team's [Bug Triage Lead](https://git.k8s.io/sig-release/release-team/role-handbooks/bug-triage/README.md) and overall community watch incoming issues and triage them, as described in the contributor guide section on [issue triage](https://k8s.dev/docs/guide/issue-triage/). Marking issues with the milestone provides the community better visibility regarding when an issue was observed and by when the community feels it must be resolved. During [Code Freeze][code-freeze], a milestone must be set to merge a PR. An open issue is no longer required for a PR, but open issues and associated PRs should have synchronized labels. For example a high priority bug issue might not have its associated PR merged if the PR is only marked as lower priority. ### PR Additions PRs are marked as targeting a milestone via the Prow "/milestone" command. This is a blocking requirement during Code Freeze as described above. ## Other Required Labels [Here is the list of labels and their use and purpose.](https://git.k8s.io/test-infra/label_sync/labels.md#labels-that-apply-to-all-repos-for-both-issues-and-prs) ### SIG Owner Label The SIG owner label defines the SIG to which we escalate if a milestone issue is languishing or needs additional attention. If there are no updates after escalation, the issue may be automatically removed from the milestone.

Enhancements are targeted for milestones by creating GitHub issues marked with the Prow "/milestone" command. The Enhancements Lead interacts with SIGs and feature owners to capture planning artifacts. Issues are also marked using the "/milestone" command and triaged by the Bug Triage Lead. Marking issues with a milestone provides visibility on observation and resolution timelines, becoming mandatory during Code Freeze for PR merges. PRs are marked as targeting a milestone via the Prow "/milestone" command. PRs must have a milestone to be merged during Code Freeze. The SIG owner label indicates which SIG to escalate to if a milestone issue is unresolved.