I suggest to open a ticket for each task which is not done yet at Google Code. @Henryk: Could you do this please!?
In my opinion we should release Camel extra 2.10.0 short term and postpone the still open tasks to Camel extra 2.10.1 or 2.11.0. Best, Christian On Wed, Sep 5, 2012 at 8:58 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > Okay I have commited to camel-extra so it supports Camel 2.10 again. > > There is a few things I want to suggest being worked on before a release. > > 1) > Upgrade all the components to latest stable release of JAR deps (eg > some are old, like the hibernate etc). > I did this for camel-esper. > > 2) > Do not use camel-core test-jar for unit testing. Should use camel-test > instead, or camel-test-spring if using spring also for testing. > > 3) > Avoid using Spring if its not really needed. > > 4) > I would love if we had a features.xml file, so it makes installing in > Karaf / SMX much easier. > Maybe not for this release. But then in the near future. > This would maybe require some OSGi bundles as well. And thus takes > longer to get done. > > 5) > Add karaf osgi tests, to ensure the components can be installed in > OSGi, as we do in tests/camel-itest-karaf at ASF Camel. > > 6) > Check the ticket tracker to see if there is any tickets to be > resolved, and get them worked on > https://code.google.com/a/apache-extras.org/p/camel-extra/issues/list > > 7) > Improve component documentation, if needed. > > > -- > 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 > --
