RELEASE

   1 This is a checklist for making Guile releases.
   2 Please don't put it in the distribution.
   3
   4 1) Verify that Guile builds and runs in your working directory.  I
   5    hope that we'll eventually have a test suite to make this more
   6    concrete, but for the moment, just make sure things seem sane.
   7 2) Make sure NEWS and the docs are up to date:
   8    a) Scan the ChangeLogs for user-visible changes, marked with an asterisk
   9       at the left margin.
  10    b) Update NEWS and the Texinfo documentation as appropriate.
  11    c) Remove the user-visible markers from the log entries once they're
  12       documented.
  13 3) Update the version numbers in GUILE-VERSION, README,
  14 4) Commit all changes to the CVS repository.
  15 5) Verify that the disty works, too:
  16    a) Make a disty, using 'make dist'.
  17    b) Unpack it somewhere else.
  18    c) Remove automake and autoconf from your path, or turn off their
  19       execute bits, or something.
  20    d) Configure, make, and install.
  21    e) Test the installed version; don't forget to unset SCHEME_LOAD_PATH.
  22    f) If you made any fixes, commit them, and start from the top of 5).
  23 6) Tag the entire source tree with a tag of the form "release_N_M".
  24 7) Copy the tar file over to the GNU machines, and ask the appropriate
  25    person to put it on prep.  At the time of this writing, Daniel Hagerty
  26    <hag@ai.mit.edu> has usually been generous enough to help with that.
  27 8) Send an announcement message to gnu-announce@prep.ai.mit.edu.  If I
  28    remember correctly, the moderator will delay it until the tar file
  29    appears on prep.
  30    a) Remember to give credit, but take responsibility.