httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Geoff Thorpe <ge...@geoffthorpe.net>
Subject Re: DO NOT REPLY [Bug 41364] chunk-size contains space
Date Sat, 02 Aug 2008 05:09:46 GMT
On Friday 01 August 2008 19:51:48 William A. Rowe, Jr. wrote:
> bugzilla@apache.org wrote:
> > https://issues.apache.org/bugzilla/show_bug.cgi?id=41364
> >
> >
> > Roy T. Fielding <fielding@apache.org> changed:
> >
> >            What    |Removed                     |Added
> > -------------------------------------------------------------------------
> >--- Status|RESOLVED                    |CLOSED
>
> I really wonder if RESOLVED vs CLOSED makes any sense to an open source
> community.
>
> While this is a sensible division of labor between dev and QA, we don't
> have two distinct groups of individuals.
>
> Should we simply dump CLOSED from the the list (or dump RESOLVED) and
> answer the question only once when we believe it to be fixed?  It's not
> as though the user can't confirm the fix themselves and reopen, when
> appropriate.

Or allow status to be moved directly to CLOSED without passing through 
RESOLVED first. I've seen bugzilla scenarios in which tickets have been 
RESOLVED awaiting the owner to CLOSE them, and others where the relevant 
person has CLOSED it because that's what makes sense. I agree with the 
observation, but I think RESOLVED and CLOSED are sometimes useful 
distinctions, so mightn't it be best to let the ticket-editor choose?

Cheers,
Geoff

-- 
Un terrien, c'est un singe avec des clefs de char...

Mime
View raw message