This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

PATCH: releasing.html (was: Stopping daily bump of version.c onold/closed branches)

On Sun, 4 May 2003, Joseph S. Myers wrote:
> (The 18-step release process documentation can also be (slightly)
> simplified; it no longer need describe additional files that contained the
> version number on pre-3.3 branches.)

Done thusly.


Index: releasing.html
RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v
retrieving revision 1.13
diff -u -3 -p -r1.13 releasing.html
--- releasing.html	25 Apr 2003 08:11:53 -0000	1.13
+++ releasing.html	4 May 2003 11:05:14 -0000
@@ -72,11 +72,7 @@ FSF.</li>

 <li>Increment the version number in <code>gcc/version.c</code>, and
 put back the date stamp and (prerelease) annotation.  Increment the
-version number in <code>doc/include/gcc-common.texi</code>.  (Branches
-cut prior to GCC 3.3 have the version number stored in more
-places.  You must edit all the files named <code>[vV]ersion.c</code>
-as well, and <code>java/gcj.texi</code>, <code>f/root.texi</code>, and
+version number in <code>doc/include/gcc-common.texi</code>.</li>

 <li>Create a new version in Bugzilla corresponding to the new branch
 version.  This can be accomplished by choosing products, choosing gcc,

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]