+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
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
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.
Sorry, too late. I already staged the Camel 2.10.6 release.
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
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
On Jun 29, 2013, at 5:40 AM, Christian Müller
wrote:
> Any notes/objections if I prepare the Camel 2.10.6 release?
No, but I'd like to have a day or so to double check some of the third party
libs to see if they can be better aligned with CXF and ActiveMQ for use for the
ServiceMix release.
The Apache Jenkins build system has built Camel.trunk.notest (build #1918)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1918/
to view the results.
