You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "William A. Rowe, Jr." <wr...@rowe-clan.net> on 2008/08/02 01:51:48 UTC
Re: DO NOT REPLY [Bug 41364] chunk-size contains space
bugzilla@apache.org wrote:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=41364
>
>
> Roy T. Fielding <fi...@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.
Re: DO NOT REPLY [Bug 41364] chunk-size contains space
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Roy T. Fielding wrote:
> On Aug 1, 2008, at 4:51 PM, William A. Rowe, Jr. wrote:
>>
>> I really wonder if RESOLVED vs CLOSED makes any sense to an open source
>> community.
>
> RESOLVED means fixed/wontfix in trunk. CLOSED means it has either been
> released or will never be released.
I don't disagree.
But your answer presupposes there are enough individual with time or the
inclination to move RESOLVED issues to CLOSED status. 10 years of history
and the current open bug list shows that this isn't necessarily the case ;-)
Re: DO NOT REPLY [Bug 41364] chunk-size contains space
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
On Aug 1, 2008, at 4:51 PM, William A. Rowe, Jr. wrote:
> bugzilla@apache.org wrote:
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=41364
>> Roy T. Fielding <fi...@apache.org> changed:
>> What |Removed |Added
>> ---------------------------------------------------------------------
>> -------
>> Status|RESOLVED |CLOSED
>
> I really wonder if RESOLVED vs CLOSED makes any sense to an open
> source
> community.
RESOLVED means fixed/wontfix in trunk. CLOSED means it has either been
released or will never be released.
....Roy
Re: DO NOT REPLY [Bug 41364] chunk-size contains space
Posted by Geoff Thorpe <ge...@geoffthorpe.net>.
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 <fi...@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...