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 5B24515815E for ; Thu, 8 Feb 2024 07:00:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4AD94E2A9A; Thu, 8 Feb 2024 07:00:45 +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 B190FE2A86 for ; Thu, 8 Feb 2024 07:00:44 +0000 (UTC) References: <0d9a35f44a050435d17c755b06dbc439956de674.camel@gentoo.org> User-agent: mu4e 1.10.8; emacs 30.0.50 From: Sam James To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] Gentoo Bugzilla: new resolution for bugs closed due to last rites Date: Thu, 08 Feb 2024 07:00:05 +0000 Organization: Gentoo In-reply-to: Message-ID: <87y1bvtp7s.fsf@gentoo.org> 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 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Archives-Salt: e863c234-6be1-49d6-bbbc-ddef0184d91d X-Archives-Hash: b127dad570f9c530749b3c2a0c7637b1 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ionen Wolkens writes: > [[PGP Signed Part:Undecided]] > On Wed, Feb 07, 2024 at 12:03:52PM +0100, Micha=C5=82 G=C3=B3rny wrote: >> Hi, >>=20 >> I think we should add a new bug resolution that would more precisely >> cover closing bugs due to packages being removed. Right now, whichever >> resolution we use (be it WONTFIX, OBSOLETE, etc.), we aren't able to >> easily distinguish whether the resolution was used "normally" or due to >> last rites. >>=20 >> Having a dedicated resolution (technical name RESO/PKGREMOVED) would >> make this clear. Furthermore, it would make it easier to reopen bugs >> if the packages are ever reintroduced. >>=20 >> WDYT? > > Sounds like it could be useful (that or some other way to identify > these if preferred), but think something that's missing either way > would be a way to automate/streamline it preferably without scripts. > Like additional actions for commit summaries (aka like 'Closes:'). > > In general think not many want to use bugz or do it manually on > removal. So these are often not even closed WONTFIX/OBSOLETE but > rather as FIXED through 'Closes:' regardless of what the devmanual > says (currently it instructs to do WONTFIX). Agreed. I like the idea, but for me, it's a non-starter unless we commit to doing this (some bug tag like 'Removed:' or 'Last-rited:' or w/e for commits) as well. It ends up being asked to be ignored/forgotten otherwise. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZcR8F18UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZCylwD5AX6HwBp86leSp7Whi2cRMFEaW3pWdkTDwzcX V/Zp0n4A/j5nGxZyFdb1fInRSKVzT9nitXgZrokIkxTVYr3RWNEM =/euS -----END PGP SIGNATURE----- --=-=-=--