Add markers for 2.34 branch to the NEWS files and ChangeLogs.

[thirdparty/binutils-gdb.git] / binutils / README-how-to-make-a-release

diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index 66c5eccccdd027e9a348cdaa9d073437dfbb1202..f0116816b2c48f796856e5fa9077ae00357a1915 100644 (file)
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -27,10 +27,11 @@ How to perform a release.
      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.
 
@@ -38,8 +39,8 @@ How to perform a release.
 
   4. Create the release branch using:
 
-       git branch binutils-2_33-branch
-        git push origin binutils-2_33-branch
+       git branch binutils-2_34-branch
+        git push origin binutils-2_34-branch
 
      If you get a message like:
      
@@ -49,7 +50,7 @@ How to perform a release.
 
   5. Make sure that the branch is there.  IE check out the branch sources:
   
-        git clone ssh://sourceware.org/git/binutils-gdb.git -b binutils-2_33-branch 2.33
+        git clone ssh://sourceware.org/git/binutils-gdb.git -b binutils-2_34-branch 2.34
 
      If you get a message about being in a "detached head" state, something
      has gone wrong...
@@ -71,7 +72,7 @@ How to perform a release.
      ask Joel Brobecker <brobecker AT adacore DOT com>.
 
   7. Rename the current HEAD version entry in Bugzilla, and create a
-     new one.  E.g. rename "2.33 (HEAD)" to 2.33, and create "2.34
+     new one.  E.g. rename "2.34 (HEAD)" to 2.34, and create "2.34
      (HEAD)":
      
         https://sourceware.org/bugzilla/editversions.cgi?product=binutils
@@ -79,13 +80,13 @@ How to perform a release.
   8. Update bfd/version.m4 on HEAD to indicate that is now a snapshot
      of the next release:
      
-       m4_define([BFD_VERSION], [2.33.51])
+       m4_define([BFD_VERSION], [2.34.51])
        
      Update the release number in bfd/version.m4 for the branch.
      The branch only needs the point value set to 90 as the release
      has not actually happened yet.
 
-       m4_define([BFD_VERSION], [2.32.90])
+       m4_define([BFD_VERSION], [2.33.90])
 
      Regenerate various files on both branch and HEAD by configuring
      with "--enable-maintainer-mode --enable-gold" and then building
@@ -279,7 +280,7 @@ When the time comes to actually make the release....
       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
@@ -304,6 +305,8 @@ When the time comes to actually make the release....
         get index.html
         [edit]
         put index.html
+         rm docs
+        ln -s docs-2.3x docs
         quit
 
       Check that the new web page is correct.
@@ -313,7 +316,10 @@ When the time comes to actually make the release....
 
   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:
       -----------------------------------------------------------------------
@@ -413,9 +419,6 @@ looks 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].
@@ -449,6 +452,7 @@ looks like this:
      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,
 
@@ -470,9 +474,15 @@ 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