diff options
Diffstat (limited to 'docs/en/xml')
-rw-r--r-- | docs/en/xml/integration.xml | 120 | ||||
-rw-r--r-- | docs/en/xml/introduction.xml | 149 | ||||
-rw-r--r-- | docs/en/xml/patches.xml | 2 | ||||
-rw-r--r-- | docs/en/xml/requiredsoftware.xml | 86 |
4 files changed, 1 insertions, 356 deletions
diff --git a/docs/en/xml/integration.xml b/docs/en/xml/integration.xml deleted file mode 100644 index 485a03dcd..000000000 --- a/docs/en/xml/integration.xml +++ /dev/null @@ -1,120 +0,0 @@ -<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > --> -<!-- Keep these tools listings in alphabetical order please. -MPB --> -<section id="integration"> - <title>Integrating Bugzilla with Third-Party Tools</title> - - <section id="bonsai" - xreflabel="Bonsai, the Mozilla automated CVS management system"> - <title>Bonsai</title> - - <para>Bonsai is a web-based tool for managing - <xref linkend="cvs" /> - - . Using Bonsai, administrators can control open/closed status of trees, - query a fast relational database back-end for change, branch, and comment - information, and view changes made since the last time the tree was - closed. Bonsai - also integrates with - <xref linkend="tinderbox" />. - </para> - </section> - - <section id="cvs" xreflabel="CVS, the Concurrent Versioning System"> - <title>CVS</title> - - <para>CVS integration is best accomplished, at this point, using the - Bugzilla Email Gateway.</para> - - <para>Follow the instructions in this Guide for enabling Bugzilla e-mail - integration. Ensure that your check-in script sends an email to your - Bugzilla e-mail gateway with the subject of - <quote>[Bug XXXX]</quote>, - and you can have CVS check-in comments append to your Bugzilla bug. If - you want to have the bug be closed automatically, you'll have to modify - the <filename>contrib/bugzilla_email_append.pl</filename> script. - </para> - - <para>There is also a CVSZilla project, based upon somewhat dated - Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to - email. Check it out at: <ulink url="http://www.cvszilla.org/"/>. - </para> - - <para>Another system capable of CVS integration with Bugzilla is - Scmbug. This system provides generic integration of Source code - Configuration Management with Bugtracking. Check it out at: <ulink - url="http://freshmeat.net/projects/scmbug/"/>. - </para> - - </section> - - <section id="scm" - xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS"> - - <title>Perforce SCM</title> - - <para>You can find the project page for Bugzilla and Teamtrack Perforce - integration (p4dti) at: - <ulink url="http://www.ravenbrook.com/project/p4dti/"/> - - . - <quote>p4dti</quote> - - is now an officially supported product from Perforce, and you can find - the "Perforce Public Depot" p4dti page at - <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html"/> - - .</para> - - <para>Integration of Perforce with Bugzilla, once patches are applied, is - seamless. Perforce replication information will appear below the comments - of each bug. Be certain you have a matching set of patches for the - Bugzilla version you are installing. p4dti is designed to support - multiple defect trackers, and maintains its own documentation for it. - Please consult the pages linked above for further information.</para> - </section> - - <section id="svn" - xreflabel="Subversion, a compelling replacement for CVS"> - <title>Subversion</title> - <para>Subversion is a free/open-source version control system, - designed to overcome various limitations of CVS. Integration of - Subversion with Bugzilla is possible using Scmbug, a system - providing generic integration of Source Code Configuration - Management with Bugtracking. Scmbug is available at <ulink - url="http://freshmeat.net/projects/scmbug/"/>.</para> - </section> - - <section id="tinderbox" - xreflabel="Tinderbox, the Mozilla automated build management system"> - <title>Tinderbox/Tinderbox2</title> - - <para>Tinderbox is a continuous-build system which can integrate with - Bugzilla - see - <ulink url="http://www.mozilla.org/projects/tinderbox"/> for details - of Tinderbox, and - <ulink url="http://tinderbox.mozilla.org/showbuilds.cgi"/> to see it - in action.</para> - </section> -</section> - -<!-- Keep this comment at the end of the file -Local variables: -mode: sgml -sgml-always-quote-attributes:t -sgml-auto-insert-required-elements:t -sgml-balanced-tag-edit:t -sgml-exposed-tags:nil -sgml-general-insert-case:lower -sgml-indent-data:t -sgml-indent-step:2 -sgml-local-catalogs:nil -sgml-local-ecat-files:nil -sgml-minimize-attributes:nil -sgml-namecase-general:t -sgml-omittag:t -sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter") -sgml-shorttag:t -sgml-tag-region-if-active:t -End: ---> - diff --git a/docs/en/xml/introduction.xml b/docs/en/xml/introduction.xml deleted file mode 100644 index 33907552b..000000000 --- a/docs/en/xml/introduction.xml +++ /dev/null @@ -1,149 +0,0 @@ -<chapter id="introduction"> - <title>Introduction</title> - - <section id="whatis"> - <title>What is Bugzilla?</title> - - <para> - 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. - </para> - - <para>Bugzilla boasts many advanced features. These include: - <itemizedlist> - <listitem> - <para>Powerful searching</para> - </listitem> - - <listitem> - <para>User-configurable email notifications of bug changes</para> - </listitem> - - <listitem> - <para>Full change history</para> - </listitem> - - <listitem> - <para>Inter-bug dependency tracking and graphing</para> - </listitem> - - <listitem> - <para>Excellent attachment management</para> - </listitem> - - <listitem> - <para>Integrated, product-based, granular security schema</para> - </listitem> - - <listitem> - <para>Fully security-audited, and runs under Perl's taint mode</para> - </listitem> - - <listitem> - <para>A robust, stable RDBMS back-end</para> - </listitem> - - <listitem> - <para>Web, XML, email and console interfaces</para> - </listitem> - - <listitem> - <para>Completely customisable and/or localisable web user - interface</para> - </listitem> - - <listitem> - <para>Extensive configurability</para> - </listitem> - - <listitem> - <para>Smooth upgrade pathway between versions</para> - </listitem> - </itemizedlist> - </para> - </section> - - <section id="why"> - <title>Why Should We Use Bugzilla?</title> - - <para>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.</para> - - <para>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.</para> - - <para>But why should - <emphasis>you</emphasis> - - use Bugzilla?</para> - - <para>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 - <ulink url="http://www.cvshome.org">CVS</ulink>, - <ulink url="http://www.mozilla.org/bonsai.html">Bonsai</ulink>, or - <ulink url="http://www.perforce.com">Perforce SCM</ulink>, Bugzilla - provides a powerful, easy-to-use solution to configuration management and - replication problems.</para> - - <para>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 - <emphasis>something</emphasis> - 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.</para> - - <para>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.</para> - </section> -</chapter> - -<!-- Keep this comment at the end of the file -Local variables: -mode: sgml -sgml-always-quote-attributes:t -sgml-auto-insert-required-elements:t -sgml-balanced-tag-edit:t -sgml-exposed-tags:nil -sgml-general-insert-case:lower -sgml-indent-data:t -sgml-indent-step:2 -sgml-local-catalogs:nil -sgml-local-ecat-files:nil -sgml-minimize-attributes:nil -sgml-namecase-general:t -sgml-omittag:t -sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter") -sgml-shorttag:t -sgml-tag-region-if-active:t -End: ---> diff --git a/docs/en/xml/patches.xml b/docs/en/xml/patches.xml index b1d92816f..12efb0ca4 100644 --- a/docs/en/xml/patches.xml +++ b/docs/en/xml/patches.xml @@ -21,7 +21,7 @@ <warning> <para> - These files pre-date the templatisation work done as part of the + These files pre-date the templatization work done as part of the 2.16 release, and have not been updated. </para> </warning> diff --git a/docs/en/xml/requiredsoftware.xml b/docs/en/xml/requiredsoftware.xml deleted file mode 100644 index 564e58539..000000000 --- a/docs/en/xml/requiredsoftware.xml +++ /dev/null @@ -1,86 +0,0 @@ -<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> --> - -<appendix id="downloadlinks"> - <title>Software Download Links</title> - <para> - All of these sites are current as of April, 2001. Hopefully - they'll stay current for a while. - </para> - <para> - Apache Web Server: <ulink url="http://www.apache.org/">http://www.apache.org</ulink> - Optional web server for Bugzilla, but recommended because of broad user base and support. - </para> - <para> - Bugzilla: <ulink url="http://www.mozilla.org/projects/bugzilla/"> - http://www.mozilla.org/projects/bugzilla/</ulink> - </para> - <para> - MySQL: <ulink url="http://www.mysql.com/">http://www.mysql.com/</ulink> - </para> - <para> - Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink> - </para> - <para> - CPAN: <ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink> - </para> - <para> - DBI Perl module: - <ulink url="http://www.cpan.org/modules/by-module/DBI/"> - http://www.cpan.org/modules/by-module/DBI/</ulink> - </para> - <para> - Data::Dumper module: - <ulink url="http://www.cpan.org/modules/by-module/Data/"> - http://www.cpan.org/modules/by-module/Data/</ulink> - </para> - <para> - MySQL related Perl modules: - <ulink url="http://www.cpan.org/modules/by-module/Mysql/"> - http://www.cpan.org/modules/by-module/Mysql/</ulink> - </para> - <para> - TimeDate Perl module collection: - <ulink url="http://www.cpan.org/modules/by-module/Date/"> - http://www.cpan.org/modules/by-module/Date/</ulink> - </para> - <para> - GD Perl module: - <ulink url="http://www.cpan.org/modules/by-module/GD/"> - http://www.cpan.org/modules/by-module/GD/</ulink> - Alternately, you should be able to find the latest version of - GD at <ulink url="http://www.boutell.com/gd/">http://www.boutell.com/gd/</ulink> - </para> - <para> - Chart::Base module: - <ulink url="http://www.cpan.org/modules/by-module/Chart/"> - http://www.cpan.org/modules/by-module/Chart/</ulink> - </para> - <para> - LinuxDoc Software: - <ulink url="http://www.linuxdoc.org/">http://www.linuxdoc.org/</ulink> - (for documentation maintenance) - </para> - -</appendix> - - -<!-- Keep this comment at the end of the file -Local variables: -mode: sgml -sgml-always-quote-attributes:t -sgml-auto-insert-required-elements:t -sgml-balanced-tag-edit:t -sgml-exposed-tags:nil -sgml-general-insert-case:lower -sgml-indent-data:t -sgml-indent-step:2 -sgml-local-catalogs:nil -sgml-local-ecat-files:nil -sgml-minimize-attributes:nil -sgml-namecase-general:t -sgml-omittag:t -sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter") -sgml-shorttag:t -sgml-tag-region-if-active:t -End: ---> |