I made a same mistake when I release the Camel 2.8.3 again without
deleting the old tag.
It should be easy fix by creating the tag manually, without running the
release prepare again.
But we need to stop Hadrian running the mvn release:performance first
before fixing this issue.
On Tue Dec 20 12:27:39 2011, Daniel Kulp wrote:
I think there is something wrong with the tag.
I see a "trunk" dir in:
http://svn.apache.org/repos/asf/camel/tags/camel-2.9.0/
which looks like it has all of camel in it as well. I think the tag is wrong
(likely didn't delete the old tag?) and I'm not really sure which was built
for the release.
Dan
On Monday, December 19, 2011 11:20:35 PM Hadrian Zbarcea wrote:
A new release candidate apache-camel-2.9.0 final is out with
approximately 478 issues resolved so far: improvements and bug fixes [1].
Please find the staging repo here:
https://repository.apache.org/content/repositories/orgapachecamel-374/
The tarballs are here
https://repository.apache.org/content/repositories/orgapachecamel-374/org/ap
ache/camel/apache-camel/2.9.0/
Tag:
http://svn.apache.org/repos/asf/camel/tags/camel-2.9.0/
Please review, help out with testing and vote to approve this release
binary. Your vote counts!
[ ] +1 Release the binary as Apache Camel 2.9.0
[ ] -1 Veto the release (provide specific comments)
Vote is open for at least 72 hours.
I still need to finish checking all the artifacts. I will do it and cast
my vote in the morning.
Hadrian
[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&ve
rsion=12316374
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
