Jean-Baptiste,
I'm not going to stop anyone who's volunteering to cut a release ;), but I think we need to decide which way to go first: - either do a 3.5.0 that corresponds with the upcoming 4.5.0 release (and probably another 3.6.0/4.6.0 set later this year), upgrading to new minor versions of CXF/Camel and reusing the utils/JBI components releases that are being done for the 4.x release - or else, as Claus suggested, stick with ServiceMix 3.4.x and sticking with Camel 2.8.x and CXF 2.4.x for ServiceMix 3 As I mentioned before (quoting myself for a sec here), the drawback of the latter approach is that it's a bit more work to set up the extra JBI component branch, backport a few bug fixes made on trunk and afterwards maintain the branch for a few more months and to cut the extra JBI components releases for the one or two remaining micro version of 3.4.x. The benefit would obviously be that it's more clear as an EOL strategy and that we might have less work updating the examples in the ServiceMix 3 build to work with newer version of Camel and CXF. Either solution works for me - we just need a decision here before we can move along... Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Sat, Jun 2, 2012 at 8:58 AM, Jean-Baptiste Onofré <[email protected]> wrote: > +1 for end of 2012 > > In that case, what do you think if I prepare a "dependency update" release > (to update CXF, Camel, etc) ? > > Regards > JB > > > On 05/22/2012 12:03 PM, Gert Vanthienen wrote: >> >> L.S., >> >> >> Redirecting diwakar's question into a new thread to separate it from the >> future of ServiceMix discussion. We have had this pop up a few more times >> now, where we generally recommend people to look at ServiceMix 4 and point >> them towards Camel and CXF directly instead of looking at JBI, but we >> never >> explicitly decided on when/how to end support for ServiceMix 3.x. It >> would >> be a good idea if we could come up with a consensus on a date/final >> release >> version of ServiceMix 3.x so at least we can start communicating that more >> clearly to our user base. >> >> What do you guys think would be a good EOL scenario for ServiceMix 3.x ? >> How can we best start communicating this to our users (add warnings to >> the >> download pages, a blog post, a news item, ...)? >> >> >> Regards, >> >> Gert Vanthienen >> ------------------------ >> FuseSource >> Web: http://fusesource.com >> Blog: http://gertvanthienen.blogspot.com/ >> >> >> On Tue, May 22, 2012 at 10:51 AM, diwakar<[email protected]> wrote: >> >>> Hi, >>> >>> Thanks for the post Paul. >>> Will ASF at least maintain Servicemix 3.x with JBI (no need for >>> new feature development)? >>> >>> With Best Regards, >>> Diwakar >>> >>> >>> -- >>> View this message in context: >>> >>> http://servicemix.396122.n5.nabble.com/DISCUSS-ServiceMix-future-tp3212177p5713316.html >>> Sent from the ServiceMix - Dev mailing list archive at Nabble.com. >>> >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
