Hrmmph..

[bpt/guile.git] / RELEASE

diff --git a/RELEASE b/RELEASE
index 3c1a6bb..b057216 100644 (file)
--- a/RELEASE
+++ b/RELEASE
@@ -5,7 +5,7 @@ it in the distribution.
 In release 1.3:
 - (done) make #/ generate a warning.
 - (done) make SCHEME_LOAD_PATH generate a warning.
-- Perry Metzger <perry@piermont.com> is willing to do beta-testing
+- (done) Perry Metzger <perry@piermont.com> is willing to do beta-testing
   for NetBSD.
 
 In release 1.4:
@@ -26,14 +26,15 @@ HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu
 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.
-3) Make sure NEWS and the docs are up to date:
+3) Make sure NEWS, INSTALL 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.
-4) Scan output from `cvs log' to find files that have changed a lot, but
+   e) Fact-check INSTALL.
+4) Scan output from `cvs diff' to find files that have changed a lot, but
    do not have up-to-date copyright notices.
 5) Update the version numbers in GUILE-VERSION, and README.  The Guile
    version number should be of the form N.M for a major release, and
@@ -57,12 +58,13 @@ HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu
        execute bits, or something.  (Users should be able to build disty
        without installing those tools.)
     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
+    e) Test the installed version; don't forget to unset GUILE_LOAD_PATH.
+    f) Test the example code in the doc directory. 
+    g) If you made any fixes, commit them, and start from a) again
+11a) Add "Guile N.M released." entry to ChangeLog, and commit it.
 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) Copy the tar file over to the GNU machines, and send mail to
+    ftp-upload@gnu.org, asking them to put it on prep.
 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
@@ -74,5 +76,6 @@ HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu
     the sources are snapshot again.  Snapshots should have version numbers 
     of the form "N.M.L", where L is odd.
 17) Start a new section of the NEWS file.
-18) Send mail to majordomo-owner@cygnus.com updating the message you get
+18) Start a new THANKS file.
+19) Send mail to majordomo-owner@cygnus.com updating the message you get
     when you ask majordomo for "info guile".