cvs commit: jakarta-tomcat-4.0 RELEASE-PLAN-4.1.txt
remm02/04/25 01:59:51 Modified:.RELEASE-PLAN-4.1.txt Log: - Update status. - Update with new build numbering scheme. Revision ChangesPath 1.5 +9 -9 jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt Index: RELEASE-PLAN-4.1.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- RELEASE-PLAN-4.1.txt 24 Apr 2002 11:59:03 - 1.4 +++ RELEASE-PLAN-4.1.txt 25 Apr 2002 08:59:51 - 1.5 @@ -1,4 +1,4 @@ -$Id: RELEASE-PLAN-4.1.txt,v 1.4 2002/04/24 11:59:03 remm Exp $ +$Id: RELEASE-PLAN-4.1.txt,v 1.5 2002/04/25 08:59:51 remm Exp $ Release Plan for Apache Tomcat 4.1 == @@ -28,18 +28,19 @@ from build.xml scripts. * Many other miscanellous improvements -This Release Plan proposes the following schedule: - - Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 +Apache Tomcat 4.1 will use the build numbering and release process first used +in the Apache HTTPd 2.0.x project. +Milestone builds, numbered 4.1.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. - Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 +This Release Plan proposes the following schedule: - Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate + Friday, April 26, 2002 Apache Tomcat 4.1.0 In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for -later releases. After the first 4.1 Release Candidate, other RC releases may -be made as needed until one is promoted as Final by the Tomcat committers. +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 @@ -78,7 +79,6 @@ 5585 Error page not displayed 5666 Implicit object _value on jsp pages 5793 variable element in tld with TagExtraInfo class -5903 version attribute in jsp:root 6196 jsp:forward should trigger IllegalStateException when buffer flushed 6908 JavaCompiler interface setOutputDir always called with null parameter 7007 Invalid names in web.xml generated by JspC for top-level JSP pages -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RELEASE-PLAN-4.1.txt
remm02/04/25 15:00:19 Modified:.RELEASE-PLAN-4.1.txt Log: - Update status. - 5199 looks like something which is unclear in the spec (I'll discuss that more in detail later). Revision ChangesPath 1.7 +2 -4 jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt Index: RELEASE-PLAN-4.1.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- RELEASE-PLAN-4.1.txt 25 Apr 2002 19:51:40 - 1.6 +++ RELEASE-PLAN-4.1.txt 25 Apr 2002 22:00:19 - 1.7 @@ -1,4 +1,4 @@ -$Id: RELEASE-PLAN-4.1.txt,v 1.6 2002/04/25 19:51:40 remm Exp $ +$Id: RELEASE-PLAN-4.1.txt,v 1.7 2002/04/25 22:00:19 remm Exp $ Release Plan for Apache Tomcat 4.1 == @@ -75,10 +75,7 @@ -- 4964 popBody() is called before doEndTag() is called in a BodyTag -5199 jsp:param in jsp:include section not correct -5666 Implicit object _value on jsp pages 5793 variable element in tld with TagExtraInfo class -6908 JavaCompiler interface setOutputDir always called with null parameter 7059 Jasper compiler holds pointers to jars in WEB-INF/lib: cannot delete 7989 jsp:setProperty and jsp:getProperty ignore information from jsp:useBean @@ -90,6 +87,7 @@ 4350 SSLAuthenticator did not associate SSO session +5199 jsp:param in jsp:include section not correct 5352 JDBCRealm does not work with CLIENT-CERT auth-method 5551 MANAGER: add system information query 5603 ServletContext.getResourcePaths() returns extra slashes -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RELEASE-PLAN-4.1.txt
remm02/04/24 04:59:03 Modified:.RELEASE-PLAN-4.1.txt Log: - Update bug status. Revision ChangesPath 1.4 +1 -6 jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt Index: RELEASE-PLAN-4.1.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- RELEASE-PLAN-4.1.txt 23 Apr 2002 18:32:11 - 1.3 +++ RELEASE-PLAN-4.1.txt 24 Apr 2002 11:59:03 - 1.4 @@ -1,4 +1,4 @@ -$Id: RELEASE-PLAN-4.1.txt,v 1.3 2002/04/23 18:32:11 remm Exp $ +$Id: RELEASE-PLAN-4.1.txt,v 1.4 2002/04/24 11:59:03 remm Exp $ Release Plan for Apache Tomcat 4.1 == @@ -61,14 +61,11 @@ Catalina -5166 CATALINA_BASE config issues for RUNNING.txt 5735 HTTP connector running out of processors under heavy load 5829 StandardManager needs to cope with sessions throwing exception in read/write 5895 Not all sessions receives HttpSessionListener.sessionDestroyed(event) using FileStore -6662 servlet context fails if webapp name smaller version of another webapp -7575 Throwing UnavailableException in JSP's init disables JSP servlet 7656 Webapplications deployed using PUT don't survive a tomcat restart 8087 HttpSessionAttributeListener.attributeRemoved() not working with URLRewriting @@ -83,9 +80,7 @@ 5793 variable element in tld with TagExtraInfo class 5903 version attribute in jsp:root 6196 jsp:forward should trigger IllegalStateException when buffer flushed -6907 jsp compiler not synchronized 6908 JavaCompiler interface setOutputDir always called with null parameter -6909 source parameter to compile method called with mangled file path 7007 Invalid names in web.xml generated by JspC for top-level JSP pages 7059 Jasper compiler holds pointers to jars in WEB-INF/lib: cannot delete 7989 jsp:setProperty and jsp:getProperty ignore information from -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0 RELEASE-PLAN-4.1.txt
remm02/04/23 11:32:11 Modified:.RELEASE-PLAN-4.1.txt Log: - Fix typo. - Add the bug status list, contributed by Craig McClanahan. Thanks Craig ! Revision ChangesPath 1.3 +76 -2 jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt Index: RELEASE-PLAN-4.1.txt === RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- RELEASE-PLAN-4.1.txt 22 Apr 2002 15:53:25 - 1.2 +++ RELEASE-PLAN-4.1.txt 23 Apr 2002 18:32:11 - 1.3 @@ -1,4 +1,4 @@ -$Id: RELEASE-PLAN-4.1.txt,v 1.2 2002/04/22 15:53:25 remm Exp $ +$Id: RELEASE-PLAN-4.1.txt,v 1.3 2002/04/23 18:32:11 remm Exp $ Release Plan for Apache Tomcat 4.1 == @@ -49,7 +49,7 @@ Please review the bug reports, and their classification as must have, nice to have, or address later. Lobbying for changes in classification -can take place on the TOMCAT-DEV mailling list. In addition, if you have a +can take place on the TOMCAT-DEV mailing list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. @@ -58,11 +58,85 @@ Bugs That Must Be Addressed Before Final Release: +Catalina + +5166 CATALINA_BASE config issues for RUNNING.txt +5735 HTTP connector running out of processors under heavy load +5829 StandardManager needs to cope with sessions throwing exception in + read/write +5895 Not all sessions receives HttpSessionListener.sessionDestroyed(event) + using FileStore +6662 servlet context fails if webapp name smaller version of another webapp +7575 Throwing UnavailableException in JSP's init disables JSP servlet +7656 Webapplications deployed using PUT don't survive a tomcat restart +8087 HttpSessionAttributeListener.attributeRemoved() not working with + URLRewriting + +Jasper +-- + +4964 popBody() is called before doEndTag() is called in a BodyTag +5199 jsp:param in jsp:include section not correct +5585 Error page not displayed +5666 Implicit object _value on jsp pages +5793 variable element in tld with TagExtraInfo class +5903 version attribute in jsp:root +6196 jsp:forward should trigger IllegalStateException when buffer flushed +6907 jsp compiler not synchronized +6908 JavaCompiler interface setOutputDir always called with null parameter +6909 source parameter to compile method called with mangled file path +7007 Invalid names in web.xml generated by JspC for top-level JSP pages +7059 Jasper compiler holds pointers to jars in WEB-INF/lib: cannot delete +7989 jsp:setProperty and jsp:getProperty ignore information from + jsp:useBean Nice To Have Fixes Before Final Release: --- +Catalina + + +4350 SSLAuthenticator did not associate SSO session +5352 JDBCRealm does not work with CLIENT-CERT auth-method +5551 MANAGER: add system information query +5603 ServletContext.getResourcePaths() returns extra slashes +5704 CgiServlet corrupting images? +5758 Server-side includes do not work properly +5762 CGI servlet misses to include port number in HTTP_HOST environment + variable +5764 Key Information Missing--Automatic Application Deployment +5858 Add tomcat dir to java.library.path +5899 HTTP POST parameters ignored in CGIServlet.java +6185 JNDIRealm working with IPlanet 5.1 +6206 Sixteen Lifecycle implementers disagree with Lifecycle API docs +6229 Need way to specify where to write catalina.out +6281 JDBCRealm+Form Login+URL re-writing session=broken +6299 SSI problem with multiple include statements in one file +6431 JNDIRealm.getRoles() should return more than a single role attribute +6797 Class loader fails if it can't read entire tree upto a classfile +6884 Need Better Error Handling in WebappClassLoader.validateJarFile +7043 database user and password for JDBC Based Store +7080 Interbase JDBCRealm - Bug # 5564 - Have a safe fix +7082 Calling an RMI Server from a servlet produces stack trace +7116 JDBC realm doesn't handle NULLpasswords +7139 Typo in manager.xml documentation +7359 Classloader problems with RMI +7360 res-sharing-scope not supported +7402 Localized responseStream.suspended message not found +7445 Can not set verbosity property of the FileLogger via server.xml + configuration file +7984 class org.apache.catalina.logger.FileLogger should be public +8323 No support for running the 64 bit JVM + +Jasper +-- + +6858 Easy Significant Performance Improvement +7160 Jasper compiles files to same classname +7993
cvs commit: jakarta-tomcat-4.0 RELEASE-PLAN-4.1.txt
remm02/04/22 08:12:23 Added: .RELEASE-PLAN-4.1.txt Log: - Major features have been added to Tomcat since 4.0.x (list of the major features is included in the document), and as all (but one) is now feature complete, I think it is time to start a new release cycle. - The proposed release cycle is short, as the codebase is an evolution of the 4.0.x codebase, and has recieved all the bugfixes introduced in the 4.0.x branch. Revision ChangesPath 1.1 jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt Index: RELEASE-PLAN-4.1.txt === $Id: RELEASE-PLAN-4.1.txt,v 1.1 2002/04/22 15:12:23 remm Exp $ Release Plan for Apache Tomcat 4.1 == Introduction: This document is a release plan for the *final* release of Apache Tomcat 4.1. The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. Apache Tomcat 4.1 includes the following major new features over Apache Tomcat 4.0: * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector * New Coyote JK2 AJP 1.4 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements * Many other miscanellous improvements This Release Plan proposes the following schedule: Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for later releases. After the first 4.1 Release Candidate, other RC releases may be made as needed until one is promoted as Final by the Tomcat committers. 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 classification as must have, nice to have, or address later. Lobbying for changes in classification can take place on the TOMCAT-DEV mailling list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. Bugs That Must Be Addressed Before Final Release: Nice To Have Fixes Before Final Release: --- Unconfirmed Bugs (Awaiting Reproducible Failure Case): - -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
