-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
CI Use "Bug: triage" label for user reports #16560
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.
thanks @rth . Have you already added the "Bug: triage" label to the list of labels?
Yes, I did. The only thing is that the label is |
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.
I'm happy with this, but wonder if "Triage" is sufficient?
Triage sounded a bit more neutral than "Bug: unconfirmed", but I'm open to suggestions for a better label name. |
What about "Potential Bug"? |
For me "potential" suggests that it can evolve into an actual bug (https://www.merriam-webster.com/dictionary/potential). While the situation is rather that it's a bug or not and someone need to confirm it, I wouldn't mind having some indication of action of "confirmation required" in the name. |
OK so I'm +1 with triage
…On Thu, 27 Feb 2020 at 17:21, Roman Yurchak ***@***.***> wrote:
What about "Potential Bug"?
For me "potential" suggests that it can evolve into an actual bug (
https://www.merriam-webster.com/dictionary/potential). While the
situation is rather that it's a bug or not and someone need to confirm it,
I wouldn't mind having some indication of action of "confirmation required"
in the name.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#16560?email_source=notifications&email_token=ABY32P5M3AXGTN3N5CKAYLTRE7SBPA5CNFSM4K4Y5GN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENE6XNI#issuecomment-592047029>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABY32P2LNAHUQK6SH6W3A5LRE7SBPANCNFSM4K4Y5GNQ>
.
--
Guillaume Lemaitre
Scikit-learn @ Inria Foundation
https://glemaitre.github.io/
|
To be sure before merging, do we have the tag created already (which should probably make it an orange color :)) |
Yes we have it. It's orangish https://github.com/scikit-learn/scikit-learn/labels :) |
With the introduction of issues templates, new reports of defects have a "Bug" label, while in a number of cases it's not a bug but rather a user question, an intended behaviour etc. This makes the "Bug" label not very reliable or useful.
I propose to use instead the "Bug: triage" label for new bug reports, which can then be changed to "Bug" once it's confirmed. There may be a way to automate that.