OpenE2K/binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update README-how-to-make-a-release with the correct sequence for creating the source tarball.

Browse Source 
* README-how-to-make-a-release: Merge steps 3, 4 and 5, and insert
	the git tag operation at the correct location.
This commit is contained in:
Nick Clifton 2017-10-05 10:52:04 +01:00
parent 9c0f3d3f20
commit ef336cb09a
2 changed files with 32 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
binutils/ChangeLog
View File

@ -1,3 +1,8 @@
2017-10-05 Nick Clifton <nickc@redhat.com>
* README-how-to-make-a-release: Merge steps 3, 4 and 5, and insert
the git tag operation at the correct location.
2017-10-05 Alan Modra <amodra@gmail.com> 2017-10-05 Alan Modra <amodra@gmail.com>
PR 22239 PR 22239

64
binutils/README-how-to-make-a-release
View File

@ -45,46 +45,39 @@ looks like this:
2. Make sure that the branch sources build, test and install 2. Make sure that the branch sources build, test and install
correctly. correctly.
3. In the branch sources... 3. In the branch sources:
Update the minor release number in bfd/version.m4. a. Update the minor release number in bfd/version.m4.
Regenerate the configure files. b. Edit bfd/development.sh and set "development=false".
Commit the updates along with a "this-is-the-2.XX.X-release" note c. Regenerate the configure files.
in the changelogs. d. Commit the updates along with a "this-is-the-2.XX.X-release"
note in all of the changelogs.
4. Tag the branch with the new release number: e. Tag the branch with the new release number:
git tag -a binutils-2_XX_X git tag -a binutils-2_XX_X
[optional -u XXXXX to sign with a gpg key] [optional: add "-u XXXXX" to sign with a gpg key]
[optional -f to move an already created tag] git push origin binutils-2_XX_X
git push origin
5. Create the release tarballs: f. Create the release tarballs:
./src-release -b -g -l -x binutils
a. Edit bfd/development.sh and set "development=false". g. Edit bfd/development.sh and set "development=true".
b. ./src-release -b -g -l -x binutils h. Commit this change into the git repository.
c. Edit bfd/development.sh and set "development=true". i. Clean up the source tree. (Use "git status" to find new
files, and remove them).
FIXME: Really the development.sh file should be changed by the
src-release script on the fly. The development=false flag only
wants to be set in the release tarballs however, not the branch
sources as the branch will continue to have (development) patches
checked in to it.
FIXME: The tarballs will contain spurious autom4te.cache FIXME: The tarballs will contain spurious autom4te.cache
directories which could be removed to reduce their size. directories which could be removed to reduce their size.
6. [If paranoid - upload the tarballs to one of the FTP servers and 4. [If paranoid - upload the tarballs to one of the FTP servers and
ask people to test it before going on to step 7]. ask people to test it before going on to step 5].
7. Upload the tarballs to ftp.gnu.org. 5. Upload the tarballs to ftp.gnu.org.
gnupload --to ftp.gnu.org:binutils binutils-X.XX.X.tar.* gnupload --to ftp.gnu.org:binutils binutils-X.XX.X.tar.*
gnupload is in the gnulib/build-aux directory. The gnupload script is in the gnulib/build-aux directory.
8. Upload the tarballs to sourceware.org: 6. Upload the tarballs to sourceware.org:
sftp sourceware.org sftp sourceware.org
cd /ftp/pub/binutils/releases cd /ftp/pub/binutils/releases
@ -93,12 +86,9 @@ looks like this:
quit quit
FIXME: Should the signatures (created by the gnupload script in FIXME: Should the signatures (created by the gnupload script in
step 7) be uploaded as well ? step 5) be uploaded as well ?
9. Clean up the source tree. (Use "git status" to find new files, 7. Update web pages. For sourceware.org:
and remove them).
10. Update web pages. For sourceware.org:
* Log on to sourceware.org * Log on to sourceware.org
* Go /www/htdocs/binutils * Go /www/htdocs/binutils
@ -107,10 +97,10 @@ looks like this:
For the www.gnu.org site you have to email webmasters@gnu.org For the www.gnu.org site you have to email webmasters@gnu.org
and ask them to make the change(s). and ask them to make the change(s).
11. Send an emails to the binutils list, info-gnu@gnu.org and 8. Send an emails to the binutils list, info-gnu@gnu.org and
David Edelsohn <dje.gcc@gmail.com> announcing the new release. David Edelsohn <dje.gcc@gmail.com> announcing the new release.
(The email to Davis is so that he can update the GNU Toolchain (The email to Davis is so that he can update the GNU Toolchain
social media). Something like this: social media). Something like this:
------------------------------------------------------------------------ ------------------------------------------------------------------------
Hi Everyone, Hi Everyone,