Open pganssle opened 5 years ago
Since the sprints are in a week, I'm going to go ahead with this scheme so we can start classifying tickets. If we decide to tweak it later hopefully it won't be too difficult to undo (or maybe we can write a script to do it).
:+1:
I've written a little bot to backfill most issues with "Needs Triage".
Some of them probably have already been triaged in some way, but I'll start manually cleaning them up based on some heuristics.
In advance of the PyPA sprint at the end of the month, I'd like to go through and do some issue labeling so we can more easily navigate the existing issues and see what work is to be done.
Looking at the issues, I think what we need most is a good indicator of what the status of a current bug is. I'm thinking we should use something like the following nomenclature:
[Needs Triage]
: Issues that have not yet been classified[Needs Repro]
: Issues that have not yet been consistently reproduced[Needs Discussion]
: Issues where a general course of action has not yet been determined[Needs Implementation]
: Issues where we know generally what to do, but there's no PR yetI have not yet used a classification system exactly like this, but this feels like a good start to me.
Before I start labeling every existing issue, I thought I'd run it up the flagpole. Thoughts @benoit-pierre @jaraco?