RE: [VOTE] Tomcat 3.2 Final Release (!) and Ongoing Maintenance P lan

[GOMEZ Henri <hg...@slib.fr>]

>(1) Build and release Tomcat 3.2 final on Wednesday 11/29/2000
>
>There are some known outstanding issues (documented in the 
>release notes), plus
>some remaining work to be done on the AJP13 connector -- but 
>in my option these
>can be dealt with successfully in a maintenance cycle that is 
>proposed below.
>The current code base appears to be stable enough for 
>production use in large
>numbers of environments, and is *substantially* improved in quality and
>performance over Tomcat 3.1.
>
>Therefore, I propose that we cut a final release of Tomcat 3.2 
>on Wednesday
>night, and publish it for the world to grab.  It will be based 
>on the current
>state of the "tomcat_32" branch -- on which there have been 
>only a couple of low
>risk and documentation oriented updates since 3.2b8.
>

+1 (known bugs to be fixed in 3.2.1 - Did you apply the patch from Clinton,
Doug [dclinton@tanning.com]

=> See attached (I could apply it but I need a quick answer)

>(2) Ongoing Support Plan for Tomcat 3.2
>
>Even though we will finish the initial release cycle for 
>Tomcat 3.2 (finally :-)
>if the previous proposal is accepted, we will not really be 
>through with it.
>Many environments have adopted beta versions of Tomcat 3.2 
>with the anticipation
>that it will continue to be supported.  What these folks need is quick
>turnaround on bugs that are discovered after the 3.2 final 
>release, and/or when
>outstanding issues that are already known are resolved.
>
>Therefore, I propose that we begin accepting and processing 
>patches to the
>existing code base (i.e. the "tomcat_32" branch), and produce 
>maintenance
>releases of this version (3.2.1, 3.2.2, and so on) as 
>appropriate.  Such fixes
>will be minimal risk bug fixes to the existing code -- not new 
>features.  As
>such, this proposal is completely independent of any major 
>development efforts
>on any other code base.
>

+1 (the dreaded ajp13 need to be fixed)

>(3) Release Manager for Tomcat 3.2.x Maintenance Releases
>
>In order to ensure that the ball doesn't get dropped (again 
>:-) on 3.2, we need
>to ensure that a release manager has been identified who has 
>the time to test
>and integrate new patches, and create timely releases, in 
>accordance to the
>ongoing support plan identified in the previous proposal.
>
>I am willing to continue this role for the 3.2.x code series 
>(at least for a
>couple of releases), but would happily assist any other 
>committer who wished to
>gain the thanks of the Tomcat 3.2 user community for taking on 
>this important
>task.  (NOTE:  I will be involved in bug fixes for 3.2.x even 
>if I'm not the
>release manager.)
>
>A +1 vote on this says "I'm fine with Craig continuing this 
>role."  A -1 is
>likely to lead to you getting nominated to take my place :-).  
>Any other
>volunteers, please feel free to speak up!
>

+1 (you did a nice job, but will you do that also for 4.0 ?)

Re: [VOTE] Tomcat 3.2 Final Release (!) and Ongoing Maintenance Plan

["Craig R. McClanahan" <Cr...@eng.sun.com>]

GOMEZ Henri wrote:

> >(1) Build and release Tomcat 3.2 final on Wednesday 11/29/2000
> >
>
> +1 (known bugs to be fixed in 3.2.1 - Did you apply the patch from Clinton,
> Doug [dclinton@tanning.com]
>

Is that the fix for the RequestDispatcher.forward() problem?  If so, then I have not
done so.  Are you completely confident that the patch works as advertised, with no
harmful effects?  (You have a lot more experience with AJP13 than I do).  If so, I can
go ahead and commit it.

Craig