Hi Krzysztof,
That looks good to me. For the Karaf 2.4.0 upgrade, I agree it would be nice if users could choose whether or not they want to do that along with the upgrade to Camel 2.14.0 - some users might prefer to bite the bullet once but others might prefer a more gradual approach. How about we keep the plan for 5.0.4, 5.1.2 and 6.0.0 as you suggested and instead of doing just one 5.2.0 release, do two releases with Camel 2.14.x: We could do a - 5.2.0 with Camel 2.14.0 and Karaf 2.3.7 - 5.3.0 with Camel 2.14.0 and Karaf 2.4.0. That way, people can choose which version of Karaf to use with Camel 2.14.x. That would give people some extra time to migrate to the newer version of Karaf if they need it - for the next minor version of Camel (2.15.0), we should drop support for Karaf 2.3.x and only use Karaf 2.4.x though to avoid we end up with an entire matrix of version combinations to support/release. Regards, Gert Vanthienen On Mon, Aug 25, 2014 at 10:20 PM, Krzysztof Sobkowiak <[email protected]> wrote: > Hi > > Camel community plans 2.14.0 release soon. I'd like to propose following: > > 1. 5.0.4 with Camel 2.12.x - still waiting for Karaf 2.3.7 > 2. 5.1.2 with Camel 2.13.x- still waiting for Karaf 2.3.7 > 3. 5.2.0 with Camel 2.14.x- Karaf 2.4.0 > 4. 6.0.0 with Camel 2.14.x - Karaf 3.0.2 > > It would be also nice to release ServiceMix with Karaf 2.3.x and Camel > 2.14.x. It would be nice to release it as 5.2.0. But 5.2.0 should be > with Karaf 2.4.0. What if we would like to make a release with Camel > 2.15.x and Karaf 2.3.x? Should we do a release based on Karaf 2.3.x and > Camel higher than 2.13.x? If yes, we should change versioning of ServiceMix > > Best regards > Krzysztof > > > > -- > Krzysztof Sobkowiak > > JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer > @ ASF > Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center > <http://www.pl.capgemini-sdm.com/> | Wroclaw > e-mail: [email protected] <mailto:[email protected]> | > Twitter: @KSobkowiak > Calendar: http://goo.gl/yvsebC
