Let's get rid of UNCONFIRMED/CONFIRMED

[Boudewijn Rempt]

On Wednesday, 28 February 2018 11:01:22 CET Luigi Toscano wrote:

> I disagree and I think it makes sense as keyword, as general attribute of
> the bug (something happened according a triaging process). It is a modifier
> of the "NEW"/initial state that is brought around later.

Yours is, of course, a possible opinion. It's just that the triaged keyword 
does not help me deal with my bug reports, I've tried. It does not aid my 
workflow. 

The only thing I've tried in this discussion and in the previous one is to 
make clear what would help me; I don't think my proposals would hamper anyone 
else's workflow either. Nothing in this or the previous discussion would help 
me. NEW instead of UNCONFIRMED? Meh, it's bikeshedding. Keyword instead of 
status for whatever reason? Meh. I don't care about what anyone feels makes 
sense if it doesn't help fix the workflow.

So, go ahead, s/UNCONFIRMED/NEW/ -- keep the rest the rest, and we'll see. I 
bet that in a couple of years, someone will have highly logical reasons to 
once more s/NEW/UNCONFIRMED/ and we'll go back, and someone will feel they 
have made an Important Improvement.

As you asked in your original mail in 2016, "what do you think" -- well, this 
is what I think. Though I'd be interested what, out of last year's top-ten bug 
wranglers in our bugzilla, others than the numbers 4, 5, 7 and 10 think. They 
haven't weighed in yet.

-- 
Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org