summaryrefslogtreecommitdiff
path: root/binutils/README-how-to-make-a-release
diff options
context:
space:
mode:
Diffstat (limited to 'binutils/README-how-to-make-a-release')
-rw-r--r--binutils/README-how-to-make-a-release24
1 files changed, 12 insertions, 12 deletions
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release
index e81b410d64f..3813a1dec91 100644
--- a/binutils/README-how-to-make-a-release
+++ b/binutils/README-how-to-make-a-release
@@ -46,8 +46,8 @@ Approx time to complete from here: 2 hours ....
4. Create the release branch using:
- git branch binutils-2_40-branch
- git push origin binutils-2_40-branch
+ git branch binutils-2_41-branch
+ git push origin binutils-2_41-branch
If you get a message like:
@@ -57,7 +57,7 @@ Approx time to complete from here: 2 hours ....
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_40-branch 2.40
+ git clone ssh://sourceware.org/git/binutils-gdb.git -b binutils-2_41-branch 2.41
If you get a message about being in a "detached head" state, something
has gone wrong...
@@ -79,27 +79,27 @@ Approx time to complete from here: 2 hours ....
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.38 (HEAD)" to 2.38, and create
- "2.39 (HEAD)":
+ new one. E.g. rename "2.41 (HEAD)" to 2.41, and create
+ "2.42 (HEAD)":
https://sourceware.org/bugzilla/editversions.cgi?product=binutils
8. Update bfd/version.m4 on HEAD to indicate that is now a snapshot
- of the next release and the BRANCH to indicated that it is almost
+ of the next release and the BRANCH to indicate that it is almost
ready for the release.
- So if the release is going to be 2.40 then the version number on
- the BRANCH should be set to 2.39.90 - ie almost, but not quite 2.40,
- and the version number on the MAINLINE should be set to 2.40.50 -
- ie half way to 2.41 release.
+ So if the release is going to be 2.41 then the version number on
+ the BRANCH should be set to 2.40.90 - ie almost, but not quite 2.41,
+ and the version number on the MAINLINE should be set to 2.41.50 -
+ ie half way to 2.42 release.
So the branch bfd/version.m4 has:
- m4_define([BFD_VERSION], [2.39.90])
+ m4_define([BFD_VERSION], [2.40.90])
and the mainline has:
- m4_define([BFD_VERSION], [2.40.50])
+ m4_define([BFD_VERSION], [2.41.50])
Regenerate various files on both branch and HEAD by configuring
with "--enable-maintainer-mode --enable-gold --enable-shared" and then building