Pick up some maint.mk improvements from gnulib.

* configure.ac (AM_INIT_AUTOMAKE): Require 1.11, and build xz
archives by default now.
* maint.mk (gzip_rsyncable): Avoid non-portable echo.
(VC-tag): Depend on gpg_key_ID.
(PREV_VERSION): Don't parse error as version.
(announcement): Populate email addresses with defaults.
(emit_upload_commands, web-manual): Reflect changes in scripts.
(update-NEWS-hash, emit-commit-log, release-prep): New macros.
* cfg.mk (announcement_Cc_, announcement_mail_headers_): Override
defaults.
* HACKING: Modernize a bit.

Signed-off-by: Eric Blake <eblake@redhat.com>

1 files changed, 4 insertions, 14 deletions

diff --git a/HACKING b/HACKING
index 42e6a799..7b5005db 100644
--- a/HACKING
+++ b/HACKING
@@ -93,13 +93,11 @@ necessary, but helps.
 
 ** Preparation for release
 Make sure you have GNU make installed.  Make sure your PATH includes a
-released version of Automake (and not a development snapshot);
-preferably 1.10.1 or later so you can build an LZMA tarball.  Make
+Automake 1.11 or later (preferably not a development snapshot).  Make
 sure your locale is sane, e.g. by exporting LC_ALL=C.  Bootstrap the
 checkout, and make sure the testsuite passes.  See above for more
-hints on the testsuite.  Update cfg.mk with details specific to your
-environment, such as your GPG key and the location of a gnulib
-checkout.
+hints on the testsuite.  If needed, update cfg.mk with details
+specific to your environment, such as the location of a gnulib checkout.
 
 ** Update the foreign files
 Running `make fetch' in the top level should grab it all for you; you
@@ -119,18 +117,10 @@ As much as possible, make sure to release an Autoconf that uses
 itself.  That's easy: just be in the top level, and run
 `tests/autoconf'.  Or install this autoconf and run `autoreconf -f'.
 
-** XZ tarball creation
-Using the `dist-xz' option of Automake requires Automake 1.11, and
-fails for everyone who does not have xz installed, but for now
-Autoconf only requires Automake 1.10.  However, as maintainer, you
-should build an xz tarball.  By using Automake 1.11 or newer, you
-can run `make dist-xz'; run this prior to the release target so that
-the release announcement will include the .tar.xz file.
-
 ** Make the release
 Run `make {alpha,beta,stable}' depending on which type of release this
 is.  This runs the various checks, creates delta files, creates a
-preliminary announcement in /tmp/announce-autoconf-<version>, prints
+preliminary announcement in ~/announce-autoconf-<version>, prints
 out the command to upload the files, and updates the previous version
 file.