On 16/06/16 09:47 AM, Michał Górny wrote: > On Thu, 16 Jun 2016 16:22:32 +0300 > Andrew Savchenko <birc...@gentoo.org> wrote: >> >> CONFIRMED state is useful, it means that dev or powerful user >> confirmed this bug and gives it more value. I'd like to keep it. > > Are you saying that bugs that haven't been marked as CONFIRMED have > less value? Maybe they don't have to be handled at all, unless someone > you consider more worthy confirms them? >
To me it's not about increased or decreased value per se, it's about workflow: - An UNCONFIRMED bug I have to reproduce myself and diagnose to determine if it's really a bug or if it's something else. - A CONFIRMED bug to me means this has already been done (by myself, others in the project, or dev's that should know the difference) and I can skip directly to identifying and fixing the issue. So when I look at the list of bugs for firefox I know what the state is more or less for things that are outstanding. If I have just a little bit of time to hack away at things I'd rather try to close a CONFIRMED bug than half-diagnose an UNCONFIRMED one. Similarly if I don't have access to my dev system but have plenty of time, I may well try and triage UNCONFIRMED bugs. IN_PROGRESS to me is something that should be reserved for when the fix is ready to go and just hasn't been fully applied or is readily available to all users (say, the fix is on an overlay for testing) -- I would prefer not to start using that instead of CONFIRMED, but if that's what the new meaning would be after UNCONFIRMED/CONFIRMED is merged to OPEN, I guess I could live with it.
signature.asc
Description: OpenPGP digital signature
