You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by ja...@apache.org on 2019/09/06 14:51:31 UTC

[ant] branch master updated: Update release instructions to make it clear that final release tags should go under "rel/"

This is an automated email from the ASF dual-hosted git repository.

jaikiran pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ant.git


The following commit(s) were added to refs/heads/master by this push:
     new 2d221de  Update release instructions to make it clear that final release tags should go under "rel/"
2d221de is described below

commit 2d221de4c1e99f0738be86b76862bb4968bb5c54
Author: Jaikiran Pai <ja...@apache.org>
AuthorDate: Fri Sep 6 20:20:14 2019 +0530

    Update release instructions to make it clear that final release tags should go under "rel/"
---
 ReleaseInstructions | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/ReleaseInstructions b/ReleaseInstructions
index 191662a..bb9c0aa 100644
--- a/ReleaseInstructions
+++ b/ReleaseInstructions
@@ -234,7 +234,11 @@ Note: This document was adapted from the one created in the context of
 16. If the vote fails, address the problems and recreate the next RC
     build.
 
-17. Once the vote has passed, tag the last RC created with the final tag
+17. Once the vote has passed, tag the last RC created with the final tag.
+    It is important to tag the release under the "rel/" path since the
+    Apache infrastructure for .git provides certain protections for tags
+    under the "rel/" path. Releases need such protections as per Apache
+    release guidelines.
 
     $ git tag -s -m "Tagging version 1.10.0 of Ant" rel/1.10.0 HASH_OF_LAST_RC
     $ git push --tags