public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Removing the distinction between UNCONFIRMED and CONFIRMED bugs
Date: Sat, 03 Dec 2022 14:50:16 +0100	[thread overview]
Message-ID: <2978f919097e1fffbadda438de3deeae558e6b57.camel@gentoo.org> (raw)
In-Reply-To: <91c0279e-4dcb-1d95-fcda-785730cb1beb@gentoo.org>

On Sat, 2022-12-03 at 14:45 +0100, Florian Schmaus wrote:
> I think having UNCONFIRMED / CONFIRMED *helps* the issue reporter, and 
> other (affected) persons, to decide if they need to "chase" the issue's 
> assigned entity.
> 
> Assume looking at the open bugs list of a developer. If the developer 
> has old bugs in UNCONFIRMED state, you may want to issue a friendly 
> ping. Sure, strictly speaking, this would require all bugs to drop back 
> to UNCONFIMRED when the bug assignee changes. But even without such an 
> implicit mechanism, those two states provide some value.

I don't understand how UNCONFIRMED/CONFIRMED makes any difference here.
If I file a bug against some package, it is CONFIRMED by default.
If an unprivileged user files it, it's UNCONFIRMED.  In both cases
the assignee didn't do anything.

-- 
Best regards,
Michał Górny



  reply	other threads:[~2022-12-03 13:50 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
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 [this message]
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=2978f919097e1fffbadda438de3deeae558e6b57.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