You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Hadrian Zbarcea <hz...@gmail.com> on 2014/02/16 05:16:25 UTC
[VOTE] Release Apache Camel 2.11.4
This is a vote to release Apache Camel 2.11.4, a patch release coming
with about 26 issues fixed.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
Staging repo:
https://repository.apache.org/content/repositories/orgapachecamel-1003/
Tarballs:
https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
Tag:
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
Please test this release candidate and cast your vote.
[ ] +1 Release the binary as Apache Camel 2.11.4
[ ] -1 Veto the release (provide specific comments)
Vote is open for at least 72 hours.
Thanks,
Hadrian
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Willem Jiang <wi...@gmail.com>.
+1
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 16, 2014 at 12:17:07 PM, Hadrian Zbarcea (hzbarcea@gmail.com) wrote:
>
> This is a vote to release Apache Camel 2.11.4, a patch release
> coming
> with about 26 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.11.4
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
>
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Raul Kripalani <ra...@evosent.com>.
+1.
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Sun, Feb 16, 2014 at 4:16 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> This is a vote to release Apache Camel 2.11.4, a patch release coming with
> about 26 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311211&version=12325645
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>
> Tarballs:
> https://repository.apache.org/content/repositories/
> orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
> ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.11.4
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
>
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Forgot my +1.
On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
> This is a vote to release Apache Camel 2.11.4, a patch release coming
> with about 26 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.11.4
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Daniel Kulp <dk...@apache.org>.
+1
Dan
On Feb 15, 2014, at 11:16 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> This is a vote to release Apache Camel 2.11.4, a patch release coming with about 26 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.11.4
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Willem Jiang <wi...@gmail.com>.
Hi Babak,
There are some patches of supporting CXF 3.x are not merged to camel-2.12.x and camel-2.11.x.
So the cxf version rang of camel-2.12.x and camel-2.11.x is right.
I don’t think it’s a show-stopper.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On February 16, 2014 at 11:38:08 PM, Babak Vahdat (babak.vahdat@swissonline.ch) wrote:
>
> -1
>
> See
> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>
> Babak
>
>
> hadrian wrote
> > This is a vote to release Apache Camel 2.11.4, a patch release
> coming
> > with about 26 issues fixed.
> >
> > Release notes:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
> >
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/orgapachecamel-1003/
> >
> > Tarballs:
> > https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
> >
> >
> > Tag:
> > https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as Apache Camel 2.11.4
> > [ ] -1 Veto the release (provide specific comments)
> > Vote is open for at least 72 hours.
> >
> > Thanks,
> > Hadrian
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747376.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Johan Edstrom <se...@gmail.com>.
I can't see what it stops, looks like cosmetics?
+1
On Feb 16, 2014, at 4:07 PM, James Carman <ja...@carmanconsulting.com> wrote:
> Why not just mark the issue as not fixed and release? Is the issue a
> show-stopper?
>
> On Sunday, February 16, 2014, Babak Vahdat <ba...@swissonline.ch>
> wrote:
>
>> -1
>>
>> See
>>
>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>
>> Babak
>>
>>
>> hadrian wrote
>>> This is a vote to release Apache Camel 2.11.4, a patch release coming
>>> with about 26 issues fixed.
>>>
>>> Release notes:
>>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>>>
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>>>
>>> Tarballs:
>>>
>> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>>>
>>>
>>> Tag:
>>>
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>>>
>>> Please test this release candidate and cast your vote.
>>> [ ] +1 Release the binary as Apache Camel 2.11.4
>>> [ ] -1 Veto the release (provide specific comments)
>>> Vote is open for at least 72 hours.
>>>
>>> Thanks,
>>> Hadrian
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747376.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
Re: [VOTE] Release Apache Camel 2.11.4
Posted by James Carman <ja...@carmanconsulting.com>.
I figured that's what was going on. Also, I don't think the
cxf-version-range property is doing what we think it's supposed to do,
perhaps. It's set to [2.6,4.0), but the ranges show up as [2.6,2.9).
So, perhaps we need to investigate that? I think CAMEL-7170 can
remain "fixed", since it did exactly as it was asked to do, though.
On Mon, Feb 17, 2014 at 8:17 AM, Babak Vahdat
<ba...@swissonline.ch> wrote:
> You're right and sorry for the confusion. I don't know why, but somehow my
> brain treated 2.7.10 as 2.9.10!
>
> So I change my vote here to +1.
>
> Babak
>
>
> James Carman wrote
>> When I open up the META-INF/MANIFEST.MF file in 2.11.3, I see:
>>
>> org.apache.cxf;version="[2.6,2.9)"
>>
>> In this prepared 2.11.4 candidate I see:
>>
>> org.apache.cxf;version="[2.6,2.9)"
>>
>> So, nothing appears to have changed there. If we look at the
>> feature.xml file in this release candidate:
>> <feature name="camel-cxf" version="2.11.4" resolver="(obr)"
>> start-level="50">
>>
>> <feature version="2.11.4">
>> camel-spring
>> </feature>
>>
>> <feature>
>> jetty
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-specs
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-core
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-jaxrs
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-jaxws
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-databinding-jaxb
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-bindings-soap
>> </feature>
>>
>> <bundle>
>> mvn:org.apache.camel/camel-cxf-transport/2.11.4
>> </bundle>
>>
>> <bundle>
>> mvn:org.apache.camel/camel-cxf/2.11.4
>> </bundle>
>> </feature>
>> Now, let's look at the 2.11.3 version:
>> <feature name="camel-cxf" version="2.11.3" resolver="(obr)"
>> start-level="50">
>>
>> <feature version="2.11.3">
>> camel-spring
>> </feature>
>>
>> <feature>
>> jetty
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-specs
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-core
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-jaxrs
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-jaxws
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-databinding-jaxb
>> </feature>
>>
>> <feature version="[2.6,2.9)">
>> cxf-bindings-soap
>> </feature>
>>
>> <bundle>
>> mvn:org.apache.camel/camel-cxf-transport/2.11.3
>> </bundle>
>>
>> <bundle>
>> mvn:org.apache.camel/camel-cxf/2.11.3
>> </bundle>
>> </feature>
>> The only thing that has changed are the version numbers (from 2.11.3
>> -> 2.11.4). Now, for the maven folks, all we did was adjust the
>> pom.xml file:
>>
>> -
>> <cxf-version>
>> 2.7.8
>> </cxf-version>
>> +
>> <cxf-version>
>> 2.7.10
>> </cxf-version>
>> I would assume this is okay. Am I missing something?
>>
>>
>> On Mon, Feb 17, 2014 at 6:11 AM, Babak Vahdat
>> <
>
>> babak.vahdat@
>
>> > wrote:
>>> Hi James,
>>>
>>> Even if we would mark the issue as not fixed, the behaviour divergency by
>>> this release candidate @ the staging repo would be still there, that's:
>>> For the non-OSGi folks who make use of camel-cxf Camel component, we
>>> would
>>> put CXF 2.7.10 for them into the classpath but for the OSGi folks who use
>>> the camel-cxf Karaf feature, we would NOT allow them to make use of CXF
>>> 2.7.10!
>>>
>>> Babak
>>>
>>>
>>> James Carman wrote
>>>> Why not just mark the issue as not fixed and release? Is the issue a
>>>> show-stopper?
>>>>
>>>> On Sunday, February 16, 2014, Babak Vahdat <
>>>
>>>> babak.vahdat@
>>>
>>>> >
>>>> wrote:
>>>>
>>>>> -1
>>>>>
>>>>> See
>>>>>
>>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>>>>
>>>>> Babak
>>>>>
>>>>>
>>>>> hadrian wrote
>>>>> > This is a vote to release Apache Camel 2.11.4, a patch release coming
>>>>> > with about 26 issues fixed.
>>>>> >
>>>>> > Release notes:
>>>>> >
>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>>>>> >
>>>>> >
>>>>> > Staging repo:
>>>>> >
>>>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>>>>> >
>>>>> > Tarballs:
>>>>> >
>>>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>>>>> >
>>>>> >
>>>>> > Tag:
>>>>> >
>>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>>>>> >
>>>>> > Please test this release candidate and cast your vote.
>>>>> > [ ] +1 Release the binary as Apache Camel 2.11.4
>>>>> > [ ] -1 Veto the release (provide specific comments)
>>>>> > Vote is open for at least 72 hours.
>>>>> >
>>>>> > Thanks,
>>>>> > Hadrian
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747376.html
>>>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747423.html
>>> Sent from the Camel Development mailing list archive at Nabble.com.
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747430.html
> Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
You're right and sorry for the confusion. I don't know why, but somehow my
brain treated 2.7.10 as 2.9.10!
So I change my vote here to +1.
Babak
James Carman wrote
> When I open up the META-INF/MANIFEST.MF file in 2.11.3, I see:
>
> org.apache.cxf;version="[2.6,2.9)"
>
> In this prepared 2.11.4 candidate I see:
>
> org.apache.cxf;version="[2.6,2.9)"
>
> So, nothing appears to have changed there. If we look at the
> feature.xml file in this release candidate:
> <feature name="camel-cxf" version="2.11.4" resolver="(obr)"
> start-level="50">
>
> <feature version="2.11.4">
> camel-spring
> </feature>
>
> <feature>
> jetty
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-specs
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-core
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-jaxrs
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-jaxws
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-databinding-jaxb
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-bindings-soap
> </feature>
>
> <bundle>
> mvn:org.apache.camel/camel-cxf-transport/2.11.4
> </bundle>
>
> <bundle>
> mvn:org.apache.camel/camel-cxf/2.11.4
> </bundle>
> </feature>
> Now, let's look at the 2.11.3 version:
> <feature name="camel-cxf" version="2.11.3" resolver="(obr)"
> start-level="50">
>
> <feature version="2.11.3">
> camel-spring
> </feature>
>
> <feature>
> jetty
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-specs
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-core
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-jaxrs
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-jaxws
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-databinding-jaxb
> </feature>
>
> <feature version="[2.6,2.9)">
> cxf-bindings-soap
> </feature>
>
> <bundle>
> mvn:org.apache.camel/camel-cxf-transport/2.11.3
> </bundle>
>
> <bundle>
> mvn:org.apache.camel/camel-cxf/2.11.3
> </bundle>
> </feature>
> The only thing that has changed are the version numbers (from 2.11.3
> -> 2.11.4). Now, for the maven folks, all we did was adjust the
> pom.xml file:
>
> -
> <cxf-version>
> 2.7.8
> </cxf-version>
> +
> <cxf-version>
> 2.7.10
> </cxf-version>
> I would assume this is okay. Am I missing something?
>
>
> On Mon, Feb 17, 2014 at 6:11 AM, Babak Vahdat
> <
> babak.vahdat@
> > wrote:
>> Hi James,
>>
>> Even if we would mark the issue as not fixed, the behaviour divergency by
>> this release candidate @ the staging repo would be still there, that's:
>> For the non-OSGi folks who make use of camel-cxf Camel component, we
>> would
>> put CXF 2.7.10 for them into the classpath but for the OSGi folks who use
>> the camel-cxf Karaf feature, we would NOT allow them to make use of CXF
>> 2.7.10!
>>
>> Babak
>>
>>
>> James Carman wrote
>>> Why not just mark the issue as not fixed and release? Is the issue a
>>> show-stopper?
>>>
>>> On Sunday, February 16, 2014, Babak Vahdat <
>>
>>> babak.vahdat@
>>
>>> >
>>> wrote:
>>>
>>>> -1
>>>>
>>>> See
>>>>
>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>>>
>>>> Babak
>>>>
>>>>
>>>> hadrian wrote
>>>> > This is a vote to release Apache Camel 2.11.4, a patch release coming
>>>> > with about 26 issues fixed.
>>>> >
>>>> > Release notes:
>>>> >
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>>>> >
>>>> >
>>>> > Staging repo:
>>>> >
>>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>>>> >
>>>> > Tarballs:
>>>> >
>>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>>>> >
>>>> >
>>>> > Tag:
>>>> >
>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>>>> >
>>>> > Please test this release candidate and cast your vote.
>>>> > [ ] +1 Release the binary as Apache Camel 2.11.4
>>>> > [ ] -1 Veto the release (provide specific comments)
>>>> > Vote is open for at least 72 hours.
>>>> >
>>>> > Thanks,
>>>> > Hadrian
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747376.html
>>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>>
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747423.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
--
View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747430.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.11.4
Posted by James Carman <ja...@carmanconsulting.com>.
I forgot to add, there haven't been any 2.9.x (nor 2.8.x) releases for
CXF yet, so we're not disallowing anything, except 3.0.x (only a
milestone release thus far), which we wanted to keep out anyway.
On Mon, Feb 17, 2014 at 7:52 AM, James Carman
<ja...@carmanconsulting.com> wrote:
> When I open up the META-INF/MANIFEST.MF file in 2.11.3, I see:
>
> org.apache.cxf;version="[2.6,2.9)"
>
> In this prepared 2.11.4 candidate I see:
>
> org.apache.cxf;version="[2.6,2.9)"
>
> So, nothing appears to have changed there. If we look at the
> feature.xml file in this release candidate:
>
> <feature name="camel-cxf" version="2.11.4" resolver="(obr)" start-level="50">
> <feature version="2.11.4">camel-spring</feature>
> <feature>jetty</feature>
> <feature version="[2.6,2.9)">cxf</feature>
> <feature version="[2.6,2.9)">cxf-specs</feature>
> <feature version="[2.6,2.9)">cxf-core</feature>
> <feature version="[2.6,2.9)">cxf-jaxrs</feature>
> <feature version="[2.6,2.9)">cxf-jaxws</feature>
> <feature version="[2.6,2.9)">cxf-databinding-jaxb</feature>
> <feature version="[2.6,2.9)">cxf-bindings-soap</feature>
> <bundle>mvn:org.apache.camel/camel-cxf-transport/2.11.4</bundle>
> <bundle>mvn:org.apache.camel/camel-cxf/2.11.4</bundle>
> </feature>
>
> Now, let's look at the 2.11.3 version:
>
> <feature name="camel-cxf" version="2.11.3" resolver="(obr)" start-level="50">
> <feature version="2.11.3">camel-spring</feature>
> <feature>jetty</feature>
> <feature version="[2.6,2.9)">cxf</feature>
> <feature version="[2.6,2.9)">cxf-specs</feature>
> <feature version="[2.6,2.9)">cxf-core</feature>
> <feature version="[2.6,2.9)">cxf-jaxrs</feature>
> <feature version="[2.6,2.9)">cxf-jaxws</feature>
> <feature version="[2.6,2.9)">cxf-databinding-jaxb</feature>
> <feature version="[2.6,2.9)">cxf-bindings-soap</feature>
> <bundle>mvn:org.apache.camel/camel-cxf-transport/2.11.3</bundle>
> <bundle>mvn:org.apache.camel/camel-cxf/2.11.3</bundle>
> </feature>
>
> The only thing that has changed are the version numbers (from 2.11.3
> -> 2.11.4). Now, for the maven folks, all we did was adjust the
> pom.xml file:
>
> - <cxf-version>2.7.8</cxf-version>
> + <cxf-version>2.7.10</cxf-version>
>
> I would assume this is okay. Am I missing something?
>
>
> On Mon, Feb 17, 2014 at 6:11 AM, Babak Vahdat
> <ba...@swissonline.ch> wrote:
>> Hi James,
>>
>> Even if we would mark the issue as not fixed, the behaviour divergency by
>> this release candidate @ the staging repo would be still there, that's:
>> For the non-OSGi folks who make use of camel-cxf Camel component, we would
>> put CXF 2.7.10 for them into the classpath but for the OSGi folks who use
>> the camel-cxf Karaf feature, we would NOT allow them to make use of CXF
>> 2.7.10!
>>
>> Babak
>>
>>
>> James Carman wrote
>>> Why not just mark the issue as not fixed and release? Is the issue a
>>> show-stopper?
>>>
>>> On Sunday, February 16, 2014, Babak Vahdat <
>>
>>> babak.vahdat@
>>
>>> >
>>> wrote:
>>>
>>>> -1
>>>>
>>>> See
>>>>
>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>>>
>>>> Babak
>>>>
>>>>
>>>> hadrian wrote
>>>> > This is a vote to release Apache Camel 2.11.4, a patch release coming
>>>> > with about 26 issues fixed.
>>>> >
>>>> > Release notes:
>>>> >
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>>>> >
>>>> >
>>>> > Staging repo:
>>>> > https://repository.apache.org/content/repositories/orgapachecamel-1003/
>>>> >
>>>> > Tarballs:
>>>> >
>>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>>>> >
>>>> >
>>>> > Tag:
>>>> >
>>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>>>> >
>>>> > Please test this release candidate and cast your vote.
>>>> > [ ] +1 Release the binary as Apache Camel 2.11.4
>>>> > [ ] -1 Veto the release (provide specific comments)
>>>> > Vote is open for at least 72 hours.
>>>> >
>>>> > Thanks,
>>>> > Hadrian
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747376.html
>>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>>
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747423.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.11.4
Posted by James Carman <ja...@carmanconsulting.com>.
When I open up the META-INF/MANIFEST.MF file in 2.11.3, I see:
org.apache.cxf;version="[2.6,2.9)"
In this prepared 2.11.4 candidate I see:
org.apache.cxf;version="[2.6,2.9)"
So, nothing appears to have changed there. If we look at the
feature.xml file in this release candidate:
<feature name="camel-cxf" version="2.11.4" resolver="(obr)" start-level="50">
<feature version="2.11.4">camel-spring</feature>
<feature>jetty</feature>
<feature version="[2.6,2.9)">cxf</feature>
<feature version="[2.6,2.9)">cxf-specs</feature>
<feature version="[2.6,2.9)">cxf-core</feature>
<feature version="[2.6,2.9)">cxf-jaxrs</feature>
<feature version="[2.6,2.9)">cxf-jaxws</feature>
<feature version="[2.6,2.9)">cxf-databinding-jaxb</feature>
<feature version="[2.6,2.9)">cxf-bindings-soap</feature>
<bundle>mvn:org.apache.camel/camel-cxf-transport/2.11.4</bundle>
<bundle>mvn:org.apache.camel/camel-cxf/2.11.4</bundle>
</feature>
Now, let's look at the 2.11.3 version:
<feature name="camel-cxf" version="2.11.3" resolver="(obr)" start-level="50">
<feature version="2.11.3">camel-spring</feature>
<feature>jetty</feature>
<feature version="[2.6,2.9)">cxf</feature>
<feature version="[2.6,2.9)">cxf-specs</feature>
<feature version="[2.6,2.9)">cxf-core</feature>
<feature version="[2.6,2.9)">cxf-jaxrs</feature>
<feature version="[2.6,2.9)">cxf-jaxws</feature>
<feature version="[2.6,2.9)">cxf-databinding-jaxb</feature>
<feature version="[2.6,2.9)">cxf-bindings-soap</feature>
<bundle>mvn:org.apache.camel/camel-cxf-transport/2.11.3</bundle>
<bundle>mvn:org.apache.camel/camel-cxf/2.11.3</bundle>
</feature>
The only thing that has changed are the version numbers (from 2.11.3
-> 2.11.4). Now, for the maven folks, all we did was adjust the
pom.xml file:
- <cxf-version>2.7.8</cxf-version>
+ <cxf-version>2.7.10</cxf-version>
I would assume this is okay. Am I missing something?
On Mon, Feb 17, 2014 at 6:11 AM, Babak Vahdat
<ba...@swissonline.ch> wrote:
> Hi James,
>
> Even if we would mark the issue as not fixed, the behaviour divergency by
> this release candidate @ the staging repo would be still there, that's:
> For the non-OSGi folks who make use of camel-cxf Camel component, we would
> put CXF 2.7.10 for them into the classpath but for the OSGi folks who use
> the camel-cxf Karaf feature, we would NOT allow them to make use of CXF
> 2.7.10!
>
> Babak
>
>
> James Carman wrote
>> Why not just mark the issue as not fixed and release? Is the issue a
>> show-stopper?
>>
>> On Sunday, February 16, 2014, Babak Vahdat <
>
>> babak.vahdat@
>
>> >
>> wrote:
>>
>>> -1
>>>
>>> See
>>>
>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>>
>>> Babak
>>>
>>>
>>> hadrian wrote
>>> > This is a vote to release Apache Camel 2.11.4, a patch release coming
>>> > with about 26 issues fixed.
>>> >
>>> > Release notes:
>>> >
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>>> >
>>> >
>>> > Staging repo:
>>> > https://repository.apache.org/content/repositories/orgapachecamel-1003/
>>> >
>>> > Tarballs:
>>> >
>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>>> >
>>> >
>>> > Tag:
>>> >
>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>>> >
>>> > Please test this release candidate and cast your vote.
>>> > [ ] +1 Release the binary as Apache Camel 2.11.4
>>> > [ ] -1 Veto the release (provide specific comments)
>>> > Vote is open for at least 72 hours.
>>> >
>>> > Thanks,
>>> > Hadrian
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747376.html
>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747423.html
> Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi James,
Even if we would mark the issue as not fixed, the behaviour divergency by
this release candidate @ the staging repo would be still there, that's:
For the non-OSGi folks who make use of camel-cxf Camel component, we would
put CXF 2.7.10 for them into the classpath but for the OSGi folks who use
the camel-cxf Karaf feature, we would NOT allow them to make use of CXF
2.7.10!
Babak
James Carman wrote
> Why not just mark the issue as not fixed and release? Is the issue a
> show-stopper?
>
> On Sunday, February 16, 2014, Babak Vahdat <
> babak.vahdat@
> >
> wrote:
>
>> -1
>>
>> See
>>
>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>>
>> Babak
>>
>>
>> hadrian wrote
>> > This is a vote to release Apache Camel 2.11.4, a patch release coming
>> > with about 26 issues fixed.
>> >
>> > Release notes:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>> >
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/orgapachecamel-1003/
>> >
>> > Tarballs:
>> >
>> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>> >
>> >
>> > Tag:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>> >
>> > Please test this release candidate and cast your vote.
>> > [ ] +1 Release the binary as Apache Camel 2.11.4
>> > [ ] -1 Veto the release (provide specific comments)
>> > Vote is open for at least 72 hours.
>> >
>> > Thanks,
>> > Hadrian
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747376.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
--
View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747423.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.11.4
Posted by James Carman <ja...@carmanconsulting.com>.
Why not just mark the issue as not fixed and release? Is the issue a
show-stopper?
On Sunday, February 16, 2014, Babak Vahdat <ba...@swissonline.ch>
wrote:
> -1
>
> See
>
> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
>
> Babak
>
>
> hadrian wrote
> > This is a vote to release Apache Camel 2.11.4, a patch release coming
> > with about 26 issues fixed.
> >
> > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
> >
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/orgapachecamel-1003/
> >
> > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
> >
> >
> > Tag:
> >
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as Apache Camel 2.11.4
> > [ ] -1 Veto the release (provide specific comments)
> > Vote is open for at least 72 hours.
> >
> > Thanks,
> > Hadrian
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747376.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Babak Vahdat <ba...@swissonline.ch>.
-1
See
http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-12-3-tp5747361p5747375.html
Babak
hadrian wrote
> This is a vote to release Apache Camel 2.11.4, a patch release coming
> with about 26 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.11.4
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
--
View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-11-4-tp5747362p5747376.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Christian Schneider <ch...@die-schneider.net>.
+1
Christian
Am 16.02.2014 05:16, schrieb Hadrian Zbarcea:
> This is a vote to release Apache Camel 2.11.4, a patch release coming
> with about 26 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.11.4
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Jon Anstey <ja...@gmail.com>.
+1
On Sun, Feb 16, 2014 at 12:46 AM, Hadrian Zbarcea <hz...@gmail.com>wrote:
> This is a vote to release Apache Camel 2.11.4, a patch release coming with
> about 26 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311211&version=12325645
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>
> Tarballs:
> https://repository.apache.org/content/repositories/
> orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
> ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.11.4
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
>
--
Cheers,
Jon
---------------
Red Hat, Inc.
Email: janstey@redhat.com
Web: http://redhat.com
Twitter: jon_anstey
Blog: http://janstey.blogspot.com
Author of Camel in Action: http://manning.com/ibsen
Re: [RESULT][VOTE] Release Apache Camel 2.11.4
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Yes, working on it.
Hadrian
On 02/20/2014 12:33 PM, Claus Ibsen wrote:
> Hi
>
> As 2.11.4 passed. Should we not add some notes on the Camel web site
> and announce this release?
> The JARs has been synced to maven central.
> I assume the ASF mirror sync is done also?
>
> On Wed, Feb 19, 2014 at 4:22 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
>> The vote passes with:
>> [10] +1 (joed, bvahdat, joed, cschneider, cmueller, raulk, janstey, dkulp,
>> ningjiang, hadrian)
>> [1] +1 - non-binding (ceposta)
>> [0] -1
>>
>> I will proceed with publishing the artifacts today and make public
>> announcement of the release tomorrow, after the mirrors sync up.
>>
>> Many thanks to all contributors,
>> Hadrian
>>
>>
>>
>> On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
>>> This is a vote to release Apache Camel 2.11.4, a patch release coming with
>>> about 26 issues fixed.
>>>
>>> Release notes:
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>>>
>>> Staging repo:
>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>>>
>>> Tarballs:
>>>
>>> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>>>
>>> Tag:
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>>>
>>> Please test this release candidate and cast your vote.
>>> [ ] +1 Release the binary as Apache Camel 2.11.4
>>> [ ] -1 Veto the release (provide specific comments)
>>> Vote is open for at least 72 hours.
>>>
>>> Thanks,
>>> Hadrian
>>
>
>
Re: [RESULT][VOTE] Release Apache Camel 2.11.4
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
As 2.11.4 passed. Should we not add some notes on the Camel web site
and announce this release?
The JARs has been synced to maven central.
I assume the ASF mirror sync is done also?
On Wed, Feb 19, 2014 at 4:22 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> The vote passes with:
> [10] +1 (joed, bvahdat, joed, cschneider, cmueller, raulk, janstey, dkulp,
> ningjiang, hadrian)
> [1] +1 - non-binding (ceposta)
> [0] -1
>
> I will proceed with publishing the artifacts today and make public
> announcement of the release tomorrow, after the mirrors sync up.
>
> Many thanks to all contributors,
> Hadrian
>
>
>
> On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
>>
>> This is a vote to release Apache Camel 2.11.4, a patch release coming with
>> about 26 issues fixed.
>>
>> Release notes:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>>
>> Tarballs:
>>
>> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>>
>> Tag:
>>
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>>
>> Please test this release candidate and cast your vote.
>> [ ] +1 Release the binary as Apache Camel 2.11.4
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks,
>> Hadrian
>
>
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io
[RESULT][VOTE] Release Apache Camel 2.11.4
Posted by Hadrian Zbarcea <hz...@gmail.com>.
The vote passes with:
[10] +1 (joed, bvahdat, joed, cschneider, cmueller, raulk, janstey,
dkulp, ningjiang, hadrian)
[1] +1 - non-binding (ceposta)
[0] -1
I will proceed with publishing the artifacts today and make public
announcement of the release tomorrow, after the mirrors sync up.
Many thanks to all contributors,
Hadrian
On 02/15/2014 11:16 PM, Hadrian Zbarcea wrote:
> This is a vote to release Apache Camel 2.11.4, a patch release coming
> with about 26 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645
>
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>
> Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.11.4
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Christian Posta <ch...@gmail.com>.
+1 (nonbinding)
On Mon, Feb 17, 2014 at 3:28 PM, Christian Müller
<ch...@gmail.com> wrote:
> +1
>
> The doc looks good.
> The signatures are also good.
> I upgraded an older version of Camel-in-action (rev 356) with the following
> test failed:
> Failed tests:
> testABCGroup(camelinaction.AggregateABCGroupTest)
> testABCGroup(camelinaction.SpringAggregateABCGroupTest)
> testCamelCallback(camelinaction.CamelCallbackTest)
> testCallback(camelinaction.RiderAutoPartsCallbackTest)
>
> Best,
>
> Christian
> -----------------
>
> Software Integration Specialist
>
> Apache Member
> V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
> Apache Incubator PMC Member
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
>
>
> On Sun, Feb 16, 2014 at 5:16 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
>
>> This is a vote to release Apache Camel 2.11.4, a patch release coming with
>> about 26 issues fixed.
>>
>> Release notes:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12311211&version=12325645
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>>
>> Tarballs:
>> https://repository.apache.org/content/repositories/
>> orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>>
>> Tag:
>> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
>> ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>>
>> Please test this release candidate and cast your vote.
>> [ ] +1 Release the binary as Apache Camel 2.11.4
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> Thanks,
>> Hadrian
>>
--
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta
Re: [VOTE] Release Apache Camel 2.11.4
Posted by Christian Müller <ch...@gmail.com>.
+1
The doc looks good.
The signatures are also good.
I upgraded an older version of Camel-in-action (rev 356) with the following
test failed:
Failed tests:
testABCGroup(camelinaction.AggregateABCGroupTest)
testABCGroup(camelinaction.SpringAggregateABCGroupTest)
testCamelCallback(camelinaction.CamelCallbackTest)
testCallback(camelinaction.RiderAutoPartsCallbackTest)
Best,
Christian
-----------------
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Sun, Feb 16, 2014 at 5:16 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> This is a vote to release Apache Camel 2.11.4, a patch release coming with
> about 26 issues fixed.
>
> Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311211&version=12325645
>
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachecamel-1003/
>
> Tarballs:
> https://repository.apache.org/content/repositories/
> orgapachecamel-1003/org/apache/camel/apache-camel/2.11.4/
>
> Tag:
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=
> ae26285a0f597c6fdc8ab8fcc7a9d0cbae71567d
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.11.4
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Thanks,
> Hadrian
>