Update documentation on how to make a release

diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index 69596150c92df6e0e46c54e6cecd04241b8c9980..8461dfc024cc9207560447ddc5c42b29d87ee540 100644 (file)
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,8 @@
+2020-07-24  Nick Clifton  <nickc@redhat.com>
+
+       * README-how-to-make-a-release: Various small updates whilst
+       creating the 2.35 release.
+
 2020-07-22  Nick Alcock  <nick.alcock@oracle.com>
 
        * testsuite/lib/binutils-common.exp (run_dump_test): Add 'cc'

diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index c56aa86f4b3ae25a0d8f011b978ffbb29b70ec23..e0d1f7880a4e8c0e9bbd1edcc338c657ea8447a1 100644 (file)
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -196,7 +196,7 @@ When the time comes to actually make the release....
 
   21. Update the release number in bfd/version.m4 on the release
       branch to a whole new minor version number, without a point
-      value.  Eg "2.34.90" becomes "2.35".  Change bfd/development.sh
+      value.  Eg "2.35.90" becomes "2.36".  Change bfd/development.sh
       to set all values to "false".  Regenerate the configure and
       makefiles.  And *info* files.  Add ChangeLog entries for the
       updates and add a  "this-is-the-2.3x-release" comment and
@@ -237,11 +237,14 @@ When the time comes to actually make the release....
        chmod -R -w binutils-2.X
        mkdir build
        cd build
-       ../binutils-2.X/configure --enable-gold --prefix=`pwd`/install
+       ../binutils-2.X/configure --enable-gold --prefix=`pwd`/install --enable-plugins
        make all-gas all-gold all-ld all-binutils all-gprof
        make check-gas check-binutils check-ld check-gold
         make install-gas install-gold install-ld install-binutils
 
+        # Needed for step 29...
+        make html
+
   26. Tag the branch with the new release number:
 
             git tag -a binutils-2_3x
@@ -297,9 +300,6 @@ When the time comes to actually make the release....
 
       Update the (local copy of the) index.html file to point to the
       new documentation and mention the new version and then upload it.
-      [NB/ FIXME: Special for updating from 2.34 documentation - restore
-      the link to the GAS/NEWS which has been changed for 2.34 to a
-      specific commit rather than the branch tag].
 
         cd ../docs-2.3x
         put index.html
@@ -328,7 +328,7 @@ When the time comes to actually make the release....
       Edit the top level binutils index.html file to change the links
       to point to the new documentation.
 
-         cd ../../..
+         cd ../..
         get index.html
         [edit]
         put index.html
@@ -336,10 +336,29 @@ When the time comes to actually make the release....
         ln -s docs-2.3x docs
         quit
 
-      Check that the new web page is correct.
-
+      Check that the new web page is correct:
+      
+          https://sourceware.org/binutils/
+         
       For the www.gnu.org site you have to email webmasters@gnu.org
-      and ask them to make the change(s).
+      and ask them to make the change(s):
+---------------------------------------
+Hi FSF Webmasters,
+
+  Please could the GNU Binutils webpage at:
+
+https://www.gnu.org/software/binutils/binutils.html
+
+  be updated to indicate that there is now a newer version available
+  (2.3x).  I have already updated the related page on the sourceware
+  website so this might be useful as a template:
+
+https://sourceware.org/binutils/
+
+  Thanks very much.
+
+Cheers
+--------------------------------------  
 
   30. Send emails to binutils@sourceware.org, info-gnu@gnu.org and
       David Edelsohn <dje.gcc@gmail.com> announcing the new release.
@@ -381,7 +400,7 @@ When the time comes to actually make the release....
       Regenerate files.  Commit these changes.
 
   33. Email the binutils list telling everyone that the 2.3x branch
-      is now open for business as usual and that patched no longer
+      is now open for business as usual and that patches no longer
       need special approval.
 
   34. Examine the bfd/config.bfd file in the mainline sources and move