NEWS, README: documented recent changes for the upcoming 2010.02.14 releasev2010.02.14

1 files changed, 17 insertions, 21 deletions

diff --git a/README-maint b/README-maint
index e37673d..78a8b14 100644
--- a/README-maint
+++ b/README-maint
@@ -19,31 +19,27 @@
   : git clone ssh://[<login>@]git.sv.gnu.org/srv/git/autoconf-archive
   : cd autoconf-archive
   : cvs -z3 -d:ext:[<login>@]cvs.savannah.nongnu.org:/web/autoconf-archive co -d html autoconf-archive
-  # set up autotools and gnulib environment
-  : ./bootstrap.sh
-  # determine system properties
-  : ./configure
-  # create/update all generated files that will be in a release
-  : make maintainer-generate
-  # update texinfo documentation
-  : make
+  : ./bootstrap.sh              # set up autotools and gnulib environment
+  : ./configure                 # determine system properties
+  : make maintainer-generate    # create/update all generated files that will be in a release
+  : make                        # update texinfo documentation
 
 * How to update the web site.
 
-  Run "make generate". The process will typically re-generate a whole bunch of
-  files in the html/ directory (which is a separate CVS repository). Check the
-  diffs, and if you things look good, commit the changes.
+  Run the following commands:
 
-  Unfortunately, the new HTML generator doesn't yet recognize cross-links or
-  any other sort of URI (see TODO file). Until those features are implemented,
-  the website probably shouldn't be regenerated, because the old pages do
-  contain links and an update would overwrite them.
+  : make web-manual             # generate an HTML rendering of the user documentation
+  : ./fix-website.sh            # massage file names generated by texinfo
+  : cp doc/manual/html/* html/  # copy the new files into the CVS checkout
+  : (cd html ; cvs commit -m "generated from autoconf-archive $(git describe)")
 
 * How to make a release.
 
   1. Determine the appropriate version number, i.e. today's date in ISO
      formatting.
 
+  2. Update the date stamps in the README file.
+
   2. Update the NEWS file. The script that generates release tarballs checks
      that the current version number in mentioned in that file. If NEWS isn't
      up-to-date, the script will fail.
@@ -55,12 +51,12 @@
      : git tag v2009.07.31 -s -m 'Autoconf Archive Version 2009.07.31'
 
   4. Run "make </dev/null alpha". Other possible release types are "beta" and
-     "major". Unfortunately, one of the tests performed during that procedure
-     doesn't terminate until it receives an EOF on standard input. I have no
-     idea why, but redirecting from /dev/null remedies the problem.
+     "major". Re-directing standard input to /dev/null ensures that the
+     procedure runs interactively. If you don't do that, you'll have to hit
+     Ctrl+d at one point to satisfy a gnulib test.
 
 * Mounting upload area via FUSE+SSHFS
 
-  : sshfs dl.sv.gnu.org:/releases/autoconf-archive /mnt
-  : ls -l /mnt
-  : fusermount -u /mnt
+  : sshfs dl.sv.gnu.org:/releases/autoconf-archive mnt
+  : ls -l mnt
+  : fusermount -u mnt