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 | |
f8c9d497 JB |
5 | Maybe we should name Guile releases after entertaining poisons: |
6 | absinthe, etc. However, the first release containing the module | |
7 | system should be called Godot: "This is the one you've been waiting | |
8 | for." | |
f7677ff2 | 9 | |
7c1e0b12 | 10 | In release 1.5: |
894a712b DH |
11 | - remove deprecated macros: SCM_INPORTP, SCM_OUTPORTP, SCM_CRDY, SCM_ICHRP, |
12 | SCM_ICHR, SCM_MAKICHR, SCM_SETJMPBUF, SCM_NSTRINGP, SCM_NRWSTRINGP, | |
13 | SCM_NVECTORP | |
820920e6 | 14 | - remove gc-thunk (It has been replaced by after-gc-hook.) |
894a712b DH |
15 | - remove scm_sysmissing |
16 | - remove gh_int2scmb (replaced by gh_bool2scm) | |
17 | - remove scm_fseek (replaced by scm_seek) | |
18 | - remove scm_tag | |
e11f8b42 DH |
19 | - remove code related to the name property of hooks. Also, check init.c, |
20 | since the dependency between hooks and objprop will then be eliminated. | |
894a712b DH |
21 | Dirk:FIXME:: look into deprecated things in numbers.h and tags.h, don't forget |
22 | to update NEWS accordingly. | |
7c1e0b12 | 23 | |
ed8c8636 MD |
24 | Modules sort.c and random.c should be factored out into separate |
25 | modules (but still be distributed with guile-core) when we get a new | |
26 | module system. | |
27 | ||
cc914709 JB |
28 | Platforms for test builds: |
29 | SunOS (gcc and pcc) --- galapas.ai.mit.edu | |
30 | Solaris (gcc and SUN cc) --- saturn.ai.mit.edu | |
31 | NetBSD (gcc) --- repo-man.ai.mit.edu (use /home/repo/jimb) | |
32 | HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu | |
33 | ||
422b92d2 | 34 | These gentlemen have kindly offered to do pre-release testing: |
99ac53b9 MD |
35 | |
36 | Tom Tromey <tromey@cygnus.com>: | |
37 | ||
38 | alphaev5-unknown-linux-gnu | |
39 | hppa1.1-hp-hpux10.20 | |
40 | hppa1.1-hp-hpux11.00 | |
41 | mips-sgi-irix5.3 | |
42 | powerpc-ibm-aix4.2.0.0 | |
43 | powerpc-unknown-linux-gnu | |
44 | sparc-sun-solaris2.6 | |
45 | i686-pc-linux-gnu | |
46 | mips-sgi-irix6.3 | |
47 | sparc-sun-sunos4.1.4 | |
48 | ||
49 | Ian Grant <I.A.N.Grant@damtp.cam.ac.uk>: | |
50 | ||
51 | alpha-dec-osf4.0e | |
52 | ||
53 | Julian Satchell <satchell@merry.dra.hmg.gb>: | |
54 | ||
55 | dec-mips-ultrix | |
cc914709 | 56 | |
d4c83f63 JB |
57 | Perry Metzger <perry@piermont.com> |
58 | ||
59 | NetBSD | |
60 | ||
3f686b10 JB |
61 | |
62 | Release Checklists =================================================== | |
63 | ||
64 | There are basically two phases to doing a release: | |
65 | ||
66 | * "SPIFFING": Updating NEWS, README, INSTALL. Running tests. Getting | |
67 | people to try builds on various machines. Getting everything | |
68 | straightened up. | |
69 | ||
70 | * "PUNTING": Updating the version numbers. Tagging the sources. Asking | |
71 | the FSF to put the disty on ftp.gnu.org. Posting announcements. | |
72 | ||
73 | The "Spiffing" phase you might go through several times as you | |
74 | discover problems. The "Punting" phase you do only once. | |
75 | ||
76 | ||
77 | Spiffing checklist: | |
78 | ||
79 | * Do a `cvs update -A', to get rid of any sticky tags in your working | |
80 | directory. | |
81 | * Check for files that have changed a lot, but do not have up-to-date | |
fba33ff1 | 82 | copyright notices. This can be as simple as doing: |
341f78c9 | 83 | grep 'Copyright' * | grep -v 1999 |
fba33ff1 | 84 | and looking for files you know you've worked on a lot. |
3f686b10 JB |
85 | * Make sure NEWS, INSTALL and the docs are up to date: |
86 | + Scan the ChangeLogs for user-visible changes, marked with an asterisk | |
87 | at the left margin. | |
88 | + Update NEWS and the Texinfo documentation as appropriate. | |
89 | + Remove the user-visible markers from the log entries once they're | |
90 | documented. | |
91 | + Check for any [[incomplete]] sections of NEWS. | |
92 | + Fact-check INSTALL. | |
e4445210 | 93 | * Make sure the downloading addresses and filenames in README are |
340a8770 | 94 | current. (But don't bump the version number yet. We do that below.) |
3f686b10 | 95 | * Check that the versions of aclocal, automake, autoconf, and autoheader |
f43aac9a | 96 | in your PATH match those given in HACKING. Note that the `make |
3f686b10 JB |
97 | dist' process always invokes these tools, even when all the |
98 | generated files are up to date. | |
99 | * Rebuild all generated files in the source tree: | |
100 | + Install the .m4 files where aclocal will find them. | |
101 | + Run aclocal. | |
3f686b10 JB |
102 | + Run autoconf. |
103 | + Run autoheader. | |
14a7a25d | 104 | + Run automake. |
3f686b10 | 105 | * Verify that Guile builds and runs in your working directory. |
f43aac9a | 106 | * Run the test suite, in guile-core/test-suite. |
3f686b10 JB |
107 | * Commit all changes to the CVS repository. |
108 | * Build a test distribution. | |
109 | + BEFORE doing 'make dist', configure the source tree for build | |
9a8a1e8a MD |
110 | in the same tree with configuration options |
111 | --enable-maintainer-mode --enable-debug-malloc --with-threads. | |
24e720c8 JB |
112 | + Make sure that readline was enabled correctly. |
113 | + Build the tree. | |
114 | (If the above steps are not done, the dependencies won't be properly | |
115 | included in the generated Makefile.in files.) | |
3f686b10 JB |
116 | + Then do 'make dist'. |
117 | * Give the test disty to various people to try. Here's what you should do: | |
118 | + Unset GUILE_LOAD_PATH. | |
119 | + Remove automake and autoconf from your path, or turn off their | |
120 | execute bits, or something. (Users must be able to build the | |
121 | disty without installing those tools.) | |
122 | + Configure, make, and install. | |
123 | + Make sure LD_LIBRARY_PATH doesn't include anything unnecessary. | |
124 | + Run the test suite on the installed version. | |
125 | + You might try the example code in the doc directory. | |
126 | ||
127 | Once you've got a disty that seems pretty solid: | |
128 | ||
129 | * Choose new interface numbers for shared libraries. | |
130 | * Update the version numbers in GUILE-VERSION and README. (There are | |
131 | many places in README that need updating!) The Guile version | |
132 | number should have one of the following forms: | |
133 | N.M - a major release | |
134 | N.M.L, where L is even - a minor release | |
135 | N.M.L, where L is odd - sources from CVS or nightly snapshot | |
136 | * Reformat the names in THANKS. | |
137 | * Do a `cvs update -A' of the whole tree, to look for any stray | |
138 | uncommitted or accidental changes. | |
139 | * Commit your changes. | |
140 | * Make one last test distribution. | |
141 | ||
142 | Punting checklist: | |
143 | ||
144 | * Add "Guile N.M released." entry to the top-level ChangeLog, and commit it. | |
145 | * Tag the entire source tree with a tag of the form "release_N_M" | |
146 | or "release_N_M_L". | |
bab4e1cc | 147 | * Do a 'make dist'. |
3f686b10 JB |
148 | * Put the distribution up for FTP somewhere, and send mail to |
149 | ftp-upload@gnu.org, asking them to put it on prep. | |
150 | * Send an announcement message to gnu-announce@gnu.org. Put a brief | |
151 | summary of the changes in this release first, then "Obtaining | |
152 | Guile", "Thanks", "About This Distribution," and "Nightly | |
153 | Snapshots." If I remember correctly, the moderator will delay it | |
154 | until the distribution appears on ftp.gnu.org. The announcement | |
155 | text should be mostly taken from Guile's README file. | |
156 | * Notify freshmeat.net, although they're probably watching anyway. | |
157 | (They got the 1.3 release just fine.) I have no idea if | |
158 | www.bowerbird.com.au will be something anyone refers to, but Guile | |
159 | does have an entry there. | |
160 | * Tweak the version numbers in GUILE-VERSION, and README to indicate | |
161 | that the sources are a snapshot again. Snapshots should have | |
162 | version numbers of the form "N.M.L", where L is odd. | |
163 | * Start a new section of the NEWS file. | |
164 | * Start a new THANKS file. | |
165 | * Send mail to majordomo-owner@cygnus.com updating the message you | |
166 | get when you ask majordomo for "info guile". |