>>>>> On Sat, 03 Dec 2022, Michał Górny wrote: >> > 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. >> >> Then rename UNCONFIRMED to NEW-WITH-SUGAR-ON-TOP-WE-ARE-A-HAPPY- >> COMMUNITY,
> Done. Seriously, we had UNCONFIRMED, NEW, and ASSIGNED before. The default status used to be NEW, but with "expert" reporting users could explicitly assign the status to UNCONFIRMED. Some people found that not satisfactory, so NEW and ASSIGNED were replaced by CONFIRMED and IN_PROGRESS. (We also had status REOPENED which was removed with the same change.) Unfortunately, I cannot find the old discussion, but [1] suggests that the change took place in 2011 or before. The Bugzilla Guide [2] still has the old wording: | • UNCONFIRMED - You're generally not going to see this too often. | This means that a bug reporter has opened a bug using the advanced | method and is uncertain their bug is an actual bug. | • NEW - Bugs that are first opened are considered new. Tracing the history of that text, it was the same in 2005 [3], and seems to originate from [4]. A previous discussion about this topic (started by you :) can be found in [5], BTW. Ulrich [1] https://bugs.gentoo.org/391203#c1 [2] https://wiki.gentoo.org/wiki/Bugzilla/Guide#Working_with_a_bug [3] https://gitweb.gentoo.org/archive/proj/gentoo.git/commit/xml/htdocs/doc/en/bugzilla-howto.xml?id=6947795f3817a6779a81d768e9a5a07380d56aa4 [4] https://bugs.gentoo.org/97274 [5] https://archives.gentoo.org/gentoo-dev/message/b24ea134d3555cd25560090cf4a87657
signature.asc
Description: PGP signature
