You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a triage guide for bug reports, which is a good thing. But that doesn’t mean everyone (me included!) always remembers all the steps. Checklists are famous in aviation and medicine for their effectiveness in saving lives. They can also help us make sure all issues are treated properly.
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:
Acknowledge
Ask for more info
Categorize
Adjust the title
Mentor
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.
The text was updated successfully, but these errors were encountered:
seanmonstar
added
B-rfc
Blocked: More comments would be useful in determine next steps.
A-meta
Area: meta (the hyper project itself)
labels
Apr 28, 2023
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.
The text was updated successfully, but these errors were encountered: