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

[jm...@apache.org]

Author: jm
Date: Tue Oct 10 04:26:15 2006
New Revision: 454705

URL: http://svn.apache.org/viewvc?view=rev&rev=454705
Log:
fix some bugs in build procedure; the '3.1.X RELEASED' commit was never working, and the website-update step had some no-ops and obscure messages in it.  backmerge some changes from 3.2.0 trunk regarding spec file updating.  update procedure to match what we're actually doing these days re the announce mail, tarball voting, and the voting requirements.  add note about new PAUSE behaviour.  adopt new means of editing the announce mail, and keeping it in SVN

Modified:
    spamassassin/trunk/build/README

Modified: spamassassin/trunk/build/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/README?view=diff&rev=454705&r1=454704&r2=454705
==============================================================================
--- spamassassin/trunk/build/README (original)
+++ spamassassin/trunk/build/README Tue Oct 10 04:26:15 2006
@@ -281,13 +281,26 @@
 
         https://pause.perl.org/pause/authenquery?ACTION=add_uri
 
+  (Note that recently, PAUSE has started indexing sub-modules under
+  Mail::SpamAssassin::, and it can't deal with our multi-maintainer
+  setup.  You may receive mail indicating that "indexing failed" after
+  the upload; as long as the main Mail::SpamAssassin module was indexed
+  correctly, this is fine.  However, it would help if you could visit
+
+        https://pause.perl.org/pause/authenquery?ACTION=share_perms
+
+  select 3.1 ("Make someone else co-maintainer"), and ensure that the
+  other releasers (JMASON, DOS, FELICITY, others?) all have permissions as
+  'co-maintainer' on the full set of your listed modules in the
+  "Mail::SpamAssassin::" namespace.
+
 - announce on the users, dev, and announce mailing lists using the
   previously-prepared release announcement.
 
-- Before doing the next step, run through the Changes file, and write up a
-  quick summary of the important changes in human-readable format.  This
-  should be less than 600 chars to fit into Freshmeat's format, and
-  to be easily understandable.
+- Before doing the next step, run through the release summary mail, and
+  write up a really short summary of the important changes in
+  human-readable format.  This should be less than 600 chars to fit into
+  Freshmeat's format, and to be easily understandable.
 
 - announce to Freshmeat at http://freshmeat.net/: