diff options
| author | gerv%gerv.net <> | 2004-01-16 07:34:12 +0100 |
|---|---|---|
| committer | gerv%gerv.net <> | 2004-01-16 07:34:12 +0100 |
| commit | 4bbb07e8048ef859cfc29c6b9d221840f2c6aed1 (patch) | |
| tree | 69ebbdef36708c17345d3220223190a3ce0b682e /docs/html/whatis.html | |
| parent | 85e651ef9836d43613c3bb55f7c1c3ff150f76d0 (diff) | |
| download | bugzilla-4bbb07e8048ef859cfc29c6b9d221840f2c6aed1.tar.gz bugzilla-4bbb07e8048ef859cfc29c6b9d221840f2c6aed1.tar.xz | |
Phase 1 of a big documentation update before 2.17.6.
Diffstat (limited to 'docs/html/whatis.html')
| -rw-r--r-- | docs/html/whatis.html | 81 |
1 files changed, 9 insertions, 72 deletions
diff --git a/docs/html/whatis.html b/docs/html/whatis.html index e92d899a3..a4f0cb41f 100644 --- a/docs/html/whatis.html +++ b/docs/html/whatis.html @@ -4,9 +4,11 @@ >What is Bugzilla?</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" -TITLE="The Bugzilla Guide - 2.17.5 Development Release" +TITLE="The Bugzilla Guide - 2.17.5 + Development Release" HREF="index.html"><LINK REL="UP" TITLE="Introduction" @@ -15,7 +17,7 @@ REL="PREVIOUS" TITLE="Introduction" HREF="introduction.html"><LINK REL="NEXT" -TITLE="Why Should We Use Bugzilla?" +TITLE="Why use a bug-tracking system?" HREF="why.html"></HEAD ><BODY CLASS="section" @@ -36,7 +38,8 @@ CELLSPACING="0" ><TH COLSPAN="3" ALIGN="center" ->The Bugzilla Guide - 2.17.5 Development Release</TH +>The Bugzilla Guide - 2.17.5 + Development Release</TH ></TR ><TR ><TD @@ -78,73 +81,7 @@ NAME="whatis" ><P > Bugzilla is a bug- or issue-tracking system. Bug-tracking systems allow individual or groups of developers effectively to keep track - of outstanding problems with their product. - Bugzilla was originally - written by Terry Weissman in a programming language called TCL, to - replace a rudimentary bug-tracking database used internally by 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 boasts many advanced features. These include: - <P -></P -><UL -><LI -><P ->Powerful searching</P -></LI -><LI -><P ->User-configurable email notifications of bug changes</P -></LI -><LI -><P ->Full change history</P -></LI -><LI -><P ->Inter-bug dependency tracking and graphing</P -></LI -><LI -><P ->Excellent attachment management</P -></LI -><LI -><P ->Integrated, product-based, granular security schema</P -></LI -><LI -><P ->Fully security-audited, and runs under Perl's taint mode</P -></LI -><LI -><P ->A robust, stable RDBMS back-end</P -></LI -><LI -><P ->Web, XML, email and console interfaces</P -></LI -><LI -><P ->Completely customisable and/or localisable web user - interface</P -></LI -><LI -><P ->Extensive configurability</P -></LI -><LI -><P ->Smooth upgrade pathway between versions</P -></LI -></UL -> + of outstanding problems with their products. </P ></DIV ><DIV @@ -205,7 +142,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Why Should We Use Bugzilla?</TD +>Why use a bug-tracking system?</TD ></TR ></TABLE ></DIV |