diff options
| author | Nick Clifton <nickc@redhat.com> | 2020-07-04 11:23:17 +0100 |
|---|---|---|
| committer | Nick Clifton <nickc@redhat.com> | 2020-07-04 11:23:17 +0100 |
| commit | 2f4172d6cbcd9a04fa0aa1aa6d6a8ba9089dbaf7 (patch) | |
| tree | 020ae23f462e84e6c7746bca69967e206ade3477 /binutils/README-how-to-make-a-release | |
| parent | b4396c5e6ea889662bbeda4fc35b8a92a5f7d85e (diff) | |
| download | gdb-2f4172d6cbcd9a04fa0aa1aa6d6a8ba9089dbaf7.zip gdb-2f4172d6cbcd9a04fa0aa1aa6d6a8ba9089dbaf7.tar.gz gdb-2f4172d6cbcd9a04fa0aa1aa6d6a8ba9089dbaf7.tar.bz2 | |
Tweak version numbers in release-howto
Diffstat (limited to 'binutils/README-how-to-make-a-release')
| -rw-r--r-- | binutils/README-how-to-make-a-release | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/binutils/README-how-to-make-a-release b/binutils/README-how-to-make-a-release index b9e7e94..c56aa86 100644 --- a/binutils/README-how-to-make-a-release +++ b/binutils/README-how-to-make-a-release @@ -39,8 +39,8 @@ How to perform a release. 4. Create the release branch using: - git branch binutils-2_34-branch - git push origin binutils-2_34-branch + git branch binutils-2_36-branch + git push origin binutils-2_36-branch If you get a message like: @@ -50,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_34-branch 2.34 + git clone ssh://sourceware.org/git/binutils-gdb.git -b binutils-2_36-branch 2.36 If you get a message about being in a "detached head" state, something has gone wrong... @@ -72,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.34 (HEAD)" to 2.34, and create "2.34 + new one. E.g. rename "2.36 (HEAD)" to 2.36, and create "2.37 (HEAD)": https://sourceware.org/bugzilla/editversions.cgi?product=binutils @@ -80,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.34.50]) + m4_define([BFD_VERSION], [2.36.50]) 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.33.90]) + m4_define([BFD_VERSION], [2.35.90]) Regenerate various files on both branch and HEAD by configuring with "--enable-maintainer-mode --enable-gold" and then building |