From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-98667-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id 43339158020
for <garchives@archives.gentoo.org>; Sat, 3 Dec 2022 18:51:04 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 718C3E0AEC;
Sat, 3 Dec 2022 18:51:01 +0000 (UTC)
Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id C18A0E0963
for <gentoo-dev@lists.gentoo.org>; Sat, 3 Dec 2022 18:51:00 +0000 (UTC)
Received: by mail-yb1-f180.google.com with SMTP id b16so940412yba.0
for <gentoo-dev@lists.gentoo.org>; Sat, 03 Dec 2022 10:50:59 -0800 (PST)
X-Gm-Message-State: ANoB5pkCJudmry7xgdygDyIHqED2koorcEI/azM01uIn+5xymInQ4wRa
OTWQUMh+Hml1G0lZx8EjmKT4a+cXXK6hQJlYBpY=
X-Google-Smtp-Source: AA0mqf697NrmyEM4OWOUF/HzpDoz8XgofcKGU2WyTmOyLixF1wRbVrR9eCtEPKe1gpAmKMSRW669SzD+PGeFHZOQvoQ=
X-Received: by 2002:a25:aa08:0:b0:6f6:686:c947 with SMTP id
s8-20020a25aa08000000b006f60686c947mr28411266ybi.606.1670093457816; Sat, 03
Dec 2022 10:50:57 -0800 (PST)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
References: <846a6db823da65215a8529f264ec23e949763810.camel@gentoo.org>
In-Reply-To: <846a6db823da65215a8529f264ec23e949763810.camel@gentoo.org>
From: Mike Gilbert <floppym@gentoo.org>
Date: Sat, 3 Dec 2022 13:50:46 -0500
X-Gmail-Original-Message-ID: <CAJ0EP42F-CoxQ7CZ80KRGTsndfC6Jr_RhUUrrbK=4wD+tXxM+w@mail.gmail.com>
Message-ID: <CAJ0EP42F-CoxQ7CZ80KRGTsndfC6Jr_RhUUrrbK=4wD+tXxM+w@mail.gmail.com>
Subject: Re: [gentoo-dev] [RFC] Removing the distinction between UNCONFIRMED
and CONFIRMED bugs
To: gentoo-dev@lists.gentoo.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt: bdb1e83c-fd6e-4344-b523-3c1f098d3071
X-Archives-Hash: 8858e71a1c74f01e8dacd27b015c0776
On Sat, Dec 3, 2022 at 2:09 AM Micha=C5=82 G=C3=B3rny <mgorny@gentoo.org> w=
rote:
>
> 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.