jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Cooper <mart...@apache.org>
Subject Re: JSTL/Standard taglib bugzilla stuff
Date Wed, 04 Dec 2002 20:00:09 GMT


On Wed, 4 Dec 2002, Pierre Delisle wrote:

> Hi Glenn,
>
> > Some of you may have noticed I have been going through the Jakarta-Taglibs bugzilla
reports.
>
> Yes. Thanks for doint it...
>
> > We currently have a JSTL category and a Standard category defined in bugzilla.
> > I propose that all the JSTL bugs be recategorized as Standard, then remove the
> > JSTL category from bugzilla.
>
> +1.
>
> > It would also be nice if the bug reports for JSTL/Standard were reviewed and the
> > status set to CLOSED for those which are completed.
>
> I just found out the description of a bug's lifecycle at
> http://nagoya.apache.org/bugzilla/bug_status.html
>
> According to this, a bug should first be RESOLVED, then VERIFIED by QA,
> and finally CLOSED when the product ships.
>
> This might be nice in an ideal setting, but seems quite redundant
> in our environment since whoever resolves the bug is normally responsible
> to verify it, as well as close it.
>
> So my question is, do we really care about VERIFIED and CLOSED, or isn't
> RESOLVED good enough?

In other Jakarta projects I'm involved with (Struts, Commons), we stop at
RESOLVED, as you suggest, and don't worry about VERIFIED or CLOSED. There
haven't been any issues with that, as far as I'm aware.

--
Martin Cooper


>
> Trying to simplify the process here. There's a cost in handling VERIFIED and
> CLOSED if it is to be done properly.
>
>     -- Pierre
>
>
> --
> To unsubscribe, e-mail:   <mailto:taglibs-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:taglibs-dev-help@jakarta.apache.org>
>
>


--
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