revise Release Instructions

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@275111 13f79535-47bb-0310-9956-ffa450edef68

ReleaseInstructions

@@ -85,6 +85,10 @@ Note: This document was created in the context of releasing Ant 1.5.
     The files should go to /www/jakarta.apache.org/builds/jakarta-ant/release
     on daedalus.
 
+    [[ FIXME: The above URL is definitively wrong, but I can't
+       remember whether we've put the betas to www.apache.org or some
+       subdirectory under ant.apache.org ]]
+
 11. Address the available release tags in BugZilla. Create a new tag 1.5Beta1 
     and a 1.6alpha. Assign all existing 1.5 alpha bugs to one of these release 
     labels.
@@ -95,7 +99,7 @@ Note: This document was created in the context of releasing Ant 1.5.
       text/plain.  Fix it by using some .htaccess magic (AddEncoding stuff)
     * Your gz.asc files are not being displayed properly (RemoveEncoing stuff)
     
-    If it looks OK, announce it on ant-dev and ant-user. After a few
+    If it looks OK, announce it on dev@ant and user@ant. After a few
     days pass and there are no major problems, a wider announcement is
     made (main jakarta website, announcements@jakarta.apache.org,
     etc).
@@ -103,8 +107,8 @@ Note: This document was created in the context of releasing Ant 1.5.
     Also ensure you:
     * Update antnews.xml (Announcement)
     * Update faq.xml (Ant's history details - not for betas)
-    * Update index.xml (Announcement, latest release details)
-    * Update problems.xml (Debug Output details - not for betas IMHO -SB)
+    * Update index.xml (Announcement, latest release details, link to
+      manual under "Documentation")
 
     Generate the html files by invoking ant on docs.xml - you need
     jakarta-site2 checked out for this.  Commit the modified/generated
@@ -126,7 +130,7 @@ Note: This document was created in the context of releasing Ant 1.5.
     To monitor the number of downloads, look at the access_log
     file under /usr/local/apache2/logs
 
-15. When the final beta is considered OK, propose a vote on ant-dev to 
+15. When the final beta is considered OK, propose a vote on dev@ant to 
     officially adopt the latest beta as the Ant 1.5 release. If it is passed, 
     (it usually does,) this would be labelled ANT_15 and built in a similar 
     fashion to the above process.
@@ -136,20 +140,11 @@ Note: This document was created in the context of releasing Ant 1.5.
     This time the directory you upload the files to is different and
     you'll have to do some house-keeping for the old release:
 
-    * create a directory for the old release in 
-      /www/jakarta.apache.org/builds/jakarta-ant/release on daedalus.
-
-    * Move the release notes, .zip files and corresponding signatures
-      and md5 hashes of the old release from /www/www.apache.org/dist/ant
-      to a matching directory structure in
-      /www/jakarta.apache.org/builds/jakarta-ant/release.
-
-    * remove the remaining files except for the KEYS file from
-      /www/www.apache.org/dist/ant.
-
     * upload the new release files to 
       /www/www.apache.org/dist/ant/[source|binary].
 
+    * remove the symbolic links from /www/www.apache.org/dist/ant.
+
     * Create proper -current symlinks in /www/www.apache.org/dist/ant/
 
 17. Change the links in /xdocs/bindownload.xml and /xdocs/srcdownload.xml,
@@ -159,10 +154,24 @@ Note: This document was created in the context of releasing Ant 1.5.
     may want to add a note to that effect to the pages and remove it a few
     days later.
 
+18. Clean up.
+
+    * remove the remaining files of the previous release from
+      /www/www.apache.org/dist/ant/[source|binary].
+
+    * rename the README.html of the old release to
+      RELAEASE-NOTES-1.4.1.html in
+      /www/archive.apache.org/dist/ant/[source|binary] on minotaur,
+
+    * remove all *tar* files of the old release from
+      /www/archive.apache.org/dist/ant/[source|binary] on minotaur,
+      leave the *zip* files alone.
+
 18. Now and perhaps during previous betas any changes on the branch must 
     be merged back into the tree.
 
 19. At this point in time, the release is done and announcements are made. 
+    PGP-sign your announcement posts.
 
     [[TODO: Identify the mailing lists where announcements are to be made.
       Also identify the webpages to which the announcements must go. ]]