You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Christian Müller <ch...@gmail.com> on 2013/06/23 11:35:30 UTC
[VOTE] Release Apache Camel 2.10.5
After 4 month of development, we have a new bug fix release candidate
apache-camel-2.10.5 ready.
It comes with 108 issues resolved [1]. You can find the release notes here
[2].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-058/
The tarballs are here
https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
Tag:
http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
Please review, help out with testing and vote to approve this release
binary. This is our first release which uses the new Camel Git repository
at https://git-wip-us.apache.org/repos/asf?p=camel.git.
Please mention what you tested to prevent duplicate work. Your vote counts!
Some notable remarks:
- At present, we don't use signed tags in Git. I don't think it's possible
at present because of the unresolved issue [3]. I also don't think this is
necessary, because we did had a similar thing in SVN.
- Because I didn't push my local changes to the central repository until
today morning and Claus did some changes on the camel-2.10.x branch (no
blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
camel-2.10.x branch because I had to do a rebase before I could push the
changes. Not sure whether this is an issue. If it's, I will will change the
maven-release-plugin settings to push the changes immediately by doing the
release:prepare and undo the release.
- The Camel manual still looks good. May be the Confluence update wasn't
started/done at the time I build the release.
[ ] +1 Release the binary as Apache Camel 2.10.5
[ ] -1 Veto the release (provide specific comments)
Vote is open for at least 72 hours.
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
[2]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
[3] http://jira.codehaus.org/browse/SCM-486
Thanks in advance,
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
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Christian Schneider <ch...@die-schneider.net>.
+1
Christian
Am 23.06.2013 11:35, schrieb Christian Müller:
> After 4 month of development, we have a new bug fix release candidate
> apache-camel-2.10.5 ready.
> It comes with 108 issues resolved [1]. You can find the release notes here
> [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-058/
>
> The tarballs are here
> https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
>
> Please review, help out with testing and vote to approve this release
> binary. This is our first release which uses the new Camel Git repository
> at https://git-wip-us.apache.org/repos/asf?p=camel.git.
> Please mention what you tested to prevent duplicate work. Your vote counts!
>
> Some notable remarks:
> - At present, we don't use signed tags in Git. I don't think it's possible
> at present because of the unresolved issue [3]. I also don't think this is
> necessary, because we did had a similar thing in SVN.
> - Because I didn't push my local changes to the central repository until
> today morning and Claus did some changes on the camel-2.10.x branch (no
> blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
> camel-2.10.x branch because I had to do a rebase before I could push the
> changes. Not sure whether this is an issue. If it's, I will will change the
> maven-release-plugin settings to push the changes immediately by doing the
> release:prepare and undo the release.
> - The Camel manual still looks good. May be the Confluence update wasn't
> started/done at the time I build the release.
>
> [ ] +1 Release the binary as Apache Camel 2.10.5
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
> [2]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
> [3] http://jira.codehaus.org/browse/SCM-486
>
> Thanks in advance,
> 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
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Hadrian Zbarcea <hz...@gmail.com>.
+1 (reversal of vote)
* I got to run the full test suite too. Everything works except one
test, but it's a test issue not a product issue.
* Checked signatures, all looks good.
* I checked with Dan this morning. For him everything looked good. Dan
mentioned that there was a discussion on the maven lists related to what
I experienced, but there is no good solution. After picking the first
2.10.5 tag, I only did a `git pull`, without a `git fetch --tags`, so
the tag in my local clone was not refreshed and hence the version I got
to see. This would not happen on a fresh copy, therefore it's not an
issue as far as the release is concerned.
* The camel-itests are still an issue that needs resolving, but not a
blocker for the release. It needs to be resolved though. For instance
camel-itest-osgi was a released artifact up until 2.10.2, we should
probably move it somewhere else if we don't plan to release. Anyway, a
discussion for another time.
* Singing the tag still an issue to be resolved, not a blocker.
Thanks Christian for the first release from the git repo!
Hadrian
On 06/25/2013 03:18 PM, Christian Müller wrote:
> Hello Hadrian!
>
> Can you please share a link to the faulty pom.xml files!? I checked Nexus
> [1] and Git [2] and they look good.
>
> [1]
> https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/camel-core/2.10.5/camel-core-2.10.5.pom
> [2]
> https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=camel-core/pom.xml;h=c1cf6b896c47ddb6cd256327a3be25452937cc31;hb=b080909f1db853e5d91e67f78a248a9950481d18
>
> 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 Tue, Jun 25, 2013 at 3:37 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
>
>> -1 (reluctantly)
>>
>> * Checking out the tag I see that all poms use 2.10.5-SNAPSHOT. Not good
>> for a release.
>> * Building from the tag went fine (didn't run all tests yet, but I plan to
>> tomorrow). However, in ./tests, both camel-itest-osgi and camel-itest-karaf
>> are excluded from the build, and what's worse, point to older versions of
>> the parent. We should have caught this earlier.
>> * Signing the tag is important (imho), but that's not a blocker, that's
>> only a -0.
>>
>> Hadrian
>>
>>
>>
>> On 06/23/2013 05:35 AM, Christian Müller wrote:
>>
>>> After 4 month of development, we have a new bug fix release candidate
>>> apache-camel-2.10.5 ready.
>>> It comes with 108 issues resolved [1]. You can find the release notes here
>>> [2].
>>>
>>> Please find the staging repo here:
>>> https://repository.apache.org/**content/repositories/**
>>> orgapachecamel-058/<https://repository.apache.org/content/repositories/orgapachecamel-058/>
>>>
>>> The tarballs are here
>>> https://repository.apache.org/**content/repositories/**
>>> orgapachecamel-058/org/apache/**camel/apache-camel/2.10.5/<https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/>
>>>
>>> Tag:
>>> http://svn.apache.org/repos/**asf/camel/tags/camel-2.10.5/<http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/>
>>>
>>> Please review, help out with testing and vote to approve this release
>>> binary. This is our first release which uses the new Camel Git repository
>>> at https://git-wip-us.apache.org/**repos/asf?p=camel.git<https://git-wip-us.apache.org/repos/asf?p=camel.git>
>>> .
>>> Please mention what you tested to prevent duplicate work. Your vote
>>> counts!
>>>
>>> Some notable remarks:
>>> - At present, we don't use signed tags in Git. I don't think it's possible
>>> at present because of the unresolved issue [3]. I also don't think this
>>> is
>>> necessary, because we did had a similar thing in SVN.
>>> - Because I didn't push my local changes to the central repository until
>>> today morning and Claus did some changes on the camel-2.10.x branch (no
>>> blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
>>> camel-2.10.x branch because I had to do a rebase before I could push the
>>> changes. Not sure whether this is an issue. If it's, I will will change
>>> the
>>> maven-release-plugin settings to push the changes immediately by doing the
>>> release:prepare and undo the release.
>>> - The Camel manual still looks good. May be the Confluence update wasn't
>>> started/done at the time I build the release.
>>>
>>> [ ] +1 Release the binary as Apache Camel 2.10.5
>>> [ ] -1 Veto the release (provide specific comments)
>>> Vote is open for at least 72 hours.
>>>
>>> [1]
>>> https://issues.apache.org/**jira/issues/?jql=project%20%**
>>> 3D%20CAMEL%20AND%20fixVersion%**20%3D%20%222.10.5%22<https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22>
>>> [2]
>>> https://issues.apache.org/**jira/secure/ReleaseNote.jspa?**
>>> projectId=12311211&version=**12324024<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024>
>>> [3] http://jira.codehaus.org/**browse/SCM-486<http://jira.codehaus.org/browse/SCM-486>
>>>
>>> Thanks in advance,
>>> 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>
>>>
>>>
>
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Christian Müller <ch...@gmail.com>.
Hello Hadrian!
Can you please share a link to the faulty pom.xml files!? I checked Nexus
[1] and Git [2] and they look good.
[1]
https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/camel-core/2.10.5/camel-core-2.10.5.pom
[2]
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=camel-core/pom.xml;h=c1cf6b896c47ddb6cd256327a3be25452937cc31;hb=b080909f1db853e5d91e67f78a248a9950481d18
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 Tue, Jun 25, 2013 at 3:37 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> -1 (reluctantly)
>
> * Checking out the tag I see that all poms use 2.10.5-SNAPSHOT. Not good
> for a release.
> * Building from the tag went fine (didn't run all tests yet, but I plan to
> tomorrow). However, in ./tests, both camel-itest-osgi and camel-itest-karaf
> are excluded from the build, and what's worse, point to older versions of
> the parent. We should have caught this earlier.
> * Signing the tag is important (imho), but that's not a blocker, that's
> only a -0.
>
> Hadrian
>
>
>
> On 06/23/2013 05:35 AM, Christian Müller wrote:
>
>> After 4 month of development, we have a new bug fix release candidate
>> apache-camel-2.10.5 ready.
>> It comes with 108 issues resolved [1]. You can find the release notes here
>> [2].
>>
>> Please find the staging repo here:
>> https://repository.apache.org/**content/repositories/**
>> orgapachecamel-058/<https://repository.apache.org/content/repositories/orgapachecamel-058/>
>>
>> The tarballs are here
>> https://repository.apache.org/**content/repositories/**
>> orgapachecamel-058/org/apache/**camel/apache-camel/2.10.5/<https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/>
>>
>> Tag:
>> http://svn.apache.org/repos/**asf/camel/tags/camel-2.10.5/<http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/>
>>
>> Please review, help out with testing and vote to approve this release
>> binary. This is our first release which uses the new Camel Git repository
>> at https://git-wip-us.apache.org/**repos/asf?p=camel.git<https://git-wip-us.apache.org/repos/asf?p=camel.git>
>> .
>> Please mention what you tested to prevent duplicate work. Your vote
>> counts!
>>
>> Some notable remarks:
>> - At present, we don't use signed tags in Git. I don't think it's possible
>> at present because of the unresolved issue [3]. I also don't think this
>> is
>> necessary, because we did had a similar thing in SVN.
>> - Because I didn't push my local changes to the central repository until
>> today morning and Claus did some changes on the camel-2.10.x branch (no
>> blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
>> camel-2.10.x branch because I had to do a rebase before I could push the
>> changes. Not sure whether this is an issue. If it's, I will will change
>> the
>> maven-release-plugin settings to push the changes immediately by doing the
>> release:prepare and undo the release.
>> - The Camel manual still looks good. May be the Confluence update wasn't
>> started/done at the time I build the release.
>>
>> [ ] +1 Release the binary as Apache Camel 2.10.5
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> [1]
>> https://issues.apache.org/**jira/issues/?jql=project%20%**
>> 3D%20CAMEL%20AND%20fixVersion%**20%3D%20%222.10.5%22<https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22>
>> [2]
>> https://issues.apache.org/**jira/secure/ReleaseNote.jspa?**
>> projectId=12311211&version=**12324024<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024>
>> [3] http://jira.codehaus.org/**browse/SCM-486<http://jira.codehaus.org/browse/SCM-486>
>>
>> Thanks in advance,
>> 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>
>>
>>
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Claus Ibsen <cl...@gmail.com>.
The osgi tests has always been excluded by default.
There is a profile to run with those enabled.
Like there is a profile to run the performance tests etc.
So there is nothing different in this release than the previous ones.
And could the "SNAPSHOT" in the tags be what Christian explained in his mail?
On Tue, Jun 25, 2013 at 3:37 AM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> -1 (reluctantly)
>
> * Checking out the tag I see that all poms use 2.10.5-SNAPSHOT. Not good for
> a release.
> * Building from the tag went fine (didn't run all tests yet, but I plan to
> tomorrow). However, in ./tests, both camel-itest-osgi and camel-itest-karaf
> are excluded from the build, and what's worse, point to older versions of
> the parent. We should have caught this earlier.
> * Signing the tag is important (imho), but that's not a blocker, that's only
> a -0.
>
> Hadrian
>
>
>
> On 06/23/2013 05:35 AM, Christian Müller wrote:
>>
>> After 4 month of development, we have a new bug fix release candidate
>> apache-camel-2.10.5 ready.
>> It comes with 108 issues resolved [1]. You can find the release notes here
>> [2].
>>
>> Please find the staging repo here:
>> https://repository.apache.org/content/repositories/orgapachecamel-058/
>>
>> The tarballs are here
>>
>> https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
>>
>> Please review, help out with testing and vote to approve this release
>> binary. This is our first release which uses the new Camel Git repository
>> at https://git-wip-us.apache.org/repos/asf?p=camel.git.
>> Please mention what you tested to prevent duplicate work. Your vote
>> counts!
>>
>> Some notable remarks:
>> - At present, we don't use signed tags in Git. I don't think it's possible
>> at present because of the unresolved issue [3]. I also don't think this
>> is
>> necessary, because we did had a similar thing in SVN.
>> - Because I didn't push my local changes to the central repository until
>> today morning and Claus did some changes on the camel-2.10.x branch (no
>> blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
>> camel-2.10.x branch because I had to do a rebase before I could push the
>> changes. Not sure whether this is an issue. If it's, I will will change
>> the
>> maven-release-plugin settings to push the changes immediately by doing the
>> release:prepare and undo the release.
>> - The Camel manual still looks good. May be the Confluence update wasn't
>> started/done at the time I build the release.
>>
>> [ ] +1 Release the binary as Apache Camel 2.10.5
>> [ ] -1 Veto the release (provide specific comments)
>> Vote is open for at least 72 hours.
>>
>> [1]
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
>> [2]
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
>> [3] http://jira.codehaus.org/browse/SCM-486
>>
>> Thanks in advance,
>> 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
>>
>
--
Claus Ibsen
-----------------
www.camelone.org: The open source integration conference.
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Hadrian Zbarcea <hz...@gmail.com>.
-1 (reluctantly)
* Checking out the tag I see that all poms use 2.10.5-SNAPSHOT. Not good
for a release.
* Building from the tag went fine (didn't run all tests yet, but I plan
to tomorrow). However, in ./tests, both camel-itest-osgi and
camel-itest-karaf are excluded from the build, and what's worse, point
to older versions of the parent. We should have caught this earlier.
* Signing the tag is important (imho), but that's not a blocker, that's
only a -0.
Hadrian
On 06/23/2013 05:35 AM, Christian Müller wrote:
> After 4 month of development, we have a new bug fix release candidate
> apache-camel-2.10.5 ready.
> It comes with 108 issues resolved [1]. You can find the release notes here
> [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-058/
>
> The tarballs are here
> https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
>
> Please review, help out with testing and vote to approve this release
> binary. This is our first release which uses the new Camel Git repository
> at https://git-wip-us.apache.org/repos/asf?p=camel.git.
> Please mention what you tested to prevent duplicate work. Your vote counts!
>
> Some notable remarks:
> - At present, we don't use signed tags in Git. I don't think it's possible
> at present because of the unresolved issue [3]. I also don't think this is
> necessary, because we did had a similar thing in SVN.
> - Because I didn't push my local changes to the central repository until
> today morning and Claus did some changes on the camel-2.10.x branch (no
> blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
> camel-2.10.x branch because I had to do a rebase before I could push the
> changes. Not sure whether this is an issue. If it's, I will will change the
> maven-release-plugin settings to push the changes immediately by doing the
> release:prepare and undo the release.
> - The Camel manual still looks good. May be the Confluence update wasn't
> started/done at the time I build the release.
>
> [ ] +1 Release the binary as Apache Camel 2.10.5
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
> [2]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
> [3] http://jira.codehaus.org/browse/SCM-486
>
> Thanks in advance,
> 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
>
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Jeff Genender <jg...@apache.org>.
+1
Jeff
On Jun 24, 2013, at 6:35 AM, Ashwin Karpe <ak...@yahoo.com> wrote:
> +1
>
>
> ________________________________
> From: Christian Müller <ch...@gmail.com>
> To: "dev@camel.apache.org" <de...@camel.apache.org>; "private@camel.apache.org" <pr...@camel.apache.org>
> Sent: Sunday, June 23, 2013 4:35 AM
> Subject: [VOTE] Release Apache Camel 2.10.5
>
>
> After 4 month of development, we have a new bug fix release candidate
> apache-camel-2.10.5 ready.
> It comes with 108 issues resolved [1]. You can find the release notes here
> [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-058/
>
> The tarballs are here
> https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
>
> Please review, help out with testing and vote to approve this release
> binary. This is our first release which uses the new Camel Git repository
> at https://git-wip-us.apache.org/repos/asf?p=camel.git.
> Please mention what you tested to prevent duplicate work. Your vote counts!
>
> Some notable remarks:
> - At present, we don't use signed tags in Git. I don't think it's possible
> at present because of the unresolved issue [3]. I also don't think this is
> necessary, because we did had a similar thing in SVN.
> - Because I didn't push my local changes to the central repository until
> today morning and Claus did some changes on the camel-2.10.x branch (no
> blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
> camel-2.10.x branch because I had to do a rebase before I could push the
> changes. Not sure whether this is an issue. If it's, I will will change the
> maven-release-plugin settings to push the changes immediately by doing the
> release:prepare and undo the release.
> - The Camel manual still looks good. May be the Confluence update wasn't
> started/done at the time I build the release.
>
> [ ] +1 Release the binary as Apache Camel 2.10.5
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
> [2]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
> [3] http://jira.codehaus.org/browse/SCM-486
>
> Thanks in advance,
> 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
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Ashwin Karpe <ak...@yahoo.com>.
+1
________________________________
From: Christian Müller <ch...@gmail.com>
To: "dev@camel.apache.org" <de...@camel.apache.org>; "private@camel.apache.org" <pr...@camel.apache.org>
Sent: Sunday, June 23, 2013 4:35 AM
Subject: [VOTE] Release Apache Camel 2.10.5
After 4 month of development, we have a new bug fix release candidate
apache-camel-2.10.5 ready.
It comes with 108 issues resolved [1]. You can find the release notes here
[2].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-058/
The tarballs are here
https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
Tag:
http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
Please review, help out with testing and vote to approve this release
binary. This is our first release which uses the new Camel Git repository
at https://git-wip-us.apache.org/repos/asf?p=camel.git.
Please mention what you tested to prevent duplicate work. Your vote counts!
Some notable remarks:
- At present, we don't use signed tags in Git. I don't think it's possible
at present because of the unresolved issue [3]. I also don't think this is
necessary, because we did had a similar thing in SVN.
- Because I didn't push my local changes to the central repository until
today morning and Claus did some changes on the camel-2.10.x branch (no
blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
camel-2.10.x branch because I had to do a rebase before I could push the
changes. Not sure whether this is an issue. If it's, I will will change the
maven-release-plugin settings to push the changes immediately by doing the
release:prepare and undo the release.
- The Camel manual still looks good. May be the Confluence update wasn't
started/done at the time I build the release.
[ ] +1 Release the binary as Apache Camel 2.10.5
[ ] -1 Veto the release (provide specific comments)
Vote is open for at least 72 hours.
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
[2]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
[3] http://jira.codehaus.org/browse/SCM-486
Thanks in advance,
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
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Christian Müller <ch...@gmail.com>.
Yes, because we are using Git since a few weeks... ;-)
Best,
Christian
Sent from a mobile device
Am 23.06.2013 12:25 schrieb "Charles Moulliard" <ch...@gmail.com>:
> Link of the tag does not exist -->
> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/ ?
>
>
> On Sun, Jun 23, 2013 at 11:35 AM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
> > After 4 month of development, we have a new bug fix release candidate
> > apache-camel-2.10.5 ready.
> > It comes with 108 issues resolved [1]. You can find the release notes
> here
> > [2].
> >
> > Please find the staging repo here:
> > https://repository.apache.org/content/repositories/orgapachecamel-058/
> >
> > The tarballs are here
> >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
> >
> > Tag:
> > http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
> >
> > Please review, help out with testing and vote to approve this release
> > binary. This is our first release which uses the new Camel Git repository
> > at https://git-wip-us.apache.org/repos/asf?p=camel.git.
> > Please mention what you tested to prevent duplicate work. Your vote
> counts!
> >
> > Some notable remarks:
> > - At present, we don't use signed tags in Git. I don't think it's
> possible
> > at present because of the unresolved issue [3]. I also don't think this
> is
> > necessary, because we did had a similar thing in SVN.
> > - Because I didn't push my local changes to the central repository until
> > today morning and Claus did some changes on the camel-2.10.x branch (no
> > blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
> > camel-2.10.x branch because I had to do a rebase before I could push the
> > changes. Not sure whether this is an issue. If it's, I will will change
> the
> > maven-release-plugin settings to push the changes immediately by doing
> the
> > release:prepare and undo the release.
> > - The Camel manual still looks good. May be the Confluence update wasn't
> > started/done at the time I build the release.
> >
> > [ ] +1 Release the binary as Apache Camel 2.10.5
> > [ ] -1 Veto the release (provide specific comments)
> > Vote is open for at least 72 hours.
> >
> > [1]
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
> > [2]
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
> > [3] http://jira.codehaus.org/browse/SCM-486
> >
> > Thanks in advance,
> > 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
> >
>
>
>
> --
> Charles Moulliard
> Apache Committer / Architect @RedHat
> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
>
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Charles Moulliard <ch...@gmail.com>.
Link of the tag does not exist -->
http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/ ?
On Sun, Jun 23, 2013 at 11:35 AM, Christian Müller <
christian.mueller@gmail.com> wrote:
> After 4 month of development, we have a new bug fix release candidate
> apache-camel-2.10.5 ready.
> It comes with 108 issues resolved [1]. You can find the release notes here
> [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-058/
>
> The tarballs are here
>
> https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
>
> Please review, help out with testing and vote to approve this release
> binary. This is our first release which uses the new Camel Git repository
> at https://git-wip-us.apache.org/repos/asf?p=camel.git.
> Please mention what you tested to prevent duplicate work. Your vote counts!
>
> Some notable remarks:
> - At present, we don't use signed tags in Git. I don't think it's possible
> at present because of the unresolved issue [3]. I also don't think this is
> necessary, because we did had a similar thing in SVN.
> - Because I didn't push my local changes to the central repository until
> today morning and Claus did some changes on the camel-2.10.x branch (no
> blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
> camel-2.10.x branch because I had to do a rebase before I could push the
> changes. Not sure whether this is an issue. If it's, I will will change the
> maven-release-plugin settings to push the changes immediately by doing the
> release:prepare and undo the release.
> - The Camel manual still looks good. May be the Confluence update wasn't
> started/done at the time I build the release.
>
> [ ] +1 Release the binary as Apache Camel 2.10.5
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> [1]
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
> [2]
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
> [3] http://jira.codehaus.org/browse/SCM-486
>
> Thanks in advance,
> 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
>
--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Christian Müller <ch...@gmail.com>.
+1
The only issue I found was [1] and it's easy to fix/work around.
I could install all other features in Karaf 2.2.10.
[1] https://issues.apache.org/jira/browse/CAMEL-6491
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 Sun, Jun 23, 2013 at 11:35 AM, Christian Müller <
christian.mueller@gmail.com> wrote:
> After 4 month of development, we have a new bug fix release candidate
> apache-camel-2.10.5 ready.
> It comes with 108 issues resolved [1]. You can find the release notes here
> [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-058/
>
> The tarballs are here
>
> https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
>
> Please review, help out with testing and vote to approve this release
> binary. This is our first release which uses the new Camel Git repository
> at https://git-wip-us.apache.org/repos/asf?p=camel.git.
> Please mention what you tested to prevent duplicate work. Your vote counts!
>
> Some notable remarks:
> - At present, we don't use signed tags in Git. I don't think it's possible
> at present because of the unresolved issue [3]. I also don't think this is
> necessary, because we did had a similar thing in SVN.
> - Because I didn't push my local changes to the central repository until
> today morning and Claus did some changes on the camel-2.10.x branch (no
> blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
> camel-2.10.x branch because I had to do a rebase before I could push the
> changes. Not sure whether this is an issue. If it's, I will will change the
> maven-release-plugin settings to push the changes immediately by doing the
> release:prepare and undo the release.
> - The Camel manual still looks good. May be the Confluence update wasn't
> started/done at the time I build the release.
>
> [ ] +1 Release the binary as Apache Camel 2.10.5
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
> [2]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
> [3] http://jira.codehaus.org/browse/SCM-486
>
> Thanks in advance,
> 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
>
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Ashwin Karpe <ak...@redhat.com>.
+1
-----
---------------------------------------------------------
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
Red Hat
http://www.redhat.com
Blog: http://opensourceknowledge.blogspot.com
---------------------------------------------------------
--
View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-10-5-tp5734607p5734655.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Christian Müller <ch...@gmail.com>.
The right Link to the Tag is:
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=dcb7b4d983ac4ab8f516f5dee520559a5c2c9567
Thanks Charles for pointing out this mistake.
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 Sun, Jun 23, 2013 at 11:35 AM, Christian Müller <
christian.mueller@gmail.com> wrote:
> After 4 month of development, we have a new bug fix release candidate
> apache-camel-2.10.5 ready.
> It comes with 108 issues resolved [1]. You can find the release notes here
> [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-058/
>
> The tarballs are here
>
> https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
>
> Please review, help out with testing and vote to approve this release
> binary. This is our first release which uses the new Camel Git repository
> at https://git-wip-us.apache.org/repos/asf?p=camel.git.
> Please mention what you tested to prevent duplicate work. Your vote counts!
>
> Some notable remarks:
> - At present, we don't use signed tags in Git. I don't think it's possible
> at present because of the unresolved issue [3]. I also don't think this is
> necessary, because we did had a similar thing in SVN.
> - Because I didn't push my local changes to the central repository until
> today morning and Claus did some changes on the camel-2.10.x branch (no
> blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
> camel-2.10.x branch because I had to do a rebase before I could push the
> changes. Not sure whether this is an issue. If it's, I will will change the
> maven-release-plugin settings to push the changes immediately by doing the
> release:prepare and undo the release.
> - The Camel manual still looks good. May be the Confluence update wasn't
> started/done at the time I build the release.
>
> [ ] +1 Release the binary as Apache Camel 2.10.5
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
> [2]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
> [3] http://jira.codehaus.org/browse/SCM-486
>
> Thanks in advance,
> 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
>
Re: [VOTE] Release Apache Camel 2.10.5
Posted by Jon Anstey <ja...@gmail.com>.
+1
On Sun, Jun 23, 2013 at 7:05 AM, Christian Müller <
christian.mueller@gmail.com> wrote:
> After 4 month of development, we have a new bug fix release candidate
> apache-camel-2.10.5 ready.
> It comes with 108 issues resolved [1]. You can find the release notes here
> [2].
>
> Please find the staging repo here:
> https://repository.apache.org/content/repositories/orgapachecamel-058/
>
> The tarballs are here
>
> https://repository.apache.org/content/repositories/orgapachecamel-058/org/apache/camel/apache-camel/2.10.5/
>
> Tag:
> http://svn.apache.org/repos/asf/camel/tags/camel-2.10.5/
>
> Please review, help out with testing and vote to approve this release
> binary. This is our first release which uses the new Camel Git repository
> at https://git-wip-us.apache.org/repos/asf?p=camel.git.
> Please mention what you tested to prevent duplicate work. Your vote counts!
>
> Some notable remarks:
> - At present, we don't use signed tags in Git. I don't think it's possible
> at present because of the unresolved issue [3]. I also don't think this is
> necessary, because we did had a similar thing in SVN.
> - Because I didn't push my local changes to the central repository until
> today morning and Claus did some changes on the camel-2.10.x branch (no
> blaming ;-) ), it now looks like the tag 2.10.5 is not part of the
> camel-2.10.x branch because I had to do a rebase before I could push the
> changes. Not sure whether this is an issue. If it's, I will will change the
> maven-release-plugin settings to push the changes immediately by doing the
> release:prepare and undo the release.
> - The Camel manual still looks good. May be the Confluence update wasn't
> started/done at the time I build the release.
>
> [ ] +1 Release the binary as Apache Camel 2.10.5
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> [1]
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.10.5%22
> [2]
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12324024
> [3] http://jira.codehaus.org/browse/SCM-486
>
> Thanks in advance,
> 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
>
--
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