diff --git a/HACKING b/HACKING index 808fc6694..a3cc004b9 100644 --- a/HACKING +++ b/HACKING @@ -24,6 +24,10 @@ Sat Aug 3 01:27:14 1996 Gary Houston * * fports.c (scm_open_file): don't return #f, throw error. +When you've written a NEWS entry and updated the documentation, go +ahead and remove the asterisk. I will use the asterisks to find and +document changes that haven't been dealt with before a release. + - Include each log entry in both the ChangeLog and in the CVS logs. If you're using Emacs, the pcl-cvs interface to CVS has features to make this easier; it checks the ChangeLog, and generates good default @@ -63,6 +67,8 @@ If you receive contributions you want to use from someone, let me know and I'll take care of the administrivia. Put the contributions aside until we have the necessary papers. +- When you make substantial changes to a file, add the current year to +the list of years in the copyright notice at the top of the file. Jim Blandy diff --git a/RELEASE b/RELEASE index e6d82a8a9..96c4c2829 100644 --- a/RELEASE +++ b/RELEASE @@ -11,12 +11,14 @@ it in the distribution. b) Update NEWS and the Texinfo documentation as appropriate. c) Remove the user-visible markers from the log entries once they're documented. -3) Update the version numbers in GUILE-VERSION, and README, to remove the +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". -4) Do a `cvs update -A', to get rid of any sticky tags. -5) Commit all changes to the CVS repository. -6) Verify that the disty works, too: +5) Do a `cvs update -A', to get rid of any sticky tags. +6) Commit all changes to the CVS repository. +7) 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 @@ -24,16 +26,16 @@ it in the distribution. 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 the top of 6). -7) Tag the entire source tree with a tag of the form "release_N_M". -8) Copy the tar file over to the GNU machines, and ask the appropriate + f) If you made any fixes, commit them, and start from a) again +8) Tag the entire source tree with a tag of the form "release_N_M". +9) 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 - has usually been generous enough to help with that. -9) 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. -10) Tweak the version numbers in GUILE-VERSION, and README to indicate that + has been generous about helping with that. +10) 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. +11) 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". -11) Start a new section of the NEWS file. +12) Start a new section of the NEWS file.