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 1C3AD158020 for ; Sat, 3 Dec 2022 16:09:13 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0BA092BC132; Sat, 3 Dec 2022 16:09:10 +0000 (UTC) Received: from smtp.gentoo.org (dev.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)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C27902BC12E for ; Sat, 3 Dec 2022 16:09:09 +0000 (UTC) Message-ID: <00d0f13e-d62a-fcd6-f344-cc82cdebda0b@gentoo.org> Date: Sat, 3 Dec 2022 11:09:06 -0500 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 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Subject: Re: [gentoo-dev] [RFC] Removing the distinction between UNCONFIRMED and CONFIRMED bugs To: gentoo-dev@lists.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> <2978f919097e1fffbadda438de3deeae558e6b57.camel@gentoo.org> Content-Language: en-US From: Mike Pagano In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: f685a91b-0b11-4efd-a402-733acc6daf50 X-Archives-Hash: 511914d8bf03d43c6f3fb8806f000ebf On 12/3/22 08:59, Florian Schmaus wrote: > On 03/12/2022 14.50, Michał Górny wrote: >> 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. > > The assignee not doing anything keeps the bug UNCONFIRMED if it is > filled by an unprivileged user. That makes the bug distinguishable from > a bug that got "verified" by the assignee. > > Yes, if *you* (as dev) fill a bug, then it is implicitly CONFIRMED > (whether or not that is sensible is a different discussion). I do not > see how this would invalidate my case, though. > > - Flow > The kernel may be a special case, but personally I use unconfirmed and don't 'confirm' it until it's determined if it's a real kernel bug. Sometimes the kernel is the messenger and not the cause. But this is not a documented process and only exists in my head. Whatever the consensus is I can live with. -- Mike Pagano Gentoo Developer - Kernel Project Gentoo Sources - Lead E-Mail : mpagano@gentoo.org GnuPG FP : 52CC A0B0 F631 0B17 0142 F83F 92A6 DBEC 81F2 B137 Public Key : http://http://pgp.mit.edu/pks/lookup?search=0x92A6DBEC81F2B137&op=index