yggdrasil/binutils-gdb
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add a note about regenerating the info files when creating a new release.

Browse Source 
* README-how-to-make-a-release: Add note about regenerating the
	info files prior to the release.
This commit is contained in:
Nick Clifton 2018-08-01 15:51:57 +01:00
parent e30985fa2b
commit e256144888
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
binutils/ChangeLog
View File

@ -1,3 +1,8 @@
2018-08-01 Nick Clifton <nickc@redhat.com>
* README-how-to-make-a-release: Add note about regenerating the
info files prior to the release.
2018-07-30 Andrew Jenner <andrew@codesourcery.com> 2018-07-30 Andrew Jenner <andrew@codesourcery.com>
* MAINTAINERS (C-SKY): Add Yunhai Shang as co-maintainer. * MAINTAINERS (C-SKY): Add Yunhai Shang as co-maintainer.

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

@ -165,9 +165,9 @@ When the time comes to actually make the release....
branch to a whole new minor version number, without a point branch to a whole new minor version number, without a point
value. Eg "2.29.90" becomes "2.30". Change bfd/development.sh value. Eg "2.29.90" becomes "2.30". Change bfd/development.sh
to set the value to "false". Regenerate the configure and to set the value to "false". Regenerate the configure and
makefiles. Add ChangeLog entries for the updates and add a makefiles. And *info* files. Add ChangeLog entries for the
"this-is-the-2.XX-release" comment and commit. Make sure to updates and add a "this-is-the-2.XX-release" comment and
include the .gmo files. commit. Make sure to include the .gmo files.
22. Check that your file creation mask will create the 22. Check that your file creation mask will create the
correct file permissions. Eg: correct file permissions. Eg: