+1 on 2 /je
On Jan 12, 2011, at 9:03 AM, Gert Vanthienen wrote: > L.S., > > > Originally, we were planning to release ServiceMix 4.3.0 with Camel > 2.5 and we already released components and NMR to use that version. > However, with https://issues.apache.org/jira/browse/SMX4-652 we're > running into an issue with that version of Camel (cfr. > https://issues.apache.org/jira/browse/CAMEL-3302). One way to fix > this would be to redo the components release and add a hack as a > workaround for this issue. We could do that today or tomorrow and get > the release process back on track that way. > > However, the Camel 2.6.0 release is due to get cut anytime soon, > they're currently waiting on our pending bundles vote to move ahead. > I think it would be worth waiting another week and then restart the > release process using Camel 2.6.0 and CXF 2.3.1 instead of the current > versions. That would allow us to pick up the latest versions of those > two important frameworks in ServiceMix as well as avoid the hack > around the issue in the components build. > > If we go for option 2, I would like to suggest we're careful about > adding new stuff to the Components/NMR/Features build in the > meanwhile. The first two have already been released a few weeks ago > without any problems, so if we only fix bugs and update the Camel and > CXF version, we can be a bit more confident in the upcoming new > release builds and votes. > > The quiet period between now and the releases would be a great time to > start the documentation hackaton by the way ;) > > > Wdyt? > > Gert Vanthienen > ------------------------ > FuseSource > Web: http://fusesource.com > Blog: http://gertvanthienen.blogspot.com/
