Sig-release: process docu: release team Bug Triage Lead

[AishSundar]

Bug triage has been super active and under went quite a bit of revamp in 1.12 cycle, mainly due to killing munger and retiring a few labels. opening this tracking bug to ensure all the changes are captured as part of the Bug triage lead handbook in time for 1.13 cycle. @guineveresaenger I know you have been on top of keeping the doc updated. If there are no more pending updates feel free to close this issue.

/assign @guineveresaenger
/cc @tpepper @nikopen
/sig release
/milestone v1.13

[guineveresaenger]

Trying to come up with a way to empower the bug triage lead to require pull requests to be labeled with kind/bug for early triage of things that don’t have an associated issue.
Honestly this sounds like a PR template concern.

I’ll mull it over and see what, if anything, should change in the handbook.

[AishSundar]

Thanks @guineveresaenger. I see that /kind is a required label throughout the release cycle. so I am curious what are folks assigning kind to if the PR is not for a feature? are you seeing other values like "failing-test", "flaky-test" etc?

[guineveresaenger]

@AishSundar I see kind/cleanup, kind/api-change, also king/bug but also a lot of needs-kind which is because folks are not sure if a "bugfix" should be labeled as "kind/bug" so it makes it harder to discover.

[guineveresaenger]

Basically, I'd suggest 2 things:

1. add notes to bug triage handbook to mark bug fixes as kind-bug early on; I can make a PR to that effect

2. some kind of education across sigs (in pr template? what does that look like? is there a PR template?) to put in kind/bug

[AishSundar]

Thanks @guineveresaenger, we should definitely do 1. Also probably link to https://github.com/kubernetes/community/blob/master/contributors/devel/release.md#issue-kind-label

For 2, here's the PR template if you want to update it with some useful label etiquettes.

As discussed offline in slack, please also add the process to ping RT lead to be added to milestone maintainer privileges.

[guineveresaenger]

@AishSundar - opened a PR for the pull request template. ^^

[guineveresaenger]

@AishSundar - this can be closed as both tasks are (finally!) done. :)

[AishSundar]

Thanks a lot for keeping at this @guineveresaenger. @nikopen as FYI.

/close

[k8s-ci-robot]

@AishSundar: Closing this issue.

In response to this:

Thanks a lot for keeping at this @guineveresaenger. @nikopen as FYI.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.