summaryrefslogtreecommitdiffstats
path: root/docs/html/whatis.html
diff options
context:
space:
mode:
authorgerv%gerv.net <>2002-05-09 06:16:36 +0200
committergerv%gerv.net <>2002-05-09 06:16:36 +0200
commit78e1dc6bd8beed4e3884875ae8a4f96753dab9cf (patch)
treed75ce3ff9bfbcfb008c0ce75eb514acb09eddb9b /docs/html/whatis.html
parentb23550bf70319f5c051acedadd35d8ce30a43363 (diff)
downloadbugzilla-78e1dc6bd8beed4e3884875ae8a4f96753dab9cf.tar.gz
bugzilla-78e1dc6bd8beed4e3884875ae8a4f96753dab9cf.tar.xz
The first installment of Gerv's spanking of the Bugzilla Guide. This is a work-in-progress.
Diffstat (limited to 'docs/html/whatis.html')
-rw-r--r--docs/html/whatis.html71
1 files changed, 21 insertions, 50 deletions
diff --git a/docs/html/whatis.html b/docs/html/whatis.html
index 9eaea4b69..9b7791a9d 100644
--- a/docs/html/whatis.html
+++ b/docs/html/whatis.html
@@ -80,7 +80,7 @@ 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
+"TCL", to replace a crappy 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
@@ -96,83 +96,54 @@ system against which all others are measured.
><UL
><LI
><P
->&#13; integrated, product-based granular security schema
- </P
+>Powerful searching</P
></LI
><LI
><P
->&#13; inter-bug dependencies and dependency graphing
- </P
+>User-configurable email notifications of bug changes</P
></LI
><LI
><P
->&#13; advanced reporting capabilities
- </P
+>Full change history</P
></LI
><LI
><P
->&#13; a robust, stable RDBMS back-end
- </P
+>Inter-bug dependency tracking and graphing</P
></LI
><LI
><P
->&#13; extensive configurability
- </P
+>Excellent attachment management</P
></LI
><LI
><P
->&#13; a very well-understood and well-thought-out natural bug resolution protocol
- </P
+>Integrated, product-based, granular security schema</P
></LI
><LI
><P
->&#13; email, XML, console, and HTTP APIs
- </P
+>Fully security-audited, and runs under Perl's taint mode</P
></LI
><LI
><P
->&#13; available integration with automated software
- configuration management systems, including Perforce and
- CVS (through the Bugzilla email interface and
- checkin/checkout scripts)
- </P
+>A robust, stable RDBMS back-end</P
></LI
><LI
><P
->&#13; too many more features to list
- </P
+>Web, XML, email and console interfaces</P
></LI
-></UL
->
- </P
+><LI
><P
->&#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
- 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
+>Completely customisable and/or localisable web user interface</P
+></LI
+><LI
><P
->&#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"
->"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
+>Extensive configurability</P
+></LI
+><LI
><P
->&#13; 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.
+>Smooth upgrade pathway between versions</P
+></LI
+></UL
+>
</P
></DIV
><DIV