system should be called Godot: "This is the one you've been waiting
for."
-In release 1.3.4:
-- remove hook support from boot-9.scm
- (only provided for backward compatibility)
-
-In release 1.4:
-- remove names evalext.c: serial-map,
- ramap.c: serial-array-copy!, serial-array-map!
-- remove module (ice-9 getopt-gnu-style)
-- remove kw.h, scm_tc16_kw
-- remove genio.h
-- remove deprecated function scm_newsmob.
-
-Modules sort.c and random.c should be factored out into separate
-modules (but still be distributed with guile-core) when we get a new
-module system.
-
Platforms for test builds:
SunOS (gcc and pcc) --- galapas.ai.mit.edu
Solaris (gcc and SUN cc) --- saturn.ai.mit.edu
Ian Grant <I.A.N.Grant@damtp.cam.ac.uk>:
- alpha-dec-osf4.0e
+ alpha-dec-osf4.0e
Julian Satchell <satchell@merry.dra.hmg.gb>:
dec-mips-ultrix
+Perry Metzger <perry@piermont.com>
+
+ NetBSD
+
Release Checklists ===================================================
* Do a `cvs update -A', to get rid of any sticky tags in your working
directory.
* Check for files that have changed a lot, but do not have up-to-date
- copyright notices. (It would be nice to have a script to do this...)
-* Make sure NEWS, INSTALL and the docs are up to date:
+ copyright notices. This can be as simple as doing:
+ grep 'Copyright' * | grep -v 1999
+ and looking for files you know you've worked on a lot.
+* Make sure NEWS, INSTALL, AUTHORS and THANKS and the docs are up to date:
+ Scan the ChangeLogs for user-visible changes, marked with an asterisk
at the left margin.
+ Update NEWS and the Texinfo documentation as appropriate.
documented.
+ Check for any [[incomplete]] sections of NEWS.
+ Fact-check INSTALL.
-* Make sure the downloading addressess and filenames in README are
+ + Make sure AUTHORS and THANKS are up-to-date (see also TODO).
+ + Remove finished items from TODO (those marked w/ "+").
+* Make sure the downloading addresses and filenames in README are
current. (But don't bump the version number yet. We do that below.)
* Check that the versions of aclocal, automake, autoconf, and autoheader
- in your PATH match those given in README. Note that the `make
+ in your PATH match those given in HACKING. Note that the `make
dist' process always invokes these tools, even when all the
generated files are up to date.
+ Make specifically sure that the files in libltdl are generated using
+ the same tools as the rest.
* Rebuild all generated files in the source tree:
+ Install the .m4 files where aclocal will find them.
+ Run aclocal.
- + Run automake.
+ Run autoconf.
+ Run autoheader.
+ + Run automake.
* Verify that Guile builds and runs in your working directory.
-* Run the test suite, in guile-modules/test-suite.
+* Run the test suite, in guile-core/test-suite.
* Commit all changes to the CVS repository.
* Build a test distribution.
+ BEFORE doing 'make dist', configure the source tree for build
- in the same tree with configuration option --with-threads.
- Make sure that readline was enabled correctly.
- If this is not done, there will be missing dependencies in two
- Makefile.in.
+ in the same tree with configuration options
+ --enable-maintainer-mode --enable-debug-malloc --with-threads.
+ + Make sure that readline was enabled correctly.
+ + Build the tree.
+ (If the above steps are not done, the dependencies won't be properly
+ included in the generated Makefile.in files.)
+ Then do 'make dist'.
+ + Check that the dependencies in guile-readline/Makefile look OK.
+ (We currently use a kludge which edits the dependencies generated
+ by automake so that Guile can be built in a directory separate
+ from the source tree also with non-GNU make programs.)
* Give the test disty to various people to try. Here's what you should do:
+ Unset GUILE_LOAD_PATH.
+ Remove automake and autoconf from your path, or turn off their
Punting checklist:
* Add "Guile N.M released." entry to the top-level ChangeLog, and commit it.
-* Tag the entire source tree with a tag of the form "release_N_M"
+* Tag the entire source tree with a tag of the form "release_N_M"
or "release_N_M_L".
+* Do a 'make dist'.
* Put the distribution up for FTP somewhere, and send mail to
ftp-upload@gnu.org, asking them to put it on prep.
* Send an announcement message to gnu-announce@gnu.org. Put a brief
version numbers of the form "N.M.L", where L is odd.
* Start a new section of the NEWS file.
* Start a new THANKS file.
-* Send mail to majordomo-owner@cygnus.com updating the message you
- get when you ask majordomo for "info guile".
HCoop / bpt / guile.git / blobdiff