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. | |
fa3f45cc JB |
14 | 3) Scan output from `cvs log' to find files that have changed a lot, but |
15 | do not have up-to-date copyright notices. | |
16 | 4) Update the version numbers in GUILE-VERSION, and README, to remove the | |
9986a72f JB |
17 | "unreleased" indications. They should be straight numbers, of the form |
18 | "N.M", not alpha numbers, of the form "N.Ma". | |
fa3f45cc JB |
19 | 5) Do a `cvs update -A', to get rid of any sticky tags. |
20 | 6) Commit all changes to the CVS repository. | |
21 | 7) Verify that the disty works, too: | |
2732830a JB |
22 | a) Make a disty, using 'make dist'. |
23 | b) Unpack it somewhere else. | |
24 | c) Remove automake and autoconf from your path, or turn off their | |
d8bb5a39 JB |
25 | execute bits, or something. (Users should be able to build disty |
26 | without installing those tools.) | |
2732830a JB |
27 | d) Configure, make, and install. |
28 | e) Test the installed version; don't forget to unset SCHEME_LOAD_PATH. | |
fa3f45cc JB |
29 | f) If you made any fixes, commit them, and start from a) again |
30 | 8) Tag the entire source tree with a tag of the form "release_N_M". | |
31 | 9) Copy the tar file over to the GNU machines, and ask the appropriate | |
2732830a | 32 | person to put it on prep. At the time of this writing, Daniel Hagerty |
fa3f45cc JB |
33 | <hag@ai.mit.edu> has been generous about helping with that. |
34 | 10) Send an announcement message to gnu-announce@prep.ai.mit.edu. If I | |
35 | remember correctly, the moderator will delay it until the tar file | |
36 | appears on prep. The announcement text should be mostly taken from | |
37 | Guile's README file. | |
38 | 11) Tweak the version numbers in GUILE-VERSION, and README to indicate that | |
9986a72f JB |
39 | the sources are snapshot again. Snapshots should have version numbers |
40 | of the form "N.Ma", where the "a" means "alpha". | |
fa3f45cc | 41 | 12) Start a new section of the NEWS file. |
538c267a JB |
42 | 13) Send mail to majordomo-owner@cygnus.com updating the message you get |
43 | when you ask majordomo for "info guile". |