[bpt/guile.git] / RELEASE

This is a checklist for making Guile releases.
Please don't put it in the distribution.

1) 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.
2) Make sure NEWS 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.
3) Update the version numbers in GUILE-VERSION, and README, to remove the
   "unreleased" indications.
4) Commit all changes to the CVS repository.
5) Verify that the disty works, too:
   a) Make a disty, using 'make dist'.
   b) Unpack it somewhere else.
   c) Remove automake and autoconf from your path, or turn off their
      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 the top of 5).
6) Tag the entire source tree with a tag of the form "release_N_M".
7) 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 usually been generous enough to help with that.
8) Send an announcement message to gnu-announce@prep.ai.mit.edu.  If I
   remember correctly, the moderator will delay it until the tar file
   appears on prep.  The announcement text should be mostly taken from 
   Guile's README file.
9) Tweak the version numbers in GUILE-VERSION, and README to indicate that 
   the sources are snapshot again.
Commit	Line	Data
2732830a JB	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.
d8bb5a39 JB	13	3) Update the version numbers in GUILE-VERSION, and README, to remove the
d8bb5a39 JB	14	"unreleased" indications.
2732830a JB	15	4) Commit all changes to the CVS repository.
	16	5) Verify that the disty works, too:
	17	a) Make a disty, using 'make dist'.
	18	b) Unpack it somewhere else.
	19	c) Remove automake and autoconf from your path, or turn off their
d8bb5a39 JB	20	execute bits, or something. (Users should be able to build disty
d8bb5a39 JB	21	without installing those tools.)
2732830a JB	22	d) Configure, make, and install.
	23	e) Test the installed version; don't forget to unset SCHEME_LOAD_PATH.
	24	f) If you made any fixes, commit them, and start from the top of 5).
	25	6) Tag the entire source tree with a tag of the form "release_N_M".
	26	7) Copy the tar file over to the GNU machines, and ask the appropriate
	27	person to put it on prep. At the time of this writing, Daniel Hagerty
	28	<hag@ai.mit.edu> has usually been generous enough to help with that.
	29	8) Send an announcement message to gnu-announce@prep.ai.mit.edu. If I
	30	remember correctly, the moderator will delay it until the tar file
d8bb5a39 JB	31	appears on prep. The announcement text should be mostly taken from
	32	Guile's README file.
	33	9) Tweak the version numbers in GUILE-VERSION, and README to indicate that
	34	the sources are snapshot again.