doc: clarify README-release

* top/README-release: Clarify: you should make a point to have
the latest stable versions of build tools in your PATH, and the
reference to buildreq is solely for its list of tool names, not
for its minimal-functional version numbers.
Prompted by discussion with Reuben Thomas and Gary V. Vaughan.

diff --git a/ChangeLog b/ChangeLog
index d37f933..e378111 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,12 @@
 2012-01-28  Jim Meyering  <meyering@redhat.com>
 
+       doc: clarify README-release
+       * top/README-release: Clarify: you should make a point to have
+       the latest stable versions of build tools in your PATH, and the
+       reference to buildreq is solely for its list of tool names, not
+       for its minimal-functional version numbers.
+       Prompted by discussion with Reuben Thomas and Gary V. Vaughan.
+
        maint.mk: use more readable (yet functionally equivalent) quoting
        It is common to quote a single quote in a single quoted string like
        this:  '...'\''...'.  Unless you know the idiom, that looks like

diff --git a/top/README-release b/top/README-release
index 0020885..d6e032a 100644 (file)
--- a/top/README-release
+++ b/top/README-release
@@ -6,9 +6,9 @@ Here are most of the steps we (maintainers) follow when making a release.
     git checkout master
     git pull origin master
 
-* Ensure that the desired versions of autoconf, automake, etc.
+* Ensure that the latest stable versions of autoconf, automake, etc.
   are in your PATH.  See the buildreq list in bootstrap.conf for
-  the complete list.
+  the complete list of tools.
 
 * Ensure that you're on "master" with no uncommitted diffs.
   This should produce no output: git checkout master; git diff