Hi Yeah it would be nice to get camel-extra released as a follow up to any of the Camel minor releases, eg 2.9.0 2.10.0, 2.11.0. I am not sure if we can keep up with all the patch releases, as camel-extra ought to be compatible.
On Mon, Jun 25, 2012 at 12:42 PM, Henryk Konsek <hekon...@gmail.com> wrote: >> I'm already delayed with camel-extra 2.9.0 :-( See [1] >> I already tagged a release but didn't uploaded the artifacts and signatures >> until now. I plan to upload it to [2] where the 2.8.0 artifacts already are. > > I want to contribute new component to Camel Extra (JGroups [1], which is > LGPL). > > If we are already delayed with Camel Extra 2.9, then maybe we could > also tag a 2.10 release? In such case Camel Extra trunk's snapshot > version will be in order with a "mainstream Camel". > > BTW I can help you with releasing Camel Extra artifacts. With my new > JGroups and existing DB4O component I'll be author of 20% of Camel > extra components, so I feel emotionally connected to it :) . In the > future there will be probably more stuff in Camel Extra, so it will be > good to have the issue of Camel Extra releases organized. > > After releasing the artifacts of 2.9 and 2.10 we could also push > forward a topic of synchronizing Camel Extra with Maven Central. > > I propose to start with tagging 2.10 release (to be in sync with main > Camel). Can we tag the 2.10 release? Should you start a vote for it or > something? > > Laters. > > [1] http://www.jgroups.org/license.html > > -- > Henryk Konsek > http://henryk-konsek.blogspot.com -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
