From 58ec231bbbf56ddf358b43bf51818c25d1b8770c Mon Sep 17 00:00:00 2001 From: "gerv%gerv.net" <> Date: Sun, 28 Jul 2002 05:03:53 +0000 Subject: Merging from 2.16 branch. --- docs/sgml/gd-makefile.patch | 22 +++++++ docs/sgml/introduction.sgml | 149 ++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 171 insertions(+) create mode 100644 docs/sgml/gd-makefile.patch create mode 100644 docs/sgml/introduction.sgml (limited to 'docs/sgml') diff --git a/docs/sgml/gd-makefile.patch b/docs/sgml/gd-makefile.patch new file mode 100644 index 000000000..8ec35a23a --- /dev/null +++ b/docs/sgml/gd-makefile.patch @@ -0,0 +1,22 @@ +--- GD-1.33/Makefile.PL Fri Aug 4 16:59:22 2000 ++++ GD-1.33-darwin/Makefile.PL Tue Jun 26 01:29:32 2001 +@@ -3,8 +3,8 @@ + warn "NOTICE: This module requires libgd 1.8.3 or higher (shared library version 4.X).\n"; + + # =====> PATHS: CHECK AND ADJUST <===== +-my @INC = qw(-I/usr/local/include -I/usr/local/include/gd); +-my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/usr/local/lib ); ++my @INC = qw(-I/sw/include -I/sw/include/gd -I/usr/local/include -I/usr/local/include/gd); ++my @LIBPATH = qw(-L/usr/lib/X11 -L/usr/X11R6/lib -L/usr/X11/lib -L/sw/lib -L/usr/local/lib); + my @LIBS = qw(-lgd -lpng -lz); + + # FEATURE FLAGS +@@ -23,7 +23,7 @@ + + push @LIBS,'-lttf' if $TTF; + push @LIBS,'-ljpeg' if $JPEG; +-push @LIBS, '-lm' unless $^O eq 'MSWin32'; ++push @LIBS, '-lm' unless ($^O =~ /^MSWin32|darwin$/); + + # FreeBSD 3.3 with libgd built from ports croaks if -lXpm is specified + if ($^O ne 'freebsd' && $^O ne 'MSWin32') { diff --git a/docs/sgml/introduction.sgml b/docs/sgml/introduction.sgml new file mode 100644 index 000000000..33907552b --- /dev/null +++ b/docs/sgml/introduction.sgml @@ -0,0 +1,149 @@ + + Introduction + +
+ What is Bugzilla? + + + 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. + + + Bugzilla boasts many advanced features. These include: + + + Powerful searching + + + + User-configurable email notifications of bug changes + + + + Full change history + + + + Inter-bug dependency tracking and graphing + + + + Excellent attachment management + + + + Integrated, product-based, granular security schema + + + + Fully security-audited, and runs under Perl's taint mode + + + + A robust, stable RDBMS back-end + + + + Web, XML, email and console interfaces + + + + Completely customisable and/or localisable web user + interface + + + + Extensive configurability + + + + Smooth upgrade pathway between versions + + + +
+ +
+ Why Should We Use Bugzilla? + + 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. + + 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. + + But why should + you + + use Bugzilla? + + 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, NASA, 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. + + 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 follow the discussion trail + that led to critical decisions. + + 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. +
+ + + -- cgit v1.2.3-24-g4f1b