[PATCH]: bugs/management.html

[Daniel Berlin <dberlin at dberlin dot org>]

This is necessary to relink the bug_status.html page to
bugs/management.html.
--Dan
Index: management.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/management.html,v
retrieving revision 1.3
diff -u -3 -p -r1.3 management.html
--- management.html	22 May 2003 01:07:28 -0000	1.3
+++ management.html	25 May 2003 21:41:07 -0000
@@ -114,5 +114,129 @@ replaced by the message "confused by ear
 release versions) should get "minor" severity.
 It should be noted in the comments that the error recovery fails.</p>

+<h1>Fields</h1>
+<a name="status"></a>
+<p>
+<table border=1 cellpadding=4 summary="Statuses">
+
+<tr align=CENTER valign=TOP>
+<td WIDTH="50%"><h2>STATUS</h2> <td><h2>RESOLUTION</h2>
+
+<tr VALIGN=TOP>
+<td>The <b>status</b> field indicates the general health of a bug. Only
+certain status transitions are allowed.
+<td>The <b>resolution</b> field indicates what happened to this bug.
+
+<tr VALIGN=TOP><td>
+<dl>
+<dt><b>UNCONFIRMED</b>
+<dd>The PR has been filed and the responsible person(s) notified.</dd>
+
+<dt><b>NEW</b>
+<dd>A maintainer has verified that this is indeed a bug in GCC. Every
+once in a while, old reports will need to be rechecked, to find out
+whether the bug still exists.</dd>
+
+<dt><b>WAITING</b></dt>
+<dd>The submitter was asked for further information, or asked to try
+out a patch. The PR remains in that state until the submitter
+responds.</dd>
+
+<dt><b>SUSPENDED</b></dt>
+<dd>Work on the problem has been postponed.  This happens if a timely
+solution is not possible or is not cost-effective at the present time.
+The PR continues to exist, though a solution is not being actively
+sought. If the problem cannot be solved at all, it should be closed
+rather than suspended.</dd>
+
+<dt><b>ASSIGNED</b>
+<dd> This bug is not yet resolved, but is assigned to the proper
+person. From here bugs can be given to another person and become
+<b>NEW</b>, or resolved and become <b>RESOLVED</b>.
+
+<dt><b>REOPENED</b>
+<dd>This bug was once resolved, but the resolution was deemed
+incorrect.  For example, a <b>WORKSFORME</b> bug is
+<b>REOPENED</b> when more information shows up and the bug is now
+reproducible.  From here bugs are either marked <b>ASSIGNED</b>
+or <b>RESOLVED</b>.
+</dl>
+
+<td>
+<dl>
+<dd> No resolution yet. All bugs which are in one of these "open" states
+have the resolution set to blank. All other bugs
+will be marked with one of the following resolutions.
+</dl>
+
+<tr VALIGN=TOP><td>
+<dl>
+<dt><b>RESOLVED</b>
+<dd> A resolution has been found for this bug. The bug is either closed
+for good, or can be re-opened and change to <b>REOPENED</b>.
+
+</dl>
+
+<td>
+<dl>
+<dt><b>FIXED</b>
+<dd> A fix for this bug is checked into the tree and tested.
+
+<dt><b>INVALID</b>
+<dd> The problem described is not a bug
+
+<dt><b>WONTFIX</b>
+<dd> The problem described is a bug which will never be fixed.
+
+<dt><b>LATER</b>
+<dd> The problem described is a bug which will not be fixed in this
+     version of the product.
+
+<dt><b>REMIND</b>
+<dd> The problem described is a bug which will probably not be fixed in this
+     version of the product, but might still be.
+
+<dt><b>DUPLICATE</b>
+<dd> The problem is a duplicate of an existing bug. Marking a bug
+     duplicate requires the bug# of the duplicating bug and will at
+     least put that bug number in the description field.
+
+<dt><b>WORKSFORME</b>
+<dd> All attempts at reproducing this bug were futile, reading the
+     code produces no clues as to why this behavior would occur. If
+     more information appears later, please re-assign the bug, for
+     now, file it.
+</dl>
+</table>
+<p>
+<table border=1 cellpadding=4>
+<tr><td><h2><a name="severity">Severity</a></h2>
+This field describes the impact of a bug.
+<table>
+<tr><th>Blocker</th><td>Blocks development and/or testing work
+<tr><th>Critical</th><td>crashes, loss of data, severe memory leak
+<tr><th>Major</th><td>major loss of function
+<tr><th>Minor</th><td>minor loss of function, or other problem where
+easy workaround is present
+<tr><th>Trivial</th><td>cosmetic problem like misspelled words or
+misaligned text
+<tr><th>Enhancement</th><td>Request for enhancement
+</table>
+</td><td>
+<h2><a name="priority">Priority</a></h2>
+This field describes the importance and order in which a bug should be
+fixed.  This field is utilized by the programmers/engineers to
+prioritize their work to be done.  The available priorities are:
+<p>
+<p>
+
+<table>
+<tr><th>P1</th><td>Most important
+<tr><th>P2</th><td>
+<tr><th>P3</th><td>
+<tr><th>P4</th><td>
+<tr><th>P5</th><td>Least important
+</table>
+</tr></table>
 </body>
 </html>