Skip to content

k/e: Streamline Issue Template #5124

Open
@kikisdeliveryservice

Description

The current issue template contains fields that are not longer strictly necessary due to the release team's usage of the project boards and has information that tends to go stale. The staleness generally happens when the original author no longer works on the issue and the new author is unable to edit it. This causes friction and stale data in the description.

Potential fields targeted for removal as they tend to change/go stale during an enhancement's lifetime:

  • Primary contact (assignee):
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y):
    • Beta release target (x.y):
    • Stable release target (x.y):
  • Alpha
    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (k/website) update PR(s):
  • Beta
    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (k/website) update(s):
  • Stable
    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (k/website) update(s):

Goals:

  • review and streamline the current issue fields
  • make it easier for a new contributor to take over an existing issue fully
  • ensure that changes cause no regressions to the Release Team's work

Target: 1.34

Metadata

Labels

area/enhancementsIssues or PRs related to the Enhancements subprojectsig/architectureCategorizes an issue or PR as relevant to SIG Architecture.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions