Re: Massive bug expiration spree

[Curtis Hovey <curtis.hovey@xxxxxxxxxxxxx>]

On Sun, 2007-09-23 at 22:59 -0300, Christian Robottom Reis wrote:
> On Mon, Sep 24, 2007 at 11:52:53AM +1000, Martin Pool wrote:
> > Frankly I don't think that's enough.  For Bazaar there are bugs in the
> > incomplete state that we want to keep open.  It is not reasonable to
> > close them with no warning or approval, or to expect us to interrupt
> > our work to manually reopen them.
> 
> There will be warning. The Incomplete status has that semantic: it is a
> status that is intended to be driven to zero. If you know enough about
> the bug to acknowledge it is a bug, mark it Confirmed.
> 
> > Aside from the inconvenience to developers, please consider what kind
> > of message it sends to a Bazaar user when they spend their time giving
> > us a good bug report only to have it brusquely discarded.
> 
> If the bug report is good, it should move rapidly to Confirmed. It's not
> meant to stay in the Incomplete status; other uses of Incomplete are
> incorrect (and I'll write a doc about this early Monday to clarify).

Am I right in my understanding that Incomplete is being used to indicate
that some party Needs Information? That isn't right for bug status, but
I acknowledge that is a valuable status for work. Should we be
considering a new work status field for states like In Planning, In
Development, In Review, Needs Information. The latter two imply no work
can be done until party provides feedback.


-- 
__Curtis C. Hovey_________
http://launchpad.net/

Attachment: signature.asc
Description: This is a digitally signed message part