svn commit: r691613 - /ant/antlibs/ReleaseInstructions

[bo...@apache.org]

Author: bodewig
Date: Wed Sep  3 06:47:59 2008
New Revision: 691613

URL: http://svn.apache.org/viewvc?rev=691613&view=rev
Log:
clarify a few things

Modified:
    ant/antlibs/ReleaseInstructions

Modified: ant/antlibs/ReleaseInstructions
URL: http://svn.apache.org/viewvc/ant/antlibs/ReleaseInstructions?rev=691613&r1=691612&r2=691613&view=diff
==============================================================================
--- ant/antlibs/ReleaseInstructions (original)
+++ ant/antlibs/ReleaseInstructions Wed Sep  3 06:47:59 2008
@@ -28,7 +28,7 @@
     may be simpler and more convenient to delay the creation of a
     branch until you want to start new development in trunk.
 
-4.  Create a file libraries.properties in the projects root dir or
+4.  Create a file version.properties in the projects root dir or
     edit it if it already exists.  Change the value of property
     artefact.version to 1.0Beta1.
 
@@ -45,7 +45,7 @@
     Update the following files for version number:
 
             * docs/index.html
-            * librares.properties (artefact.version property)
+            * version.properties (artefact.version property)
 
         Commit your changes.
 
@@ -99,21 +99,25 @@
 
     [[ TODO: This must perhaps be an Ant task. ]]
 
-13. Once this is uploaded, unpack things, create the release directory,
-    something like v1.0beta1, push the release and RELEASE-NOTES files
-    into this directory.  Create a symbolic link named README.html
-    that points to the RELEASE-NOTES.
+13. Once this is uploaded, unpack things in your home directory
+    and call for a release vote on dev@ant.  The vote will only pass
+    if at least three PMC members have voted +1 and more +1s than -1s
+    have been cast.  The vote will run for a week.
+
+14. Once the vote has passed, push the release and RELEASE-NOTES files
+    into the release directory.  Create a symbolic link named
+    README.html that points to the RELEASE-NOTES.
 
     The files should go to
-    /www/people.apache.org/dist/ant/antlibs/dotnet/ on people.apache.org.
+    /www/www.apache.org/dist/ant/antlibs/ANTLIB-NAME/ on people.apache.org.
 
-14. Address the available release tags in BugZilla. Create a new tag 1.0Beta1
+15. Address the available release tags in BugZilla. Create a new tag 1.0Beta1
     and a 1.1Alpha. Assign all existing 1.0 alpha bugs to one of these release
     labels. Note that such massive changes can be done at once by choosing the
     link "Change several bugs at once" at the bottom of the bug list
     displaying the 1.0alpha bugs.
 
-14. Once that is done, do a test download to make sure everything is OK. A
+16. Once that is done, do a test download to make sure everything is OK. A
     common problem may be:
     * the file's mime type is not recognized and is interpreted as
       text/plain.  Fix it by using some .htaccess magic (AddEncoding stuff)
@@ -124,32 +128,34 @@
     made (ant website, main jakarta website, announcements@jakarta.apache.org,
     etc).
 
-    and also perform a cvs update on files in minotaur's
+    and also perform a svn update on files in minotaur's
     /www/ant.apache.org/
 
     Announce beta releases at freshmeat.net.
 
-15. As problems in the beta are discovered, there may be a need for
+17. As problems in the beta are discovered, there may be a need for
     one or more subsequent betas. The release manager makes this
     call. Each time, the versions are updated and the above process is
     repeated. Try not to have too many betas.
 
-16. Try to advertise the need for testing of the betas as much as possible.
+18. Try to advertise the need for testing of the betas as much as possible.
     This would eliminate the need to release minor patch versions like
     we had to do when releasing Ant 1.4.
 
     To monitor the number of downloads, look at the access_log
     file under /usr/local/apache2/logs
 
-17. When the final beta is considered OK, propose a vote on dev@ant to
-    officially adopt the latest beta as the 1.0 release. If it is passed,
+19. When the final beta is considered OK, propose a vote on dev@ant to
+    officially adopt the latest beta as the new release. If it is passed,
     (it usually does,) this would be labelled 1_0 and built in a similar
     fashion to the above process.
 
-18. BUT
+    Remember to edit the file changes.xml to contain the proper
+    release version and date.
 
-    This time the directory you upload the files to is different and
-    you'll have to do some house-keeping for the old release:
+20. BUT
+
+    This time you'll have to do some house-keeping for the old release:
 
     * upload the new release files to
 
@@ -171,12 +177,14 @@
     * Create proper -current symlinks in
       /www/www.apache.org/dist/ant/antlibs/dotnet.
 
+    * remove the beta release files
+
     * Make sure that the symbolic link README.html points to the new
       RELEASE-NOTES.
 
     (**)
 
-19. Update the ant.apache.org site :
+21. Update the ant.apache.org site :
 
     running svn update *.html under /www/ant.apache.org should update the
     files regenerated and committed in point 5 above (index.html, faq.html,
@@ -184,16 +192,16 @@
 
     Update the online manual too.
 
-20. Clean up.
+22. Clean up.
 
     * remove the remaining files of the previous release from
       /www/www.apache.org/dist/ant/antlibs/dotnet/[source|binaries].
       This includes the old release notes.
 
-21. If you've created a branch, now and perhaps during previous betas
+23. If you've created a branch, now and perhaps during previous betas
     any changes on the branch must be merged back into the tree.
 
-22. At this point in time, the release is done and announcements are made.
+24. 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.
@@ -208,7 +216,9 @@
     Announce release in the usenet groups comp.lang.java.softwaretools
     and comp.lang.java.announce.
 
-23. You can now reacquaint yourself with your family and friends.
+25. Add a new release tag to doap_*.rdf in the AntLib's trunk.
+
+26. You can now reacquaint yourself with your family and friends.
 
 (*)  the xdocs need to be updated on both the branch and the HEAD revision
      because traditionally the ant.apache.org web site reflects the HEAD