You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Remy Maucherat <re...@apache.org> on 2003/08/04 11:16:54 UTC
[VOTE] Tomcat 5.0 release plan
I have updated the dates mentioned in the release plan (given that
Tomcat 5 can't go to beta before the end of last month ;-) ). It now
calls for a beta before the 15th of August, which means either Tomcat
5.0.6 or 5.0.7 would have to be declared beta to fit the schedule
(assuming the one release per week keeps on, plus one week test/vote to
decide on the build stability). Of course, the release plan would be
affected by last minute changes or delays in the Servlet and JSP
specifications.
I consider the current 5.0.6 build to be feature complete, so I believe
this schedule is realistic. I volunteer to continue being the release
manager for this Tomcat branch.
This release plan vote if a maority vote. Please send any comments on
the release plan ASAP if some modifications are required.
<ballot>
[ ] +1 I approve this release plan, and I will help
[ ] +0 I approve this release plan
[ ] -0 I disagree with the release plan
[ ] -1 I am against this release plan
</ballot>
<comments>
</comments>
Remy
Re: [VOTE] Tomcat 5.0 release plan
Posted by Costin Manolache <cm...@yahoo.com>.
Remy Maucherat wrote:
> I have updated the dates mentioned in the release plan (given that
> Tomcat 5 can't go to beta before the end of last month ;-) ). It now
> calls for a beta before the 15th of August, which means either Tomcat
> 5.0.6 or 5.0.7 would have to be declared beta to fit the schedule
> (assuming the one release per week keeps on, plus one week test/vote to
> decide on the build stability). Of course, the release plan would be
> affected by last minute changes or delays in the Servlet and JSP
> specifications.
>
> I consider the current 5.0.6 build to be feature complete, so I believe
> this schedule is realistic. I volunteer to continue being the release
> manager for this Tomcat branch.
>
> This release plan vote if a maority vote. Please send any comments on
> the release plan ASAP if some modifications are required.
>
> <ballot>
> [ ] +1 I approve this release plan, and I will help
> [X] +0 I approve this release plan
> [ ] -0 I disagree with the release plan
> [ ] -1 I am against this release plan
> </ballot>
For the next few months I can't help too much - really sorry, but my work
schedule is crazy.
Costin
Re: [OT] New job
Posted by Costin Manolache <cm...@yahoo.com>.
Remy Maucherat wrote:
> This is OT, sorry.
>
> I've accepted a position of Consultant at the JBoss Group, where I will
> help maintain the JBoss / Tomcat integration (which has become
> especially important since their decision to use Tomcat as their default
> servlet container in the upcoming JBoss releases), spend a significant
> amount of time working on Tomcat (as before), and provide commercial
> support / consulting / training on Tomcat.
>
> So the cool part is that my Tomcat work is funded again :)
Great !!!
Isn't it nice to be able to do some open source as part of your day job ?
:-)
Costin
Re: [OT] New job
Posted by Costin Manolache <cm...@yahoo.com>.
Remy Maucherat wrote:
> This is OT, sorry.
>
> I've accepted a position of Consultant at the JBoss Group, where I will
> help maintain the JBoss / Tomcat integration (which has become
> especially important since their decision to use Tomcat as their default
> servlet container in the upcoming JBoss releases), spend a significant
> amount of time working on Tomcat (as before), and provide commercial
> support / consulting / training on Tomcat.
>
> So the cool part is that my Tomcat work is funded again :)
Great !!!
Isn't it nice to be able to do some open source as part of your day job ?
:-)
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
[OT] New job
Posted by Remy Maucherat <re...@apache.org>.
This is OT, sorry.
I've accepted a position of Consultant at the JBoss Group, where I will
help maintain the JBoss / Tomcat integration (which has become
especially important since their decision to use Tomcat as their default
servlet container in the upcoming JBoss releases), spend a significant
amount of time working on Tomcat (as before), and provide commercial
support / consulting / training on Tomcat.
So the cool part is that my Tomcat work is funded again :)
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
[OT] New job
Posted by Remy Maucherat <re...@apache.org>.
This is OT, sorry.
I've accepted a position of Consultant at the JBoss Group, where I will
help maintain the JBoss / Tomcat integration (which has become
especially important since their decision to use Tomcat as their default
servlet container in the upcoming JBoss releases), spend a significant
amount of time working on Tomcat (as before), and provide commercial
support / consulting / training on Tomcat.
So the cool part is that my Tomcat work is funded again :)
Remy
Re: [VOTE] Tomcat 5.0 release plan
Posted by Tim Funk <fu...@joedog.org>.
Remy Maucherat wrote:
>
> <ballot>
> [X] +1 I approve this release plan, and I will help
> [ ] +0 I approve this release plan
> [ ] -0 I disagree with the release plan
> [ ] -1 I am against this release plan
> </ballot>
>
<comments>
I will be without a computer (therefore not checking email) next week aug 10-17.
</comments>
Re: [VOTE] Tomcat 5.0 release plan
Posted by Tim Funk <fu...@joedog.org>.
Remy Maucherat wrote:
>
> <ballot>
> [X] +1 I approve this release plan, and I will help
> [ ] +0 I approve this release plan
> [ ] -0 I disagree with the release plan
> [ ] -1 I am against this release plan
> </ballot>
>
<comments>
I will be without a computer (therefore not checking email) next week aug 10-17.
</comments>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] [5.0.6] Stability ratings
Posted by Remy Maucherat <re...@apache.org>.
Remy Maucherat wrote:
> <ballot>
> [X] Alpha
> [ ] Beta
> </ballot>
I am going to vote alpha for this build, because of the wealth of small
bugs I just fixed (manager, the fix for the old cross context problem,
etc). It is encouraging that people are showing up to test it, and it
seems the build stability is good enough to make 5.0.7 a likely beta
(which would allow to meet the schedule :) ).
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] [5.0.6] Stability ratings
Posted by Remy Maucherat <re...@apache.org>.
Remy Maucherat wrote:
> <ballot>
> [X] Alpha
> [ ] Beta
> </ballot>
I am going to vote alpha for this build, because of the wealth of small
bugs I just fixed (manager, the fix for the old cross context problem,
etc). It is encouraging that people are showing up to test it, and it
seems the build stability is good enough to make 5.0.7 a likely beta
(which would allow to meet the schedule :) ).
Remy
[VOTE] [5.0.6] Stability ratings
Posted by Remy Maucherat <re...@apache.org>.
<ballot>
[ ] Alpha
[ ] Beta
</ballot>
Add comments if needed :)
Remy
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
[VOTE] [5.0.6] Stability ratings
Posted by Remy Maucherat <re...@apache.org>.
<ballot>
[ ] Alpha
[ ] Beta
</ballot>
Add comments if needed :)
Remy
Re: [VOTE] Tomcat 5.0 release plan
Posted by Jean-Francois Arcand <Je...@Sun.COM>.
+1
-- Jeanfrancois
Remy Maucherat wrote:
> I have updated the dates mentioned in the release plan (given that
> Tomcat 5 can't go to beta before the end of last month ;-) ). It now
> calls for a beta before the 15th of August, which means either Tomcat
> 5.0.6 or 5.0.7 would have to be declared beta to fit the schedule
> (assuming the one release per week keeps on, plus one week test/vote to
> decide on the build stability). Of course, the release plan would be
> affected by last minute changes or delays in the Servlet and JSP
> specifications.
>
> I consider the current 5.0.6 build to be feature complete, so I believe
> this schedule is realistic. I volunteer to continue being the release
> manager for this Tomcat branch.
>
> This release plan vote if a maority vote. Please send any comments on
> the release plan ASAP if some modifications are required.
>
> <ballot>
> [ ] +1 I approve this release plan, and I will help
> [ ] +0 I approve this release plan
> [ ] -0 I disagree with the release plan
> [ ] -1 I am against this release plan
> </ballot>
>
> <comments>
> </comments>
>
> Remy
>
>
> ------------------------------------------------------------------------
>
> $Id: RELEASE-PLAN-5.0.txt,v 1.2 2003/08/04 08:17:02 remm Exp $
>
> Release Plan for Apache Tomcat 5.0
> ==================================
>
>
> Introduction:
> ------------
>
> This document is a release plan for the final release of Apache Tomcat 5.0.
>
> The goal of the Apache Tomcat 5.0 final release is to provide a stable
> container that supports 100% of the mandatory requirements of the Servlet 2.4
> and JSP 2.0 specifications, as well as to improve and add many useful
> additional features on top of the existing Apache Tomcat 4.1.x releases.
>
> Apache Tomcat 5.0 includes the following major new features over
> Apache Tomcat 4.1:
>
> * Performance optimizations and reduced garbage collection
> * Refactored application deployer, with an optional standalone deployer
> allowing validation and compilation of a web application before putting
> it in production
> * Complete server monitoring using JMX and the manager web application
> * Scalability and reliability enhancements
> * Improved Taglibs handling, including advanced pooling and tag plugins
> * Improved platform integration, with native Windows and Unix wrappers
> * Embedding of Tomcat using JMX
> * Expanded documentation
>
> Apache Tomcat 5.0 will use the build numbering and release process first used
> in the Apache HTTPd 2.0.x project.
> Milestone builds, numbered 5.0.x, will be released as needed and will
> recieve a stability rating after a one week testing period. The rating can be
> either: Alpha, Beta, or Stable.
>
> This Release Plan proposes the following prospective target dates
> for stability:
>
> Middle of August, 2003
> ----------------------
>
> Tomcat 5.0 should reach Beta status by this date.
>
> Servlet 2.4 and JSP 2.0 Final Specification Releases (expected by 09/2003)
> ----------------------------------------------------
>
> At least another Beta rated release should be made simultaneous to the release
> of the specification.
>
> Two to four weeks after Final Specification Releases
> ----------------------------------------------------
>
> Best effort should be made for Tomcat 5.0 to reach Stable status as soon as
> possible after the specification releases. However, it should be pointed out
> that wide testing cannot occur before the specifications are released, so
> a Stable release should only be made after a period of time.
>
> In order to complete a first Stable release, all outstanding Bugzilla bug
> reports against Tomcat 5.0 above NORMAL severity need to be fixed or deferred
> for later releases.
>
> This Release Plan proposes the following classification of current outstanding
> bug reports in the bug tracking system, sorted by component and their ID
> numbers in our bug tracking system at:
>
> http://nagoya.apache.org/bugzilla/
>
> Please review the bug reports, and their severity accordingly.
>
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] Tomcat 5.0 release plan
Posted by Costin Manolache <cm...@yahoo.com>.
Remy Maucherat wrote:
> I have updated the dates mentioned in the release plan (given that
> Tomcat 5 can't go to beta before the end of last month ;-) ). It now
> calls for a beta before the 15th of August, which means either Tomcat
> 5.0.6 or 5.0.7 would have to be declared beta to fit the schedule
> (assuming the one release per week keeps on, plus one week test/vote to
> decide on the build stability). Of course, the release plan would be
> affected by last minute changes or delays in the Servlet and JSP
> specifications.
>
> I consider the current 5.0.6 build to be feature complete, so I believe
> this schedule is realistic. I volunteer to continue being the release
> manager for this Tomcat branch.
>
> This release plan vote if a maority vote. Please send any comments on
> the release plan ASAP if some modifications are required.
>
> <ballot>
> [ ] +1 I approve this release plan, and I will help
> [X] +0 I approve this release plan
> [ ] -0 I disagree with the release plan
> [ ] -1 I am against this release plan
> </ballot>
For the next few months I can't help too much - really sorry, but my work
schedule is crazy.
Costin
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: [VOTE] Tomcat 5.0 release plan
Posted by Jean-Francois Arcand <Je...@Sun.COM>.
+1
-- Jeanfrancois
Remy Maucherat wrote:
> I have updated the dates mentioned in the release plan (given that
> Tomcat 5 can't go to beta before the end of last month ;-) ). It now
> calls for a beta before the 15th of August, which means either Tomcat
> 5.0.6 or 5.0.7 would have to be declared beta to fit the schedule
> (assuming the one release per week keeps on, plus one week test/vote to
> decide on the build stability). Of course, the release plan would be
> affected by last minute changes or delays in the Servlet and JSP
> specifications.
>
> I consider the current 5.0.6 build to be feature complete, so I believe
> this schedule is realistic. I volunteer to continue being the release
> manager for this Tomcat branch.
>
> This release plan vote if a maority vote. Please send any comments on
> the release plan ASAP if some modifications are required.
>
> <ballot>
> [ ] +1 I approve this release plan, and I will help
> [ ] +0 I approve this release plan
> [ ] -0 I disagree with the release plan
> [ ] -1 I am against this release plan
> </ballot>
>
> <comments>
> </comments>
>
> Remy
>
>
> ------------------------------------------------------------------------
>
> $Id: RELEASE-PLAN-5.0.txt,v 1.2 2003/08/04 08:17:02 remm Exp $
>
> Release Plan for Apache Tomcat 5.0
> ==================================
>
>
> Introduction:
> ------------
>
> This document is a release plan for the final release of Apache Tomcat 5.0.
>
> The goal of the Apache Tomcat 5.0 final release is to provide a stable
> container that supports 100% of the mandatory requirements of the Servlet 2.4
> and JSP 2.0 specifications, as well as to improve and add many useful
> additional features on top of the existing Apache Tomcat 4.1.x releases.
>
> Apache Tomcat 5.0 includes the following major new features over
> Apache Tomcat 4.1:
>
> * Performance optimizations and reduced garbage collection
> * Refactored application deployer, with an optional standalone deployer
> allowing validation and compilation of a web application before putting
> it in production
> * Complete server monitoring using JMX and the manager web application
> * Scalability and reliability enhancements
> * Improved Taglibs handling, including advanced pooling and tag plugins
> * Improved platform integration, with native Windows and Unix wrappers
> * Embedding of Tomcat using JMX
> * Expanded documentation
>
> Apache Tomcat 5.0 will use the build numbering and release process first used
> in the Apache HTTPd 2.0.x project.
> Milestone builds, numbered 5.0.x, will be released as needed and will
> recieve a stability rating after a one week testing period. The rating can be
> either: Alpha, Beta, or Stable.
>
> This Release Plan proposes the following prospective target dates
> for stability:
>
> Middle of August, 2003
> ----------------------
>
> Tomcat 5.0 should reach Beta status by this date.
>
> Servlet 2.4 and JSP 2.0 Final Specification Releases (expected by 09/2003)
> ----------------------------------------------------
>
> At least another Beta rated release should be made simultaneous to the release
> of the specification.
>
> Two to four weeks after Final Specification Releases
> ----------------------------------------------------
>
> Best effort should be made for Tomcat 5.0 to reach Stable status as soon as
> possible after the specification releases. However, it should be pointed out
> that wide testing cannot occur before the specifications are released, so
> a Stable release should only be made after a period of time.
>
> In order to complete a first Stable release, all outstanding Bugzilla bug
> reports against Tomcat 5.0 above NORMAL severity need to be fixed or deferred
> for later releases.
>
> This Release Plan proposes the following classification of current outstanding
> bug reports in the bug tracking system, sorted by component and their ID
> numbers in our bug tracking system at:
>
> http://nagoya.apache.org/bugzilla/
>
> Please review the bug reports, and their severity accordingly.
>
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org