public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Should we disable RESOLVED LATER from bugzilla?
Date: Sun, 11 Apr 2010 17:20:24 -0600	[thread overview]
Message-ID: <20100411172024.5fa50577@gentoo.org> (raw)
In-Reply-To: 20100408001341.4aae0114@gentoo.org

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Thu, 8 Apr 2010 00:13:41 +0200
Christian Faulhammer <fauli@gentoo.org> wrote:

> Petteri Räty <betelgeuse@gentoo.org>:
> > 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"
> 
>  Kill REMIND and LATER, introduce Later keyword or ASSIGNED LATER.

"Me too."©

What happens to bugs already in that state though?


-- 
fonts,                                            by design, by neglect
gcc-porting,                              for a fact or just for effect
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-04-11 23:18 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
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 [this message]
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=20100411172024.5fa50577@gentoo.org \
    --to=dirtyepic@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