-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Issue Triage Workflow and Automation #1553
Copy link
Copy link
Closed
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.Categorizes an issue or PR as relevant to SIG Contributor Experience.sig/releaseCategorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Release.tracked/out-of-treeDenotes an out-of-tree enhancement issue, which does not need to be tracked by the Release TeamDenotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team
Milestone
Description
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.Categorizes an issue or PR as relevant to SIG Contributor Experience.sig/releaseCategorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Release.tracked/out-of-treeDenotes an out-of-tree enhancement issue, which does not need to be tracked by the Release TeamDenotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team
Type
Fields
No fields configured for issues without a type.
Issue Triage Workflow and Automation
kubernetes/kubernetesby defining a workflow and automation for contributors(I'm not sure if this needs to be officially tracked by the @kubernetes/release-team, but given that the process improvement will affect issues in k/k and transitively, the team, it might make sense)
/assign
/milestone v1.18
/priority important-soon
/kind feature
/sig contributor-experience pm release
cc: @kubernetes/sig-release-admins
ref: