-
Notifications
You must be signed in to change notification settings - Fork 519
Add support for kind/regression #1232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@saschagrunert -- I'm inclined to suggest that maybe regressions should have their own section instead of being bundled in Other
...
Thoughts @liggitt @tpepper @kubernetes/release-engineering?
/hold
I'd group fixed regressions under bugs in release notes. The distinction doesn't seem that important here. |
The new kind/regression will now be added to the "Other (...)" category as well. Signed-off-by: Sascha Grunert <[email protected]>
Alright, I merged "Bug" and "Regression" into a new section, ready for review again :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold for Stephen review as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, hasheddan, justaugustus, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
The new kind/regression will now be added to the "Other (...)" category
as well.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?