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.muel...@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 >
