On Sat, Dec 3, 2022 at 2:09 AM Michał Górny <mgo...@gentoo.org> wrote: > > Hi, > > I'd like to propose replacing the current UNCONFIRMED and CONFIRMED bug > states with a simple NEW state. Why? > > 1. Only a handful of developers actually uses these two statuses > in a meaningful way. > > 2. Some users are confused and demotivated by having their bugs stay > UNCONFIRMED for a long time.
I think I could be counted among the devs who at least try to use the two statuses. If I stumble upon bugs that I have run into myself, I will flip them from UNCONFIRMED to CONFIRMED. On the opposite end, I occasionally downgrade bugs from CONFIRMED to UNCONFIRMED if they are particularly strange looking and were filed by a script (tinderbox). Anyway, if you decide to make the change, please ensure that it doesn't generate a bunch of pointless bugmail. I have noticed that some devs will replace obsolete values in Product/Component without making any other meaningful changes to the bug. Let's avoid that situation if possible here.