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. >
