summaryrefslogtreecommitdiffstats
path: root/docs/html/whatis.html
diff options
context:
space:
mode:
authorjake%acutex.net <>2002-01-19 08:26:39 +0100
committerjake%acutex.net <>2002-01-19 08:26:39 +0100
commitd7f381254270028c7d239463521005f576575151 (patch)
tree5b931a13bc0e87145649ae1d4bb1ca28cdb81af8 /docs/html/whatis.html
parentad00e1f08f41931963b741d03bf20b082c7ae8f4 (diff)
downloadbugzilla-d7f381254270028c7d239463521005f576575151.tar.gz
bugzilla-d7f381254270028c7d239463521005f576575151.tar.xz
Latest version of compiled docs (picking up recent SGML changes).
Diffstat (limited to 'docs/html/whatis.html')
-rw-r--r--docs/html/whatis.html36
1 files changed, 18 insertions, 18 deletions
diff --git a/docs/html/whatis.html b/docs/html/whatis.html
index 248467ef5..c78fa9ef7 100644
--- a/docs/html/whatis.html
+++ b/docs/html/whatis.html
@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Why Should We Use Bugzilla?"
HREF="why.html"></HEAD
><BODY
-CLASS="SECTION"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@@ -66,15 +66,15 @@ HREF="why.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="SECTION"
+CLASS="section"
><H1
-CLASS="SECTION"
+CLASS="section"
><A
-NAME="WHATIS"
+NAME="whatis"
>2.1. What is Bugzilla?</A
></H1
><P
-> Bugzilla is one example of a class of programs called "Defect
+>&#13; Bugzilla is one example of a class of programs called "Defect
Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
Tracking Systems allow individual or groups of developers to keep
track of outstanding bugs in their product effectively. Bugzilla was
@@ -89,48 +89,48 @@ project, Mozilla). It is now the de-facto standard defect-tracking
system against which all others are measured.
</P
><P
-> Bugzilla has matured immensely, and now boasts many advanced features. These include:
+>&#13; Bugzilla has matured immensely, and now boasts many advanced features. These include:
<P
></P
><UL
><LI
><P
-> integrated, product-based granular security schema
+>&#13; integrated, product-based granular security schema
</P
></LI
><LI
><P
-> inter-bug dependencies and dependency graphing
+>&#13; inter-bug dependencies and dependency graphing
</P
></LI
><LI
><P
-> advanced reporting capabilities
+>&#13; advanced reporting capabilities
</P
></LI
><LI
><P
-> a robust, stable RDBMS back-end
+>&#13; a robust, stable RDBMS back-end
</P
></LI
><LI
><P
-> extensive configurability
+>&#13; extensive configurability
</P
></LI
><LI
><P
-> a very well-understood and well-thought-out natural bug resolution protocol
+>&#13; a very well-understood and well-thought-out natural bug resolution protocol
</P
></LI
><LI
><P
-> email, XML, console, and HTTP APIs
+>&#13; email, XML, console, and HTTP APIs
</P
></LI
><LI
><P
-> available integration with automated software
+>&#13; available integration with automated software
configuration management systems, including Perforce and
CVS (through the Bugzilla email interface and
checkin/checkout scripts)
@@ -138,14 +138,14 @@ system against which all others are measured.
></LI
><LI
><P
-> too many more features to list
+>&#13; too many more features to list
</P
></LI
></UL
>
</P
><P
-> Despite its current robustness and popularity, Bugzilla faces
+>&#13; Despite its current robustness and popularity, Bugzilla faces
some near-term challenges, such as reliance on a single
database, a lack of abstraction of the user interface and
program logic, verbose email bug notifications, a powerful but
@@ -156,7 +156,7 @@ system against which all others are measured.
some nonstandard libraries.
</P
><P
-> Some recent headway has been made on the query front, however.
+>&#13; Some recent headway has been made on the query front, however.
If you are using the latest version of Bugzilla, you should see
a <SPAN
CLASS="QUOTE"
@@ -167,7 +167,7 @@ CLASS="QUOTE"
available as "queryhelp.cgi".
</P
><P
-> Despite these small problems, Bugzilla is very hard to beat. It
+>&#13; Despite these small problems, Bugzilla is very hard to beat. It
is under <EM
>very</EM
> active development to address