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

[do...@apache.org]

Author: dos
Date: Fri Jan 29 02:29:50 2010
New Revision: 904356

URL: http://svn.apache.org/viewvc?rev=904356&view=rev
Log:
add note about trunk's automated sa-update nightly builds needing a version bump before major releases

Modified:
    spamassassin/trunk/build/README

Modified: spamassassin/trunk/build/README
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/README?rev=904356&r1=904355&r2=904356&view=diff
==============================================================================
--- spamassassin/trunk/build/README (original)
+++ spamassassin/trunk/build/README Fri Jan 29 02:29:50 2010
@@ -274,6 +274,28 @@
 
 	(where X.Y.N is the new version number)
 
+- [X.Y.0 RELEASES ONLY]: in trunk, bump the version to the correct
+  version in the following files (just as above for the branch):
+
+  - lib/Mail/SpamAssassin.pm
+  - spamassassin.spec
+
+- [X.Y.0 RELEASES ONLY]: NOTE: This may change, make sure this info is
+  still accurate before changing this (preferrably find out BEFORE doing
+  an X.Y.0 release.  Update the mkupdates stuff:
+
+  - In build/mkupdates/run_part2 change versions="X.Y.0" to the new
+    development version (X.Y+1.0).
+
+  - Create an empty file for the new version number in
+    /var/named/updates.dev.spamassassin.org.d/ on the zone
+
+  - Add "$INCLUDE /var/named/updates.spamassassin.org.d/X.Y+1.0" to the
+    spamassassin.org zone file in spamassassin/dns/
+
+  - commit the changes, update the zone (if not doing above on the zone)
+    and tick the zone file using build/mkupdates/tick_zone_serial
+
 - !WARNING! After the next step, the version number will be considered
   "burned". The number is locked for this particular code.  The same
   number cannot be used for a future different release.  So make sure