Hi Cristiano,
Yeah, if we can pick up an upgrade of Karaf as well for 5.1.0 (or any other upgrade, for that matter), that would be even better. The only thing we have to watch out for is that things work properly together and that we don't end up waiting for the next great release for all of our dependencies, but other than that I'm definitely +1 on upgrading other stuff too. For Karaf: I just noticed this thread on the karaf-dev list though (http://karaf.922171.n3.nabble.com/On-Karaf-2-3-x-stay-with-Spring-3-2-5-RELEASE-td4032399.html) which looks like it might impact us too if we upgrade to 2.4.0. Regards, Gert Vanthienen On Tue, Mar 25, 2014 at 1:48 PM, Cristiano Costantini <[email protected]> wrote: > Hi Gert, > I've seen on the mailing list of Karaf that also the release 2.4.0 is going > to be out soon. > I would add this to the list of significant updates to be done together > with Camel for SMX 5.1.0. > > For the rest, I agree with your ideas. > > Cristiano > > > > > > > 2014-03-25 13:39 GMT+01:00 Gert Vanthienen <[email protected]>: > >> L.S., >> >> >> Now that we released Apache ServiceMix 5.0.0, we should start planning >> for our next releases. >> >> There already is a Camel 2.13.0 release out, so it would be good if we >> could do a ServiceMix release with that new Camel version sometime >> soon. We also want to start working on a Karaf 3 based release >> somewhere in the future too. >> >> How about we ...? >> - create a servicemix-5.0.x branch to do bugfixes and micro version >> upgrades on the 5.0.0 release >> - create a servicemix-5.1.x branch to do the upgrade to Camel 2.13.0 >> and get a 5.1.0 release out >> - start working towards a Karaf 3 based release in trunk >> >> >> Regards, >> >> Gert Vanthienen >>
