From 81d43fa41c61fc801863c9aabeae137c122e5e46 Mon Sep 17 00:00:00 2001 From: "justdave%syndicomm.com" <> Date: Wed, 1 May 2002 16:28:45 +0000 Subject: Full recompile of the docs so everyone can see what the current SGML docs actually look like in HTML. --- docs/html/programadmin.html | 94 +++++++++++++++------------------------------ 1 file changed, 31 insertions(+), 63 deletions(-) (limited to 'docs/html/programadmin.html') diff --git a/docs/html/programadmin.html b/docs/html/programadmin.html index b4e3bca3d..2d7ad3a2e 100644 --- a/docs/html/programadmin.html +++ b/docs/html/programadmin.html @@ -5,7 +5,7 @@ Administration
Prev

4.3. Product, Component, Milestone, and Version - Administration

4.3. Product, Component, Milestone, and Version + Administration
Next

4.3.1. Products

4.3.1. ProductsFormerly, and in some spots still, called @@ -223,27 +222,21 @@ CLASS="section" >

4.3.2. Components

4.3.2. Components

Components are subsections of a Product.

Example 4-1. Creating some Components

The computer game you are designing may have a "UI" @@ -376,9 +369,7 @@ CLASS="section" >

4.3.3. Versions

4.3.3. Versions

Versions are the revisions of the product, such as "Flinders 3.1", "Flinders 95", and "Flinders 2000". Using Versions @@ -387,18 +378,14 @@ NAME="versions"

Example 4-2. Common Use of Versions

A user reports a bug against Version "Beta 2.0" of your @@ -418,18 +405,14 @@ NAME="AEN1501"

Example 4-3. A Different Use of Versions

This field has been used to good effect by an online @@ -496,9 +479,7 @@ CLASS="section" >

4.3.4. Milestones

4.3.4. Milestones

Milestones are "targets" that you plan to get a bug fixed by. For example, you have a bug that you plan to fix for your 3.0 @@ -564,18 +545,14 @@ TYPE="1" >

Example 4-4. Using SortKey with Target Milestone

Let's say you create a target milestone called @@ -666,9 +643,7 @@ CLASS="section" >

4.3.5. Voting

4.3.5. Voting

The concept of "voting" is a poorly understood, yet powerful feature for the management of open-source projects. Each user @@ -775,9 +750,7 @@ CLASS="section" >

4.3.6. Groups and Group Security

4.3.6. Groups and Group Security

Groups can be very useful in bugzilla, because they allow users to isolate bugs or products that should only be seen by @@ -787,18 +760,14 @@ NAME="groups"

Example 4-5. When to Use Group Security

Many Bugzilla sites isolate "Security-related" bugs from @@ -913,18 +882,14 @@ TYPE="1"

Example 4-6. Creating a New Group

I created a group called DefaultGroup with a @@ -1048,9 +1013,7 @@ VALIGN="TOP"

Example 4-7. Bugzilla Groups


Bug7 can be seen by anyone who is in Group1, Group2, and Group3.  This
is only User4.  All of the others are missing at least one of those
-group priveleges, and thus cannot see the bug.
+group privileges, and thus cannot see the bug.

Bug8 can be seen by anyone who is in Group1, Group2, Group3, and
Group4.  There is nobody in all four of these groups, so nobody can
@@ -1157,6 +1120,7 @@ CLASS="NAVFOOTER" >
PrevUp
HomeNext