Thanks Hadrian for the offer. If we are not able to start the release this week, I'm happy to take this over to you :-).
I updated the maven release plugin configuration for the 2.11.x maintenance branch to use the Git repo and merged Dan's change to only generate the HTML manual. I tested it and it works fine. Claus and me pushed a few issues to Camel 2.11.2 and now, we only have 9 outstanding issues scheduled for Camel 2.11.1. 2 of these issues are classified as bug and should be fixed. 2 other issues addressing missing documentation for new components (ical and scala-extraz). All other issues are 'nice to have' in Camel 2.11.1, but not 'required', in my opinion. Best, Christian ----------------- 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 Fri, Jun 28, 2013 at 12:06 AM, Hadrian Zbarcea <hzbar...@gmail.com>wrote: > Hi Christian, > > Next week I'll be in vacation, but I can do the 2.11.1 after I come back. > It should be ok, I assume the 22 issues will not be all resolved next week. > > Cheers, > Hadrian > > > > On 06/27/2013 05:02 PM, Christian Müller wrote: > >> We agreed to not build the PDF manual starting with Camel 2.12.0. We still >> have to discuss whether the HTML manual should still created or not. >> However, because we only publish the HTML/PDF manual for major/minor >> releases, it's not important for Camel 2.11.1. >> >> We have 22 unresolved issues assigned to Camel 2.11.1 [1]. Could everybody >> please have a look and mention the issues which should be included in this >> release. I will move all others to 2.11.2, probably at the weekend... >> >> And I could do the release or support the release manager, if someone else >> would like to do it. >> >> [1] >> https://issues.apache.org/**jira/issues/?jql=project%20%** >> 3D%20CAMEL%20AND%20resolution%**20%3D%20Unresolved%20AND%** >> 20fixVersion%20%3D%20%222.11.**1%22<https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.11.1%22> >> >> Best, >> Christian >> ----------------- >> >> Software Integration Specialist >> >> Apache Camel committer: https://camel.apache.org/team >> V.P. Apache Camel: >> https://www.apache.org/**foundation/<https://www.apache.org/foundation/> >> Apache Member: >> https://www.apache.org/**foundation/members.html<https://www.apache.org/foundation/members.html> >> >> https://www.linkedin.com/pub/**christian-mueller/11/551/642<https://www.linkedin.com/pub/christian-mueller/11/551/642> >> >> >> On Thu, Jun 27, 2013 at 3:21 PM, Daniel Kulp <dk...@apache.org> wrote: >> >> >>> On Jun 27, 2013, at 6:04 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: >>> >>> Hi >>>> >>>> We recently released the 2.10.5 release after our git migration. >>>> It would be great if we could start working on a 2.11.1 release as well. >>>> >>> >>> I certainly support the idea of a 2.11.1 release, but we *DO* need to >>> figure out what we want to do with the PDF manual first. We can no >>> longer >>> produce a usable manual. >>> >>> Dan >>> >>> >>> >>>> >>>> >>>> -- >>>> 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 >>>> >>> >>> -- >>> Daniel Kulp >>> dk...@apache.org - http://dankulp.com/blog >>> Talend Community Coder - http://coders.talend.com >>> >>> >>> >>
