diff options
| author | barnboy%trilobyte.net <> | 2001-08-11 07:15:12 +0200 |
|---|---|---|
| committer | barnboy%trilobyte.net <> | 2001-08-11 07:15:12 +0200 |
| commit | 5bef49c26c5d3c49da84aeddee3217a2fa917e8c (patch) | |
| tree | 1c32feb9b9d72305a28beb0482ca68a9f4c805b8 /docs/html/whatis.html | |
| parent | d819eae3af3b13d4b6f17e818d449eaabe58ff9d (diff) | |
| download | bugzilla-5bef49c26c5d3c49da84aeddee3217a2fa917e8c.tar.gz bugzilla-5bef49c26c5d3c49da84aeddee3217a2fa917e8c.tar.xz | |
Removal of HTML from docs temporarily due to massive renaming
in the latest restructuring of the Bugzilla Guide.
Diffstat (limited to 'docs/html/whatis.html')
| -rw-r--r-- | docs/html/whatis.html | 226 |
1 files changed, 0 insertions, 226 deletions
diff --git a/docs/html/whatis.html b/docs/html/whatis.html deleted file mode 100644 index d53d68370..000000000 --- a/docs/html/whatis.html +++ /dev/null @@ -1,226 +0,0 @@ -<HTML -><HEAD -><TITLE ->What is Bugzilla?</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.64 -"><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. - 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, and HTTP APIs - </P -></LI -><LI -><P -> available integration with automated software configuration management systems, including - Perforce and CVS. - </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 -> Some recent headway has been made on the query front, however. If you are using the latest - version of Bugzilla, you should see a "simple search" 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 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 |