Using Bugzilla to track unfixed bugs in Tomcat 3.3

[Larry Isaacs <La...@sas.com>]

Hi All,

Assuming the Tomcat 3.3 Release Plan is approved and proceeds
to reach a release vote, it would be nice if a simple Bugzilla
query would identify which bugs are and aren't fixed in Tomcat
3.3.  In order to achieve this, I think we will need to
standardize on a procedure to mark old bugs as fixed in
Tomcat 3.3.

As a simple way to achieve this, I would propose the following:

Any Tomcat 3.x bug that is fixed in Tomcat 3.3 must have a
comment containing the text "Fixed in Tomcat 3.3" to be
considered fixed in Tomcat 3.3. That way, a search
for all bugs missing this text would reveal which bugs are
not fixed.  If the bug didn't actually apply to Tomcat 3.3,
an explanation could be added to make that clear.

For example, a bug logged against Tomcat 3.1 could be resolved
by setting the resolution to "later" or "wontfix", which I
assume would apply to the 3.1.x version of Tomcat.  To indicate
that the bug doesn't apply or is fixed in Tomcat 3.3, the
comment would be added so it doesn't appear unfixed in 3.3.
Simply setting the resolution to "fixed" would not indicate
whether it was fixed in 3.1.1, 3.2.x or 3.3.

I don't see a way in Bugzilla to have a single bug open
against multiple versions of a project.  It looks like you
would have to enter separate bugs if you wanted to be able
to "resolve" them separately.  I don't see a big enough
benefit to justify re-entering all the old bugs against
Tomcat 3.3.  If I am missing something about the capabilities
of Bugzilla, or you know of a better way, please let me know.

Cheers,
Larry

__________
Larry Isaacs		
Larry.Isaacs@sas.com
SAS Institute Inc.