svn commit: r1572366 - /spamassassin/trunk/build/README

[km...@apache.org]

Author: kmcgrail
Date: Thu Feb 27 00:26:42 2014
New Revision: 1572366

URL: http://svn.apache.org/r1572366
Log:
Updating build docs to reflect svnpubsub for publishing tarballs

Modified:
    spamassassin/trunk/build/README

Modified: spamassassin/trunk/build/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/README?rev=1572366&r1=1572365&r2=1572366&view=diff
==============================================================================
--- spamassassin/trunk/build/README (original)
+++ spamassassin/trunk/build/README Thu Feb 27 00:26:42 2014
@@ -383,27 +383,37 @@ SPAMASSASSIN RELEASE PROCEDURE
 
         http://people.apache.org/~kmcgrail/devel/ for example
 
+  NOTE: It's also feasible that you could publish via SVNPubSub as noted 
+  below but using the SVN repository at:
+
+    https://dist.apache.org/repos/dist/dev/SpamAssassin
+ 
+  The choice is up to the Release Manager for these test builds.
+
+
   For full release builds, you need to publish using SVNPubSub.
  
-  Need to commit the new artifacts and signature files to 
-  https://dist.apache.org/repos/dist/spamassassin once a
+  This is a simple matter of committing the new artifacts and signature 
+  files to https://dist.apache.org/repos/dist/spamassassin once a
   release vote passes. 
 
-        **** NEEDS SPECIFIC COMMANDS FOR HOW TO COMMIT VIA SVNPUBSUB ****
-
   [note: Symlinks may not work on all mirrors even though there may be 
   documentation to the contrary.]
 
-  See https://issues.apache.org/jira/browse/INFRA-7295
+  As documented at http://www.apache.org/dev/release.html, SpamAssassin
+  as of 2014-02-26 publishes tarballs by manipulating the repo on svn.
+
+  svn co https://dist.apache.org/repos/dist/release/spamassassin/ release
 
-- Remove tar-balls for now-obsolete versions from dist:
+  - Manipulate the files to add the new version artifacts to the source dir
+  - Remove tar-balls for now-obsolete versions from dist:
 
-  Only the most recent version of each supported release line should be
-  stored.  The archives will auto update.  
-  See http://www.apache.org/dev/release#archived.
+    Only the most recent version of each supported release line should be
+    stored.  The archives will auto update.  
+    See http://www.apache.org/dev/release#archived.
+  - Commit 
+  - Wait 24 hours before you announce to allow mirrors to update
 
-        **** NEEDS SPECIFIC COMMANDS FOR HOW TO COMMIT VIA SVNPUBSUB ****
-        
   (NOTE: it may be better to wait a while before doing this; it appears to
   take a while for the spamassassin.apache.org website mirror script to
   run, so the old downloads page will stick around for a while before it's