I wouldn't imagine these separate component releases would be able to have differing dependency versions anyway. So no win there. We would get into the situation of having multiple versions of the same lib being used across Camel. That is one of the nice things about releasing everything at once, most of the time we can align the dependency versions.
I don't yet like the idea of releasing the components separately either, sounds like it would be a lot of work for little gain. Maybe in the future we will need this but I don't think we need it now. I'm with Christian on postponing this discussion to a later 3.x release. On Thu, Feb 21, 2013 at 8:22 AM, Henryk Konsek <hekon...@gmail.com> wrote: > > If the goal is to deliver fixes to users, > > why not increase the release frequency of micro releases ? > > Micro releases don't include new features added to the components. Nor > support updates of the version of the dependencies. > > -- > Henryk Konsek > http://henryk-konsek.blogspot.com > -- Cheers, Jon --------------- Red Hat, Inc. Email: jans...@redhat.com Web: http://redhat.com Twitter: jon_anstey Blog: http://janstey.blogspot.com Author of Camel in Action: http://manning.com/ibsen
