+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Development (https://forum.cuberite.org/forum-13.html)
+--- Thread: Regression on Github labels (/thread-2438.html)
Pages:
1
2
RE: Regression on Github labels - LogicParrot - 05-19-2016
There are many branches of Minecraft, and there are many labels accordingly. I don't see a problem with that. It helps make lookups faster.
The current amount of labels is more or less static, it shouldn't grow further.
I wouldn't want to remove barely populated labels. Being small doesn't make them undesired. e.g. looking up all achievement problems is still a valid lookup use case, even if there aren't many such problems currently.
Furthermore, some labels have few issues because, in part, we have a backlog of unlabeled issues.
I don't know, I like it, and it's useful
It's not like we're paying Github for each label. I did not zoom in to a boring resolution and do not intend to. I just had a label made for every major gameplay element and this is working nicely. At least, for me.
RE: Regression on Github labels - tigerw - 05-25-2016
Yes. And the list of labels looks colourful and pretty. me gusta mucho