Skip to content

bugzilla
bugzilla
Commit 78e1dc6b authored by gerv%gerv.net's avatar gerv%gerv.net
Browse files
Options

The first installment of Gerv's spanking of the Bugzilla Guide. This is a work-in-progress.

parent b23550bf
master dev master-old release-5.0-stable version-5.2 release-5.0.6-etersoft release-5.0.5-etersoft release-5.0.4-etersoft
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 296 additions and 505 deletions
docs/html/about.html
View file @ 78e1dc6b
......@@ -104,21 +104,11 @@ HREF="credits.html"
></DT
><DT
>1.6. <A
HREF="contributors.html"
>Contributors</A
></DT
><DT
>1.7. <A
HREF="feedback.html"
>Feedback</A
></DT
><DT
>1.8. <A
HREF="translations.html"
>Translations</A
></DT
><DT
>1.9. <A
>1.7. <A
HREF="conventions.html"
>Document Conventions</A
></DT
......
docs/html/aboutthisguide.html
View file @ 78e1dc6b
......@@ -75,13 +75,6 @@ CLASS="section"
><A
NAME="aboutthisguide">1.1. Purpose and Scope of this Guide</H1
><P
>&#13; 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
>&#13; 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,
......@@ -90,7 +83,7 @@ NAME="aboutthisguide">1.1. Purpose and Scope of this Guide</H1
><P
>&#13; This release of the Bugzilla Guide is the
<EM
>2.14</EM
>2.16</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,
......@@ -117,26 +110,12 @@ TARGET="_top"
>http://www.bugzilla.org/</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
of Bugzilla, as of this writing (April 2nd, 2002) is 2.16; 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.1, 2.14.2, etc.).
digit to indicate the update (2.16.1, 2.16.2, etc.).
Got it? Good.
</P
><P
>&#13; 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@trilobyte.net"
>barnboy@trilobyte.net</A
>&#62;</TT
> to correct them.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/bzhacking.html
View file @ 78e1dc6b
......@@ -86,7 +86,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN2517">D.5.1. Things that have caused problems and should be avoided</H2
NAME="AEN2436">D.5.1. Things that have caused problems and should be avoided</H2
><P
></P
><OL
......@@ -180,7 +180,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN2531">D.5.2. Coding Style for Bugzilla</H2
NAME="AEN2450">D.5.2. Coding Style for Bugzilla</H2
><P
>&#13; While it's true that not all of the code currently in Bugzilla adheres to
this (or any) styleguide, it is something that is being worked toward. Therefore,
......
docs/html/conventions.html
View file @ 78e1dc6b
......@@ -73,14 +73,14 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="conventions">1.9. Document Conventions</H1
NAME="conventions">1.7. Document Conventions</H1
><P
>&#13; This document uses the following conventions
</P
><DIV
CLASS="informaltable"
><A
NAME="AEN129"><P
NAME="AEN91"><P
></P
><TABLE
BORDER="0"
......@@ -127,7 +127,7 @@ ALT="Caution"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Warnings.</P
>Don't run with scissors!</P
></TD
></TR
></TABLE
......@@ -163,7 +163,7 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Hint.</P
>Warm jar lids under the hot tap to loosen them.</P
></TD
></TR
></TABLE
......@@ -199,7 +199,7 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Note.</P
>Dear John...</P
></TD
></TR
></TABLE
......@@ -235,7 +235,7 @@ ALT="Warning"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Warning.</P
>Read this or the cat gets it.</P
></TD
></TR
></TABLE
......
docs/html/copyright.html
View file @ 78e1dc6b
......@@ -75,7 +75,7 @@ CLASS="section"
><A
NAME="copyright">1.2. Copyright Information</H1
><A
NAME="AEN70"><TABLE
NAME="AEN39"><TABLE
BORDER="0"
WIDTH="100%"
CELLSPACING="0"
......@@ -96,7 +96,7 @@ VALIGN="TOP"
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".
Documentation License".
</P
></TD
><TD
......@@ -111,7 +111,7 @@ ALIGN="RIGHT"
VALIGN="TOP"
>--<SPAN
CLASS="attribution"
>Copyright (c) 2000-2001 Matthew P. Barnson</SPAN
>Copyright (c) 2000-2002 Matthew P. Barnson and The Bugzilla Team</SPAN
></TD
><TD
WIDTH="10%"
......@@ -121,7 +121,7 @@ WIDTH="10%"
><P
>&#13; If you have any questions regarding this document, its
copyright, or publishing this document in non-electronic form,
please contact Matthew P. Barnson.
please contact The Bugzilla Team.
</P
></DIV
><DIV
......
docs/html/credits.html
View file @ 78e1dc6b
......@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="New Versions"
HREF="newversions.html"><LINK
REL="NEXT"
TITLE="Contributors"
HREF="contributors.html"></HEAD
TITLE="Translations"
HREF="translations.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
......@@ -59,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="contributors.html"
HREF="translations.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -82,6 +82,14 @@ NAME="credits">1.5. Credits</H1
</P
><P
>&#13; <A
HREF="mailto://mbarnson@sisna.com"
TARGET="_top"
>Matthew P. Barnson</A
>
for pulling together the Bugzilla Guide and shepherding it to 2.14.
</P
><P
>&#13; <A
HREF="mailto://terry@mozilla.org"
TARGET="_top"
>Terry Weissman</A
......@@ -124,6 +132,14 @@ TARGET="_top"
> netscape.public.mozilla.webtools</A
> newsgroup. Without your discussions, insight, suggestions, and patches, this could never have happened.
</P
><P
>&#13; Thanks also go to the following people for significant contributions
to this documentation (in no particular order):
</P
><P
>&#13; Zach Liption, Andrew Pearson, Spencer Smith, Eric Hanson, Kevin Brannen,
Ron Teitelbaum, Jacob Steenhagen, Joe Robins.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
......@@ -159,7 +175,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="contributors.html"
HREF="translations.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -183,7 +199,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Contributors</TD
>Translations</TD
></TR
></TABLE
></DIV
......
docs/html/dbdoc.html
View file @ 78e1dc6b
......@@ -138,7 +138,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN2353">C.2.1. Bugzilla Database Basics</H2
NAME="AEN2272">C.2.1. Bugzilla Database Basics</H2
><P
>&#13; If you were like me, at this point you're totally clueless
about the internals of MySQL, and if it weren't for this
......@@ -259,7 +259,7 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN2382">C.2.1.1. Bugzilla Database Tables</H3
NAME="AEN2301">C.2.1.1. Bugzilla Database Tables</H3
><P
> Imagine your MySQL database as a series of
spreadsheets, and you won't be too far off. If you use this
......
docs/html/disclaimer.html
View file @ 78e1dc6b
......@@ -92,7 +92,7 @@ NAME="disclaimer">1.3. Disclaimer</H1
</P
><P
>&#13; Naming of particular products or brands should not be seen as
endorsements, with the exception of the term "GNU/Linux". I
endorsements, with the exception of the term "GNU/Linux". We
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
......@@ -101,8 +101,7 @@ NAME="disclaimer">1.3. Disclaimer</H1
><P
>&#13; 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!
If you implement any suggestion in this Guide, implement this one!
</P
><P
>&#13; Although the Bugzilla development team has taken great care to
......
docs/html/errata.html
View file @ 78e1dc6b
......@@ -127,7 +127,7 @@ CLASS="filename"
></TR
><TR
><TD
>&#13; Release Notes for Bugzilla 2.14 are available at
>&#13; Release Notes for Bugzilla 2.16 are available at
<TT
CLASS="filename"
>docs/rel_notes.txt</TT
......
docs/html/geninstall.html
View file @ 78e1dc6b
......@@ -79,7 +79,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN942">3.5.1. Modifying Your Running System</H2
NAME="AEN874">3.5.1. Modifying Your Running System</H2
><P
>&#13; Bugzilla optimizes database lookups by storing all relatively static
information in the versioncache file, located in the data/ subdirectory
......@@ -110,13 +110,26 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN949">3.5.2. Upgrading From Previous Versions</H2
NAME="AEN881">3.5.2. Upgrading From Previous Versions</H2
><P
>&#13; The developers of Bugzilla are constantly adding new tables, columns and
fields. You'll get SQL errors if you just update the code. The strategy
to update is to simply always run the checksetup.pl script whenever
you upgrade your installation of Bugzilla. If you want to see what has
changed, you can read the comments in that file, starting from the end.
>&#13; A plain Bugzilla is fairly easy to upgrade from one version to a newer one.
However, things get a bit more complicated if you've made changes to
Bugzilla's code. In this case, you may have to re-make or reapply those
changes.
It is recommended that you take a backup of your database and your entire
Bugzilla installation before attempting an upgrade. You can upgrade a 'clean'
installation by untarring a new tarball over the old installation. If you
are upgrading from 2.12 or later, you can type <TT
CLASS="filename"
>cvs -z3
update</TT
>, and resolve conflicts if there are any.
</P
><P
>&#13; Because the developers of Bugzilla are constantly adding new tables, columns
and fields, you'll probably get SQL errors if you just update the code and
attempt to use Bugzilla. Always run the checksetup.pl script whenever
you upgrade your installation.
</P
><P
>&#13; If you are running Bugzilla version 2.8 or lower, and wish to upgrade to
......@@ -148,7 +161,9 @@ CLASS="filename"
generate the <TT
CLASS="filename"
>.htaccess</TT
> files.
> files. These .htaccess files
will not work with Apache 1.2.x - but this has security holes, so you
shouldn't be using it anyway.
<DIV
CLASS="note"
......
docs/html/gfdl-howto.html
View file @ 78e1dc6b
......@@ -79,7 +79,7 @@ NAME="gfdl-howto">How to use this License for your documents</H1
a copy of the License in the document and put the following
copyright and license notices just after the title page:</P
><A
NAME="AEN2686"><BLOCKQUOTE
NAME="AEN2605"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13; Copyright (c) YEAR YOUR NAME.
......
docs/html/gfdl.html
View file @ 78e1dc6b
......@@ -142,7 +142,7 @@ HREF="gfdl-howto.html"
><P
>Version 1.1, March 2000</P
><A
NAME="AEN2596"><BLOCKQUOTE
NAME="AEN2515"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>Copyright (C) 2000 Free Software Foundation, Inc.
......
docs/html/glossary.html
View file @ 78e1dc6b
......@@ -68,7 +68,7 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="AEN2691">0-9, high ascii</H1
NAME="AEN2610">0-9, high ascii</H1
><DL
><DT
><B
......@@ -378,7 +378,7 @@ NAME="gloss-p">P</H1
><DIV
CLASS="example"
><A
NAME="AEN2782"><P
NAME="AEN2701"><P
><B
>Example 1. A Sample Product</B
></P
......
docs/html/index.html
View file @ 78e1dc6b
......@@ -46,166 +46,33 @@ NAME="AEN2">The Bugzilla Guide</H1
><H3
CLASS="author"
><A
NAME="AEN27">Matthew P. Barnson</H3
NAME="AEN5">Matthew P. Barnson</H3
><DIV
CLASS="affiliation"
><DIV
CLASS="address"
><P
CLASS="address"
>barnboy@trilobyte.net</P
>mbarnson@sisna.com</P
></DIV
></DIV
><SPAN
CLASS="collab"
><SPAN
CLASS="collabname"
>Zach Lipton</SPAN
><DIV
CLASS="affiliation"
><DIV
CLASS="address"
><P
CLASS="address"
>zach AT zachlipton DOT com</P
></DIV
></DIV
><BR></SPAN
><P
CLASS="pubdate"
>2001-04-25<BR></P
><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="AEN39"><P
NAME="AEN12"><P
></P
><P
>&#13; This is the documentation for Bugzilla, the Mozilla
>&#13; This is the documentation for Bugzilla, the mozilla.org
bug-tracking system.
</P
><P
>&#13; Bugzilla is an enterprise-class set of software utilities
that, when used together, power issue-tracking for hundreds of
Bugzilla is an enterprise-class piece of software
that powers issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
While it is easy to use and quite flexible, it is
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 for the operating system upon which you install
Bugzilla.
</P
><P
>&#13; THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT.
IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
ADDITIONS TO THE GUIDE WRITTEN IN HTML!
>&#13; This documentation is maintained in DocBook 4.1.2 XML format.
Changes are best submitted as plain text or SGML diffs, attached
to a Bugzilla bug.
</P
><P
></P
......@@ -253,21 +120,11 @@ HREF="credits.html"
></DT
><DT
>1.6. <A
HREF="contributors.html"
>Contributors</A
></DT
><DT
>1.7. <A
HREF="feedback.html"
>Feedback</A
></DT
><DT
>1.8. <A
HREF="translations.html"
>Translations</A
></DT
><DT
>1.9. <A
>1.7. <A
HREF="conventions.html"
>Document Conventions</A
></DT
......@@ -407,43 +264,38 @@ HREF="tinderbox.html"
></DD
><DT
>6. <A
HREF="future.html"
>The Future of Bugzilla</A
></DT
><DT
>7. <A
HREF="variants.html"
>Bugzilla Variants and Competitors</A
></DT
><DD
><DL
><DT
>7.1. <A
>6.1. <A
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
></DT
><DT
>7.2. <A
>6.2. <A
HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>7.3. <A
>6.3. <A
HREF="variant-issuezilla.html"
>Issuezilla</A
></DT
><DT
>7.4. <A
>6.4. <A
HREF="variant-scarab.html"
>Scarab</A
></DT
><DT
>7.5. <A
>6.5. <A
HREF="variant-perforce.html"
>Perforce SCM</A
></DT
><DT
>7.6. <A
>6.6. <A
HREF="variant-sourceforge.html"
>SourceForge</A
></DT
......@@ -605,85 +457,75 @@ CLASS="LOT"
>List of Examples</B
></DT
><DT
>2-1. <A
HREF="how.html#AEN307"
>Some Famous Software Versions</A
></DT
><DT
>2-2. <A
HREF="how.html#AEN317"
>Mozilla's Bugzilla Components</A
></DT
><DT
>3-1. <A
HREF="stepbystep.html#AEN709"
HREF="stepbystep.html#AEN641"
>Setting up bonsaitools symlink</A
></DT
><DT
>3-2. <A
HREF="stepbystep.html#AEN800"
HREF="stepbystep.html#AEN732"
>Running checksetup.pl as the web user</A
></DT
><DT
>3-3. <A
HREF="win32.html#AEN1051"
HREF="win32.html#AEN985"
>Installing ActivePerl ppd Modules on Microsoft Windows</A
></DT
><DT
>3-4. <A
HREF="win32.html#AEN1064"
HREF="win32.html#AEN998"
>Installing OpenInteract ppd Modules manually on Microsoft
Windows</A
></DT
><DT
>3-5. <A
HREF="win32.html#AEN1246"
HREF="win32.html#AEN1180"
>Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</A
></DT
><DT
>4-1. <A
HREF="programadmin.html#AEN1483"
HREF="programadmin.html#AEN1405"
>Creating some Components</A
></DT
><DT
>4-2. <A
HREF="programadmin.html#AEN1512"
HREF="programadmin.html#AEN1434"
>Common Use of Versions</A
></DT
><DT
>4-3. <A
HREF="programadmin.html#AEN1516"
HREF="programadmin.html#AEN1438"
>A Different Use of Versions</A
></DT
><DT
>4-4. <A
HREF="programadmin.html#AEN1544"
HREF="programadmin.html#AEN1466"
>Using SortKey with Target Milestone</A
></DT
><DT
>4-5. <A
HREF="programadmin.html#AEN1580"
HREF="programadmin.html#AEN1502"
>When to Use Group Security</A
></DT
><DT
>4-6. <A
HREF="programadmin.html#AEN1597"
HREF="programadmin.html#AEN1519"
>Creating a New Group</A
></DT
><DT
>4-7. <A
HREF="programadmin.html#AEN1614"
HREF="programadmin.html#AEN1536"
>Bugzilla Groups</A
></DT
><DT
>D-1. <A
HREF="setperl.html#AEN2461"
HREF="setperl.html#AEN2380"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
HREF="glossary.html#AEN2782"
HREF="glossary.html#AEN2701"
>A Sample Product</A
></DT
></DL
......
docs/html/installation.html
View file @ 78e1dc6b
......@@ -91,12 +91,12 @@ HREF="stepbystep.html"
><DL
><DT
>3.2.1. <A
HREF="stepbystep.html#AEN509"
HREF="stepbystep.html#AEN441"
>Introduction</A
></DT
><DT
>3.2.2. <A
HREF="stepbystep.html#AEN515"
HREF="stepbystep.html#AEN447"
>Installing the Prerequisites</A
></DT
><DT
......@@ -111,57 +111,57 @@ HREF="stepbystep.html#install-perl"
></DT
><DT
>3.2.5. <A
HREF="stepbystep.html#AEN602"
HREF="stepbystep.html#AEN534"
>DBI Perl Module</A
></DT
><DT
>3.2.6. <A
HREF="stepbystep.html#AEN640"
HREF="stepbystep.html#AEN572"
>Data::Dumper Perl Module</A
></DT
><DT
>3.2.7. <A
HREF="stepbystep.html#AEN645"
HREF="stepbystep.html#AEN577"
>MySQL related Perl Module Collection</A
></DT
><DT
>3.2.8. <A
HREF="stepbystep.html#AEN654"
HREF="stepbystep.html#AEN586"
>TimeDate Perl Module Collection</A
></DT
><DT
>3.2.9. <A
HREF="stepbystep.html#AEN658"
HREF="stepbystep.html#AEN590"
>GD Perl Module (1.8.3)</A
></DT
><DT
>3.2.10. <A
HREF="stepbystep.html#AEN667"
HREF="stepbystep.html#AEN599"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
>3.2.11. <A
HREF="stepbystep.html#AEN671"
HREF="stepbystep.html#AEN603"
>DB_File Perl Module</A
></DT
><DT
>3.2.12. <A
HREF="stepbystep.html#AEN674"
HREF="stepbystep.html#AEN606"
>HTTP Server</A
></DT
><DT
>3.2.13. <A
HREF="stepbystep.html#AEN693"
HREF="stepbystep.html#AEN625"
>Installing the Bugzilla Files</A
></DT
><DT
>3.2.14. <A
HREF="stepbystep.html#AEN722"
HREF="stepbystep.html#AEN654"
>Setting Up the MySQL Database</A
></DT
><DT
>3.2.15. <A
HREF="stepbystep.html#AEN769"
HREF="stepbystep.html#AEN701"
>Tweaking <TT
CLASS="filename"
>localconfig</TT
......@@ -169,22 +169,22 @@ CLASS="filename"
></DT
><DT
>3.2.16. <A
HREF="stepbystep.html#AEN807"
HREF="stepbystep.html#AEN739"
>Setting Up Maintainers Manually (Optional)</A
></DT
><DT
>3.2.17. <A
HREF="stepbystep.html#AEN818"
HREF="stepbystep.html#AEN750"
>The Whining Cron (Optional)</A
></DT
><DT
>3.2.18. <A
HREF="stepbystep.html#AEN828"
HREF="stepbystep.html#AEN760"
>Bug Graphs (Optional)</A
></DT
><DT
>3.2.19. <A
HREF="stepbystep.html#AEN840"
HREF="stepbystep.html#AEN772"
>Securing MySQL</A
></DT
></DL
......@@ -208,12 +208,12 @@ HREF="geninstall.html"
><DL
><DT
>3.5.1. <A
HREF="geninstall.html#AEN942"
HREF="geninstall.html#AEN874"
>Modifying Your Running System</A
></DT
><DT
>3.5.2. <A
HREF="geninstall.html#AEN949"
HREF="geninstall.html#AEN881"
>Upgrading From Previous Versions</A
></DT
><DT
......
docs/html/newversions.html
View file @ 78e1dc6b
......@@ -75,7 +75,7 @@ CLASS="section"
><A
NAME="newversions">1.4. New Versions</H1
><P
>&#13; This is the 2.14 version of The Bugzilla Guide. If you are
>&#13; This is the 2.16 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.
......@@ -90,18 +90,9 @@ NAME="newversions">1.4. New Versions</H1
><LI
><P
>&#13; <A
HREF="http://www.trilobyte.net/barnsons/"
HREF="http://www.bugzilla.org/"
TARGET="_top"
>TriloBYTE</A
>
</P
></LI
><LI
><P
>&#13; <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
>Mozilla.org</A
>bugzilla.org</A
>
</P
></LI
......@@ -124,7 +115,10 @@ TARGET="_top"
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"
>the Mozilla CVS page</A
>, and check out the mozilla/webtools/bugzilla/docs/ branch.
>, and check out the <TT
CLASS="filename"
>mozilla/webtools/bugzilla/docs/</TT
> branch.
</P
></DIV
><DIV
......
docs/html/patches.html
View file @ 78e1dc6b
......@@ -109,12 +109,12 @@ HREF="bzhacking.html"
><DL
><DT
>D.5.1. <A
HREF="bzhacking.html#AEN2517"
HREF="bzhacking.html#AEN2436"
>Things that have caused problems and should be avoided</A
></DT
><DT
>D.5.2. <A
HREF="bzhacking.html#AEN2531"
HREF="bzhacking.html#AEN2450"
>Coding Style for Bugzilla</A
></DT
></DL
......
docs/html/programadmin.html
View file @ 78e1dc6b
......@@ -229,14 +229,14 @@ NAME="components">4.3.2. Components</H2
<DIV
CLASS="example"
><A
NAME="AEN1483"><P
NAME="AEN1405"><P
><B
>Example 4-1. Creating some Components</B
></P
><DIV
CLASS="informalexample"
><A
NAME="AEN1485"><P
NAME="AEN1407"><P
></P
><P
>&#13; The computer game you are designing may have a "UI"
......@@ -378,14 +378,14 @@ NAME="versions">4.3.3. Versions</H2
<DIV
CLASS="example"
><A
NAME="AEN1512"><P
NAME="AEN1434"><P
><B
>Example 4-2. Common Use of Versions</B
></P
><DIV
CLASS="informalexample"
><A
NAME="AEN1514"><P
NAME="AEN1436"><P
></P
><P
>&#13; A user reports a bug against Version "Beta 2.0" of your
......@@ -405,14 +405,14 @@ NAME="AEN1514"><P
<DIV
CLASS="example"
><A
NAME="AEN1516"><P
NAME="AEN1438"><P
><B
>Example 4-3. A Different Use of Versions</B
></P
><DIV
CLASS="informalexample"
><A
NAME="AEN1518"><P
NAME="AEN1440"><P
></P
><P
>&#13; This field has been used to good effect by an online
......@@ -545,14 +545,14 @@ TYPE="1"
><DIV
CLASS="example"
><A
NAME="AEN1544"><P
NAME="AEN1466"><P
><B
>Example 4-4. Using SortKey with Target Milestone</B
></P
><DIV
CLASS="informalexample"
><A
NAME="AEN1546"><P
NAME="AEN1468"><P
></P
><P
>&#13; Let's say you create a target milestone called
......@@ -760,14 +760,14 @@ NAME="groups">4.3.6. Groups and Group Security</H2
<DIV
CLASS="example"
><A
NAME="AEN1580"><P
NAME="AEN1502"><P
><B
>Example 4-5. When to Use Group Security</B
></P
><DIV
CLASS="informalexample"
><A
NAME="AEN1582"><P
NAME="AEN1504"><P
></P
><P
>&#13; Many Bugzilla sites isolate "Security-related" bugs from
......@@ -882,14 +882,14 @@ TYPE="1"
<DIV
CLASS="example"
><A
NAME="AEN1597"><P
NAME="AEN1519"><P
><B
>Example 4-6. Creating a New Group</B
></P
><DIV
CLASS="informalexample"
><A
NAME="AEN1599"><P
NAME="AEN1521"><P
></P
><P
>&#13; I created a group called DefaultGroup with a
......@@ -1013,7 +1013,7 @@ VALIGN="TOP"
<DIV
CLASS="example"
><A
NAME="AEN1614"><P
NAME="AEN1536"><P
><B
>Example 4-7. Bugzilla Groups</B
></P
......
docs/html/rhbugzilla.html
View file @ 78e1dc6b
......@@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -73,7 +73,7 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="rhbugzilla">7.1. Red Hat Bugzilla</H1
NAME="rhbugzilla">6.1. Red Hat Bugzilla</H1
><P
>&#13; Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
......
docs/html/security.html
View file @ 78e1dc6b
......@@ -323,6 +323,45 @@ TARGET="_top"
></TABLE
></DIV
><P
>&#13; When you run checksetup.pl, the script will attempt to modify various
permissions on files which Bugzilla uses. If you do not have a
webservergroup set in the localconfig file, then Bugzilla will have to
make certain files world readable and/or writable. <EM
>THIS IS
INSECURE!</EM
>. This means that anyone who can get access to
your system can do whatever they want to your Bugzilla installation.
</P
><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
>&#13; This also means that if your webserver runs all cgi scripts as the
same user/group, anyone on the system who can run cgi scripts will
be able to take control of your Bugzilla installation.
</P
></TD
></TR
></TABLE
></DIV
><P
>&#13; On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <A
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=57161"
......
docs/html/setperl.html
View file @ 78e1dc6b
......@@ -217,7 +217,7 @@ CLASS="command"
<DIV
CLASS="example"
><A
NAME="AEN2461"><P
NAME="AEN2380"><P
><B
>Example D-1. Using Setperl to set your perl path</B
></P
......
docs/html/stepbystep.html
View file @ 78e1dc6b
......@@ -79,7 +79,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN509">3.2.1. Introduction</H2
NAME="AEN441">3.2.1. Introduction</H2
><P
>&#13; Installation of bugzilla is pretty straightforward, particularly if your
machine already has MySQL and the MySQL-related perl packages installed.
......@@ -108,7 +108,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN515">3.2.2. Installing the Prerequisites</H2
NAME="AEN447">3.2.2. Installing the Prerequisites</H2
><DIV
CLASS="note"
><P
......@@ -604,7 +604,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN602">3.2.5. DBI Perl Module</H2
NAME="AEN534">3.2.5. DBI Perl Module</H2
><P
>&#13; The DBI module is a generic Perl module used by other database related
Perl modules. For our purposes it's required by the MySQL-related
......@@ -631,7 +631,7 @@ HREF="downloadlinks.html"
<DIV
CLASS="informalexample"
><A
NAME="AEN609"><P
NAME="AEN541"><P
></P
><P
>&#13; <TT
......@@ -683,7 +683,7 @@ VALIGN="TOP"
<DIV
CLASS="informalexample"
><A
NAME="AEN616"><P
NAME="AEN548"><P
></P
><P
>&#13; Untar the module tarball -- it should create its own directory
......@@ -774,7 +774,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN640">3.2.6. Data::Dumper Perl Module</H2
NAME="AEN572">3.2.6. Data::Dumper Perl Module</H2
><P
>&#13; The Data::Dumper module provides data structure persistence for Perl
(similar to Java's serialization). It comes with later sub-releases of
......@@ -797,7 +797,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN645">3.2.7. MySQL related Perl Module Collection</H2
NAME="AEN577">3.2.7. MySQL related Perl Module Collection</H2
><P
>&#13; The Perl/MySQL interface requires a few mutually-dependent perl
modules. These modules are grouped together into the the
......@@ -841,7 +841,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN654">3.2.8. TimeDate Perl Module Collection</H2
NAME="AEN586">3.2.8. TimeDate Perl Module Collection</H2
><P
>&#13; Many of the more common date/time/calendar related Perl
modules have been grouped into a bundle similar to the MySQL
......@@ -861,7 +861,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN658">3.2.9. GD Perl Module (1.8.3)</H2
NAME="AEN590">3.2.9. GD Perl Module (1.8.3)</H2
><P
>&#13; The GD library was written by Thomas Boutell a long while
ago to programatically generate images in C. Since then it's
......@@ -925,7 +925,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN667">3.2.10. Chart::Base Perl Module (0.99c)</H2
NAME="AEN599">3.2.10. Chart::Base Perl Module (0.99c)</H2
><P
>&#13; The Chart module provides bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it
......@@ -944,7 +944,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN671">3.2.11. DB_File Perl Module</H2
NAME="AEN603">3.2.11. DB_File Perl Module</H2
><P
>&#13; DB_File is a module which allows Perl programs to make use
of the facilities provided by Berkeley DB version 1.x. This
......@@ -958,7 +958,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN674">3.2.12. HTTP Server</H2
NAME="AEN606">3.2.12. HTTP Server</H2
><P
>&#13; You have a freedom of choice here - Apache, Netscape or any
other server on UNIX would do. You can easily run the web
......@@ -1133,7 +1133,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN693">3.2.13. Installing the Bugzilla Files</H2
NAME="AEN625">3.2.13. Installing the Bugzilla Files</H2
><P
>&#13; You should untar the Bugzilla files into a directory that
you're willing to make writable by the default web server user
......@@ -1222,7 +1222,7 @@ HREF="patches.html"
<DIV
CLASS="example"
><A
NAME="AEN709"><P
NAME="AEN641"><P
><B
>Example 3-1. Setting up bonsaitools symlink</B
></P
......@@ -1277,7 +1277,8 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="programlisting"
>&#13;perl -pi -e 's@#!/usr/bonsaitools/bin/perl@#!/usr/bin/perl@' *cgi *pl Bug.pm processmail syncshadowdb
>&#13;perl -pi -e 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm
processmail syncshadowdb
</PRE
></FONT
></TD
......@@ -1331,7 +1332,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN722">3.2.14. Setting Up the MySQL Database</H2
NAME="AEN654">3.2.14. Setting Up the MySQL Database</H2
><P
>&#13; After you've gotten all the software installed and working you're ready
to start preparing the database for its life as a the back end to a high
......@@ -1567,7 +1568,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN769">3.2.15. Tweaking <TT
NAME="AEN701">3.2.15. Tweaking <TT
CLASS="filename"
>localconfig</TT
></H2
......@@ -1691,7 +1692,7 @@ CLASS="QUOTE"
<DIV
CLASS="example"
><A
NAME="AEN800"><P
NAME="AEN732"><P
><B
>Example 3-2. Running checksetup.pl as the web user</B
></P
......@@ -1769,7 +1770,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN807">3.2.16. Setting Up Maintainers Manually (Optional)</H2
NAME="AEN739">3.2.16. Setting Up Maintainers Manually (Optional)</H2
><P
>&#13; If you want to add someone else to every group by hand, you
can do it by typing the appropriate MySQL commands. Run
......@@ -1817,7 +1818,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN818">3.2.17. The Whining Cron (Optional)</H2
NAME="AEN750">3.2.17. The Whining Cron (Optional)</H2
><P
>&#13; By now you have a fully functional bugzilla, but what good
are bugs if they're not annoying? To help make those bugs
......@@ -1901,7 +1902,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN828">3.2.18. Bug Graphs (Optional)</H2
NAME="AEN760">3.2.18. Bug Graphs (Optional)</H2
><P
>&#13; As long as you installed the GD and Graph::Base Perl modules
you might as well turn on the nifty bugzilla bug reporting
......@@ -1956,7 +1957,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN840">3.2.19. Securing MySQL</H2
NAME="AEN772">3.2.19. Securing MySQL</H2
><P
>&#13; If you followed the installation instructions for setting up
your "bugs" and "root" user in MySQL, much of this should not
......
docs/html/tinderbox.html
View file @ 78e1dc6b
......@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="Perforce SCM"
HREF="scm.html"><LINK
REL="NEXT"
TITLE="The Future of Bugzilla"
HREF="future.html"></HEAD
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
......@@ -59,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="future.html"
HREF="variants.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -111,7 +111,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="future.html"
HREF="variants.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -135,7 +135,7 @@ ACCESSKEY="U"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Future of Bugzilla</TD
>Bugzilla Variants and Competitors</TD
></TR
></TABLE
></DIV
......
docs/html/translations.html
View file @ 78e1dc6b
......@@ -13,8 +13,8 @@ REL="UP"
TITLE="About This Guide"
HREF="about.html"><LINK
REL="PREVIOUS"
TITLE="Feedback"
HREF="feedback.html"><LINK
TITLE="Credits"
HREF="credits.html"><LINK
REL="NEXT"
TITLE="Document Conventions"
HREF="conventions.html"></HEAD
......@@ -45,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="feedback.html"
HREF="credits.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -73,7 +73,7 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="translations">1.8. Translations</H1
NAME="translations">1.6. Translations</H1
><P
>&#13; The Bugzilla Guide needs translators! Please volunteer your
translation into the language of your choice. If you will
......@@ -86,7 +86,7 @@ HREF="mailto:mozilla-webtools@mozilla.org"
>mozilla-webtools@mozilla.org</A
>&#62;</TT
>, and arrange with
Matt Barnson to check it into CVS.
The Bugzilla Team to check it into CVS.
</P
></DIV
><DIV
......@@ -105,7 +105,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="feedback.html"
HREF="credits.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -133,7 +133,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Feedback</TD
>Credits</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/useradmin.html
View file @ 78e1dc6b
......@@ -443,75 +443,6 @@ VALIGN="TOP"
><LI
><P
>&#13; <EM
>Email Notification</EM
>: You may choose
from one of three options:
<P
></P
><OL
TYPE="1"
><LI
><P
>&#13; All qualifying bugs except those which I change:
The user will be notified of any change to any bug
for which she is the reporter, assignee, QA
Contact, CC recipient, or "watcher".
</P
></LI
><LI
><P
>&#13; Only those bugs which I am listed on the CC line:
The user will not be notified of changes to bugs
where she is the assignee, reporter, or QA
Contact, but will receive them if she is on the CC
list.
<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
>&#13; She will still receive whining cron emails if
you set up the "whinemail" feature.
</P
></TD
></TR
></TABLE
></DIV
>
</P
></LI
><LI
><P
>&#13; <EM
>All Qualifying Bugs</EM
>: This
user is a glutton for punishment. If her name is
in the reporter, QA Contact, CC, assignee, or is a
"watcher", she will get email updates regarding
the bug.
</P
></LI
></OL
>
</P
><P
>&#13; <EM
>Disable Text</EM
>: If you type anything
in this box, including just a space, the user account is
......
docs/html/using.html
View file @ 78e1dc6b
......@@ -124,13 +124,23 @@ HREF="how.html#myaccount"
></DT
><DT
>2.3.2. <A
HREF="how.html#query"
>The Bugzilla Query Page</A
HREF="how.html#bug_page"
>Anatomy of a Bug</A
></DT
><DT
>2.3.3. <A
HREF="how.html#query"
>Searching for Bugs</A
></DT
><DT
>2.3.4. <A
HREF="how.html#list"
>Bug Lists</A
></DT
><DT
>2.3.5. <A
HREF="how.html#bugreports"
>Creating and Managing Bug Reports</A
>Filing Bugs</A
></DT
></DL
></DD
......
docs/html/variant-fenris.html
View file @ 78e1dc6b
......@@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -73,7 +73,7 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-fenris">7.2. Loki Bugzilla (Fenris)</H1
NAME="variant-fenris">6.2. Loki Bugzilla (Fenris)</H1
><P
>Fenris can be found at <A
HREF="http://fenris.lokigames.com/"
......
docs/html/variant-issuezilla.html
View file @ 78e1dc6b
......@@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -73,7 +73,7 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-issuezilla">7.3. Issuezilla</H1
NAME="variant-issuezilla">6.3. Issuezilla</H1
><P
>Issuezilla is another fork from Bugzilla, and seems nearly
as popular as the Red Hat Bugzilla fork. Some Issuezilla team
......
docs/html/variant-perforce.html
View file @ 78e1dc6b
......@@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -73,7 +73,7 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-perforce">7.5. Perforce SCM</H1
NAME="variant-perforce">6.5. Perforce SCM</H1
><P
>Although Perforce isn't really a bug tracker, it can be used
as such through the <SPAN
......
docs/html/variant-scarab.html
View file @ 78e1dc6b
......@@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -73,7 +73,7 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-scarab">7.4. Scarab</H1
NAME="variant-scarab">6.4. Scarab</H1
><P
>Scarab is a promising new bug-tracking system built using
Java Serlet technology. As of this writing, no source code has
......
docs/html/variant-sourceforge.html
View file @ 78e1dc6b
......@@ -53,7 +53,7 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
>Chapter 6. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -73,7 +73,7 @@ CLASS="section"
><H1
CLASS="section"
><A
NAME="variant-sourceforge">7.6. SourceForge</H1
NAME="variant-sourceforge">6.6. SourceForge</H1
><P
>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the
......
docs/html/variants.html
View file @ 78e1dc6b
......@@ -10,8 +10,8 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Future of Bugzilla"
HREF="future.html"><LINK
TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"><LINK
REL="NEXT"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"></HEAD
......@@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="future.html"
HREF="tinderbox.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -69,7 +69,7 @@ WIDTH="100%"></DIV
CLASS="chapter"
><H1
><A
NAME="variants">Chapter 7. Bugzilla Variants and Competitors</H1
NAME="variants">Chapter 6. Bugzilla Variants and Competitors</H1
><DIV
CLASS="TOC"
><DL
......@@ -78,32 +78,32 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>7.1. <A
>6.1. <A
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
></DT
><DT
>7.2. <A
>6.2. <A
HREF="variant-fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>7.3. <A
>6.3. <A
HREF="variant-issuezilla.html"
>Issuezilla</A
></DT
><DT
>7.4. <A
>6.4. <A
HREF="variant-scarab.html"
>Scarab</A
></DT
><DT
>7.5. <A
>6.5. <A
HREF="variant-perforce.html"
>Perforce SCM</A
></DT
><DT
>7.6. <A
>6.6. <A
HREF="variant-sourceforge.html"
>SourceForge</A
></DT
......@@ -135,7 +135,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="future.html"
HREF="tinderbox.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -163,7 +163,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The Future of Bugzilla</TD
>Tinderbox/Tinderbox2</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/whatis.html
View file @ 78e1dc6b
......@@ -80,7 +80,7 @@ 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
"TCL", to replace a crappy 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
......@@ -96,83 +96,54 @@ system against which all others are measured.
><UL
><LI
><P
>&#13; integrated, product-based granular security schema
</P
>Powerful searching</P
></LI
><LI
><P
>&#13; inter-bug dependencies and dependency graphing
</P
>User-configurable email notifications of bug changes</P
></LI
><LI
><P
>&#13; advanced reporting capabilities
</P
>Full change history</P
></LI
><LI
><P
>&#13; a robust, stable RDBMS back-end
</P
>Inter-bug dependency tracking and graphing</P
></LI
><LI
><P
>&#13; extensive configurability
</P
>Excellent attachment management</P
></LI
><LI
><P
>&#13; a very well-understood and well-thought-out natural bug resolution protocol
</P
>Integrated, product-based, granular security schema</P
></LI
><LI
><P
>&#13; email, XML, console, and HTTP APIs
</P
>Fully security-audited, and runs under Perl's taint mode</P
></LI
><LI
><P
>&#13; available integration with automated software
configuration management systems, including Perforce and
CVS (through the Bugzilla email interface and
checkin/checkout scripts)
</P
>A robust, stable RDBMS back-end</P
></LI
><LI
><P
>&#13; too many more features to list
</P
>Web, XML, email and console interfaces</P
></LI
></UL
>
</P
><LI
><P
>&#13; Despite its current robustness and popularity, 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, little internationalization (although non-US
character sets are accepted for comments), and dependence on
some nonstandard libraries.
</P
>Completely customisable and/or localisable web user interface</P
></LI
><LI
><P
>&#13; Some recent headway has been made on the query front, however.
If you are using the latest version of Bugzilla, you should see
a <SPAN
CLASS="QUOTE"
>"simple search"</SPAN
> 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
>Extensive configurability</P
></LI
><LI
><P
>&#13; Despite these small problems, Bugzilla is very hard to beat. It
is under <EM
>very</EM
> active development to address
the current issues, and continually gains new features.
>Smooth upgrade pathway between versions</P
></LI
></UL
>
</P
></DIV
><DIV
......
docs/html/win32.html
View file @ 78e1dc6b
......@@ -313,7 +313,7 @@ CLASS="command"
><DIV
CLASS="example"
><A
NAME="AEN1051"><P
NAME="AEN985"><P
><B
>Example 3-3. Installing ActivePerl ppd Modules on Microsoft Windows</B
></P
......@@ -364,7 +364,7 @@ TARGET="_top"
<DIV
CLASS="example"
><A
NAME="AEN1064"><P
NAME="AEN998"><P
><B
>Example 3-4. Installing OpenInteract ppd Modules manually on Microsoft
Windows</B
......@@ -1407,7 +1407,7 @@ VALIGN="TOP"
><P
>&#13; From Andrew Pearson:
<A
NAME="AEN1234"><BLOCKQUOTE
NAME="AEN1168"><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
>&#13; You can make Bugzilla work with Personal Web Server for
......@@ -1487,11 +1487,11 @@ VALIGN="TOP"
>not necessary</EM
> for Bugzilla 2.13 and
later, which includes the current release, Bugzilla
2.14.
2.16.
<DIV
CLASS="example"
><A
NAME="AEN1246"><P
NAME="AEN1180"><P
><B
>Example 3-5. Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</B
......
docs/images/caution.gif
View replaced file @ b23550bf View file @ 78e1dc6b
docs/images/caution.gif

