update active versions on GCC home page

update active versions on GCC home page

[Janis Johnson]

The list of releases on the GCC home page is out of date, and Gerald is
gone for another week.  Mark, does this change look OK?

The NOTE wasn't updated after the ordering of the releases changed, but
this matches the meaning from earlier versions of the file.

Janis

Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.347
diff -u -r1.347 index.html
--- index.html	5 Dec 2002 12:23:21 -0000	1.347
+++ index.html	17 Dec 2002 00:58:45 -0000
@@ -36,37 +36,40 @@
 
 
 <!-- NOTE: Of the following four items, we always want to show exactly
-     three - either the first, second, and third, or the second, third,
+     three - either the first, second, and fourth, or the second, third,
      and fourth.
 -->
 
 <dl>
+<dt><strong>Active release branch:</strong>
+  will become <a href="gcc-3.3/changes.html">GCC 3.3</a>
+</dt><dd>
+  <a href="develop.html#stage3">Stage 3</a>; open for all maintainers.
+</dd>
+
 <dt><strong>Current release series:</strong>
   <a href="gcc-3.2/">GCC 3.2.1</a> (released 2002-11-21)
 </dt><dd>
   Open for all maintainers; fixes for regressions only.
 </dd>
 
+<!--
 <dt><strong>Previous release series:</strong>
   <a href="gcc-3.1/">GCC 3.1.1</a> (released 2002-07-26) 
 </dt><dd>
   GCC 3.1.1 is the last 3.1 release; the 3.1-branch became the
   <a href="gcc-3.2/changes.html">GCC 3.2</a>-branch.
 </dd>
-
-<!--
-<dt><strong>Active release branch:</strong>
-  GCC 3.2.1 (<a href="gcc-3.1/criteria.html">release criteria</a>,
-             <a href="gcc-3.2/changes.html">changes</a>)
-</dt><dd>
-  Non-documentation commits require approval by release manager.
-</dd>
 -->
 
 <dt><strong>Active development (mainline):</strong>
-  will become <a href="gcc-3.3/changes.html">GCC 3.3</a>
+  will become <a href="gcc-3.4/changes.html">GCC 3.4</a>
 </dt><dd>
-  <a href="develop.html#stage3">Stage 3</a>; open for all maintainers.
+  <a href="develop.html#stage1">Stage 1</a>;
+  temporarily limited to fixes to stabilize the merge from the
+  basic improvements branch.
+<!-- open for all maintainers.
+-->
 </dd>
 </dl>
 

Re: update active versions on GCC home page

[Mark Mitchell]

--On Monday, December 16, 2002 05:06:16 PM -0800 Janis Johnson 
<janis187@us.ibm.com> wrote:

> The list of releases on the GCC home page is out of date, and Gerald is
> gone for another week.  Mark, does this change look OK?

Perfect!

Thanks,

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com

Re: update active versions on GCC home page

[Joseph S. Myers]

On Mon, 16 Dec 2002, Janis Johnson wrote:

> The list of releases on the GCC home page is out of date, and Gerald is
> gone for another week.  Mark, does this change look OK?

Please also add updating the home page to the list in branching.html.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

Re: update active versions on GCC home page

[Janis Johnson]

On Tue, Dec 17, 2002 at 03:16:01AM +0000, Joseph S. Myers wrote:
> On Mon, 16 Dec 2002, Janis Johnson wrote:
> 
> > The list of releases on the GCC home page is out of date, and Gerald is
> > gone for another week.  Mark, does this change look OK?
> 
> Please also add updating the home page to the list in branching.html.

Done, with the following patch:

Index: branching.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v
retrieving revision 1.7
diff -u -r1.7 branching.html
--- branching.html	24 Sep 2002 03:44:43 -0000	1.7
+++ branching.html	17 Dec 2002 17:11:22 -0000
@@ -36,6 +36,10 @@
 <code>criteria.html</code>.  Update the toplevel
 <code>buildstat.html</code> to refer to this version.</li>
 
+<li>Update the <code>index.html</code> web page to show the new active
+release branch, the current release series, and active development
+(mainline).  Update the version and development stage for mainline.</li>
+
 <li>Update <code>f/root.texi</code> on the branch to use <code>@clear
 DEVELOPMENT</code>.</li>