From: Krzysztof Pawlik <nelchael@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Should we disable RESOLVED LATER from bugzilla?
Date: Sat, 03 Apr 2010 11:27:38 +0100 [thread overview]
Message-ID: <4BB7181A.6050907@gentoo.org> (raw)
In-Reply-To: <4BB713D5.7000909@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1822 bytes --]
On 04/03/10 11:09, "Paweł Hajdan, Jr." wrote:
> On 4/3/10 12:03 PM, Krzysztof Pawlik wrote:
>> On 04/03/10 10:50, Petteri Räty wrote:
>>> I don't think later is valid resolution. If there's a valid bug it just
>>> means it's never looked at again. If the bug is not valid then a
>>> different resolution should be used. So what do you think about
>>> disabling later? I would like to avoid things like this:
>>>
>>> https://bugs.gentoo.org/show_bug.cgi?id=113121#c21
>>>
>>> Not applicable to the bug above but in general our social contract says:
>>> "We will not hide problems"
>>
>> Sounds good, can we at the same time get RESOLVED OBSOLETE (for bugs that are
>> not valid anymore due to changed situation, RESOLVED INVALID isn't applicable in
>> this case as it implies the bug is and was invalid from the begining).
>
> Wouldn't WORKSFORME apply in that case? Just renaming the resolutions
> doesn't gain us much. Reducing the number of possible resolutions does,
> I'd say.
In my opinion: no. WORKSFORME is for a problems that can't be reproduced.
OBSOLETE would be: yes, this bug has been applicable, but situation changed,
ignore it. One of the examples could be stabilization bugs: you have an open
stabilization bug, but new version comes out with important security fix and it
needs to go stable ASAP. You mark the old stabilization bug as OBSOLETE and
continue in the one opened for security issue (as it usually happens).
To summarize: I'm suggesting axing two resolutions (LATER and REMIND) and
introduce OBSOLETE. If OBSOLETE doesn't sound like a good idea I'm ok with not
having it -- removing two resolutions is a nice achievement too :)
--
Krzysztof Pawlik <nelchael at gentoo.org> key id: 0xF6A80E46
desktop-misc, java, apache, ppc, vim, kernel, python...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]
next prev parent reply other threads:[~2010-04-03 10:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 9:50 [gentoo-dev] Should we disable RESOLVED LATER from bugzilla? Petteri Räty
2010-04-03 10:03 ` Krzysztof Pawlik
2010-04-03 10:09 ` "Paweł Hajdan, Jr."
2010-04-03 10:27 ` Krzysztof Pawlik [this message]
2010-04-04 16:55 ` Andreas K. Huettel
2010-04-03 15:25 ` Jorge Manuel B. S. Vicetto
2010-04-03 17:10 ` Petteri Räty
2010-04-03 17:54 ` Alec Warner
2010-04-03 18:23 ` Petteri Räty
2010-04-05 17:58 ` Denis Dupeyron
2010-04-03 18:58 ` Tiziano Müller
2010-04-03 21:35 ` Gilles Dartiguelongue
2010-04-03 22:01 ` Alec Warner
2010-04-04 9:05 ` Petteri Räty
2010-04-04 9:16 ` Nirbheek Chauhan
2010-04-04 9:36 ` Petteri Räty
2010-04-05 17:54 ` Denis Dupeyron
2010-04-05 20:20 ` Nirbheek Chauhan
2010-04-05 0:54 ` Mart Raudsepp
2010-04-05 10:07 ` [gentoo-dev] " Peter Hjalmarsson
2010-04-06 5:47 ` [gentoo-dev] " Rémi Cardona
2010-04-06 7:42 ` Maciej Mrozowski
2010-04-06 9:46 ` Michał Górny
2010-04-07 22:13 ` [gentoo-dev] " Christian Faulhammer
2010-04-11 23:20 ` Ryan Hill
2010-04-12 9:00 ` Petteri Räty
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=4BB7181A.6050907@gentoo.org \
--to=nelchael@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