On 23/05/2010 23:38, Mark Thomas wrote: > All, > > The next Tomcat 7.0.0 release candiate is ready for testing. 7.0.0-RC3 > can be obtained from: > http://people.apache.org/~markt/dev/tomcat-7/v7.0.0-RC3/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_0_RC3/ > > Please test this release candidate and provide feedback. > > The 7.0.0-RC3 tag is > [ ] Broken - do not release > [ ] Alpha - go ahead and release 7.0.0 Alpha based on 7.0.0-RC3 > [X] Beta - go ahead and release 7.0.0 Beta based on 7.0.0-RC3 > [ ] Stable - go ahead and release 7.0.0 Stable based on 7.0.0-RC3
Servlet TCK passes with security manager for HTTP BIO Servlet TCK passes with security manager for HTTP NIO apart from CLIENT-CERT [1] Servlet TCK passes with security manager for HTTP APR/native Servlet TCK fails with security manager for AJP BIO [2] Servlet TCK fails with security manager for AJP APR/native [3] JSP TCK passes with security manager for HTTP BIO EL TCK passes with security manager I don't see any show-stoppers in the current open bug list. The following issues were noted: - [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=49284 - [2] Security manager specific issues - fixed in r947717 - [3] Async issues - may be one issue breaking subsequent tests [1] has been thay way for numerous stable 6.0.x releases, [3] can be worked around by not using APR/native and [2] is unlikely to be an issue given that the use of a security manager is pretty rare. My Beta vote is based more on what I expect the early adopters will discover rather than these issues. I'd like to get 7.0.0 out there ASAP and start getting some user feedback. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
