Re: SC decision on version numbering: 4.0

[Mike Stump <mrs at apple dot com>]

On Sep 9, 2004, at 2:48 PM, Joseph S. Myers wrote:
> branching.html lists all the places that need changing for new major
> versions

http://gcc.gnu.org/branching.html

	5.  	Update doc/include/gcc-common.texi on the mainline to use the 
next major release number.


mrs $ mkdiff .
Doing diffs in .:
*** ./doc/include/gcc-common.texi.~1~   Sat Jun  5 00:01:51 2004
--- ./doc/include/gcc-common.texi       Thu Sep  9 16:37:23 2004
***************
*** 4,10 ****

  @c Common values used in the GCC manuals:

! @set version-GCC 3.5.0

  @c DEVELOPMENT is set to indicate an in-development version,
  @c as compared to a release version.  When making a release
--- 4,10 ----

  @c Common values used in the GCC manuals:

! @set version-GCC 4.0.0

  @c DEVELOPMENT is set to indicate an in-development version,
  @c as compared to a release version.  When making a release
--------------

Checked in as (now) obvious.  The other two are checked in as well, and 
I don't understand that any more changes are necessary.  Let me know if 
I got that wrong.

maintainer-scripts might need caressing...  I see:

43 17 * * 7 sh /home/gccadmin/scripts/gcc_release -s 3.5:HEAD           
-l -d /sourceware/snapshot-tmp/gcc all

in crontab, but am unsure if bumping this to 4.0.0 (or 4.0) is 
correct/wise.  Also, that would require updating a crontab for 
gccadmin, whcih I think I just want to punt to the _right_ person...