From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Gentoo Bugzilla: new resolution for bugs closed due to last rites
Date: Wed, 7 Feb 2024 06:45:35 -0500 [thread overview]
Message-ID: <ZcNtXzBiCXacqXOX@eversor> (raw)
In-Reply-To: <0d9a35f44a050435d17c755b06dbc439956de674.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
On Wed, Feb 07, 2024 at 12:03:52PM +0100, Michał Górny wrote:
> Hi,
>
> 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.
>
> 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.
>
> 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).
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-02-07 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 11:03 [gentoo-dev] [RFC] Gentoo Bugzilla: new resolution for bugs closed due to last rites Michał Górny
2024-02-07 11:45 ` Ionen Wolkens [this message]
2024-02-08 7:00 ` Sam James
2024-02-07 22:46 ` Jonas Stein
2024-05-08 9:23 ` Michał Górny
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=ZcNtXzBiCXacqXOX@eversor \
--to=ionen@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