aboutsummaryrefslogtreecommitdiffstats
path: root/phpBB/phpbb/user_loader.php
diff options
context:
space:
mode:
authorMarc Alexander <admin@m-a-styles.de>2015-08-17 09:39:16 +0200
committerMarc Alexander <admin@m-a-styles.de>2015-08-17 09:39:16 +0200
commitdce1c5d4c923f852a1eae8cb14c307b0d452549d (patch)
treea87324d1cdd21f35d68c4467497fcf211dfaecae /phpBB/phpbb/user_loader.php
parenta2e19e4ea8dafc9dd70eaa09a48501047981d6d0 (diff)
parentdcf12cad26f0368785017914ccc4af6e29a04d77 (diff)
downloadforums-dce1c5d4c923f852a1eae8cb14c307b0d452549d.tar
forums-dce1c5d4c923f852a1eae8cb14c307b0d452549d.tar.gz
forums-dce1c5d4c923f852a1eae8cb14c307b0d452549d.tar.bz2
forums-dce1c5d4c923f852a1eae8cb14c307b0d452549d.tar.xz
forums-dce1c5d4c923f852a1eae8cb14c307b0d452549d.zip
Merge branch '3.1.x'
Conflicts: phpBB/styles/subsilver2/theme/stylesheet.css
Diffstat (limited to 'phpBB/phpbb/user_loader.php')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.1 (git 2.21.0) at 2026-05-15 04:45:54 +0000
e1edc97a6c62bc1a03f442b'>docs/html/Bugzilla-Guide.html
@@ -0,0 +1,15022 @@
+<HTML
+><HEAD
+><TITLE
+>The Bugzilla Guide</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+"><META
+NAME="KEYWORD"
+CONTENT="Bugzilla"><META
+NAME="KEYWORD"
+CONTENT="Guide"><META
+NAME="KEYWORD"
+CONTENT="installation"><META
+NAME="KEYWORD"
+CONTENT="FAQ"><META
+NAME="KEYWORD"
+CONTENT="administration"><META
+NAME="KEYWORD"
+CONTENT="integration"><META
+NAME="KEYWORD"
+CONTENT="MySQL"><META
+NAME="KEYWORD"
+CONTENT="Mozilla"><META
+NAME="KEYWORD"
+CONTENT="webtools"></HEAD
+><BODY
+CLASS="BOOK"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="BOOK"
+><A
+NAME="INDEX"
+></A
+><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+><A
+NAME="AEN2"
+>The Bugzilla Guide</A
+></H1
+><H3
+CLASS="AUTHOR"
+><A
+NAME="AEN27"
+>Matthew P. Barnson</A
+></H3
+><DIV
+CLASS="AFFILIATION"
+><DIV
+CLASS="ADDRESS"
+><P
+CLASS="ADDRESS"
+>barnboy@NOSPAM.trilobyte.net</P
+></DIV
+></DIV
+><SPAN
+CLASS="COLLAB"
+><SPAN
+CLASS="COLLABNAME"
+>Zach Lipton</SPAN
+><DIV
+CLASS="AFFILIATION"
+><DIV
+CLASS="ADDRESS"
+><P
+CLASS="ADDRESS"
+>zach@NOSPAM.zachlipton.com</P
+></DIV
+></DIV
+><BR></SPAN
+><H4
+CLASS="EDITEDBY"
+>Edited by</H4
+><H3
+CLASS="EDITOR"
+>I. P. Freely</H3
+><DIV
+CLASS="REVHISTORY"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+><TR
+><TH
+ALIGN="LEFT"
+VALIGN="TOP"
+COLSPAN="3"
+><B
+>Revision History</B
+></TH
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+>Revision v2.11</TD
+><TD
+ALIGN="LEFT"
+>20 December 2000</TD
+><TD
+ALIGN="LEFT"
+>Revised by: MPB</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+COLSPAN="3"
+>Converted the README, FAQ, and DATABASE information into
+ SGML docbook format.</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+>Revision 2.11.1</TD
+><TD
+ALIGN="LEFT"
+>06 March 2001</TD
+><TD
+ALIGN="LEFT"
+>Revised by: MPB</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+COLSPAN="3"
+>Took way too long to revise this for 2.12 release. Updated
+ FAQ to use qandaset tags instead of literallayout, cleaned
+ up administration section, added User Guide section,
+ miscellaneous FAQ updates and third-party integration
+ information. From this point on all new tags are lowercase
+ in preparation for the 2.13 release of the Guide in XML
+ format instead of SGML.</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+>Revision 2.12.0</TD
+><TD
+ALIGN="LEFT"
+>24 April 2001</TD
+><TD
+ALIGN="LEFT"
+>Revised by: MPB</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+COLSPAN="3"
+>Things fixed this release: Elaborated on queryhelp
+ interface, added FAQ regarding moving bugs from one keyword
+ to another, clarified possible problems with the Landfill
+ tutorial, fixed a boatload of typos and unclear sentence
+ structures. Incorporated the README into the UNIX
+ installation section, and changed the README to indicate the
+ deprecated status. Things I know need work: Used
+ "simplelist" a lot, where I should have used "procedure" to
+ tag things. Need to lowercase all tags to be XML compliant.</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+>Revision 2.14.0</TD
+><TD
+ALIGN="LEFT"
+>07 August 2001</TD
+><TD
+ALIGN="LEFT"
+>Revised by: MPB</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+COLSPAN="3"
+>Attempted to integrate relevant portions of the UNIX and
+ Windows installation instructions, moved some data from FAQ
+ to Install, removed references to README from text, added
+ Mac OS X install instructions, fixed a bunch
+ of tpyos (Mark Harig), linked text that referenced other
+ parts of the Guide, and nuked the old MySQL permissions
+ section.</TD
+></TR
+></TABLE
+></DIV
+><DIV
+><DIV
+CLASS="ABSTRACT"
+><A
+NAME="AEN46"
+></A
+><P
+></P
+><P
+> This is the documentation for Bugzilla, the Mozilla
+ bug-tracking system.
+ </P
+><P
+> Bugzilla is an enterprise-class set of software utilities
+ that, when used together, power issue-tracking for hundreds of
+ organizations around the world, tracking millions of bugs.
+ While it is easy to use and quite flexible, it is very
+ difficult for a novice to install and maintain. Although we
+ have provided step-by-step directions, Bugzilla is not always
+ easy to get working. Please be sure the person responsible
+ for installing and maintaining this software is a qualified
+ professional on operating system upon which you install
+ Bugzilla.
+ </P
+><P
+></P
+></DIV
+></DIV
+><HR></DIV
+><DIV
+CLASS="TOC"
+><DL
+><DT
+><B
+>Table of Contents</B
+></DT
+><DT
+>1. <A
+HREF="#ABOUT"
+>About This Guide</A
+></DT
+><DD
+><DL
+><DT
+>1.1. <A
+HREF="#ABOUTTHISGUIDE"
+>Purpose and Scope of this Guide</A
+></DT
+><DT
+>1.2. <A
+HREF="#COPYRIGHT"
+>Copyright Information</A
+></DT
+><DT
+>1.3. <A
+HREF="#DISCLAIMER"
+>Disclaimer</A
+></DT
+><DT
+>1.4. <A
+HREF="#NEWVERSIONS"
+>New Versions</A
+></DT
+><DT
+>1.5. <A
+HREF="#CREDITS"
+>Credits</A
+></DT
+><DT
+>1.6. <A
+HREF="#CONTRIBUTORS"
+>Contributors</A
+></DT
+><DT
+>1.7. <A
+HREF="#FEEDBACK"
+>Feedback</A
+></DT
+><DT
+>1.8. <A
+HREF="#TRANSLATIONS"
+>Translations</A
+></DT
+><DT
+>1.9. <A
+HREF="#CONVENTIONS"
+>Document Conventions</A
+></DT
+></DL
+></DD
+><DT
+>2. <A
+HREF="#USING"
+>Using Bugzilla</A
+></DT
+><DD
+><DL
+><DT
+>2.1. <A
+HREF="#WHATIS"
+>What is Bugzilla?</A
+></DT
+><DT
+>2.2. <A
+HREF="#WHY"
+>Why Should We Use Bugzilla?</A
+></DT
+><DT
+>2.3. <A
+HREF="#HOW"
+>How do I use Bugzilla?</A
+></DT
+><DD
+><DL
+><DT
+>2.3.1. <A
+HREF="#MYACCOUNT"
+>Create a Bugzilla Account</A
+></DT
+><DT
+>2.3.2. <A
+HREF="#QUERY"
+>The Bugzilla Query Page</A
+></DT
+><DT
+>2.3.3. <A
+HREF="#BUGREPORTS"
+>Creating and Managing Bug Reports</A
+></DT
+><DD
+><DL
+><DT
+>2.3.3.1. <A
+HREF="#BUG_WRITING"
+>Writing a Great Bug Report</A
+></DT
+><DT
+>2.3.3.2. <A
+HREF="#BUG_MANAGE"
+>Managing your Bug Reports</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>2.4. <A
+HREF="#INIT4ME"
+>What's in it for me?</A
+></DT
+><DD
+><DL
+><DT
+>2.4.1. <A
+HREF="#ACCOUNTSETTINGS"
+>Account Settings</A
+></DT
+><DT
+>2.4.2. <A
+HREF="#EMAILSETTINGS"
+>Email Settings</A
+></DT
+><DD
+><DL
+><DT
+>2.4.2.1. <A
+HREF="#NOTIFICATION"
+>Email Notification</A
+></DT
+><DT
+>2.4.2.2. <A
+HREF="#NEWEMAILTECH"
+>New Email Technology</A
+></DT
+><DT
+>2.4.2.3. <A
+HREF="#WATCHSETTINGS"
+>"Watching" Users</A
+></DT
+></DL
+></DD
+><DT
+>2.4.3. <A
+HREF="#FOOTERSETTINGS"
+>Page Footer</A
+></DT
+><DT
+>2.4.4. <A
+HREF="#PERMISSIONSETTINGS"
+>Permissions</A
+></DT
+></DL
+></DD
+><DT
+>2.5. <A
+HREF="#USINGBZ-CONC"
+>Using Bugzilla-Conclusion</A
+></DT
+></DL
+></DD
+><DT
+>3. <A
+HREF="#INSTALLATION"
+>Installation</A
+></DT
+><DD
+><DL
+><DT
+>3.1. <A
+HREF="#ERRATA"
+>ERRATA</A
+></DT
+><DT
+>3.2. <A
+HREF="#STEPBYSTEP"
+>Step-by-step Install</A
+></DT
+><DD
+><DL
+><DT
+>3.2.1. <A
+HREF="#AEN478"
+>Introduction</A
+></DT
+><DT
+>3.2.2. <A
+HREF="#AEN484"
+>Installing the Prerequisites</A
+></DT
+><DT
+>3.2.3. <A
+HREF="#INSTALL-MYSQL"
+>Installing MySQL Database</A
+></DT
+><DT
+>3.2.4. <A
+HREF="#INSTALL-PERL"
+>Perl (5.004 or greater)</A
+></DT
+><DT
+>3.2.5. <A
+HREF="#AEN537"
+>DBI Perl Module</A
+></DT
+><DT
+>3.2.6. <A
+HREF="#AEN574"
+>Data::Dumper Perl Module</A
+></DT
+><DT
+>3.2.7. <A
+HREF="#AEN578"
+>MySQL related Perl Module Collection</A
+></DT
+><DT
+>3.2.8. <A
+HREF="#AEN587"
+>TimeDate Perl Module Collection</A
+></DT
+><DT
+>3.2.9. <A
+HREF="#AEN590"
+>GD Perl Module (1.8.3)</A
+></DT
+><DT
+>3.2.10. <A
+HREF="#AEN596"
+>Chart::Base Perl Module (0.99c)</A
+></DT
+><DT
+>3.2.11. <A
+HREF="#AEN599"
+>DB_File Perl Module</A
+></DT
+><DT
+>3.2.12. <A
+HREF="#AEN602"
+>HTTP Server</A
+></DT
+><DT
+>3.2.13. <A
+HREF="#AEN616"
+>Installing the Bugzilla Files</A
+></DT
+><DT
+>3.2.14. <A
+HREF="#AEN636"
+>Setting Up the MySQL Database</A
+></DT
+><DT
+>3.2.15. <A
+HREF="#AEN675"
+>Tweaking "localconfig"</A
+></DT
+><DT
+>3.2.16. <A
+HREF="#AEN704"
+>Setting Up Maintainers Manually (Optional)</A
+></DT
+><DT
+>3.2.17. <A
+HREF="#AEN713"
+>The Whining Cron (Optional)</A
+></DT
+><DT
+>3.2.18. <A
+HREF="#AEN723"
+>Bug Graphs (Optional)</A
+></DT
+><DT
+>3.2.19. <A
+HREF="#AEN735"
+>Securing MySQL</A
+></DT
+></DL
+></DD
+><DT
+>3.3. <A
+HREF="#OSX"
+>Mac OS X Installation Notes</A
+></DT
+><DT
+>3.4. <A
+HREF="#BSDINSTALL"
+>BSD Installation Notes</A
+></DT
+><DT
+>3.5. <A
+HREF="#GENINSTALL"
+>Installation General Notes</A
+></DT
+><DD
+><DL
+><DT
+>3.5.1. <A
+HREF="#AEN837"
+>Modifying Your Running System</A
+></DT
+><DT
+>3.5.2. <A
+HREF="#AEN844"
+>Upgrading From Previous Versions</A
+></DT
+><DT
+>3.5.3. <A
+HREF="#HTACCESS"
+><TT
+CLASS="FILENAME"
+>.htaccess</TT
+> files and security</A
+></DT
+><DT
+>3.5.4. <A
+HREF="#AEN865"
+>UNIX Installation Instructions History</A
+></DT
+></DL
+></DD
+><DT
+>3.6. <A
+HREF="#WIN32"
+>Win32 Installation Notes</A
+></DT
+><DD
+><DL
+><DT
+>3.6.1. <A
+HREF="#WININSTALL"
+>Win32 Installation: Step-by-step</A
+></DT
+><DT
+>3.6.2. <A
+HREF="#ADDLWINTIPS"
+>Additional Windows Tips</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>4. <A
+HREF="#ADMINISTRATION"
+>Administering Bugzilla</A
+></DT
+><DD
+><DL
+><DT
+>4.1. <A
+HREF="#POSTINSTALL-CHECK"
+>Post-Installation Checklist</A
+></DT
+><DT
+>4.2. <A
+HREF="#USERADMIN"
+>User Administration</A
+></DT
+><DD
+><DL
+><DT
+>4.2.1. <A
+HREF="#DEFAULTUSER"
+>Creating the Default User</A
+></DT
+><DT
+>4.2.2. <A
+HREF="#MANAGEUSERS"
+>Managing Other Users</A
+></DT
+><DD
+><DL
+><DT
+>4.2.2.1. <A
+HREF="#LOGIN"
+>Logging In</A
+></DT
+><DT
+>4.2.2.2. <A
+HREF="#CREATENEWUSERS"
+>Creating new users</A
+></DT
+><DT
+>4.2.2.3. <A
+HREF="#DISABLEUSERS"
+>Disabling Users</A
+></DT
+><DT
+>4.2.2.4. <A
+HREF="#MODIFYUSERS"
+>Modifying Users</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>4.3. <A
+HREF="#PROGRAMADMIN"
+>Product, Component, Milestone, and Version
+ Administration</A
+></DT
+><DD
+><DL
+><DT
+>4.3.1. <A
+HREF="#PRODUCTS"
+>Products</A
+></DT
+><DT
+>4.3.2. <A
+HREF="#COMPONENTS"
+>Components</A
+></DT
+><DT
+>4.3.3. <A
+HREF="#VERSIONS"
+>Versions</A
+></DT
+><DT
+>4.3.4. <A
+HREF="#MILESTONES"
+>Milestones</A
+></DT
+><DT
+>4.3.5. <A
+HREF="#VOTING"
+>Voting</A
+></DT
+><DT
+>4.3.6. <A
+HREF="#GROUPS"
+>Groups and Group Security</A
+></DT
+></DL
+></DD
+><DT
+>4.4. <A
+HREF="#SECURITY"
+>Bugzilla Security</A
+></DT
+></DL
+></DD
+><DT
+>5. <A
+HREF="#INTEGRATION"
+>Integrating Bugzilla with Third-Party Tools</A
+></DT
+><DD
+><DL
+><DT
+>5.1. <A
+HREF="#BONSAI"
+>Bonsai</A
+></DT
+><DT
+>5.2. <A
+HREF="#CVS"
+>CVS</A
+></DT
+><DT
+>5.3. <A
+HREF="#SCM"
+>Perforce SCM</A
+></DT
+><DT
+>5.4. <A
+HREF="#TINDERBOX"
+>Tinderbox</A
+></DT
+></DL
+></DD
+><DT
+>6. <A
+HREF="#FUTURE"
+>The Future of Bugzilla</A
+></DT
+><DT
+>A. <A
+HREF="#FAQ"
+>The Bugzilla FAQ</A
+></DT
+><DT
+>B. <A
+HREF="#DOWNLOADLINKS"
+>Software Download Links</A
+></DT
+><DT
+>C. <A
+HREF="#DATABASE"
+>The Bugzilla Database</A
+></DT
+><DD
+><DL
+><DT
+>C.1. <A
+HREF="#DBSCHEMA"
+>Database Schema Chart</A
+></DT
+><DT
+>C.2. <A
+HREF="#DBDOC"
+>MySQL Bugzilla Database Introduction</A
+></DT
+><DD
+><DL
+><DT
+>C.2.1. <A
+HREF="#AEN2089"
+>Bugzilla Database Basics</A
+></DT
+><DD
+><DL
+><DT
+>C.2.1.1. <A
+HREF="#AEN2118"
+>Bugzilla Database Tables</A
+></DT
+></DL
+></DD
+></DL
+></DD
+><DT
+>C.3. <A
+HREF="#GRANTTABLES"
+>MySQL Permissions &#38; Grant Tables</A
+></DT
+></DL
+></DD
+><DT
+>7. <A
+HREF="#VARIANTS"
+>Bugzilla Variants</A
+></DT
+><DD
+><DL
+><DT
+>7.1. <A
+HREF="#RHBUGZILLA"
+>Red Hat Bugzilla</A
+></DT
+></DL
+></DD
+><DT
+>D. <A
+HREF="#PATCHES"
+>Useful Patches and Utilities for Bugzilla</A
+></DT
+><DD
+><DL
+><DT
+>D.1. <A
+HREF="#SETPERL"
+>The setperl.csh Utility</A
+></DT
+><DT
+>D.2. <A
+HREF="#CMDLINE"
+>Command-line Bugzilla Queries</A
+></DT
+><DT
+>D.3. <A
+HREF="#QUICKSEARCH"
+>The Quicksearch Utility</A
+></DT
+></DL
+></DD
+><DT
+>E. <A
+HREF="#GFDL"
+>GNU Free Documentation License</A
+></DT
+><DD
+><DL
+><DT
+>0. <A
+HREF="#GFDL_0"
+>PREAMBLE</A
+></DT
+><DT
+>1. <A
+HREF="#GFDL_1"
+>APPLICABILITY AND DEFINITIONS</A
+></DT
+><DT
+>2. <A
+HREF="#GFDL_2"
+>VERBATIM COPYING</A
+></DT
+><DT
+>3. <A
+HREF="#GFDL_3"
+>COPYING IN QUANTITY</A
+></DT
+><DT
+>4. <A
+HREF="#GFDL_4"
+>MODIFICATIONS</A
+></DT
+><DT
+>5. <A
+HREF="#GFDL_5"
+>COMBINING DOCUMENTS</A
+></DT
+><DT
+>6. <A
+HREF="#GFDL_6"
+>COLLECTIONS OF DOCUMENTS</A
+></DT
+><DT
+>7. <A
+HREF="#GFDL_7"
+>AGGREGATION WITH INDEPENDENT WORKS</A
+></DT
+><DT
+>8. <A
+HREF="#GFDL_8"
+>TRANSLATION</A
+></DT
+><DT
+>9. <A
+HREF="#GFDL_9"
+>TERMINATION</A
+></DT
+><DT
+>10. <A
+HREF="#GFDL_10"
+>FUTURE REVISIONS OF THIS LICENSE</A
+></DT
+><DT
+><A
+HREF="#GFDL_HOWTO"
+>How to use this License for your documents</A
+></DT
+></DL
+></DD
+><DT
+><A
+HREF="#GLOSSARY"
+>Glossary</A
+></DT
+></DL
+></DIV
+><DIV
+CLASS="LOT"
+><DL
+CLASS="LOT"
+><DT
+><B
+>List of Examples</B
+></DT
+><DT
+>2-1. <A
+HREF="#AEN297"
+>Some Famous Software Versions</A
+></DT
+><DT
+>2-2. <A
+HREF="#AEN307"
+>Mozilla Webtools Components</A
+></DT
+><DT
+>3-1. <A
+HREF="#AEN625"
+>Setting up bonsaitools symlink</A
+></DT
+><DT
+>3-2. <A
+HREF="#AEN697"
+>Running checksetup.pl as the web user</A
+></DT
+><DT
+>3-3. <A
+HREF="#AEN910"
+>Installing ActivePerl ppd Modules on Microsoft Windows</A
+></DT
+><DT
+>3-4. <A
+HREF="#AEN1084"
+>Removing encrypt() for Windows NT installations</A
+></DT
+><DT
+>4-1. <A
+HREF="#AEN1279"
+>Creating some Components</A
+></DT
+><DT
+>4-2. <A
+HREF="#AEN1308"
+>Common Use of Versions</A
+></DT
+><DT
+>4-3. <A
+HREF="#AEN1312"
+>A Different Use of Versions</A
+></DT
+><DT
+>4-4. <A
+HREF="#AEN1340"
+>Using SortKey with Target Milestone</A
+></DT
+><DT
+>4-5. <A
+HREF="#AEN1376"
+>When to Use Group Security</A
+></DT
+><DT
+>4-6. <A
+HREF="#AEN1393"
+>Creating a New Group</A
+></DT
+><DT
+>D-1. <A
+HREF="#AEN2193"
+>Using Setperl to set your perl path</A
+></DT
+><DT
+>1. <A
+HREF="#AEN2389"
+>A Sample Product</A
+></DT
+></DL
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="ABOUT"
+>Chapter 1. About This Guide</A
+></H1
+><DIV
+CLASS="SECTION"
+><H1
+CLASS="SECTION"
+><A
+NAME="ABOUTTHISGUIDE"
+>1.1. Purpose and Scope of this Guide</A
+></H1
+><P
+> This document was started on September 17, 2000 by Matthew P.
+ Barnson after a great deal of procrastination updating the
+ Bugzilla FAQ, which I left untouched for nearly half a year.
+ After numerous complete rewrites and reformatting, it is the
+ document you see today.
+ </P
+><P
+> Despite the lack of updates, Bugzilla is simply the best piece
+ of bug-tracking software the world has ever seen. This document
+ is intended to be the comprehensive guide to the installation,
+ administration, maintenance, and use of the Bugzilla
+ bug-tracking system.
+ </P
+><P
+> This release of the Bugzilla Guide is the
+ <EM
+>2.14.0</EM
+> release. It is so named that it
+ may match the current version of Bugzilla. The numbering
+ tradition stems from that used for many free software projects,
+ in which <EM
+>even-numbered</EM
+> point releases (1.2,
+ 1.14, etc.) are considered "stable releases", intended for
+ public consumption; on the other hand,
+ <EM
+>odd-numbered</EM
+> point releases (1.3, 2.09,
+ etc.) are considered unstable <EM
+>development</EM
+>
+ releases intended for advanced users, systems administrators,
+ developers, and those who enjoy a lot of pain.
+ </P
+><P
+> Newer revisions of the Bugzilla Guide follow the numbering
+ conventions of the main-tree Bugzilla releases, available at
+ <A
+HREF="http://www.mozilla.org/projects/bugzilla"
+TARGET="_top"
+>http://www.mozilla.org/projects/bugzilla</A
+>. Intermediate releases will have
+ a minor revision number following a period. The current version
+ of Bugzilla, as of this writing (August 10, 2001) is 2.14; if
+ something were seriously wrong with that edition of the Guide,
+ subsequent releases would receive an additional dotted-decimal
+ digit to indicate the update (2.14.0.1, 2.14.0.2, etc.).
+ Got it? Good.
+ </P
+><P
+> I wrote this in response to the enormous demand for decent
+ Bugzilla documentation. I have incorporated instructions from
+ the Bugzilla README, Frequently Asked Questions, Database Schema
+ Document, and various mailing lists to create it. Chances are,
+ there are glaring errors in this documentation; please contact
+ <TT
+CLASS="EMAIL"
+>&#60;<A
+HREF="mailto:barnboy@NOSPAM.trilobyte.net"
+>barnboy@NOSPAM.trilobyte.net</A
+>&#62;</TT
+> to correct them.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="COPYRIGHT"
+>1.2. Copyright Information</A
+></H1
+><A
+NAME="AEN76"
+></A
+><TABLE
+BORDER="0"
+WIDTH="100%"
+CELLSPACING="0"
+CELLPADDING="0"
+CLASS="BLOCKQUOTE"
+><TR
+><TD
+WIDTH="10%"
+VALIGN="TOP"
+>&nbsp;</TD
+><TD
+WIDTH="80%"
+VALIGN="TOP"
+><P
+> Permission is granted to copy, distribute and/or modify this
+ document under the terms of the GNU Free Documentation
+ License, Version 1.1 or any later version published by the
+ Free Software Foundation; with no Invariant Sections, no
+ Front-Cover Texts, and with no Back-Cover Texts. A copy of
+ the license is included in the section entitled "GNU Free
+ Documentation LIcense".
+ </P
+></TD
+><TD
+WIDTH="10%"
+VALIGN="TOP"
+>&nbsp;</TD
+></TR
+><TR
+><TD
+COLSPAN="2"
+ALIGN="RIGHT"
+VALIGN="TOP"
+>--<SPAN
+CLASS="ATTRIBUTION"
+>Copyright (c) 2000-2001 Matthew P. Barnson</SPAN
+></TD
+><TD
+WIDTH="10%"
+>&nbsp;</TD
+></TR
+></TABLE
+><P
+> If you have any questions regarding this document, its
+ copyright, or publishing this document in non-electronic form,
+ please contact Matthew P. Barnson. Remove "NOSPAM" from email address
+ to send.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="DISCLAIMER"
+>1.3. Disclaimer</A
+></H1
+><P
+> No liability for the contents of this document can be accepted.
+ Use the concepts, examples, and other content at your own risk.
+ As this is a new edition of this document, there may be errors
+ and inaccuracies that may damage your system. Use of this
+ document may cause your girlfriend to leave you, your cats to
+ pee on your furniture and clothing, your computer to cease
+ functioning, your boss to fire you, and global thermonuclear
+ war. Proceed with caution.
+ </P
+><P
+> All copyrights are held by their respective owners, unless
+ specifically noted otherwise. Use of a term in this document
+ should not be regarded as affecting the validity of any
+ trademark or service mark.
+ </P
+><P
+> Naming of particular products or brands should not be seen as
+ endorsements, with the exception of the term "GNU/Linux". I
+ wholeheartedly endorse the use of GNU/Linux in every situation
+ where it is appropriate. It is an extremely versatile, stable,
+ and robust operating system that offers an ideal operating
+ environment for Bugzilla.
+ </P
+><P
+> You are strongly recommended to make a backup of your system
+ before installing Bugzilla and at regular intervals thereafter.
+ Heaven knows it's saved my bacon time after time; if you
+ implement any suggestion in this Guide, implement this one!
+ </P
+><P
+> Although the Bugzilla development team has taken great care to
+ ensure that all easily-exploitable bugs or options are
+ documented or fixed in the code, security holes surely exist.
+ Great care should be taken both in the installation and usage of
+ this software. Carefully consider the implications of installing
+ other network services with Bugzilla. The Bugzilla development
+ team members, Netscape Communications, America Online Inc., and
+ any affiliated developers or sponsors assume no liability for
+ your use of this product. You have the source code to this
+ product, and are responsible for auditing it yourself to insure
+ your security needs are met.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="NEWVERSIONS"
+>1.4. New Versions</A
+></H1
+><P
+> This is the 2.14.0 version of The Bugzilla Guide. If you are
+ reading this from any source other than those below, please
+ check one of these mirrors to make sure you are reading an
+ up-to-date version of the Guide.
+ </P
+><P
+> This document can be found in the following places:
+ </P
+><P
+> <P
+></P
+><UL
+><LI
+><P
+> <A
+HREF="http://www.trilobyte.net/barnsons/"
+TARGET="_top"
+>TriloBYTE</A
+>
+ </P
+></LI
+><LI
+><P
+> <A
+HREF="http://www.mozilla.org/projects/bugzilla/"
+TARGET="_top"
+>Mozilla.org</A
+>
+ </P
+></LI
+><LI
+><P
+> <A
+HREF="http://www.linuxdoc.org/"
+TARGET="_top"
+>The Linux
+ Documentation Project</A
+>
+ </P
+></LI
+></UL
+>
+ </P
+><P
+> The latest version of this document can be checked out via CVS.
+ Please follow the instructions available at <A
+HREF="http://www.mozilla.org/cvs.html"
+TARGET="_top"
+>the Mozilla CVS page</A
+>, and check out the mozilla/webtools/bugzilla/docs/ branch.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="CREDITS"
+>1.5. Credits</A
+></H1
+><P
+> The people listed below have made enormous contributions to the
+ creation of this Guide, through their dedicated hacking efforts,
+ numerous e-mail and IRC support sessions, and overall excellent
+ contribution to the Bugzilla community:
+ </P
+><P
+> <A
+HREF="mailto://terry@mozilla.org"
+TARGET="_top"
+>Terry Weissman</A
+>
+ for initially converting Bugzilla from BugSplat! and writing the
+ README upon which this documentation is largely based.
+ </P
+><P
+> <A
+HREF="mailto://tara@tequilarista.org"
+TARGET="_top"
+>Tara
+ Hernandez</A
+> for keeping Bugzilla development going
+ strong after Terry left Mozilla.org
+ </P
+><P
+> <A
+HREF="mailto://dkl@redhat.com"
+TARGET="_top"
+>Dave Lawrence</A
+> for
+ providing insight into the key differences between Red Hat's
+ customized Bugzilla, and being largely responsible for the "Red
+ Hat Bugzilla" appendix
+ </P
+><P
+> <A
+HREF="mailto://endico@mozilla.org"
+TARGET="_top"
+>Dawn Endico</A
+> for
+ being a hacker extraordinaire and putting up with my incessant
+ questions and arguments on irc.mozilla.org in #mozwebtools
+ </P
+><P
+> Last but not least, all the members of the <A
+HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
+TARGET="_top"
+> netscape.public.mozilla.webtools</A
+> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="CONTRIBUTORS"
+>1.6. Contributors</A
+></H1
+><P
+> Thanks go to these people for significant contributions to this
+ documentation (in no particular order):
+ </P
+><P
+> Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen, Ron Teitelbaum
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="FEEDBACK"
+>1.7. Feedback</A
+></H1
+><P
+> I welcome feedback on this document. Without your submissions
+ and input, this Guide cannot continue to exist. Please mail
+ additions, comments, criticisms, etc. to
+ <TT
+CLASS="EMAIL"
+>&#60;<A
+HREF="mailto:barnboy@trilobyte.net"
+>barnboy@trilobyte.net</A
+>&#62;</TT
+>. Please send flames to
+ <TT
+CLASS="EMAIL"
+>&#60;<A
+HREF="mailto:devnull@localhost"
+>devnull@localhost</A
+>&#62;</TT
+>
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="TRANSLATIONS"
+>1.8. Translations</A
+></H1
+><P
+> The Bugzilla Guide needs translators! Please volunteer your
+ translation into the language of your choice. If you will
+ translate this Guide, please notify the members of the
+ mozilla-webtools mailing list at
+ <TT
+CLASS="EMAIL"
+>&#60;<A
+HREF="mailto:mozilla-webtools@mozilla.org"
+>mozilla-webtools@mozilla.org</A
+>&#62;</TT
+>, and arrange with
+ Matt Barnson to check it into CVS.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="CONVENTIONS"
+>1.9. Document Conventions</A
+></H1
+><P
+> This document uses the following conventions
+ </P
+><DIV
+CLASS="INFORMALTABLE"
+><A
+NAME="AEN135"
+></A
+><P
+></P
+><TABLE
+BORDER="0"
+CLASS="CALSTABLE"
+><THEAD
+><TR
+><TH
+ALIGN="LEFT"
+VALIGN="TOP"
+>Descriptions</TH
+><TH
+ALIGN="LEFT"
+VALIGN="TOP"
+>Appearance</TH
+></TR
+></THEAD
+><TBODY
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Warnings</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><DIV
+CLASS="CAUTION"
+><P
+></P
+><TABLE
+CLASS="CAUTION"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/caution.gif"
+HSPACE="5"
+ALT="Caution"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Warnings.</P
+></TD
+></TR
+></TABLE
+></DIV
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Hint</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><DIV
+CLASS="TIP"
+><P
+></P
+><TABLE
+CLASS="TIP"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/tip.gif"
+HSPACE="5"
+ALT="Tip"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Hint.</P
+></TD
+></TR
+></TABLE
+></DIV
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Notes</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Note.</P
+></TD
+></TR
+></TABLE
+></DIV
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Information requiring special attention</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/warning.gif"
+HSPACE="5"
+ALT="Warning"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+>Warning.</P
+></TD
+></TR
+></TABLE
+></DIV
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>File Names</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><TT
+CLASS="FILENAME"
+>file.extension</TT
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Directory Names</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><TT
+CLASS="FILENAME"
+>directory</TT
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Commands to be typed</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><B
+CLASS="COMMAND"
+>command</B
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Applications Names</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><SPAN
+CLASS="APPLICATION"
+>application</SPAN
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><I
+CLASS="FOREIGNPHRASE"
+>Prompt</I
+> of users command under bash shell</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>bash$</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><I
+CLASS="FOREIGNPHRASE"
+>Prompt</I
+> of root users command under bash shell</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>bash#</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><I
+CLASS="FOREIGNPHRASE"
+>Prompt</I
+> of user command under tcsh shell</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>tcsh$</TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Environment Variables</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><TT
+CLASS="ENVAR"
+>VARIABLE</TT
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Emphasized word</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><EM
+>word</EM
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Code Example</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><FONT
+COLOR="#000000"
+><PRE
+CLASS="PROGRAMLISTING"
+><TT
+CLASS="SGMLTAG"
+>&#60;para&#62;</TT
+>Beginning and end of paragraph<TT
+CLASS="SGMLTAG"
+>&#60;/para&#62;</TT
+></PRE
+></FONT
+></TD
+></TR
+></TABLE
+></TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+></DIV
+></DIV
+></DIV
+><DIV
+CLASS="CHAPTER"
+><HR><H1
+><A
+NAME="USING"
+>Chapter 2. Using 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
+>What, Why, How, &#38; What's in it for me?</I
+></P
+></I
+></TD
+></TR
+></TABLE
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="WHATIS"
+>2.1. What is Bugzilla?</A
+></H1
+><P
+> Bugzilla is one example of a class of programs called "Defect
+Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
+Tracking Systems allow individual or groups of developers to keep
+track of outstanding bugs in their product effectively. Bugzilla was
+originally written by Terry Weissman in a programming language called
+"TCL", to replace a crappy bug-tracking database used internally for
+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.
+ </P
+><P
+> Bugzilla has matured immensely, and now boasts many advanced features. These include:
+ <P
+></P
+><UL
+><LI
+><P
+> integrated, product-based granular security schema
+ </P
+></LI
+><LI
+><P
+> inter-bug dependencies and dependency graphing
+ </P
+></LI
+><LI
+><P
+> advanced reporting capabilities
+ </P
+></LI
+><LI
+><P
+> a robust, stable RDBMS back-end
+ </P
+></LI
+><LI
+><P
+> extensive configurability
+ </P
+></LI
+><LI
+><P
+> a very well-understood and well-thought-out natural bug resolution protocol
+ </P
+></LI
+><LI
+><P
+> email, XML, console, and HTTP APIs
+ </P
+></LI
+><LI
+><P
+> available integration with automated software configuration management systems, including
+ Perforce and CVS
+ </P
+></LI
+><LI
+><P
+> too many more features to list
+ </P
+></LI
+></UL
+>
+ </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.
+ </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".
+ </P
+><P
+> 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.
+ </P
+></DIV
+><DIV
+CLASS="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="WHY"
+>2.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="SECTION"
+><HR><H1
+CLASS="SECTION"
+><A
+NAME="HOW"
+>2.3. How do I 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
+>Hey! I'm Woody! Howdy, Howdy, Howdy!</I
+></P
+></I
+></TD
+></TR
+></TABLE
+><P
+> Bugzilla is a large, complex system. Describing how to use it
+ requires some time. If you are only interested in installing or administering
+ a Bugzilla installation, please consult the Installing and Administering
+ Bugzilla portions of this Guide. This section is principally aimed towards
+ developing end-user mastery of Bugzilla, so you may fully enjoy the benefits
+ afforded by using this reliable open-source bug-tracking software.
+ </P
+><P
+> Throughout this portion of the Guide, we will refer to user account
+ options available at the Bugzilla test installation,
+ <A
+HREF="http://landfill.tequilarista.org/"
+TARGET="_top"
+> landfill.tequilarista.org</A
+>.
+ <DIV
+CLASS="NOTE"
+><P
+></P
+><TABLE
+CLASS="NOTE"
+WIDTH="100%"
+BORDER="0"
+><TR
+><TD
+WIDTH="25"
+ALIGN="CENTER"
+VALIGN="TOP"
+><IMG
+SRC="../images/note.gif"
+HSPACE="5"
+ALT="Note"></TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+><P
+> Some people have run into difficulties completing this tutorial. If
+ you run into problems, please check the updated, online documentation available
+ at <A
+HREF="http://www.trilobyte.net/barnsons/"
+TARGET="_top"
+>http://www.trilobyte.net/barnsons</A
+>.
+ If you're still stumped, please subscribe to the newsgroup and provide details of exactly
+ what's stumping you! If enough people complain, I'll have to fix it in the next
+ version of this Guide. You can subscribe to the newsgroup at
+ <A
+HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
+TARGET="_top"
+> news://news.mozilla.org/netscape.public.mozilla.webtools</A
+>
+ </P
+></TD
+></TR
+></TABLE
+></DIV
+>
+ Although Landfill serves as a great introduction to Bugzilla, it does not offer
+ all the options you would have as a user on your own installation of Bugzilla,
+ nor can it do more than serve as a general introduction to Bugzilla. Additionally,
+ Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
+ may work slightly differently than mentioned here.
+ </P
+><DIV
+CLASS="SECTION"
+><HR><H2
+CLASS="SECTION"
+><A