It's specific to the FSF's development environment; please don't put
it in the distribution.
-In release 1.3:
-- (done) make #/ generate a warning.
-- (done) make SCHEME_LOAD_PATH generate a warning.
-- Perry Metzger <perry@piermont.com> is willing to do beta-testing
- for NetBSD.
+Maybe we should name Guile releases after entertaining poisons:
+absinthe, etc. However, the first release containing the module
+system should be called Godot: "This is the one you've been waiting
+for."
-In release 1.4:
-- remove #/ syntax
-- Remove SCHEME_LOAD_PATH.
+In release 1.3.2:
+* Release is titled ``wormwood'' release.
+* remove #/ syntax
+* Remove SCHEME_LOAD_PATH.
+- remove hook support from boot-9.scm
+ (only provided for backward compatibility)
+
+In release 1.3.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
2) Verify that Guile builds and runs in your working directory. I
hope that we'll eventually have a test suite to make this more
concrete, but for the moment, just make sure things seem sane.
-3) Make sure NEWS and the docs are up to date:
+3) Make sure NEWS, INSTALL and the docs are up to date:
a) Scan the ChangeLogs for user-visible changes, marked with an asterisk
at the left margin.
b) Update NEWS and the Texinfo documentation as appropriate.
c) Remove the user-visible markers from the log entries once they're
documented.
d) Check for any [[incomplete]] sections of NEWS.
-4) Scan output from `cvs log' to find files that have changed a lot, but
+ e) Fact-check INSTALL.
+4) Scan output from `cvs diff' to find files that have changed a lot, but
do not have up-to-date copyright notices.
5) Update the version numbers in GUILE-VERSION, and README. The Guile
version number should be of the form N.M for a major release, and
without installing those tools.)
d) Configure, make, and install.
e) Test the installed version; don't forget to unset GUILE_LOAD_PATH.
- f) If you made any fixes, commit them, and start from a) again
+ f) Test the example code in the doc directory.
+ g) If you made any fixes, commit them, and start from a) again
+11a) Add "Guile N.M released." entry to ChangeLog, and commit it.
12) Tag the entire source tree with a tag of the form "release_N_M".
-13) Copy the tar file over to the GNU machines, and ask the appropriate
- person to put it on prep. At the time of this writing, Joel Weber
- <devnull@gnu.org> has been generous about helping with that.
+13) Copy the tar file over to the GNU machines, and send mail to
+ ftp-upload@gnu.org, asking them to put it on prep.
14) Send an announcement message to gnu-announce@gnu.org. Put
"Obtaining Guile" first, then a brief summary of the changes in
this release, then "Thanks," "About This Distribution," and
delay it until the tar file appears on prep. The announcement
text should be mostly taken from Guile's README file.
15) Notify freshmeat.net, although they're probably watching anyway.
+ (They got the 1.3 release just fine.) I have no idea if
+ www.bowerbird.com.au will be something anyone refers to, but Guile
+ does have an entry there.
16) Tweak the version numbers in GUILE-VERSION, and README to indicate that
the sources are snapshot again. Snapshots should have version numbers
of the form "N.M.L", where L is odd.
17) Start a new section of the NEWS file.
-18) Send mail to majordomo-owner@cygnus.com updating the message you get
+18) Start a new THANKS file.
+19) Send mail to majordomo-owner@cygnus.com updating the message you get
when you ask majordomo for "info guile".
HCoop / bpt / guile.git / blobdiff