[RESULT][VOTE] Release Apache Camel 2.10.6

2013-07-07 Thread Christian Müller
The vote has passed with the following result: [3] binding +1 (akarpe, dkulb, cmueller) [1] non binding +1 (jbonofre) [0] -1 [0] +0 The artifacts will be released to the public maven repo immediately, followed by the ASF site and mirror and the public announcement. Many thanks to all who took the

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-07 Thread Christian Müller
Here is my +1 Best, Christian 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/pu

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-03 Thread Daniel Kulp
+1 Dan On Jul 3, 2013, at 6:27 AM, Christian Müller wrote: > To address CVE-2013-2160 [1], we have a new bug fix release candidate > apache-camel-2.10.6 ready. This bug fix was necessary, because the Apache > Camel feature descriptor for Apache Karaf was still using Apache CXF > 2.6.6.1. Th

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-03 Thread Jean-Baptiste Onofré
+1 (non binding) Regards JB On 07/03/2013 01:59 PM, akarpe wrote: +1 Ashwin Karpe Apache Camel Committer & Forward Deployed Engineer Red Hat http://www.redhat.com Mobile: (972)-971-1700 Blog: http://opensourceknowledge.blogspot.com -

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-03 Thread akarpe
+1 Ashwin Karpe Apache Camel Committer & Forward Deployed Engineer Red Hat http://www.redhat.com Mobile: (972)-971-1700 Blog: http://opensourceknowledge.blogspot.com - On Jul 3, 2013

[VOTE] Release Apache Camel 2.10.6

2013-07-03 Thread Christian Müller
To address CVE-2013-2160 [1], we have a new bug fix release candidate apache-camel-2.10.6 ready. This bug fix was necessary, because the Apache Camel feature descriptor for Apache Karaf was still using Apache CXF 2.6.6.1. This release comes with 8 issues resolved [2]. You can find the release notes

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-02 Thread Willem jiang
Just a quick question, can we lock the branch when doing the release? If so , it can avoid this kind of issue. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogsp

[CANCEL][VOTE] Release Apache Camel 2.10.6

2013-07-02 Thread Christian Müller
I cancel this VOTE because of Dan's comments. I will start cutting a new Camel 2.10.6 release which include Dan's changes in a few minutes. Best, Christian - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apach

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-02 Thread Christian Müller
Hi Dan! [snip] Just make sure you push as quickly as possible after the build. At most, the difference should be an hour or two. It's not something you can start the build and go to bed and push the tags and stuff the next day. That and better communication ahead of time (including time for

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-02 Thread Daniel Kulp
On Jul 2, 2013, at 2:10 PM, Christian Müller wrote: > I'm ok with cutting a new release if it solves an issue with > camel-xmlsecurity, CXF or whatever. > > I'm a bit concerned about the following minor updates: > servicemix-specs-version from 1.9.0 to 2.2.0 This is needed to not end up with

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-02 Thread Christian Müller
I'm ok with cutting a new release if it solves an issue with camel-xmlsecurity, CXF or whatever. I'm a bit concerned about the following minor updates: servicemix-specs-version from 1.9.0 to 2.2.0 xmlbeans-bundle-version from 2.5.0_2 to 2.6.0_2 In general, we only have micro (bug fix) dependency u

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-01 Thread Jeff Genender
+1 Jeff On Jul 1, 2013, at 4:01 PM, Christian Müller wrote: > To address CVE-2013-2160 [1], we have a new bug fix release candidate > apache-camel-2.10.6 ready. This bug fix was necessary, because the Apache > Camel feature descriptor for Apache Karaf was still using Apache CXF > 2.6.6.1. Thi

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-01 Thread Daniel Kulp
I think I'm -1 on this (not a veto, just a vote). If you look at the history of the 2.10.x branch: https://git-wip-us.apache.org/repos/asf?p=camel.git;a=shortlog;h=refs/heads/camel-2.10.x It LOOKS like my changes should be in the release since all the changes were done before the maven-release-p

Re: [VOTE] Release Apache Camel 2.10.6

2013-07-01 Thread Christian Müller
The correct link to the Camel 2.10.6 release notes is https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324640 Best, Christian - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.

[VOTE] Release Apache Camel 2.10.6

2013-07-01 Thread Christian Müller
To address CVE-2013-2160 [1], we have a new bug fix release candidate apache-camel-2.10.6 ready. This bug fix was necessary, because the Apache Camel feature descriptor for Apache Karaf was still using Apache CXF 2.6.6.1. This release comes with 8 issues resolved [2]. You can find the release notes