Document setting experimental on release branch.

	* README-how-to-make-a-release: Document setting "experimental"
	to false.

diff --git a/binutils/ChangeLog b/binutils/ChangeLog
index 69ca9aa3adf1950c00ebd48598f6754c3efe4031..09f599bcee4e0d26aedd7343c80fe2b66773dd5b 100644 (file)
--- a/binutils/ChangeLog
+++ b/binutils/ChangeLog
@@ -1,3 +1,8 @@
+2018-08-23  H.J. Lu  <hongjiu.lu@intel.com>
+
+       * README-how-to-make-a-release: Document setting "experimental"
+       to false.
+
 2018-08-22  Alan Modra  <amodra@gmail.com>
 
        * readelf.c (process_file_header): Assign updated values from

diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index c58515a96a73fd288bfdcb9275bc6b0da2cb724b..7ad9ebfde7b89d1bc15cb00c66bd98008c2302b3 100644 (file)
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -164,7 +164,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.29.90" becomes "2.30".  Change bfd/development.sh
-      to set the value to "false".  Regenerate the configure and
+      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.XX-release" comment and
       commit.  Make sure to include the .gmo files.
@@ -313,7 +313,8 @@ looks like this:
   3. In the branch sources:
 
        a. Update the minor release number in bfd/version.m4.
-       b. Edit bfd/development.sh and set "development=false".
+       b. Edit bfd/development.sh, set "development=false" and
+       "experimental=false".
        c. Regenerate the configure files.
        c.1. Remove spurious autom4te.cache files: