From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 B5031158020 for ; Sat, 3 Dec 2022 13:50:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AC803E0DF3; Sat, 3 Dec 2022 13:50:20 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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 51D19E0DD0 for ; Sat, 3 Dec 2022 13:50:20 +0000 (UTC) Message-ID: <2978f919097e1fffbadda438de3deeae558e6b57.camel@gentoo.org> Subject: Re: [gentoo-dev] [RFC] Removing the distinction between UNCONFIRMED and CONFIRMED bugs From: =?UTF-8?Q?Micha=C5=82_G=C3=B3rny?= To: gentoo-dev@lists.gentoo.org Date: Sat, 03 Dec 2022 14:50:16 +0100 In-Reply-To: <91c0279e-4dcb-1d95-fcda-785730cb1beb@gentoo.org> References: <846a6db823da65215a8529f264ec23e949763810.camel@gentoo.org> <815ea364-0feb-aaba-f1a6-7b865ac11d52@gentoo.org> <2a8006c0-1294-0fb5-a46b-dfcd34859fe2@gentoo.org> <6a2ba31fda5ec0a56978a36c6ca2e3f38dbe081f.camel@gentoo.org> <91c0279e-4dcb-1d95-fcda-785730cb1beb@gentoo.org> Organization: Gentoo Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail 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 X-Archives-Salt: 98351e17-23f8-4633-a128-9bd96cdd7c0a X-Archives-Hash: 0b160b21f78c4a0b78e8e2d945bfa997 On Sat, 2022-12-03 at 14:45 +0100, Florian Schmaus wrote: > I think having UNCONFIRMED / CONFIRMED *helps* the issue reporter, and= =20 > other (affected) persons, to decide if they need to "chase" the issue's= =20 > assigned entity. >=20 > Assume looking at the open bugs list of a developer. If the developer=20 > has old bugs in UNCONFIRMED state, you may want to issue a friendly=20 > ping. Sure, strictly speaking, this would require all bugs to drop back= =20 > to UNCONFIMRED when the bug assignee changes. But even without such an= =20 > 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. --=20 Best regards, Micha=C5=82 G=C3=B3rny