From: bryce-mozilla%nextbus.com <> Date: Wed, 12 May 1999 11:40:02 +0000 (+0000) Subject: I keep chipping away at the Mozilla-specific things. X-Git-Tag: bugzilla-2.6~70 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5d3976a50f596cde69715a7c14b093f8dfdae776;p=thirdparty%2Fbugzilla.git I keep chipping away at the Mozilla-specific things. --- diff --git a/bug_status.html b/bug_status.html index 9bb68272f8..3fd38c60e7 100755 --- a/bug_status.html +++ b/bug_status.html @@ -145,21 +145,6 @@ prioritized their work to be done. The available priorities are: - -

Area

-This is the general area which is covered by the bug report. This allows -bugs to migrate over to testing, but not show up on the "daily bug list". -Most bugs should have area set to CODE. Legal values include: -

Platform

This is the hardware platform against which the bug was reported. Legal platforms include: @@ -195,10 +180,6 @@ 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. -

List of module owners. -

- - 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. @@ -206,6 +187,6 @@ status field appropriately.


Terry Weissman <terry@netscape.com>
-Last modified: Fri Apr 30 13:14:35 1999 +Last modified: Tue May 11 21:34:56 1999