*** empty log message ***

[bpt/guile.git] / RELEASE

diff --git a/RELEASE b/RELEASE
index 76ab6f9..f1ae2e0 100644 (file)
--- a/RELEASE
+++ b/RELEASE
@@ -29,14 +29,6 @@ Tom Tromey <tromey@cygnus.com>:
   mips-sgi-irix6.3
   sparc-sun-sunos4.1.4
 
-Ian Grant <I.A.N.Grant@damtp.cam.ac.uk>:
-
-  alpha-dec-osf4.0e
-
-Julian Satchell <satchell@merry.dra.hmg.gb>:
-
-  dec-mips-ultrix
-
 Perry Metzger <perry@piermont.com>
 
   NetBSD
@@ -118,17 +110,26 @@ Spiffing checklist:
 * Commit all changes to the CVS repository.
 
 * Build a test distribution.
+
   + update GUILE-VERSION each time you make a test distribution.  For
     example, just before the 1.6.0 release, we went through some
     number of 1.5.X test releases.
+
   + BEFORE doing 'make dist', configure the source tree for build
-    in the same tree with configuration options
-    --enable-maintainer-mode --enable-debug-malloc --with-threads.
+    in the same tree with these configuration options:
+      --enable-maintainer-mode
+      --enable-debug-malloc
+      --with-threads
+      --enable-error-on-warning
+
   + Make sure that readline was enabled correctly.
+
   + Build the tree.
     (If the above steps are not done, the dependencies won't be properly
     included in the generated Makefile.in files.)
+
   + Then do 'make dist'.
+
   + Check that the dependencies in guile-readline/Makefile look OK.
     (We currently use a kludge which edits the dependencies generated
     by automake so that Guile can be built in a directory separate
@@ -192,7 +193,7 @@ Once you've got a disty that seems pretty solid:
 
 Punting checklist:
 
-* Add "Guile N.M released." entry to the top-level ChangeLog, and commit it.
+* Add "Guile X.Y.Z released." entry to the top-level ChangeLog, and commit it.
 
 * Tag the entire source tree with a tag of the form "release_X-Y-Z",
   i.e for release 1.6.0, use release_1-6-0