On Fri, Jan 18, 2013 at 6:33 PM, Christian Müller <christian.muel...@gmail.com> wrote: > Have in mind the trunk is already 2.11-SNAPSHOT. You have to create a > camel-extra-2.10.x maintenane branch first and merge your changes from > trunk into this branche. Afterwards you can release camel-extra-2.10.1. >
I dont think we need to fix camel-extra at every matching ASF Camel release. There is a camel-extra 2.10.0 release and that is fine IMHO. The next could just be the 2.11.0 which has the OSGi features XML file. So we introduce the OSGi features in the 2.11 onwards. > Sent from a mobile device > Am 18.01.2013 11:34 schrieb "Henryk Konsek" <hekon...@gmail.com>: > >> Hi, >> >> I wanted to proceed with the missing camel-extra releases, but I found >> out that zeromq component tests sometimes fails (~20% of runs). >> >> The cause was the ZeromqConsumerTest#stopInterruptsExecutor test. The >> assertions in tests could not be satisfied if executor didn't manage >> to close the jobs after call to the ExecutorService#shutdownNow >> method. >> >> I refactored the test (rev962) to make it more "Mockito-sh" and thread >> safe. >> >> I'll continue with releasing Camel Extra from this point. The one >> thing I want to fix before 2.10.1 release is OSGI Camel imports issue >> [1]. >> >> Best regards. >> >> [1] >> http://code.google.com/a/apache-extras.org/p/camel-extra/issues/detail?id=30 >> >> -- >> Henryk Konsek >> http://henryk-konsek.blogspot.com >> -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
