summaryrefslogtreecommitdiffstats
path: root/docs/html/why.html
diff options
context:
space:
mode:
Diffstat (limited to 'docs/html/why.html')
-rw-r--r--docs/html/why.html207
1 files changed, 0 insertions, 207 deletions
diff --git a/docs/html/why.html b/docs/html/why.html
deleted file mode 100644
index b3110f1ec..000000000
--- a/docs/html/why.html
+++ /dev/null
@@ -1,207 +0,0 @@
-<HTML
-><HEAD
-><TITLE
->Why Should We Use 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="What is Bugzilla?"
-HREF="whatis.html"><LINK
-REL="NEXT"
-TITLE="How do I use Bugzilla?"
-HREF="how.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="whatis.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="how.html"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECTION"
-><H1
-CLASS="SECTION"
-><A
-NAME="WHY"
->4.2. Why Should We Use Bugzilla?</A
-></H1
-><TABLE
-BORDER="0"
-WIDTH="100%"
-CELLSPACING="0"
-CELLPADDING="0"
-CLASS="EPIGRAPH"
-><TR
-><TD
-WIDTH="45%"
->&nbsp;</TD
-><TD
-WIDTH="45%"
-ALIGN="LEFT"
-VALIGN="TOP"
-><I
-><P
-><I
->No, Who's on first...</I
-></P
-></I
-></TD
-></TR
-></TABLE
-><P
-> For many years, defect-tracking software has remained principally the domain
- of large software development houses. Even then, most shops never bothered
- with bug-tracking software, and instead simply relied on shared lists and
- email to monitor the status of defects. This procedure is error-prone and
- tends to cause those bugs judged least significant by developers to be
- dropped or ignored
- </P
-><P
-> These days, many companies are finding that integrated defect-tracking
- systems reduce downtime, increase productivity, and raise customer
- satisfaction with their systems. Along with full disclosure, an open
- bug-tracker allows manufacturers to keep in touch with their clients
- and resellers, to communicate about problems effectively throughout
- the data management chain. Many corporations have also discovered that
- defect-tracking helps reduce costs by providing IT support accountability,
- telephone support knowledge bases, and a common, well-understood system
- for accounting for unusual system or software issues.
- </P
-><P
-> But why should <EM
->you</EM
-> use Bugzilla?
- </P
-><P
-> Bugzilla is very adaptable to various situations. Known uses currently
- include IT support queues, Systems Administration deployment management,
- chip design and development problem tracking (both pre-and-post fabrication),
- and software and hardware bug tracking for luminaries such as Redhat, Loki software,
- Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
- or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
- configuration management and replication problems
- </P
-><P
-> Bugzilla can dramatically increase the productivity and accountability
- of individual employees by providing a documented workflow and positive
- feedback for good performance. How many times do you wake up in the
- morning, remembering that you were supposed to do *something* today,
- but you just can't quite remember? Put it in Bugzilla, and you have a record
- of it from which you can extrapolate milestones, predict product versions
- for integration, and by using Bugzilla's e-mail integration features
- be able to follow the discussion trail that led to critical decisions.
- </P
-><P
-> Ultimately, Bugzilla puts the power in your hands to improve your value
- to your employer or business while providing a usable framework for your natural
- attention to detail and knowledge store to flourish.
- </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="whatis.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="how.html"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->What is Bugzilla?</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="using.html"
->Up</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->How do I use Bugzilla?</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
-> \ No newline at end of file