svn commit: r1493990 [3/3] - in /spamassassin/trunk: Changes build/README lib/Mail/SpamAssassin.pm

[km...@apache.org]

Modified: spamassassin/trunk/build/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/README?rev=1493990&r1=1493989&r2=1493990&view=diff
==============================================================================
--- spamassassin/trunk/build/README (original)
+++ spamassassin/trunk/build/README Tue Jun 18 03:00:43 2013
@@ -112,9 +112,16 @@ SPAMASSASSIN RELEASE PROCEDURE
     for the point you want to start at if different. I used r1149751 to
     produce the first 3.4.0-pre release, for example.
 
+- Exclude some automated changes from the logs
+
+    cat Changes | perl -ne ' BEGIN{$/=("-"x72)."\n"}
+    chomp; @ln=split/^/;
+    next if @ln==3 && $ln[2]=~/^\s*(promotions validated|auto-generated rules|)\s*$/;
+    print "@ln$/"' > Changes.tmp
+
 - Word wrap the Changes file with something like 
 
-    'fold -sw 74 Changes > Changes.2; mv Changes.2 Changes'
+    fold -sw 74 Changes.tmp > Changes && rm Changes.tmp
 
 - run "make distcheck" to ensure all files are included in the
   distribution that should be, and to ensure all files that are listed

Modified: spamassassin/trunk/lib/Mail/SpamAssassin.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin.pm?rev=1493990&r1=1493989&r2=1493990&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin.pm Tue Jun 18 03:00:43 2013
@@ -99,7 +99,7 @@ $IS_DEVEL_BUILD = 1;        # change for
 # Used during the prerelease/release-candidate part of the official release
 # process. If you hacked up your SA, you should add a version_tag to your .cf
 # files; this variable should not be modified.
-@EXTRA_VERSION = qw(pre3);
+@EXTRA_VERSION = qw(rc1);
 
 @ISA = qw();