Re: AW: Confirmed bug labels

On 29/10/2019 12:34, Matt Caswell wrote: > > > On 29/10/2019 12:24, Matthias St. Pierre wrote: >> >> It might be useful to add more reasons for why the issue is resolved. >> OTOH we should watch out that we don't create too many labels. >> >>     "resolved: fixed" >>     "resolved: answered" >

Re: AW: Confirmed bug labels

I decided to change the 'issue: *' colors to a more 'yelling' cyan color making the untriaged issues more prominent, and use the more relaxed blue color for the 'triaged: *' labels instead. Also added an 'unresolved' label. Matthias On 29.10.19 13:38, Matt Caswell wrote: On 29/10/2019 12:37,

Re: AW: Confirmed bug labels

On 29.10.19 13:34, Matt Caswell wrote:     ... For the unresolved issues, an 'unresolved: *' label makes sense:     "unresolved: " Possible reasons for marking something as unresolved: - The question is stale - no activity for a prolonged period - Off topic - the question is about some

Re: AW: Confirmed bug labels

On 29/10/2019 12:37, Matthias St. Pierre wrote: > The 'unresolved: *' labels could carry the same grey color as the > 'resolved: *' labels. > For the 'triaged: *' labels we need a new color. I can make a suggestion... Please do! Matt

Re: AW: Confirmed bug labels

The 'unresolved: *' labels could carry the same grey color as the 'resolved: *' labels. For the 'triaged: *' labels we need a new color. I can make a suggestion... Matthias

Re: AW: Confirmed bug labels

On 29/10/2019 12:24, Matthias St. Pierre wrote: > > > On 29.10.19 13:14, Matt Caswell wrote: >> Do we just need "triaged: bug" and "triaged: feature"? Or should we also >> have "triaged: documentation" and "triaged: question" (so that there is >> one for every corresponding "issue" label)? >

Re: AW: Confirmed bug labels

On 29.10.19 13:14, Matt Caswell wrote: Do we just need "triaged: bug" and "triaged: feature"? Or should we also have "triaged: documentation" and "triaged: question" (so that there is one for every corresponding "issue" label)? Yes, that makes sense. Then it is assured that the 'issue: *' la

Re: Confirmed bug labels

What about "proposed bug" "proposed feature" etc. And a single "accepted" label?

Re: AW: Confirmed bug labels

efix: > > 'bug' > 'feature' > etc. > > Matthias > >> -Ursprüngliche Nachricht- >> Von: openssl-project Im Auftrag von >> Matt Caswell >> Gesendet: Dienstag, 29. Oktober 2019 10:23 >> An: openssl-pro

Re: Confirmed bug labels

We try to group the labels into categories using prefixes, see https://github.com/openssl/openssl/labels and my initial post https://mta.openssl.org/pipermail/openssl-project/2019-October/001593.html Note that the 'issue: *' labels are automatically

Re: AW: Confirmed bug labels

Our replies overlapped. 'resolved: *' is even better than 'triaged: *'. On 29.10.19 12:57, Matthias St. Pierre wrote: Another idea just occurred to me: we could join the 'closed: *' labels with the 'triaged: *' labels:     triaged: duplicate     triaged: not a bug     triaged: wont fix

Re: AW: Confirmed bug labels

On 29/10/2019 11:53, Matthias St. Pierre wrote: > > > On 29.10.19 12:41, Matt Caswell wrote: >> >> On 29/10/2019 11:34, Dr. Matthias St. Pierre wrote: >>> A similar problem applies to 'issue: feature request'.  Just having a >>> 'confirmed' label for bugs >>> wouldn't help in that case. >>> >>

Re: AW: Confirmed bug labels

Another idea just occurred to me: we could join the 'closed: *' labels with the 'triaged: *' labels:     triaged: duplicate     triaged: not a bug     triaged: wont fix On 29.10.19 12:53, Matthias St. Pierre wrote: On 29.10.19 12:41, Matt Caswell wrote: On 29/10/2019 11:34, Dr. Matthias S

Re: AW: Confirmed bug labels

On 29.10.19 12:41, Matt Caswell wrote: On 29/10/2019 11:34, Dr. Matthias St. Pierre wrote: A similar problem applies to 'issue: feature request'. Just having a 'confirmed' label for bugs wouldn't help in that case. So what do you think about adding a new 'triaged: *' family of labels, in

Re: AW: Confirmed bug labels

or example we might want to label something as "not a bug" but leave it open for a little while to allow the reporter to respond or argue why it really should be treated as a bug. Similarly with "wont fix" and maybe even "duplicate". Matt > > Matthias > >>

AW: Confirmed bug labels

swell > Gesendet: Dienstag, 29. Oktober 2019 10:23 > An: openssl-project@openssl.org > Betreff: Confirmed bug labels > > Do we need a "confirmed bug" or similar label? I was looking at #10283 > which is labelled with "issue: bug report". But this only tells us

Confirmed bug labels

Do we need a "confirmed bug" or similar label? I was looking at #10283 which is labelled with "issue: bug report". But this only tells us that the reporter thought it was a bug. I wanted to add a label confirming that it really is a bug...but nothing suitable seems to be there. Matt