Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <3A0C356A.94C61ABF@eng.sun.com>
Date: Fri, 10 Nov 2000 09:50:34 -0800
From: "Craig R. McClanahan" <Craig.McClanahan@eng.sun.com>
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Ready for 3.2b7?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

It's been a week now, and I've committed > 20 patches to the 3.2 tree,
ranging from simple tweaks to security problems to spec compliance
bugs.  I believe that I've gotten all of the critical bug reports
submitted on the mailing lists or via BugRat.  Does anyone know of any
I've missed (see below for one issue I know is outstanding)?

What I'd like to do is build a "beta 7" release this afternoon and post
it.  That will give people a chance to pound on it.  Any critical bugs
we find will need to be fixed, but we need to hold off on changing
non-essential stuff so we can get a final 3.2 release out the door.

NOTE:  One issue that's been discussed in the last couple of days is
problems supporting the "load balancing" feature for root webapps.  I
haven't seen a proposed patch for this, but understand from the comments
of people that have tried kludges to work around it -- and it seems
unreasonable to risk destabilizing things at this late date.  I suggest
that any work on fixing this problem be deferred to a post-3.2-final
maintenance cycle.

Craig McClanahan

PS:  Thanks to everyone for all the bug reports, and to Larry and Nacho
for chipping in on the commits!

PPS:  When the 3.2 final release is completed, my personal focus is
going to return to the Tomcat 4.0 code base (which does not suffer from
any of the bugs patched in 3.2, although I did find one 4.0 bug along
the way :-).  If and when bugs show up in 3.2 final, I will be happy to
commit patches that people supply -- but any big debugging effort or
major new work on the 3.x track will need to be done by someone else.