Commit | Line | Data |
---|---|---|
2732830a | 1 | This is a checklist for making Guile releases. |
251ca7ab JB |
2 | It's specific to the FSF's development environment; please don't put |
3 | it in the distribution. | |
2732830a JB |
4 | |
5 | 1) Verify that Guile builds and runs in your working directory. I | |
6 | hope that we'll eventually have a test suite to make this more | |
7 | concrete, but for the moment, just make sure things seem sane. | |
8 | 2) Make sure NEWS and the docs are up to date: | |
9 | a) Scan the ChangeLogs for user-visible changes, marked with an asterisk | |
10 | at the left margin. | |
11 | b) Update NEWS and the Texinfo documentation as appropriate. | |
12 | c) Remove the user-visible markers from the log entries once they're | |
13 | documented. | |
d8bb5a39 | 14 | 3) Update the version numbers in GUILE-VERSION, and README, to remove the |
9986a72f JB |
15 | "unreleased" indications. They should be straight numbers, of the form |
16 | "N.M", not alpha numbers, of the form "N.Ma". | |
251ca7ab JB |
17 | 4) Do a `cvs update -A', to get rid of any sticky tags. |
18 | 5) Commit all changes to the CVS repository. | |
19 | 6) Verify that the disty works, too: | |
2732830a JB |
20 | a) Make a disty, using 'make dist'. |
21 | b) Unpack it somewhere else. | |
22 | c) Remove automake and autoconf from your path, or turn off their | |
d8bb5a39 JB |
23 | execute bits, or something. (Users should be able to build disty |
24 | without installing those tools.) | |
2732830a JB |
25 | d) Configure, make, and install. |
26 | e) Test the installed version; don't forget to unset SCHEME_LOAD_PATH. | |
251ca7ab JB |
27 | f) If you made any fixes, commit them, and start from the top of 6). |
28 | 7) Tag the entire source tree with a tag of the form "release_N_M". | |
29 | 8) Copy the tar file over to the GNU machines, and ask the appropriate | |
2732830a JB |
30 | person to put it on prep. At the time of this writing, Daniel Hagerty |
31 | <hag@ai.mit.edu> has usually been generous enough to help with that. | |
251ca7ab | 32 | 9) Send an announcement message to gnu-announce@prep.ai.mit.edu. If I |
2732830a | 33 | remember correctly, the moderator will delay it until the tar file |
d8bb5a39 JB |
34 | appears on prep. The announcement text should be mostly taken from |
35 | Guile's README file. | |
251ca7ab | 36 | 10) Tweak the version numbers in GUILE-VERSION, and README to indicate that |
9986a72f JB |
37 | the sources are snapshot again. Snapshots should have version numbers |
38 | of the form "N.Ma", where the "a" means "alpha". | |
39 | 11) Start a new section of the NEWS file. |