svn commit: r122586 - /httpd/apreq/tags/v1_33 /httpd/apreq/tags/v1_33/RELEASE

[st...@apache.org]

Author: stas
Date: Thu Dec 16 13:52:13 2004
New Revision: 122586

URL: http://svn.apache.org/viewcvs?view=rev&rev=122586
Log:
tag v1_33

Added:
   httpd/apreq/tags/v1_33/
      - copied from r122585, httpd/apreq/branches/1.x/
Modified:
   httpd/apreq/tags/v1_33/RELEASE

Modified: httpd/apreq/tags/v1_33/RELEASE
Url: http://svn.apache.org/viewcvs/httpd/apreq/tags/v1_33/RELEASE?view=diff&rev=122586&p1=httpd/apreq/branches/1.x/RELEASE&r1=122585&p2=httpd/apreq/tags/v1_33/RELEASE&r2=122586
==============================================================================
--- httpd/apreq/branches/1.x/RELEASE	(original)
+++ httpd/apreq/tags/v1_33/RELEASE	Thu Dec 16 13:52:13 2004
@@ -6,7 +6,7 @@
         % perl Makefile.PL
         % make dist
 
-   This will generate a libapreq-1.X.tar.gz candidate in the 
+   This will generate a libapreq-1.xx.tar.gz candidate in the 
    current directory.   You should keep this source tree
    intact to generate the final release.
 
@@ -33,34 +33,34 @@
 5. The candidate is ok. Now return to the original source tree
    and edit ./Changes:
 
-   =item 1.X - <Today's Date>
+   =item 1.33 - <Today's Date>
 
-   libapreq-1.X released.
+   libapreq-1.33 released.
 
 6.  Tag the tree, s/./_/g in the version number, and roll the release.
 
-    % cvs tag v1_X
+    % svn copy . https://svn.apache.org/repos/asf/httpd/apreq/tags/v1_33
     % make dist
 
 7. Test the release package, repeating step 2.  If all tests pass,
    sign it via gpg:
 
-     % gpg --detach-sign --armor libapreq-1.X.tar.gz
+     % gpg --detach-sign --armor libapreq-1.33.tar.gz
 
    or pgp:
 
-     % pgp -sba libapreq-1.X.tar.gz
+     % pgp -sba libapreq-1.33.tar.gz
 
 8. Upload (scp) the package and signature to www.apache.org
    for distribution:
 
-    % scp libapreq-1.X.tar.gz* \
+    % scp libapreq-1.33.tar.gz* \
       <username>@www.apache.org:/www/www.apache.org/dist/httpd/libapreq/
 
    Ask another developer to confirm the uploaded signature is ok.
 
-    % gpg --verify libapreq-1.X.tar.gz.asc
-    % pgp libapreq-1.X.tar.gz.asc
+    % gpg --verify libapreq-1.33.tar.gz.asc
+    % pgp libapreq-1.33.tar.gz.asc
 
    Check that your public key is among those listed in the
    /www/www.apache.org/dist/httpd/KEYS file.
@@ -74,7 +74,32 @@
 
 11. Post a final announcement to the modperl@ and apreq-dev@ lists:
 
-        Subject: [ANNOUNCE] libapreq 1.X release
+        Subject: [ANNOUNCE] libapreq 1.33 release
 
     Include the md5 signature in the announcement, as well as
     a list of the latest Changes (since the previous release).
+
+12. Prepare for the next cycle
+
+  a. increment version in Request/Request.pm
+
+  b. edit ./Changes:
+     - start a new item with incremented version + '-dev'
+
+  =item 1.34-dev
+
+  c. add a release entry in STATUS
+
+  d. update this file versions to make it easy to copy-n-paste things
+    on the next release:
+
+   perl -pi -e 's/\.34/\.35/g' RELEASE
+   perl -pi -e 's/\.33/\.34/g' RELEASE
+   perl -pi -e 's/_33/_34/g'   RELEASE
+
+    now reload this file and bump up the last number of the first
+    command.
+
+  e. commit the changed files
+
+     % svn ci Changes Request/Request.pm STATUS RELEASE
\ No newline at end of file