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 | |
f7677ff2 | 5 | Maybe we should name Guile releases after entertaining poisons. |
e54a0ce9 JB |
6 | However, the first release containing the module system should be |
7 | called Godot: "This is the one you've been waiting for." | |
f7677ff2 | 8 | |
deaceb4e | 9 | In release 1.3.2: |
f7677ff2 | 10 | - Release is titled ``wormwood'' release. |
caa8de98 | 11 | - remove #/ syntax |
d33e93c1 | 12 | - Remove SCHEME_LOAD_PATH. |
67ad463a MD |
13 | - remove hook support from boot-9.scm |
14 | (only provided for backward compatibility) | |
15 | ||
deaceb4e | 16 | In release 1.3.4: |
67ad463a MD |
17 | - remove names evalext.c: serial-map, |
18 | ramap.c: serial-array-copy!, serial-array-map! | |
deaceb4e | 19 | - remove module (ice-9 getopt-gnu-style) |
caa8de98 | 20 | |
ed8c8636 MD |
21 | Modules sort.c and random.c should be factored out into separate |
22 | modules (but still be distributed with guile-core) when we get a new | |
23 | module system. | |
24 | ||
cc914709 JB |
25 | Platforms for test builds: |
26 | SunOS (gcc and pcc) --- galapas.ai.mit.edu | |
27 | Solaris (gcc and SUN cc) --- saturn.ai.mit.edu | |
28 | NetBSD (gcc) --- repo-man.ai.mit.edu (use /home/repo/jimb) | |
29 | HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu | |
30 | ||
31 | ||
fb2c2b9e JB |
32 | 1) Check that the versions of aclocal, automake, autoconf, and autoheader |
33 | in your PATH match those given in README. Note that the `make | |
34 | dist' process always invokes these tools, even when all the | |
35 | generated files are up to date. | |
36 | 2) Verify that Guile builds and runs in your working directory. I | |
2732830a JB |
37 | hope that we'll eventually have a test suite to make this more |
38 | concrete, but for the moment, just make sure things seem sane. | |
dbdd0c16 | 39 | 3) Make sure NEWS, INSTALL and the docs are up to date: |
2732830a JB |
40 | a) Scan the ChangeLogs for user-visible changes, marked with an asterisk |
41 | at the left margin. | |
42 | b) Update NEWS and the Texinfo documentation as appropriate. | |
43 | c) Remove the user-visible markers from the log entries once they're | |
44 | documented. | |
9e2310a8 | 45 | d) Check for any [[incomplete]] sections of NEWS. |
dbdd0c16 | 46 | e) Fact-check INSTALL. |
5469b4a1 | 47 | 4) Scan output from `cvs diff' to find files that have changed a lot, but |
fa3f45cc | 48 | do not have up-to-date copyright notices. |
75d6cdf0 JB |
49 | 5) Update the version numbers in GUILE-VERSION, and README. The Guile |
50 | version number should be of the form N.M for a major release, and | |
51 | N.M.L for snapshots and beta releases; L should be even for beta | |
52 | releases, and odd for snapshots. | |
fb2c2b9e | 53 | 6) Set up README appropriately for the release; check name spellings |
a14e4791 | 54 | in THANKS, and reformat. |
fb2c2b9e JB |
55 | 7) Choose new interface numbers for shared libraries. |
56 | 8) Do a `cvs update -A', to get rid of any sticky tags. | |
57 | 9) Rebuild all generated files in the source tree: | |
2bb68285 JB |
58 | a) Install the .m4 files where aclocal will find them. |
59 | b) Run aclocal. | |
60 | c) Run automake. | |
61 | d) Run autoconf. | |
62 | e) Run autoheader. | |
fb2c2b9e JB |
63 | 10) Commit all changes to the CVS repository. |
64 | 11) Verify that the disty works, too: | |
2bb68285 JB |
65 | a) Make a disty, using 'make dist'. |
66 | b) Unpack it somewhere else. | |
67 | c) Remove automake and autoconf from your path, or turn off their | |
68 | execute bits, or something. (Users should be able to build disty | |
69 | without installing those tools.) | |
70 | d) Configure, make, and install. | |
5ec51d13 | 71 | e) Test the installed version; don't forget to unset GUILE_LOAD_PATH. |
716290a7 JB |
72 | f) Test the example code in the doc directory. |
73 | g) If you made any fixes, commit them, and start from a) again | |
14725cbb | 74 | 11a) Add "Guile N.M released." entry to ChangeLog, and commit it. |
fb2c2b9e | 75 | 12) Tag the entire source tree with a tag of the form "release_N_M". |
dbdd0c16 JB |
76 | 13) Copy the tar file over to the GNU machines, and send mail to |
77 | ftp-upload@gnu.org, asking them to put it on prep. | |
fb2c2b9e | 78 | 14) Send an announcement message to gnu-announce@gnu.org. Put |
c484bf7f JB |
79 | "Obtaining Guile" first, then a brief summary of the changes in |
80 | this release, then "Thanks," "About This Distribution," and | |
81 | "Nightly Snapshots." If I remember correctly, the moderator will | |
82 | delay it until the tar file appears on prep. The announcement | |
83 | text should be mostly taken from Guile's README file. | |
fb2c2b9e | 84 | 15) Notify freshmeat.net, although they're probably watching anyway. |
105ac23a JB |
85 | (They got the 1.3 release just fine.) I have no idea if |
86 | www.bowerbird.com.au will be something anyone refers to, but Guile | |
87 | does have an entry there. | |
fb2c2b9e | 88 | 16) Tweak the version numbers in GUILE-VERSION, and README to indicate that |
9986a72f | 89 | the sources are snapshot again. Snapshots should have version numbers |
75d6cdf0 | 90 | of the form "N.M.L", where L is odd. |
fb2c2b9e | 91 | 17) Start a new section of the NEWS file. |
14725cbb JB |
92 | 18) Start a new THANKS file. |
93 | 19) Send mail to majordomo-owner@cygnus.com updating the message you get | |
538c267a | 94 | when you ask majordomo for "info guile". |