From: Ulrich Mueller <ulm@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Removing the distinction between UNCONFIRMED and CONFIRMED bugs
Date: Sat, 03 Dec 2022 09:39:39 +0100 [thread overview]
Message-ID: <ubkokc244@gentoo.org> (raw)
In-Reply-To: <846a6db823da65215a8529f264ec23e949763810.camel@gentoo.org> ("Michał Górny"'s message of "Sat, 03 Dec 2022 08:09:57 +0100")
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
>>>>> 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,
and leave CONFIRMED alone? :)
However, I suspect that the real problem isn't the status label, but
when there's no action on the bug (sometimes for months or years).
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2022-12-03 8:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 7:09 [gentoo-dev] [RFC] Removing the distinction between UNCONFIRMED and CONFIRMED bugs Michał Górny
2022-12-03 7:58 ` Sam James
2022-12-03 8:39 ` Ulrich Mueller [this message]
2022-12-03 9:53 ` Michał Górny
2022-12-03 10:09 ` Toralf Förster
2022-12-03 11:48 ` Ulrich Mueller
2022-12-03 12:14 ` Ulrich Mueller
2022-12-03 10:42 ` Florian Schmaus
2022-12-03 11:34 ` Michał Górny
2022-12-03 12:10 ` Florian Schmaus
2022-12-03 12:20 ` Michał Górny
2022-12-03 13:45 ` Florian Schmaus
2022-12-03 13:50 ` Michał Górny
2022-12-03 13:59 ` Florian Schmaus
2022-12-03 16:09 ` Mike Pagano
2022-12-03 18:46 ` Jonas Stein
2022-12-03 18:50 ` Mike Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ubkokc244@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox