-
Notifications
You must be signed in to change notification settings - Fork 2.9k
prow: dev-release-note functionality #5843
Copy link
Copy link
Closed
Labels
area/jobsarea/prowIssues or PRs related to prowIssues or PRs related to prowkind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.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.
Description
Metadata
Metadata
Assignees
Labels
area/jobsarea/prowIssues or PRs related to prowIssues or PRs related to prowkind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.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.
sig-api-machinery are trying to improve the developer experience when building Kubernetes. We currently have a list of >100 PRs that do not specify release notes as they are solely developer facing changes, however this has caused many problems resulting in end users needing to look through recently merged PRs in order to work out how to fix their own code.
Ideally, there'd be some way for users to specify a 'developer' release note when writing PRs. After some discussion, @sttts suggested something along the lines of a new
dev-release-notetag that is optional for all PRs (in order to not require all users to specify a dev-release-note on existing PRs).Ideally we'd then have some kind of regex that matches directories, and enforces a dev-release-note for PRs that touch files matching the regex. It'd be possible to specify
NONEjust like with release-note still (for cases where it does not make sense to include a dev-release-note).Is this something that can be considered to be included in Prow, and have sig-testing got any thoughts on how this might/should look?
/cc @sttts @nikhita @BenTheElder @fejta @spiffxp