The Camel 2.10.5 release is overdue. We released Camel 2.10.4 almost 4 month ago...
The git mirror issue is resolved. CAMEL-6309 and CAMEL-6309 are still open. Do we consider these as critical? If yes, somebody familiar with the camel-ftp component (Claus?) should have a look and fix this soon. Do we wait for something else? If we are ready beginning of next week, I could try to cut our first release using GIT if Hadrian hasn't the time to do it. Otherwise I'm happy to support him by testing the release candidate... Best, Christian Müller ----------------- Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Sun, May 26, 2013 at 7:10 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > We have some time, as I am still waiting for infra to resolve the git > mirror issue and I need to switch the release builds to use git tags > instead of svn. > > Cheers, > Hadrian > > > > On 05/25/2013 10:26 AM, Christian Müller wrote: > >> The two issues mentioned by Bengt are still open, but I can give it a >> try... >> >> Christian >> >> Sent from a mobile device >> Am 24.05.2013 13:52 schrieb "Claus Ibsen" <claus.ib...@gmail.com>: >> >> Hi >>> >>> Any news on the possibility of a 2.10.5 release. >>> >>> The next release will actually be out 50th release. So that is a good >>> milestone to reach :) >>> >>> >>> >>> On Wed, May 15, 2013 at 2:32 PM, Hadrian Zbarcea <hzbar...@gmail.com> >>> wrote: >>> >>> Yep, it's about time. I will take care of the necessary changes to be >>>> build system and get ready for the release. What are the issues that >>>> >>> still >>> >>>> need to be finished for 2.10.5? Let's start closing down. >>>> >>>> Hadrian >>>> >>>> >>>> >>>> >>>> On 05/15/2013 03:10 AM, Claus Ibsen wrote: >>>> >>>> Hi >>>>> >>>>> Its been 2.5 months ago we released 2.10.4. >>>>> >>>>> I think we should start considering doing a 2.10.5 release. Which is >>>>> also needed by the ServiceMix team for any new 4.5.x releases of >>>>> theirs. >>>>> >>>>> And since we migrated to git, it would be a good idea to cut a release >>>>> to ensure that we can still do releases, and that we iron out any >>>>> issues we encounter after the svn -> git change. >>>>> >>>>> Any thoughts? >>>>> >>>>> -- >>>>> Claus Ibsen >>>>> ----------------- >>>>> www.camelone.org: The open source integration conference. >>>>> >>>>> 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 >>> ----------------- >>> www.camelone.org: The open source integration conference. >>> >>> 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 >>> >>> >>
