Mailing List Archive

Author: jm
Date: Tue May 3 14:31:46 2005
New Revision: 167999

URL: http://svn.apache.org/viewcvs?rev=167999&view=rev
Log:
added note on redoing a messed-up release attempt

Modified:
spamassassin/trunk/build/README

Modified: spamassassin/trunk/build/README
URL: http://svn.apache.org/viewcvs/spamassassin/trunk/build/README?rev=167999&r1=167998&r2=167999&view=diff
==============================================================================
--- spamassassin/trunk/build/README (original)
+++ spamassassin/trunk/build/README Tue May 3 14:31:46 2005
@@ -156,11 +156,20 @@
the release official. The release manager (that's you) may vote as
well. Once there are three or more +1 votes, you may proceed.

-- publish the tarballs
+- !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
+ you're happy before you go on!

- After this 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.
+ If you need to redo something, re-comment the $IS_DEVEL_BUILD line,
+ revert the $VERSION bump, and go back to 'Ensure the new version number
+ takes hold'. You can retag with the normal 'svn copy' command used in
+ 'SVN tag the release files', even if that tag already existed; but be
+ sure to check in another commit message to note what happened, e.g.:
+
+ svn commit -m "oops, had to redo: THIS IS THE REAL X.Y.Z RELEASE"
+
+- publish the tarballs.

(for rc and prerelease builds) copy the tarballs to the website.