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 | 4 | |
caa8de98 JB |
5 | In release 1.2: |
6 | - note that #/ syntax is going to go away. | |
2b272b1e | 7 | - fix all uses of #/ in the dist. |
caa8de98 JB |
8 | |
9 | In release 1.3: | |
10 | - make #/ generate a warning. | |
11 | ||
12 | In release 1.4: | |
13 | - remove #/ syntax | |
14 | ||
2732830a JB |
15 | 1) Verify that Guile builds and runs in your working directory. I |
16 | hope that we'll eventually have a test suite to make this more | |
17 | concrete, but for the moment, just make sure things seem sane. | |
18 | 2) Make sure NEWS and the docs are up to date: | |
19 | a) Scan the ChangeLogs for user-visible changes, marked with an asterisk | |
20 | at the left margin. | |
21 | b) Update NEWS and the Texinfo documentation as appropriate. | |
22 | c) Remove the user-visible markers from the log entries once they're | |
23 | documented. | |
fa3f45cc JB |
24 | 3) Scan output from `cvs log' to find files that have changed a lot, but |
25 | do not have up-to-date copyright notices. | |
26 | 4) Update the version numbers in GUILE-VERSION, and README, to remove the | |
9986a72f JB |
27 | "unreleased" indications. They should be straight numbers, of the form |
28 | "N.M", not alpha numbers, of the form "N.Ma". | |
8225b156 JB |
29 | 5) Choose new interface numbers for shared libraries. |
30 | 6) Do a `cvs update -A', to get rid of any sticky tags. | |
31 | 7) Commit all changes to the CVS repository. | |
32 | 8) Verify that the disty works, too: | |
2732830a JB |
33 | a) Make a disty, using 'make dist'. |
34 | b) Unpack it somewhere else. | |
35 | c) Remove automake and autoconf from your path, or turn off their | |
d8bb5a39 JB |
36 | execute bits, or something. (Users should be able to build disty |
37 | without installing those tools.) | |
2732830a JB |
38 | d) Configure, make, and install. |
39 | e) Test the installed version; don't forget to unset SCHEME_LOAD_PATH. | |
fa3f45cc | 40 | f) If you made any fixes, commit them, and start from a) again |
8225b156 JB |
41 | 9) Tag the entire source tree with a tag of the form "release_N_M". |
42 | 10) Copy the tar file over to the GNU machines, and ask the appropriate | |
43 | person to put it on prep. At the time of this writing, Daniel Hagerty | |
44 | <hag@ai.mit.edu> has been generous about helping with that. | |
45 | 11) Send an announcement message to gnu-announce@prep.ai.mit.edu. If I | |
fa3f45cc JB |
46 | remember correctly, the moderator will delay it until the tar file |
47 | appears on prep. The announcement text should be mostly taken from | |
48 | Guile's README file. | |
8225b156 | 49 | 12) Tweak the version numbers in GUILE-VERSION, and README to indicate that |
9986a72f JB |
50 | the sources are snapshot again. Snapshots should have version numbers |
51 | of the form "N.Ma", where the "a" means "alpha". | |
8225b156 JB |
52 | 13) Start a new section of the NEWS file. |
53 | 14) Send mail to majordomo-owner@cygnus.com updating the message you get | |
538c267a | 54 | when you ask majordomo for "info guile". |