Add note about creating a bugzilla tag for a point release.

	* README-how-to-make-a-release (https): Add a reminder to create a
	new Bugzilla tag for the point release, once it has been published.

diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index 44c388a23f87cf6cbe5e1258149bb1f6db883617..98823188e9c53a64d13bf2a74b9e52291691f267 100644 (file)
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,8 @@
+2020-09-15  Nick Clifton  <nickc@redhat.com>
+
+       * README-how-to-make-a-release (https): Add a reminder to create a
+       new Bugzilla tag for the point release, once it has been published.
+
 2020-09-11  H.J. Lu  <hongjiu.lu@intel.com>
 
        * readelf.c (get_note_type): Support NT_X86_CET.

diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index e0d1f7880a4e8c0e9bbd1edcc338c657ea8447a1..abb2438c5c493ea527533db70c2618eddcebf437 100644 (file)
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -499,6 +499,10 @@ looks like this:
      (The email to Davis is so that he can update the GNU Toolchain
      social media).  Something like this:
 
+  9. Create a new Bugzilla entry for the point release.
+     
+        https://sourceware.org/bugzilla/editversions.cgi?product=binutils
+
 ------------------------------------------------------------------------
 Hi Everyone,