From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-project@lists.gentoo.org, bugzilla@gentoo.org, mgorny@gentoo.org
Subject: Re: [gentoo-project] The meaning of RESOLVED/UPSTREAM on bugzie
Date: Thu, 30 Mar 2017 19:55:58 +0200 [thread overview]
Message-ID: <2bd89033-0ea1-f9e0-e8e6-82736306069d@gentoo.org> (raw)
In-Reply-To: <20170330175217.GA4981@whubbs1.gaikai.biz>
[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]
On 03/30/2017 07:52 PM, William Hubbs wrote:
>
> I disagree with resolved/invalid being appropriate. That means it isn't
> a bug at all. Resolved/upstream should be used when we direct a user to
> file an issue upstream or file the issue ourselves.
>
> Resolved/upstream acknowledges that this is an issue but directs it
> upstream. Resolved/invalid says this isn't an issue.
>
If it actually is a bug affecting users it shouldn't be closed to begin
with but kept open , this would be appropriate use of the UPSTREAM
keyword after filing the bug and preferably updating URL field to point
to bug report.
From a gentoo point of view, the issue would require fixing and
stabilization before the bug is closed.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-03-30 17:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 7:56 [gentoo-project] The meaning of RESOLVED/UPSTREAM on bugzie Michał Górny
2017-03-29 9:29 ` Marek Szuba
2017-03-29 13:49 ` Paweł Hajdan, Jr.
2017-03-29 14:10 ` Seemant Kulleen
2017-03-29 14:01 ` Ulrich Mueller
2017-03-29 14:15 ` Michał Górny
2017-03-30 17:58 ` William Hubbs
2017-03-30 18:34 ` Kent Fredric
2017-03-30 18:41 ` William L. Thomson Jr.
2017-03-30 18:46 ` Michał Górny
2017-03-30 19:05 ` William L. Thomson Jr.
2017-03-31 13:13 ` Rich Freeman
2017-03-31 14:38 ` William L. Thomson Jr.
2017-03-31 14:45 ` Rich Freeman
2017-04-06 18:14 ` Thomas Deutschmann
2017-03-30 18:50 ` William L. Thomson Jr.
2017-03-30 19:40 ` Kent Fredric
2017-03-30 19:50 ` Kristian Fiskerstrand
2017-03-30 19:58 ` Kent Fredric
2017-03-30 20:49 ` Michał Górny
2017-03-29 14:15 ` Kristian Fiskerstrand
2017-03-30 17:52 ` William Hubbs
2017-03-30 17:54 ` M. J. Everitt
2017-03-30 17:55 ` Kristian Fiskerstrand [this message]
2017-04-01 12:28 ` Andreas K. Huettel
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=2bd89033-0ea1-f9e0-e8e6-82736306069d@gentoo.org \
--to=k_f@gentoo.org \
--cc=bugzilla@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=mgorny@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