> I am not sure if we can keep up with all the patch releases, as > camel-extra ought to be compatible.
I think we should. It should be transparent for user (as transparent as possible at least) whether she's using camel or camel-extra. This is licensing stuff, users usually do not care if they include LGPL- or Apache- licensed library in their POM file. There should be always camel-extra artifacts available in the same versions as Camel Core. I think that we need to perform the following steps: * tag 2.10 release (so Camel Extra can be in sync mainstream Camel) * release 2.9 and 2.10 artifacts * start syncing artifacts from apache-extra with Maven Central (via Sonatype I guess) * make sure that whenever new version of Camel (major and minor) is released, we release Camel-Extra as well Let's start fixing Camel-Extra state with tagging the releases so they can be in sync mainstream Camel. So... can I tag 2.10 release? (I got appropriate permissions) -- Henryk Konsek http://henryk-konsek.blogspot.com
