From d495a972854500ce323f15d024605ec395fab155 Mon Sep 17 00:00:00 2001 From: Max Kanat-Alexander Date: Mon, 1 Feb 2010 13:39:54 -0800 Subject: Fix the data in the bzr repo to match the data in the CVS repo. During the CVS imports into Bzr, there were some inconsistencies introduced (mostly that files that were deleted in CVS weren't being deleted in Bzr). So this checkin makes the bzr repo actually consistent with the CVS repo, including fixing permissions of files. --- docs/en/xml/integration.xml | 120 ------------------------------- docs/en/xml/introduction.xml | 149 --------------------------------------- docs/en/xml/patches.xml | 2 +- docs/en/xml/requiredsoftware.xml | 86 ---------------------- 4 files changed, 1 insertion(+), 356 deletions(-) delete mode 100644 docs/en/xml/integration.xml delete mode 100644 docs/en/xml/introduction.xml delete mode 100644 docs/en/xml/requiredsoftware.xml (limited to 'docs/en') 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 @@ - - -
- Integrating Bugzilla with Third-Party Tools - -
- Bonsai - - Bonsai is a web-based tool for managing - - - . 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 - . - -
- -
- CVS - - CVS integration is best accomplished, at this point, using the - Bugzilla Email Gateway. - - 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 - [Bug XXXX], - 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 contrib/bugzilla_email_append.pl script. - - - 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: . - - - 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: . - - -
- -
- - Perforce SCM - - You can find the project page for Bugzilla and Teamtrack Perforce - integration (p4dti) at: - - - . - p4dti - - is now an officially supported product from Perforce, and you can find - the "Perforce Public Depot" p4dti page at - - - . - - 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. -
- -
- Subversion - 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 . -
- -
- Tinderbox/Tinderbox2 - - Tinderbox is a continuous-build system which can integrate with - Bugzilla - see - for details - of Tinderbox, and - to see it - in action. -
-
- - - 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 @@ - - 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. -
- - - 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 @@ - 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. 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 @@ - - - - Software Download Links - - All of these sites are current as of April, 2001. Hopefully - they'll stay current for a while. - - - Apache Web Server: http://www.apache.org - Optional web server for Bugzilla, but recommended because of broad user base and support. - - - Bugzilla: - http://www.mozilla.org/projects/bugzilla/ - - - MySQL: http://www.mysql.com/ - - - Perl: http://www.perl.org/ - - - CPAN: http://www.cpan.org/ - - - DBI Perl module: - - http://www.cpan.org/modules/by-module/DBI/ - - - Data::Dumper module: - - http://www.cpan.org/modules/by-module/Data/ - - - MySQL related Perl modules: - - http://www.cpan.org/modules/by-module/Mysql/ - - - TimeDate Perl module collection: - - http://www.cpan.org/modules/by-module/Date/ - - - GD Perl module: - - http://www.cpan.org/modules/by-module/GD/ - Alternately, you should be able to find the latest version of - GD at http://www.boutell.com/gd/ - - - Chart::Base module: - - http://www.cpan.org/modules/by-module/Chart/ - - - LinuxDoc Software: - http://www.linuxdoc.org/ - (for documentation maintenance) - - - - - - -- cgit v1.2.3-24-g4f1b