On 26/07/2011 18:30, 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)
Thanks to all those that responded. I have been through the thread and have reported the result of the discussion below. > Therefore, after the next Tomcat 7 release, I would like to do the > following: > - Copy tomcat/trunk to tomcat/tc7.0.x/trunk No objections. > - Start making Servlet API changes to tomcat/trunk Overall, there were no objections but there were some queries on why this was necessary / could it be delayed / should it be on a separate branch. I agree that there is a risk that truck gets too experimental or too far away from what everyone is comfortable with. There are three aspects to separating trunk and 7.0.x: a) spec changes b) re-factoring c) new features b) & c) should not get too experimental. If we stick to small incremental commits we can call a halt if things go to far and revert as required. a) might get experimental. My suggestion is to work with trunk for now but move to a branch if there are any new features that require lots of changes or something where the EG is undecided on and there may be significant changes. > 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? The balance of opinion was for CTR for now. I suspect the balance will shift towards RTC over time. I suggest we revisit this in ~3 months. > 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? No objections. There was a query about providing just security fixes for a further year. My suggestion is that we announce 5.5.x End-Of-Life ASAP with a date of 31 August 2012 with a caveat (as there is with 3.x, 4.x and 5.0.x) that a committer may choose to release 5.5.x after that date but that any release should not be expected or relied upon. Assuming there are no objections, I'll create 7.0.x during the next 7.0.x release and announce EOL for 5.5.x in a week or so. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
