camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject Re: [DISCUSS] - Moving towards Camel 2.11 release
Date Tue, 12 Mar 2013 22:24:06 GMT
I still have two issues I would like to fix:

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)?


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

On Tue, Mar 12, 2013 at 1:06 PM, Claus Ibsen <> 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
> 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:
> Web:
> Twitter: davsclaus
> Blog:
> Author of Camel in Action:


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message