taylor 2004/04/22 14:55:48
Modified: . RELEASE-TODO
Log:
live and learn
changed the order of steps so that you don't tag the release until testing it
Revision Changes Path
1.24 +7 -7 jakarta-jetspeed/RELEASE-TODO
Index: RELEASE-TODO
===================================================================
RCS file: /home/cvs/jakarta-jetspeed/RELEASE-TODO,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- RELEASE-TODO 22 Apr 2004 20:42:33 -0000 1.23
+++ RELEASE-TODO 22 Apr 2004 21:55:48 -0000 1.24
@@ -64,16 +64,16 @@
(recommended that you run the tests at least once before releasing)
-10) Tag CVS with the revision release number (for example, JETSPEED-RELEASE-1-5):
-
- cvs tag JETSPEED-RELEASE-xxx
-
-11) Copy the distributions to the download directory on minotaur.apache.org:
+10) Copy the distributions to the download directory on minotaur.apache.org:
jetspeed-1.xxx-war.zip -> /www/www.apache.org/dist/jakarta/jetspeed/binaries
jetspeed-1.xxx-src.zip -> /www/www.apache.org/dist/jakarta/jetspeed/source
-12) Download the distributions to a local machine and test the .war file
+11) Download the distributions to a local machine and test the .war file
+
+12) If everything tests out OK, then Tag CVS with the revision release number (for
example, JETSPEED-RELEASE-1-5):
+
+ cvs tag JETSPEED-RELEASE-xxx
13) Sign the distributions on a local machine:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
