Meta issue: Clarify the intent of the "Needs-Triage" label, notably with respect to "Issue-Enhancement", and use it consistently going forward. #19731
Labels
Issue-Discussion
the issue may not have a clear classification yet. The issue may generate an RFC or may be reclassif
Issue-Enhancement
the issue is more of a feature request than a bug
Needs-Triage
The issue is new and needs to be triaged by a work group.
Summary of the new feature / enhancement
The description of the Needs-Triage label currently reads:
However, the first act of triage comes before any working-group action: namely identifying which working group to assign, by using the appropriate
WG-*
label.One way of conceiving of "triage" is to consider this act of assigning a working-group alone as the act of triaging, which would imply that the "Needs-Triage" label should be removed once a "WG-*" label is assigned.
Another, extended way of conceiving of "triage" is to only consider it complete after an assigned working-group has jointly decided a feature request's fate, by either rejecting or accepting it, resulting in the appropriate labels getting assigned ("Resolution-Declined" (followed by closure) vs. "Up-for-Grabs", "RFC needed", ...), and that the "Needs-Triage" label should only be removed then.
Ideally - to avoid ambiguity - an automated process would ensure that the "Needs-Triage" label is removed when appropriate.
De facto, the use of "Needs-Triage" is inconsistent:
Among the feature requests whose fate has in effect not be decided, as of this writing 31 do have the "Needs-Triage" label, whereas 62 do not - see the two consecutive comments at #14013 (comment)
Additionally, some issues whose fate has been decided still have that label.
Is anyone paying attention to the 62 in the absence of "Needs-Triage"?
Therefore:
Proposed technical implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: