jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glenn Nielsen <gl...@mail.more.net>
Subject Re: JSTL/Standard taglib bugzilla stuff
Date Thu, 05 Dec 2002 03:13:37 GMT
Pierre Delisle wrote:
> 
> Glenn Nielsen wrote:
> ...
> 
>>>So my question is, do we really care about VERIFIED and CLOSED, or isn't
>>>RESOLVED good enough?
>>
>>Except that some of the bugs are set at RESOLVED LATER or RESOLVED REMIND
>>which to me means that these may be addressed at a later time.
> 
> 
> Correct. 
> 
> However, as it seems to be the case in other projects (as Martin mentioned),
> it looks like we could keep the bugs in their resolved states and not mandate 
> to update them to VERIFIED or CLOSED.
> 
> One would only have to remember that to get a full list of "PENDING" bugs,
> the following bugs must be queried:
> 
>    NEW
>    ASSIGNED
>    REOPENED
>    RESOLVED - LATER
>    RESOLVED - REMIND
> 
> And ideally, I'd suggest not using RESOLVED-LATER or RESOLVED-REMIND, but
> rather make use of the priority and severity fields so that a simple query
> for "OPEN" bugs (i.e. NEW, ASSIGNED, RESOLVED) gets them all.
> 
>     -- Pierre

If it works for those maintaining the Standard Taglib I'm happy with it. :-)

I'll go ahead and recategorize the JSTL bugs as Standard bugs, then remove
the JSTL category.

Glenn


--
To unsubscribe, e-mail:   <mailto:taglibs-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:taglibs-dev-help@jakarta.apache.org>


Mime
View raw message