Mark, On 7/26/2011 1:30 PM, Mark Thomas wrote: > The Servlet EG is starting to discuss changes to the Servlet API for > 3.1. It would be useful if the option existed to implement some of these > changes in Tomcat trunk. The benefits of this are: > - we can see how feasible the API changes are to implement > - users can try out the new APIs (assuming we do a Tomcat 8 alpha release)
How much of this stuff could reasonably be built-into Tomcat 7 without breaking anything? I ask because Tomcat will have to be backward-compatible with earlier versions of the spec, anyway, so is there a real danger to adding to trunk and continuing to release 7.0.x versions from it? > Assuming that there are no objections to that plan, that leads to a > couple of other questions. > > 1. Should tomcat/tc7.0.x/trunk be RTC or CTR? If development will stay almost entirely within trunk, I would say RTC, but I'm not sure all development should be separated from the 7.0 branch (see above). > 2. With tomcat/trunk becoming the basis for Tomcat 8, I would like to > see earlier and more frequent alpha/beta releases than we had for Tomcat > 7. That would increase the effective number of versions we are > supporting. With that in mind, should we announce end of support for > 5.5.x with the last release expected in ~12 months time? +1 to announcing end of support for 5.5 in the first half of 2012. -chris
signature.asc
Description: OpenPGP digital signature
