Regression on Github labels
#2
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)
Reply
Thanks given by:


Messages In This Thread
Regression on Github labels - by sphinxc0re - 05-16-2016, 08:41 AM
RE: Regression on Github labels - by bearbin - 05-16-2016, 05:33 PM
RE: Regression on Github labels - by xoft - 05-17-2016, 04:40 AM
RE: Regression on Github labels - by sphinxc0re - 05-17-2016, 04:51 AM
RE: Regression on Github labels - by xoft - 05-17-2016, 04:55 AM
RE: Regression on Github labels - by LogicParrot - 05-18-2016, 08:30 PM
RE: Regression on Github labels - by LogicParrot - 05-18-2016, 08:39 PM
RE: Regression on Github labels - by LogicParrot - 05-18-2016, 08:48 PM
RE: Regression on Github labels - by LogicParrot - 05-18-2016, 10:10 PM
RE: Regression on Github labels - by bearbin - 05-19-2016, 05:24 PM
RE: Regression on Github labels - by LogicParrot - 05-19-2016, 08:41 PM
RE: Regression on Github labels - by tigerw - 05-25-2016, 02:08 AM



Users browsing this thread: 1 Guest(s)