From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] Removing the distinction between UNCONFIRMED and CONFIRMED bugs
Date: Sat, 03 Dec 2022 08:09:57 +0100 [thread overview]
Message-ID: <846a6db823da65215a8529f264ec23e949763810.camel@gentoo.org> (raw)
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.
--
Best regards,
Michał Górny
next reply other threads:[~2022-12-03 7:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 7:09 Michał Górny [this message]
2022-12-03 7:58 ` [gentoo-dev] [RFC] Removing the distinction between UNCONFIRMED and CONFIRMED bugs Sam James
2022-12-03 8:39 ` Ulrich Mueller
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=846a6db823da65215a8529f264ec23e949763810.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.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