Update release notes with a reminder to check the gpg key being used.

	* README-how-to-make-a-release: Add note about checking gpg key
	and the results of gnupload.

diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index 7bd68ff30f2e76534e132a79eeda4727511beae0..56a43052b0d70d6dd09866bdc21ccf9b854e8b62 100644 (file)
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,8 @@
+2018-01-28  Nick Clifton  <nickc@redhat.com>
+
+       * README-how-to-make-a-release: Add note about checking gpg key
+       and the results of gnupload.
+
 2018-01-27  Nick Clifton  <nickc@redhat.com>
 
        * README-how-to-make-a-release: Add details on how to actually

diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index c37c25d8b55285a6808f994bfb40b42c20f3f008..c46ba7c4a5d061d3db344198e91113a2c6998c00 100644 (file)
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -170,6 +170,9 @@ When the time comes to actually make the release....
              [optional: add "-u XXXXX" to sign with a gpg key]
            git push origin binutils-2_XX
 
+        NB/ If you do sign the binaries make sure to use a key
+       that has been published with the FSF.
+
   27. Clean up the source tree.  (Use "git status" to find new
       files, and remove them).
 
@@ -180,11 +183,14 @@ When the time comes to actually make the release....
 
   29. Upload the tarballs to ftp.gnu.org.
 
-       gnupload --to ftp.gnu.org:binutils binutils-X.XX.X.tar.*
+       gnupload --to ftp.gnu.org:binutils binutils-X.XX.tar.*
 
       The gnupload script is in the gnulib/build-aux directory.
 
-  30. Upload the tarballs to sourceware.org:
+      Check for an email response from the upload.  If necessary
+      fix any problems.
+
+  30. Upload the tarballs (and signatures) to sourceware.org:
 
        sftp sourceware.org
          cd /sourceware/ftp/pub/binutils/releases