Regression on Github labels
#1
I noticed that in the past month the amount of issue and PR labels has grown quite a lot. I don't know how everyone thinks about this but I find this amount of labels rather confusing. I also know that @xoft thinks the same way. So whay I'm suggesting is that we should think of a fixed set of labels that can help us determine bugs, feature requests, bugs that are critical and PRs that need to be tested. I also suggest to never remove nor add any label so that we can get familiar with the ones we are using. Labels are used to mark certain issues not to categorize them.

So what how do you guys think about this?
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: 3 Guest(s)