I still have two issues I would like to fix:
CAMEL-6121
CAMEL-5979

After coming back from my vacation, I have now some time to work on it.
So, when did you plan to cut a release? Do you plan to be the release
manager (otherwise I could do it at the next weekend)?

Best,
Christian

P.S. Can start a build over night on my Windows 8 box (virtual
environment)...


On Tue, Mar 12, 2013 at 1:06 PM, Claus Ibsen <claus.ib...@gmail.com> wrote:

> Hi
>
> So we are good on the OSGi front. The features file has been upgraded
> with the latest OSGi bundle release from the SMX team. Only
> camel-neo4j is not possible to install, and has been disabled.
>
> There is 22 unresolved tickets for Camel 2.11
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22%20AND%20resolution%20%3D%20Unresolved
>
> We should start getting those resolved. If you do not have time to
> work on your tickets, then you can move them to 2.11.1. If its really
> important to get in 2.11.0 and you do not have the time, then shout
> here on the mailing list, and we can see what we can do.
>
> And if there is any errors on the CI servers then we should work on
> fixing those as well. Though I think we are in pretty good shape there
> as well.
>
> Anyone with a Windows box is much welcome to give the source code a
> test run there as well.
>
>
>
>
> --
> 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
>



--

Reply via email to