Repository: ant-ivy
Updated Branches:
  refs/heads/2.4.x b7f132a46 -> 79cb7c627


Update release process


Project: http://git-wip-us.apache.org/repos/asf/ant-ivy/repo
Commit: http://git-wip-us.apache.org/repos/asf/ant-ivy/commit/3badf698
Tree: http://git-wip-us.apache.org/repos/asf/ant-ivy/tree/3badf698
Diff: http://git-wip-us.apache.org/repos/asf/ant-ivy/diff/3badf698

Branch: refs/heads/2.4.x
Commit: 3badf6981de1d09f2bb3fbf1a55c29e01ea0da61
Parents: b7f132a
Author: Nicolas Lalevée <[email protected]>
Authored: Fri Nov 14 18:19:33 2014 +0100
Committer: Nicolas Lalevée <[email protected]>
Committed: Fri Nov 14 18:20:14 2014 +0100

----------------------------------------------------------------------
 doc/dev/makerelease.html | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/3badf698/doc/dev/makerelease.html
----------------------------------------------------------------------
diff --git a/doc/dev/makerelease.html b/doc/dev/makerelease.html
index c4101b5..deefd80 100644
--- a/doc/dev/makerelease.html
+++ b/doc/dev/makerelease.html
@@ -88,6 +88,11 @@ As soon as you are happy with the artifacts to be released, 
it is time to tag th
 git tag 2.0.0-beta1
 </code>
 
+And push the changes to the ASF repo
+<code>
+git push --tags 
+</code>
+
 <h3>Publish the release candidate</h3>
 
 All artifacts in <tt>build/distrib</tt> except the <tt>maven2</tt> folder 
needs to be published on the 'dist' svn of the ASF, in the <b>dev</b> part.
@@ -103,7 +108,7 @@ Subject: [VOTE] Ivy ${version} Release
 
 I have built a release candidate for Ivy ${version}
 
-The svn tag of this release is: 
https://svn.apache.org/repos/asf/ant/ivy/core/tags/${version}@${svn-rev-of-the-tag}
+The svn tag of this release is: 
https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=SHA1-OF-THE-TAG
 
 The artifacts has been published to: 
https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION@${svn-rev-of-the-check-in}
 

Reply via email to