*** empty log message ***

[bpt/guile.git] / RELEASE

diff --git a/RELEASE b/RELEASE
index 21c13b8..61d3ac0 100644 (file)
--- a/RELEASE
+++ b/RELEASE
@@ -14,6 +14,7 @@ In release 1.4:
 - remove kw.h, scm_tc16_kw
 - remove genio.h
 - remove deprecated function scm_newsmob.
+- remove deprecated function scm_make_named_hook.
 
 Modules sort.c and random.c should be factored out into separate
 modules (but still be distributed with guile-core) when we get a new
@@ -48,6 +49,10 @@ Julian Satchell <satchell@merry.dra.hmg.gb>:
 
   dec-mips-ultrix
 
+Perry Metzger <perry@piermont.com>
+
+  NetBSD
+
 
 Release Checklists ===================================================
 
@@ -89,18 +94,19 @@ Spiffing checklist:
 * Rebuild all generated files in the source tree:
   + Install the .m4 files where aclocal will find them.
   + Run aclocal.
-  + Run automake.
   + Run autoconf.
   + Run autoheader.
+  + Run automake.
 * Verify that Guile builds and runs in your working directory.
 * Run the test suite, in guile-modules/test-suite.
 * Commit all changes to the CVS repository.
 * Build a test distribution.
   + BEFORE doing 'make dist', configure the source tree for build
     in the same tree with configuration option --with-threads.
-    Make sure that readline was enabled correctly.
-    If this is not done, there will be missing dependencies in two
-    Makefile.in.
+  + 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'.
 * Give the test disty to various people to try.  Here's what you should do:
   + Unset GUILE_LOAD_PATH.
@@ -132,6 +138,7 @@ Punting checklist:
 * Add "Guile N.M released." entry to the top-level ChangeLog, and commit it.
 * Tag the entire source tree with a tag of the form "release_N_M" 
   or "release_N_M_L".
+* Do a 'make dist'.
 * Put the distribution up for FTP somewhere, and send mail to
   ftp-upload@gnu.org, asking them to put it on prep.
 * Send an announcement message to gnu-announce@gnu.org.  Put a brief