RELEASE

   1 This is a checklist for making Guile releases.
   2 It's specific to the FSF's development environment; please don't put
   3 it in the distribution.
   4
   5 In release 1.3:
   6 - make #/ generate a warning.
   7
   8 In release 1.4:
   9 - remove #/ syntax
  10
  11 Platforms for test builds:
  12 SunOS (gcc and pcc) --- galapas.ai.mit.edu
  13 Solaris (gcc and SUN cc) --- saturn.ai.mit.edu
  14 NetBSD (gcc) --- repo-man.ai.mit.edu (use /home/repo/jimb)
  15 HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu
  16
  17
  18 1) Verify that Guile builds and runs in your working directory.  I
  19    hope that we'll eventually have a test suite to make this more
  20    concrete, but for the moment, just make sure things seem sane.
  21 2) Make sure NEWS and the docs are up to date:
  22    a) Scan the ChangeLogs for user-visible changes, marked with an asterisk
  23       at the left margin.
  24    b) Update NEWS and the Texinfo documentation as appropriate.
  25    c) Remove the user-visible markers from the log entries once they're
  26       documented.
  27    d) Check for any [[incomplete]] sections of NEWS.
  28 3) Scan output from `cvs log' to find files that have changed a lot, but
  29    do not have up-to-date copyright notices.
  30 4) Update the version numbers in GUILE-VERSION, and README, to remove the
  31    "unreleased" indications.  They should be straight numbers, of the form
  32    "N.M", not alpha numbers, of the form "N.Ma".
  33 5) Set up README appropriately for the release.
  34 6) Choose new interface numbers for shared libraries.
  35 7) Do a `cvs update -A', to get rid of any sticky tags.
  36 8) Commit all changes to the CVS repository.
  37 9) Verify that the disty works, too:
  38    a) Make a disty, using 'make dist'.
  39    b) Unpack it somewhere else.
  40    c) Remove automake and autoconf from your path, or turn off their
  41       execute bits, or something.  (Users should be able to build disty
  42       without installing those tools.)
  43    d) Configure, make, and install.
  44    e) Test the installed version; don't forget to unset SCHEME_LOAD_PATH.
  45    f) If you made any fixes, commit them, and start from a) again
  46 10) Tag the entire source tree with a tag of the form "release_N_M".
  47 11) Copy the tar file over to the GNU machines, and ask the appropriate
  48     person to put it on prep.  At the time of this writing, Daniel Hagerty
  49     <hag@ai.mit.edu> has been generous about helping with that.
  50 12) Send an announcement message to gnu-announce@prep.ai.mit.edu.  Put
  51     "Obtaining Guile" first, then a brief summary of the changes in
  52     this release, then "Thanks," "About This Distribution," and
  53     "Nightly Snapshots."  If I remember correctly, the moderator will
  54     delay it until the tar file appears on prep.  The announcement
  55     text should be mostly taken from Guile's README file.
  56 13) Tweak the version numbers in GUILE-VERSION, and README to indicate that
  57     the sources are snapshot again.  Snapshots should have version numbers
  58     of the form "N.Ma", where the "a" means "alpha".
  59 14) Start a new section of the NEWS file.
  60 15) Send mail to majordomo-owner@cygnus.com updating the message you get
  61     when you ask majordomo for "info guile".