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]

Re: SC decision on version numbering: 4.0

On Thu, 9 Sep 2004, Joseph S. Myers wrote:
branching.html lists all the places that need changing for new major
versions (mutatis mutandis for this case where the version number changes
on mainline without an associated branch).  It is however out of date with
regard to Gerald's changes to do snapshots from multiple branches; some
special measures may be needed so that the first 4.0 snapshot has diffs
from the last 3.5 one (and branching.html should document the applicable
special measures).

Done thusly.

That won't win a beauty contest, but it works reasonably well.


Index: branching.html
RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v
retrieving revision 1.16
diff -u -3 -p -r1.16 branching.html
--- branching.html	27 Aug 2004 16:13:32 -0000	1.16
+++ branching.html	11 Sep 2004 19:53:17 -0000
@@ -45,14 +45,20 @@ release branch, the current release seri
 <li>Update <code>doc/include/gcc-common.texi</code> on the branch to use
 <code>@clear DEVELOPMENT</code>.</li>

-<li>Update <code>maintainer-scripts/gcc_release</code> on the
-mainline, where it says &quot;# For now snapshots come from the
-mainline.&quot;, to make snapshots come from the branch instead.
-Also update the description of where snapshots come from in
-(Also, <code>cvs update</code> will also need to be run in the scripts
-directory in the <code>gccadmin</code> account, to update the version
-actually called from cron.)</li>
+<li>Update <code>maintainer-scripts/crontab</code> on the mainline by
+adding an entry to make shapshots of the new branch and adjusting the
+version number of the mainline snapshots.
+Run <code>cvs update</code> in the <code>scripts</code> directory of
+the gccadmin account, and then actually install the updated crontab
+<br />
+Generate the next mainline snapshot manually, using the <code>-p</code>
+option of the <code>gcc_release</code> script.  For that single run,
+adjust the script such that the announcement mail is sent to you
+personally so that you can adjust references to the previous snapshot
+in the  <code>README</code> and <code>index.html</code> files of the
+new snapshot as well as the mail itself before relaying it.

 <li><a href="translation.html#regen">Regenerate
 <code>gcc.pot</code></a> and <code>cpplib.pot</code>.

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