W3C home > Mailing lists > Public > public-w3process@w3.org > February 2019

Re: Label, project, or milestone

From: Karl Dubost <karl@la-grange.net>
Date: Fri, 15 Feb 2019 09:14:36 +0900
Cc: public-w3process <public-w3process@w3.org>
Message-Id: <3E03575B-B98D-4A55-A944-C065DB6A95C9@la-grange.net>
To: Florian Rivoal <florian@rivoal.net>


Le 14 févr. 2019 à 01:28, Florian Rivoal <florian@rivoal.net> a écrit :
> Does anyone want to defend the use of Labels for this kind of triaging?


My two cents on using milestones and labels.
On the webcompat.com project [1], we are using GitHub as a backend [2] and indeed labels and milestones for categorising.


Here a way to think about it:


* labels == class values in HTML
  You can assign multiple labels to an issue. 

* milestone == id value in HTML.
  You can assign only ONE milestone to an issue. An issue can only be in one milestone at a time.


On webcompat.com, we assign a milestone for the phase the issue is in, it moves from 

1. needstriage 
2. needsdiagnosis
3. needscontact
4. contactready
5. sitewait

then a list of "closed" status milestones like duplicate, fixed, etc.
The issue can only be in one stage at a time.
The labels on the other hand are things like browser-* type-* etc.
 

Hope it helps. 


[1]: https://webcompat.com/
[2]: https://github.com/webcompat/web-bugs/issues


-- 
Karl Dubost 🐄
http://www.la-grange.net/karl/
Received on Friday, 15 February 2019 00:15:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:51:49 UTC