directories and the top level configure files.
3. When branch day arrives add markers for the upcoming release to
- the NEWS files in gas, ld, gold and binutils.
+ the NEWS files in gas, ld, and binutils. No need to update NEWS
+ in the gold directory - it has its own release numbering.
Likewise for the ChangeLog files in: bfd, binutils, config, cpu,
- elfcpp, gas, gold, gprof, include, ld, opcodes and toplevel.
+ elfcpp, gas, gold, gprof, include, ld, libctf, opcodes and toplevel.
Add a note of the name of the new branch to binutils/BRANCHES.
Make the html documentation locally with the "make html" command
and then upload and rename the directories as needed. (sftp
does not appear to support recursive uploads however, so the
- directories will have to be made by hand).
+ directories had to be made by hand, as shown above).
cd as
lcd <build-dir>/gas/doc/as.html
30. Send emails to binutils@sourceware.org, info-gnu@gnu.org and
David Edelsohn <dje.gcc@gmail.com> announcing the new release.
- Sign the email and include the checksum.
+ Sign the email and include the checksum:
+
+ md5sum binutils-2.3x.tar.*
+
(The email to Davis is so that he can update the GNU Toolchain
social media). Something like this:
-----------------------------------------------------------------------
i. Edit bfd/development.sh and set "development=true".
j. Commit this change into the git repository.
- k. Clean up the source tree.
-
- git clean -dfx .
4. [If paranoid - upload the tarballs to one of the FTP servers and
ask people to test it before going on to step 5].
David Edelsohn <dje.gcc@gmail.com> announcing the new release.
(The email to Davis is so that he can update the GNU Toolchain
social media). Something like this:
+
------------------------------------------------------------------------
Hi Everyone,
xx
xx
--------------------------------------------------------------------------
+ 9. Clean up the source tree.
+
+ git clean -dfx .
+
+ 10. Edit bfd/development.sh on the branch and set the development flag
+ to "true". Commit this change.
\f
-Copyright (C) 2017-2019 Free Software Foundation, Inc.
+Copyright (C) 2017-2020 Free Software Foundation, Inc.
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright