+1 To getting newer ideas in faster. I guess the question to ponder is what are the future changes pending for 7? What are the changes for the servlet spec?
I have a feeling that the servlet spec changes are more of a playground for ideas which would bring about lots of change and potential reversions. With that in mind - it seems like it belongs in the sandbox. But sandbox might imply a private playground or its a ghetto (american slang) area of the repository that only the brave should wander into. So to test servlet spec changes, would it be better to create a branch called servlet3.1 so if new ideas come into trunk - they might not conflict for servlet 3.1 concepts? Then once servlet 3.1 goes into public review (or some similar status) - then the changes get merged back into trunk and tomcat7 gets its own branch? -Tim On Tue, Jul 26, 2011 at 1:30 PM, Mark Thomas <ma...@apache.org> 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) > > Therefore, after the next Tomcat 7 release, I would like to do the > following: > - Copy tomcat/trunk to tomcat/tc7.0.x/trunk > - Start making Servlet API changes to tomcat/trunk > > 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? > > 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? > >
