This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[Patch] Merge information from bugzilla/bug_status.html intobugs/management.html
- From: Wolfgang Bangerth <bangerth at ices dot utexas dot edu>
- To: gcc-patches at gcc dot gnu dot org, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Tue, 3 Jun 2003 20:24:24 -0500 (CDT)
- Subject: [Patch] Merge information from bugzilla/bug_status.html intobugs/management.html
bugs/management.html already had almost all the information found in
bugzilla/bug_status.html. This patch adds the last bit of real information
that wasn't already duplicated, as well as a small sentence that separates
two tables to make them look a little more decent (they were fused in a
weird way before -- html layout sucks :-)
The patch was preapproved by Gerald, and passed the validator.
Gerald, bugzilla/bug_status.html is now obsolete, so you can go ahead
with removing it. I don't know how to check for dangling references, so
will happily leave this to you.
W.
Index: management.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/management.html,v
retrieving revision 1.9
diff -c -r1.9 management.html
*** management.html 4 Jun 2003 01:01:08 -0000 1.9
--- management.html 4 Jun 2003 01:17:34 -0000
***************
*** 140,145 ****
--- 140,148 ----
</tr>
</table>
+ <p>The following two fields describe how serious a bug is from a user's
+ perspective (severity) and which priority we assign to it in fixing it:</p>
+
<table border="1" cellpadding="4"><tr>
<td valign="top">
***************
*** 175,180 ****
--- 178,195 ----
</td></tr>
</table>
+
+
+ <h3><a name="assigned_to">Assigned To</a></h3>
+
+ <p>This is the person in charge of resolving the bug. Every time this
+ field changes, the status changes to NEW to make it easy to see
+ which new bugs have appeared on a person's list.</p>
+
+ <p>The default status for queries is set to NEW, ASSIGNED and REOPENED. When
+ searching for bugs that have been resolved or verified, remember to set the
+ status field appropriately.</p>
+
<h2>Procedures and Policies</h2>