-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Create a bug/triage checklist #3215
Copy link
Copy link
Open
Labels
A-metaArea: meta (the hyper project itself)Area: meta (the hyper project itself)B-rfcBlocked: More comments would be useful in determine next steps.Blocked: More comments would be useful in determine next steps.
Metadata
Metadata
Assignees
Labels
A-metaArea: meta (the hyper project itself)Area: meta (the hyper project itself)B-rfcBlocked: More comments would be useful in determine next steps.Blocked: More comments would be useful in determine next steps.
Type
Fields
Give feedbackNo fields configured for issues without a type.
This is an action item of the COE on hyper's surprise CVE:
Making sure the checklist is complete would be part of the routine decided on in #3214.
If I just take the headlines from the triager's guide, they would be this:
I think there's a need to fill in a few more items for step 2, "Ask for more info".
There's also a question of how to make sure we complete the checklist for each bug report. One idea I had was to setup an autoresponder bot which includes the checklist in markdown checkbox form. Then the first comment would always have it, and triagers should have "edit" permissions which would be required to check them off.