github severity labels

[Andrei Matei]

Yoz,

I've created unqualified issue severity labels:
S-0 Urgent priority

S-1 High priority

S-2 Normal priority

S-3 Low priority
(maybe there should also be a S-4 Don't bother me ?)

This is analogous to the common set of "priority" labels that all the bug trackers I've seen have.
The new labels are in addition to the proliferation of more qualified S labels like S-0-visible-logical-error. I, for one, consider those harmful because it's not clear how they relate to the A(rea) labels, they almost never match what I want in any given situation, and generally they force you into combinations of orthogonal things (e.g. should we have both a S-0-corruption-or-data-loss and an S-2-corruption-or-data-loss?). I wish they were gone, but I'll let someone else do it (and I assume that if one is delete it we'd have to manually reassign or the issues that were already tagged).

Any opinions?

- a_m

[Jordan Lewis]

Andrei, Tim and I have a work in progress document that recommends something similar. Perhaps you could hold off on using those too much until Tim finalizes that proposal and sends it out. 

I have a tool that can move issues from one label to another, so once we're all agreed on this, we can utilize it.

--
You received this message because you are subscribed to the Google Groups "CockroachDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cockroach-db...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cockroach-db/CAPqkKgnUmcjLnRmCqB6TAW7uweTX9%3DqDzu27jfwzrYa8nnJ3Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.