Hi On Thu, Mar 10, 2011 at 12:09 PM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Yeah, it's just because the Camel release was already known (which is not the > case for ActiveMQ) :)
I suggest that SMX target Camel 2.8. As to reiterate the 2.7 release was a sort of early preview for ppl to test and migrate to spot any gremlins for the jdk6/spring3/slf4j stuff. I think the Camel community would consensus that we aim to cut a Camel 2.8 release in the usual timeframe, eg in about 1.5month, so there would be about 3 months after the Camel 2.6 release. Of course we can try to align this with the SMX 4.4 timeframe, if we can cut back to eg 1 month if that's really needed. But you should respect the fact we must have time to ensure a change like that is throughly tested and works. Camel is being used in many different scenarios. Not just SMX. So let's go happy and cut the 2.7 as is. And aim for 2.8 in SMX 4.4. And in between the Karaf team may have found their gremlins in their new 2.2.0 release and cut a 2.2.1+ we can use for SMX 4.4. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
