I started the process of migrating camel-extra to apachextras.org [1]. I would suggest waiting for the transition to take place and release them both at the same time and start maintaining camel-extra better. There are also a few fixes we need for rat.
I am all for releasing early. I hope we'll continue to release more often in the future too, not just make an exception with 2.7. If the community decides not to wait for camel-extra, I can start the release builds earlier. I added a comment to the google issue, hopefully they'll answer and that will help us decide. My $0.02, Hadrian [1] http://code.google.com/p/support/issues/detail?id=4979 On Feb 18, 2011, at 7:19 AM, Claus Ibsen wrote: > Hi > > Now that the major migration efforts for Camel 2.7 is in-house > (JDK1.6,spring3,slf4j, etc.). and the fact that we did this really > fast. > Thanks everyone. > > I would like to propose that we consider doing an earlier release of > Camel 2.7, then the usual 3 months release cycle. > The reason is I would like people to give the community the chance to > take and upgrade their Camel applications to Camel 2.7. > And then report back if there was any issues doing so. > > By having a shorter release cycle then the release is focused about > those changes, and not the usual bunch of 300 JIRA tickets resolved. > So if there is something that makes upgrading 2.x -> 2.7 problematic > or impossible, then we have a better chance to catch this earlier. > > Then the Camel 2.8 release can follow and be released at the usual timeframe. > > I propose to > =========== > - Release Camel 2.7 at the end of this month > - Release Camel 2.8 at the usual time, which would be in mid / end of April. > > You thoughts? > > > And are there any tickets which is a must have for a Camel 2.7 release? > > > > -- > Claus Ibsen > ----------------- > FuseSource > Email: cib...@fusesource.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.blogspot.com/ > Author of Camel in Action: http://www.manning.com/ibsen/
