*** empty log message ***

diff --git a/RELEASE b/RELEASE
index d0ae561..abae67f 100644 (file)
--- a/RELEASE
+++ b/RELEASE
@@ -3,8 +3,8 @@ It's specific to the FSF's development environment; please don't put
 it in the distribution.
 
 In release 1.3:
-- make #/ generate a warning.
-- make SCHEME_LOAD_PATH generate a warning.
+- (done) make #/ generate a warning.
+- (done) make SCHEME_LOAD_PATH generate a warning.
 - Perry Metzger <perry@piermont.com> is willing to do beta-testing
   for NetBSD.
 
@@ -19,35 +19,37 @@ NetBSD (gcc) --- repo-man.ai.mit.edu (use /home/repo/jimb)
 HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu
 
 
-1) Verify that Guile builds and runs in your working directory.  I
+1) Check that the versions of aclocal, automake, autoconf, and autoheader
+   in your PATH match those given in README.  Note that the `make
+   dist' process always invokes these tools, even when all the
+   generated files are up to date.
+2) Verify that Guile builds and runs in your working directory.  I
    hope that we'll eventually have a test suite to make this more
    concrete, but for the moment, just make sure things seem sane.
-2) Make sure NEWS and the docs are up to date:
+3) Make sure NEWS and the docs are up to date:
    a) Scan the ChangeLogs for user-visible changes, marked with an asterisk
       at the left margin.
    b) Update NEWS and the Texinfo documentation as appropriate.
    c) Remove the user-visible markers from the log entries once they're
       documented.
    d) Check for any [[incomplete]] sections of NEWS.
-3) Scan output from `cvs log' to find files that have changed a lot, but
+4) Scan output from `cvs log' to find files that have changed a lot, but
    do not have up-to-date copyright notices.
-4) Update the version numbers in GUILE-VERSION, and README, to remove the
+5) Update the version numbers in GUILE-VERSION, and README, to remove the
    "unreleased" indications.  They should be straight numbers, of the form
    "N.M", not alpha numbers, of the form "N.Ma".
-5) Set up README appropriately for the release; check name spellings
+6) Set up README appropriately for the release; check name spellings
    in THANKS, and reformat.
-6) Choose new interface numbers for shared libraries.
-7) Do a `cvs update -A', to get rid of any sticky tags.
-8) Rebuild all generated files in the source tree:
-   a) Check that the versions of aclocal, automake, autoconf, and autoheader
-      in your PATH match those given in README.
+7) Choose new interface numbers for shared libraries.
+8) Do a `cvs update -A', to get rid of any sticky tags.
+9) Rebuild all generated files in the source tree:
    a) Install the .m4 files where aclocal will find them.
    b) Run aclocal.
    c) Run automake.
    d) Run autoconf.
    e) Run autoheader.
-9) Commit all changes to the CVS repository.
-10) Verify that the disty works, too:
+10) Commit all changes to the CVS repository.
+11) Verify that the disty works, too:
     a) Make a disty, using 'make dist'.
     b) Unpack it somewhere else.
     c) Remove automake and autoconf from your path, or turn off their
@@ -56,20 +58,21 @@ HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu
     d) Configure, make, and install.
     e) Test the installed version; don't forget to unset SCHEME_LOAD_PATH.
     f) If you made any fixes, commit them, and start from a) again
-11) Tag the entire source tree with a tag of the form "release_N_M".
-12) Copy the tar file over to the GNU machines, and ask the appropriate
+12) Tag the entire source tree with a tag of the form "release_N_M".
+13) Copy the tar file over to the GNU machines, and ask the appropriate
     person to put it on prep.  At the time of this writing, Daniel Hagerty
     <hag@ai.mit.edu> has been generous about helping with that.
-13) Send an announcement message to gnu-announce@gnu.org.  Put
+14) Send an announcement message to gnu-announce@gnu.org.  Put
     "Obtaining Guile" first, then a brief summary of the changes in
     this release, then "Thanks," "About This Distribution," and
     "Nightly Snapshots."  If I remember correctly, the moderator will
     delay it until the tar file appears on prep.  The announcement
     text should be mostly taken from Guile's README file.
-14) Notify freshmeat.net, although they're probably watching anyway.
-15) Tweak the version numbers in GUILE-VERSION, and README to indicate that 
+15) Notify freshmeat.net, although they're probably watching anyway.
+16) Tweak the version numbers in GUILE-VERSION, and README to indicate that 
     the sources are snapshot again.  Snapshots should have version numbers 
-    of the form "N.Ma", where the "a" means "alpha".
-16) Start a new section of the NEWS file.
-17) Send mail to majordomo-owner@cygnus.com updating the message you get
+    of the form "N.M.L", where L is odd for snapshots, and even for
+    real releases.
+17) Start a new section of the NEWS file.
+18) Send mail to majordomo-owner@cygnus.com updating the message you get
     when you ask majordomo for "info guile".