260 Bytes | W: 0px | H: 0px

docs/images/caution.gif

134 Bytes | W: 0px | H: 0px

  • 2-up
  • Swipe
  • Onion skin
docs/images/tip.gif
View replaced file @ b23550bf View file @ 78e1dc6b
docs/images/tip.gif

2.38 KB | W: 0px | H: 0px

docs/images/tip.gif

1.2 KB | W: 0px | H: 0px

  • 2-up
  • Swipe
  • Onion skin
docs/images/warning.gif
View replaced file @ b23550bf View file @ 78e1dc6b
docs/images/warning.gif

151 Bytes | W: 0px | H: 0px

docs/images/warning.gif

140 Bytes | W: 0px | H: 0px

  • 2-up
  • Swipe
  • Onion skin
docs/sgml/administration.sgml
View file @ 78e1dc6b
......@@ -1373,12 +1373,14 @@ Group3, since he isn't in Group4.
make certain files world readable and/or writable. <emphasis>THIS IS
INSECURE!</emphasis>. This means that anyone who can get access to
your system can do whatever they want to your Bugzilla installation.
<note>
</para>
<note>
<para>
This also means that if your webserver runs all cgi scripts as the
same user/group, anyone on the system who can run cgi scripts will
be able to take control of your Bugzilla installation.
</note>
</para>
</para>
</note>
<para>
On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ulink> for the localconfig file, and <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"> Bug 65572</ulink> for adequate protection in your data/ and shadow/ directories.
......
docs/sgml/conventions.sgml
View file @ 78e1dc6b
......@@ -23,25 +23,25 @@
<row>
<entry>Warnings</entry>
<entry><caution>
<para>Warnings.</para>
<para>Don't run with scissors!</para>
</caution></entry>
</row>
<row>
<entry>Hint</entry>
<entry><tip>
<para>Hint.</para>
<para>Warm jar lids under the hot tap to loosen them.</para>
</tip></entry>
</row>
<row>
<entry>Notes</entry>
<entry><note>
<para>Note.</para>
<para>Dear John...</para>
</note></entry>
</row>
<row>
<entry>Information requiring special attention</entry>
<entry><warning>
<para>Warning.</para>
<para>Read this or the cat gets it.</para>
</warning></entry>
</row>
<row>
......
docs/xml/administration.xml
View file @ 78e1dc6b
......@@ -1373,12 +1373,14 @@ Group3, since he isn't in Group4.
make certain files world readable and/or writable. <emphasis>THIS IS
INSECURE!</emphasis>. This means that anyone who can get access to
your system can do whatever they want to your Bugzilla installation.
<note>
</para>
<note>
<para>
This also means that if your webserver runs all cgi scripts as the
same user/group, anyone on the system who can run cgi scripts will
be able to take control of your Bugzilla installation.
</note>
</para>
</para>
</note>
<para>
On Apache, you can use .htaccess files to protect access
to these directories, as outlined in <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ulink> for the localconfig file, and <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"> Bug 65572</ulink> for adequate protection in your data/ and shadow/ directories.
......
docs/xml/conventions.xml
View file @ 78e1dc6b
......@@ -23,25 +23,25 @@
<row>
<entry>Warnings</entry>
<entry><caution>
<para>Warnings.</para>
<para>Don't run with scissors!</para>
</caution></entry>
</row>
<row>
<entry>Hint</entry>
<entry><tip>
<para>Hint.</para>
<para>Warm jar lids under the hot tap to loosen them.</para>
</tip></entry>
</row>
<row>
<entry>Notes</entry>
<entry><note>
<para>Note.</para>
<para>Dear John...</para>
</note></entry>
</row>
<row>
<entry>Information requiring special attention</entry>
<entry><warning>
<para>Warning.</para>
<para>Read this or the cat gets it.</para>
</warning></entry>
</row>
<row>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment