From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] Gentoo Bugzilla: new resolution for bugs closed due to last rites
Date: Wed, 07 Feb 2024 12:03:52 +0100 [thread overview]
Message-ID: <0d9a35f44a050435d17c755b06dbc439956de674.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
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?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next reply other threads:[~2024-02-07 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 11:03 Michał Górny [this message]
2024-02-07 11:45 ` [gentoo-dev] [RFC] Gentoo Bugzilla: new resolution for bugs closed due to last rites Ionen Wolkens
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=0d9a35f44a050435d17c755b06dbc439956de674.camel@gentoo.org \
--to=mgorny@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