aboutsummaryrefslogtreecommitdiffstats
path: root/docs/html/whatis.html
diff options
context:
space:
mode:
authorbarnboy%trilobyte.net <>2001-03-08 13:35:44 +0000
committerbarnboy%trilobyte.net <>2001-03-08 13:35:44 +0000
commit6b607da839992bead01d7cba308f216e17eed520 (patch)
treedce2e5e7aac71ccb906eb18b292712e93cd1ed85 /docs/html/whatis.html
parent3208181dc05fa0633e6cde53fec641f1db4b35ef (diff)
downloadbugs-6b607da839992bead01d7cba308f216e17eed520.tar
bugs-6b607da839992bead01d7cba308f216e17eed520.tar.gz
bugs-6b607da839992bead01d7cba308f216e17eed520.tar.bz2
bugs-6b607da839992bead01d7cba308f216e17eed520.tar.xz
bugs-6b607da839992bead01d7cba308f216e17eed520.zip
Documentation update; added docs/sgml, docs/html, docs/txt.
No text version of The Bugzilla Guide availabe yet, however.
Diffstat (limited to 'docs/html/whatis.html')
-rw-r--r--docs/html/whatis.html216
1 files changed, 216 insertions, 0 deletions
diff --git a/docs/html/whatis.html b/docs/html/whatis.html
new file mode 100644
index 000000000..2a53115b6
--- /dev/null
+++ b/docs/html/whatis.html
@@ -0,0 +1,216 @@
+<HTML
+><HEAD
+><TITLE
+>What is Bugzilla?</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Using Bugzilla"
+HREF="using.html"><LINK
+REL="PREVIOUS"
+TITLE="Using Bugzilla"
+HREF="using.html"><LINK
+REL="NEXT"
+TITLE="Why Should We Use Bugzilla?"
+HREF="why.html"></HEAD
+><BODY
+CLASS="SECTION"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="using.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 4. Using Bugzilla</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="why.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="WHATIS"
+>4.1. What is Bugzilla?</A
+></H1
+><P
+> 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.
+ At the time Bugzilla was originally written, as a port from Netscape Communications'
+ "Bugsplat!" program to Perl from TCL, there were very few competitors in the market
+ for bug-tracking software. Most commercial defect-tracking software vendors at the
+ time charged enormous licensing fees. Bugzilla quickly became a favorite of the
+ open-source crowd (with its genesis in the open-source browser project, Mozilla) and
+ 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:
+ <P
+></P
+><UL
+><LI
+><P
+> integrated, product-based granular security schema
+ </P
+></LI
+><LI
+><P
+> inter-bug dependencies and dependency graphing
+ </P
+></LI
+><LI
+><P
+> advanced reporting capabilities
+ </P
+></LI
+><LI
+><P
+> a robust, stable RDBMS back-end
+ </P
+></LI
+><LI
+><P
+> extensive configurability
+ </P
+></LI
+><LI
+><P
+> a very well-understood and well-thought-out natural bug resolution protocol
+ </P
+></LI
+><LI
+><P
+> email, XML, and HTTP APIs
+ </P
+></LI
+><LI
+><P
+> integration with several automated software configuration management systems
+ </P
+></LI
+><LI
+><P
+> too many more features to list
+ </P
+></LI
+></UL
+>
+ </P
+><P
+> Despite its current robustness and popularity, however, 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 daunting query interface, little reporting configurability,
+ problems with extremely large queries, some unsupportable bug resolution options,
+ no internationalization, and dependence on some nonstandard libraries.
+ </P
+><P
+> Despite these small problems, Bugzilla is very hard to beat. It is under <EM
+>very</EM
+>
+ active development to address the current issues, and a long-awaited overhaul in the form
+ of Bugzilla 3.0 is expected sometime later this year.
+ </P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="using.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="why.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Using Bugzilla</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="using.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Why Should We Use Bugzilla?</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file