===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/criteria.html,v
retrieving revision 1.1
@@ -9,7 +9,7 @@
<p>This page provides the release criteria for GCC 5.</p>
-<p>The GCC team (and, in particular, the Release Manager) will attempt
+<p>The GCC team (and, in particular, the Release Managers) will attempt
to meet these criteria before the release of GCC 5.</p>
<p>In all cases, these criteria represent the minimum functionality
@@ -23,7 +23,7 @@
would be released even though it did not support the Intel Pentium.</p>
<p>Because the development of GCC is largely dependent on volunteers,
-the Release Manager and/or Steering Committee may eventually have to
+the Release Managers and/or Steering Committee may eventually have to
decide whether to make a release, even if the criteria here are not
met. For example, if no volunteer can be found to verify correct
operation of a particular application program on a particular system,
@@ -32,7 +32,8 @@
<h1>Languages</h1>
<p>GCC supports several programming languages, including Ada, C, C++,
-Objective-C, Fortran, and Java. For the purposes of making releases,
+Fortran, Objective-C, Objective-C++, Go and Java.
+For the purposes of making releases,
however, we will consider primarily C and C++, as those are the
languages used by the vast majority of users. Therefore, if, below,
the criteria indicate, for example, that there should be no DejaGNU
@@ -84,6 +85,9 @@
<p>There are no release criteria for tertiary platforms.</p>
+<p>In general bugs blocking the release are marked with priority P1
+in bugzilla (<a href=""https://gcc.gnu.org/bugs/management.html">Maintaining the GCC Bugzilla database</a>).</p>
+
<p>In contrast to previous releases, we have removed all mention of
explicit application testing. It is our experience that, with the
resources available, it is very difficult to methodically carry out