aboutsummaryrefslogtreecommitdiff
path: root/binutils/README-how-to-make-a-release
diff options
context:
space:
mode:
authorH.J. Lu <hjl.tools@gmail.com>2018-08-23 05:56:03 -0700
committerH.J. Lu <hjl.tools@gmail.com>2018-08-23 05:56:18 -0700
commit44c2eb66808a928b8101f1b880f3482312cbcc1e (patch)
treeac80f4edb7292141378121306b6d5f4793c5443e /binutils/README-how-to-make-a-release
parent38cf70ca4d7adaad7ef085ce34e24e1e0bbee945 (diff)
downloadgdb-44c2eb66808a928b8101f1b880f3482312cbcc1e.zip
gdb-44c2eb66808a928b8101f1b880f3482312cbcc1e.tar.gz
gdb-44c2eb66808a928b8101f1b880f3482312cbcc1e.tar.bz2
Document setting experimental on release branch.
* README-how-to-make-a-release: Document setting "experimental" to false.
Diffstat (limited to 'binutils/README-how-to-make-a-release')
-rw-r--r--binutils/README-how-to-make-a-release5
1 files changed, 3 insertions, 2 deletions
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index c58515a..7ad9ebf 100644
--- 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: