+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<!--
The <B>status</B> and <B>resolution</B> field define and track the
life cycle of a bug.
-<a name="status">
+<a name="status"></a>
<p>
-</a>
<TABLE BORDER=1 CELLPADDING=4>
<TR ALIGN=CENTER VALIGN=TOP>
-<TD WIDTH=50%><H1>STATUS</H1> <TD><H1>RESOLUTION</H1>
+<TD WIDTH="50%"><H1>STATUS</H1> <TD><H1>RESOLUTION</H1>
<TR VALIGN=TOP>
<TD>The <B>status</B> field indicates the general health of a bug. Only
<H1>Other Fields</H1>
<table border=1 cellpadding=4><tr><td>
-<a name="severity"><h2>Severity</h2></a>
+<h2><a name="severity">Severity</a></h2>
This field describes the impact of a bug.
<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 misspelt words or misaligned text
+<tr><th>Trivial</th><td>cosmetic problem like misspelled words or misaligned text
<tr><th>Enhancement</th><td>Request for enhancement
</table>
</td><td>
-<a name="priority"><h2>Priority</h2></a>
+<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
</table>
</tr></table>
-<a name="rep_platform"><h2>Platform</h2></a>
+<h2><a name="rep_platform">Platform</a></h2>
This is the hardware platform against which the bug was reported. Legal
platforms include:
<b>Note:</b> Selecting the option "All" does not select bugs assigned against all platforms. It
merely selects bugs that <b>occur</b> on all platforms.
-<a name="op_sys"><h2>Operating System</h2></a>
+<h2><a name="op_sys">Operating System</a></h2>
This is the operating system against which the bug was reported. Legal
operating systems include:
Note that the operating system implies the platform, but not always.
For example, Linux can run on PC and Macintosh and others.
-<a name="assigned_to"><h2>Assigned To</h2></a>
+<h2><a name="assigned_to">Assigned To</a></h2>
This is the person in charge of resolving the bug. Every time this
field changes, the status changes to <B>NEW</B> to make it easy to see
+
+
#!/usr/bonsaitools/bin/perl -w
# -*- Mode: perl; indent-tabs-mode: nil -*-
#
"AND name = " . SqlQuote($::FORM{'namedcmd'}));
print "Content-type: text/html\n\n";
- PutHeader("Forget what?", "");
+ PutHeader("Query is gone", "");
print qq{
OK, the <B>$::FORM{'namedcmd'}</B> query is gone.
permissions) decides that the bug is a valid one, and confirms
it. We hope to gather a small army of responsible volunteers
to regularly go through bugs for us.
- <li> The bug gathers a certain number of votes. <b>Any</b> valid
- Bugzilla user may vote for bugs (each user gets a certain
- number of bugs); any UNCONFIRMED bug which enough bugs becomes
- automatically confirmed, and enters the NEW state.
+ <li> The bug gathers a certain number of votes. <B>Any</B> valid Bugzilla user may vote for
+bugs (each user gets a certain number of bugs); any UNCONFIRMED bug which
+gets enough votes becomes automatically confirmed, and enters the NEW state.
</ul>
One implication of this is that it is worth your time to search the