summaryrefslogtreecommitdiff
path: root/RELEASE
diff options
context:
space:
mode:
Diffstat (limited to 'RELEASE')
-rw-r--r--RELEASE61
1 files changed, 61 insertions, 0 deletions
diff --git a/RELEASE b/RELEASE
new file mode 100644
index 000000000..c1716b04b
--- /dev/null
+++ b/RELEASE
@@ -0,0 +1,61 @@
+This is a checklist for making Guile releases.
+It's specific to the FSF's development environment; please don't put
+it in the distribution.
+
+In release 1.2:
+- note that #/ syntax is going to go away.
+- fix all uses of #/ in the dist.
+
+In release 1.3:
+- make #/ generate a warning.
+
+In release 1.4:
+- remove #/ syntax
+
+Platforms for test builds:
+SunOS (gcc and pcc) --- galapas.ai.mit.edu
+Solaris (gcc and SUN cc) --- saturn.ai.mit.edu
+NetBSD (gcc) --- repo-man.ai.mit.edu (use /home/repo/jimb)
+HP/UX (gcc, HP cc) --- nutrimat.gnu.ai.mit.edu
+
+
+1) 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.
+2) Make sure NEWS 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.
+3) Scan output from `cvs log' to find files that have changed a lot, but
+ do not have up-to-date copyright notices.
+4) Update the version numbers in GUILE-VERSION, and README, to remove the
+ "unreleased" indications. They should be straight numbers, of the form
+ "N.M", not alpha numbers, of the form "N.Ma".
+5) Choose new interface numbers for shared libraries.
+6) Do a `cvs update -A', to get rid of any sticky tags.
+7) Commit all changes to the CVS repository.
+8) Verify that the disty works, too:
+ a) Make a disty, using 'make dist'.
+ b) Unpack it somewhere else.
+ c) Remove automake and autoconf from your path, or turn off their
+ execute bits, or something. (Users should be able to build disty
+ without installing those tools.)
+ d) Configure, make, and install.
+ e) Test the installed version; don't forget to unset SCHEME_LOAD_PATH.
+ f) If you made any fixes, commit them, and start from a) again
+9) Tag the entire source tree with a tag of the form "release_N_M".
+10) 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, Daniel Hagerty
+ <hag@ai.mit.edu> has been generous about helping with that.
+11) Send an announcement message to gnu-announce@prep.ai.mit.edu. If I
+ remember correctly, the moderator will delay it until the tar file
+ appears on prep. The announcement text should be mostly taken from
+ Guile's README file.
+12) 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.Ma", where the "a" means "alpha".
+13) Start a new section of the NEWS file.
+14) Send mail to majordomo-owner@cygnus.com updating the message you get
+ when you ask majordomo for "info guile".