Posts: 1,469
Threads: 57
Joined: Jul 2012
Thanks: 66
Given 127 thank(s) in 108 post(s)
Labelling "bug", "feature request", etc is completely useless. We did that before and found it to be no help at all.
I think what we should have as labels are:
critical/crash bugs
major area (redstone, worldgen, mobs, protocol etc)
easy issues
proposal
Minor areas of the code should be added as milestones rather than labels (e.g. performance, check if 1.9 only, configuration)
Posts: 721
Threads: 77
Joined: Apr 2014
Thanks: 113
Given 130 thank(s) in 91 post(s)
Which is why I think e.g. "AI" is a bad milestone. We already have the label.
"Implement all Vanilla mobs" would have been a good milestone, but in practice we have the "mob progress" post.
Posts: 721
Threads: 77
Joined: Apr 2014
Thanks: 113
Given 130 thank(s) in 91 post(s)
The current coloring is like this:
Blue - "visible" - Labels that directly impact gameplay, e.g. achievements, entities, generator.
Yellow - "hidden" - Labels that involve internals and are not as visible to players as above. e.g. storage, protocol.
Pink - "poweruser" - Labels that are relevant to admins, devs, and plugin devs. e.g. docs, lua api, configuration..
Cyan - "meta" - Labels that talk about the issues. e.g. needs-confirm, proposal, question
Green is for things suitable for newbies (namely "easy" and "ingame-testing-needed").
Red is for high priority things (namely "crash" and "important").
Posts: 1,469
Threads: 57
Joined: Jul 2012
Thanks: 66
Given 127 thank(s) in 108 post(s)
LogicParrot, I agree with most of your labels and the system is sensible, I simply feel there are too many. If we removed some that only had 1/2 issues in them, then it would be cleaner but would not significantly affect anything.