305a7218e6
known outstanding doc bug! Yay release. Still many things to fix. Aren't there always? git-svn-id: svn://10.0.0.236/trunk@101604 18797224-902f-48f8-a5cc-f745e15eee43
236 lines
4.5 KiB
HTML
236 lines
4.5 KiB
HTML
<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 2. 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"
|
|
>2.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. Bugzilla was
|
|
originally written by Terry Weissman in a programming language called
|
|
"TCL", to replace a crappy bug-tracking database used internally for
|
|
Netscape Communications. Terry later ported Bugzilla to Perl from
|
|
TCL, and in Perl it remains to this day. Most commercial
|
|
defect-tracking software vendors at the time charged enormous
|
|
licensing fees, and Bugzilla quickly became a favorite of the
|
|
open-source crowd (with its genesis in the open-source browser
|
|
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:
|
|
<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, console, and HTTP APIs
|
|
</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> available integration with automated software
|
|
configuration management systems, including Perforce and
|
|
CVS (through the Bugzilla email interface and
|
|
checkin/checkout scripts)
|
|
</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> too many more features to list
|
|
</P
|
|
></LI
|
|
></UL
|
|
>
|
|
</P
|
|
><P
|
|
> 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
|
|
daunting query interface, little reporting configurability,
|
|
problems with extremely large queries, some unsupportable bug
|
|
resolution options, little internationalization (although non-US
|
|
character sets are accepted for comments), and dependence on
|
|
some nonstandard libraries.
|
|
</P
|
|
><P
|
|
> 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"
|
|
>"simple search"</SPAN
|
|
> form on the default front page of
|
|
your Bugzilla install. Type in two or three search terms and
|
|
you should pull up some relevant information. This is also
|
|
available as "queryhelp.cgi".
|
|
</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 continually gains new features.
|
|
</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
|
|
> |