ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bode...@apache.org
Subject svn commit: r442825 - /ant/antlibs/ReleaseInstructions
Date Wed, 13 Sep 2006 04:06:41 GMT
Author: bodewig
Date: Tue Sep 12 21:06:40 2006
New Revision: 442825

URL: http://svn.apache.org/viewvc?view=rev&rev=442825
Log:
update

Modified:
    ant/antlibs/ReleaseInstructions

Modified: ant/antlibs/ReleaseInstructions
URL: http://svn.apache.org/viewvc/ant/antlibs/ReleaseInstructions?view=diff&rev=442825&r1=442824&r2=442825
==============================================================================
--- ant/antlibs/ReleaseInstructions (original)
+++ ant/antlibs/ReleaseInstructions Tue Sep 12 21:06:40 2006
@@ -28,37 +28,43 @@
     may be simpler and more convenient to delay the creation of a
     branch until you want to start new development in trunk.
 
-4.  The artefact.version property in build.xml becomes 1.0beta1.
+4.  Create a file libraries.properties in the projects root dir or
+    edit it if it already exists.  Change the value of property
+    artefact.version to 1.0Beta1.
 
     [[ TODO: Check if the documentation files also need to be updated to point
     to the right areas of Ant's website. ]]
 
 5.  Before a build :
 
-    the first beta should be called 1.0beta1, ...
+    the first beta should be called 1.0Beta1, ...
 
-    the artefact.version property in build.xml governs the naming of
+    the artefact.version property in libraries.properties governs the naming of
     the distribution files.
 
     Update the following files for version number:
 
             * docs/index.html
-            * build.xml (artefact.version property)
+            * librares.properties (artefact.version property)
 
         Commit your changes.
 
-6.  Ensure you have all the external libraries that the Antlib uses in your
+6.  Ensure you have all the external libraries that the Antlib uses
     available to your build.
 
-7.  Next build and run the tests.  Then build the distribution.  It is
-    important that this be a clean build. Label this with a tag
-    1_0B1.
+7.  Tag the version
 
     > svn cp https://svn.apache.org/repos/asf/ant/antlibs/dotent/trunk \
     https://svn.apache.org/repos/asf/ant/antlibs/dotnet/tags/1_0B1 \
     -m "Tagging version 1.0beta1 of .NET Antlib"
 
-8.  Sign the distribution files using the following simple script
+8.  Choose the correct tagged version of common as your svn:externals
+    property, if necessary tag common first.
+
+9.  Next build and run the tests.  Then build the distribution.  It is
+    important that this be a clean build.
+
+10. Sign the distribution files using the following simple script
     #!/bin/sh
     for i in `/usr/bin/find distribution \( -name "*.bz2" -o -name  "*.zip" -o -name "*.gz"
\)`
     do
@@ -76,10 +82,10 @@
     Also make sure you have sent the key that you use to a public
     keyserver.
 
-9.  The beta distribution is now ready to go. Bundle it up into a tar.gz file
+11. The beta distribution is now ready to go. Bundle it up into a tar.gz file
     and scp to your apache account.
 
-10. This step may become meaningful once you do a second release ;-)
+12. This step may become meaningful once you do a second release ;-)
 
     Meanwhile, convert the part of the WHATSNEW file covering the changes
     since the last release into HTML for the README file on the
@@ -93,21 +99,21 @@
 
     [[ TODO: This must perhaps be an Ant task. ]]
 
-11. Once this is uploaded, unpack things, create the release directory,
+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.
 
     The files should go to
-    /www/cvs.apache.org/dist/ant/antlibs/dotnet/ on people.apache.org.
+    /www/people.apache.org/dist/ant/antlibs/dotnet/ on people.apache.org.
 
-12. Address the available release tags in BugZilla. Create a new tag 1.0Beta1
+14. 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.
 
-13. Once that is done, do a test download to make sure everything is OK. A
+14. 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)
@@ -123,24 +129,24 @@
 
     Announce beta releases at freshmeat.net.
 
-14. As problems in the beta are discovered, there may be a need for
+15. 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.
 
-15. Try to advertise the need for testing of the betas as much as possible.
+16. 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
 
-16. When the final beta is considered OK, propose a vote on dev@ant to
+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,
     (it usually does,) this would be labelled 1_0 and built in a similar
     fashion to the above process.
 
-17. BUT
+18. BUT
 
     This time the directory you upload the files to is different and
     you'll have to do some house-keeping for the old release:
@@ -170,7 +176,7 @@
 
     (**)
 
-18. Update the ant.apache.org site :
+19. 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,
@@ -178,16 +184,16 @@
 
     Update the online manual too.
 
-19. Clean up.
+20. 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.
 
-20. If you've created a branch, now and perhaps during previous betas
+21. If you've created a branch, now and perhaps during previous betas
     any changes on the branch must be merged back into the tree.
 
-21. At this point in time, the release is done and announcements are made.
+22. 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.
@@ -202,7 +208,7 @@
     Announce release in the usenet groups comp.lang.java.softwaretools
     and comp.lang.java.announce.
 
-22. You can now reacquaint yourself with your family and friends.
+23. 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



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message