Re:Use native context menus on Mac OS
by marcosdumay on Tuesday May 25, 2021 @06:32AM
(#27275157)
> There's nearly zero cost to leaving a stale bug report open.
Triaging an endless list is very costly.
I do agree with the idea that if you expect your project to be public (and not just something you did that you'll share if somebody wants) it is a cost you are expected to take. But it's wrong to pretend it's free.
Re:Use native context menus on Mac OS
by oooooooooooow on Tuesday May 25, 2021 @07:50AM
(#27275701)
Triage is what happens when you first look at a new ticket and decide what to do with it, any encounter/interaction after that is not a triage.
If maintainers feel like they need to close tickets only to keep order, than that's a problem with the tooling: tickets should only be closed if they're malformed, solved, or (arguably) wontfix.
Re:Use native context menus on Mac OS
by marcosdumay on Tuesday May 25, 2021 @09:34AM
(#27276564)
> If maintainers feel like they need to close tickets only to keep order, than that's a problem with the tooling
Oh, yes. Yes it is!
I think you were downvoted because the first part of your answer is wrong, but this one hits right on the mark.
Re:Use native context menus on Mac OS
by oooooooooooow on Wednesday May 26, 2021 @04:56PM
(#27295989)
I've always interpreted "triage" as the first response whenever something comes up (paralleling the medical term were it's from), is that not how it is?
Priority is a constantly moving slide.
Re:Use native context menus on Mac OS
by thaumasiotes on Tuesday May 25, 2021 @04:58AM
(#27274540)
> But closing tickets and fixing bugs are not the same thing.
You can't measure how many bugs you have, but you can measure how many bug reports you have. ;D
If you're not working on a bug, then, by definition, it's not taking up your time.
Some people are just obsessive about not wanting to look like they have open bugs on their project. But closing tickets and fixing bugs are not the same thing.