On Thu, Mar 28, 2013 at 10:22 AM, Christian Müller <christian.muel...@gmail.com> wrote: > Ok, I fixed [1] and removed it from the official Apache Camel SVN and > update the docs. I will commit it into Camel Extra and add the docs there > in a few minutes/hours. > > We only have two outstanding issues [2]. > > I will run a "mvn release:prepare -DdryRun=true" to check whether I hit > some issues. > Do we already have a release manager for Camel 2.11 (to make sure nobody is > waiting for somebody)? >
Christian if you have the time then maybe you can be the manager? We should possible start to take turns to cut releases so we dont put all the load on one person. But that also ensures that more people know and can do a release. And also maybe that can help cutting releases a bit more frequent. Anyway thats another topic. Getting Camel 2.11 out to the community would be great. And if we get a RC, we should possible blog and promote this so we encourage more end users to give it a test spin. Before we grace the RC as GA. This is because Camel 2.11 is a big release, and Camel 2.10 was released laster summer, so its about 10 or so months ago. For example if end users have the time on a test system to upgrade existing apps and see if this upgrade process goes painless, or there is some gremlins in there. We can then possible fix that before we go GA. > [1] https://issues.apache.org/jira/browse/CAMEL-5483 > [2] > https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.11.0%22 > > Best, > Christian > > On Thu, Mar 28, 2013 at 2:18 AM, Raul Kripalani <r...@evosent.com> wrote: > >> Hi, >> >> Managed to find time to commit the improvement for CAMEL-5698. >> >> For CAMEL-5916 the fix is almost ready. Hopefully I'll reach in time before >> we cut the release. It'll be a great improvement for the usability of >> camel-cxfrs. >> >> Regards, >> Raúl. >> >> On Wed, Mar 27, 2013 at 1:30 PM, Claus Ibsen <claus.ib...@gmail.com> >> wrote: >> >> > Hi >> > >> > Oh yeah and CAMEL-5483 is a issue we must resolve. I think Hadrian is >> > working on that. >> > >> > >> > On Wed, Mar 27, 2013 at 2:25 PM, Claus Ibsen <claus.ib...@gmail.com> >> > wrote: >> > > Hi >> > > >> > > Okay we are getting there. The JIRA tracker has 3 tickets for 2.11.0. >> > > >> > >> https://issues.apache.org/jira/issues/?filter=12315472&jql=project%20%3D%20CAMEL%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.11.0%22 >> > > >> > > And I think Willem have almost/done his 2 tickets. >> > > >> > > And the last ticket CAMEL-6042 requires some documentation about this >> > > new functionality. I have asked Aaron to help with that. And it would >> > > be great with a better set of unit tests 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 >> > >> > >> > >> > -- >> > 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 >> > >> -- 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
