aboutsummaryrefslogtreecommitdiffstats
path: root/docs/html/whatis.html
diff options
context:
space:
mode:
authorbarnboy%trilobyte.net <>2001-08-22 10:44:14 +0000
committerbarnboy%trilobyte.net <>2001-08-22 10:44:14 +0000
commitbf8ac7551058df22dd5eb712631d9e383fc587a5 (patch)
tree8cf0b9bb7d0755c75266bd30cf7059d556a23703 /docs/html/whatis.html
parentf210bb460c786a31bc7677f0e547a67880997558 (diff)
downloadbugs-bf8ac7551058df22dd5eb712631d9e383fc587a5.tar
bugs-bf8ac7551058df22dd5eb712631d9e383fc587a5.tar.gz
bugs-bf8ac7551058df22dd5eb712631d9e383fc587a5.tar.bz2
bugs-bf8ac7551058df22dd5eb712631d9e383fc587a5.tar.xz
bugs-bf8ac7551058df22dd5eb712631d9e383fc587a5.zip
Big checkin of docs to resolve every
known outstanding doc bug! Yay release. Still many things to fix. Aren't there always?
Diffstat (limited to 'docs/html/whatis.html')
-rw-r--r--docs/html/whatis.html42
1 files changed, 26 insertions, 16 deletions
diff --git a/docs/html/whatis.html b/docs/html/whatis.html
index 81a8cd49a..248467ef5 100644
--- a/docs/html/whatis.html
+++ b/docs/html/whatis.html
@@ -130,8 +130,10 @@ system against which all others are measured.
></LI
><LI
><P
-> available integration with automated software configuration management systems, including
- Perforce and CVS
+> available integration with automated software
+ configuration management systems, including Perforce and
+ CVS (through the Bugzilla email interface and
+ checkin/checkout scripts)
</P
></LI
><LI
@@ -143,25 +145,33 @@ system against which all others are measured.
>
</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.
+> 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 "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".
+> 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
+> 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.
+> active development to address
+ the current issues, and continually gains new features.
</P
></DIV
><DIV