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