mozilla
/
gecko-dev
зеркало из https://github.com/mozilla/gecko-dev.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность

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

This commit is contained in:
gerv%gerv.net 2002-05-08 21:16:47 +00:00
Родитель b49562453f
Коммит f752e3aa12
45 изменённых файлов: 1342 добавлений и 2262 удалений
Показать статистику Скачать Patch файл Скачать Diff файл Показать все файлы Свернуть все файлы

12
webtools/bugzilla/docs/html/about.html
Просмотреть файл

@ -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

27
webtools/bugzilla/docs/html/aboutthisguide.html
Просмотреть файл

@ -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"

4
webtools/bugzilla/docs/html/bzhacking.html
Просмотреть файл

@ -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,

12
webtools/bugzilla/docs/html/conventions.html
Просмотреть файл

@ -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

8
webtools/bugzilla/docs/html/copyright.html
Просмотреть файл

@ -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

26
webtools/bugzilla/docs/html/credits.html
Просмотреть файл

@ -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

4
webtools/bugzilla/docs/html/dbdoc.html
Просмотреть файл

@ -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

5
webtools/bugzilla/docs/html/disclaimer.html
Просмотреть файл

@ -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

2
webtools/bugzilla/docs/html/errata.html
Просмотреть файл

@ -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

314
webtools/bugzilla/docs/html/faq.html
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

31
webtools/bugzilla/docs/html/geninstall.html
Просмотреть файл

@ -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"

2
webtools/bugzilla/docs/html/gfdl-howto.html
Просмотреть файл

@ -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.

2
webtools/bugzilla/docs/html/gfdl.html
Просмотреть файл

@ -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.

4
webtools/bugzilla/docs/html/glossary.html
Просмотреть файл

@ -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

945
webtools/bugzilla/docs/html/how.html
Просмотреть файл

Разница между файлами не показана из-за своего большого размера Загрузить разницу

218
webtools/bugzilla/docs/html/index.html
Просмотреть файл

@ -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

38
webtools/bugzilla/docs/html/installation.html
Просмотреть файл

@ -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

20
webtools/bugzilla/docs/html/newversions.html
Просмотреть файл

@ -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

4
webtools/bugzilla/docs/html/patches.html
Просмотреть файл

@ -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

26
webtools/bugzilla/docs/html/programadmin.html
Просмотреть файл

@ -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

4
webtools/bugzilla/docs/html/rhbugzilla.html
Просмотреть файл

@ -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

39
webtools/bugzilla/docs/html/security.html
Просмотреть файл

@ -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"

2
webtools/bugzilla/docs/html/setperl.html
Просмотреть файл

@ -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

45
webtools/bugzilla/docs/html/stepbystep.html
Просмотреть файл

@ -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

10
webtools/bugzilla/docs/html/tinderbox.html
Просмотреть файл

@ -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

14
webtools/bugzilla/docs/html/translations.html
Просмотреть файл

@ -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"

69
webtools/bugzilla/docs/html/useradmin.html
Просмотреть файл

@ -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

16
webtools/bugzilla/docs/html/using.html
Просмотреть файл

@ -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

4
webtools/bugzilla/docs/html/variant-fenris.html
Просмотреть файл

@ -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/"

4
webtools/bugzilla/docs/html/variant-issuezilla.html
Просмотреть файл

@ -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

4
webtools/bugzilla/docs/html/variant-perforce.html
Просмотреть файл

@ -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

4
webtools/bugzilla/docs/html/variant-scarab.html
Просмотреть файл

@ -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

4
webtools/bugzilla/docs/html/variant-sourceforge.html
Просмотреть файл

@ -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

24
webtools/bugzilla/docs/html/variants.html
Просмотреть файл

@ -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"

73
webtools/bugzilla/docs/html/whatis.html
Просмотреть файл

@ -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,84 +96,55 @@ 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
><LI
><P
>Completely customisable and/or localisable web user interface</P
></LI
><LI
><P
>Extensive configurability</P
></LI
><LI
><P
>Smooth upgrade pathway between versions</P
></LI
></UL
>
</P
><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
><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
><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.
</P
></DIV
><DIV
CLASS="NAVFOOTER"

10
webtools/bugzilla/docs/html/win32.html
Просмотреть файл

@ -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

Двоичные данные
webtools/bugzilla/docs/images/caution.gif
Просмотреть файл

Двоичный файл не отображается.
Режим "рядом" Свайп Оверлей

До

Ширина:  |  Высота:  |  Размер: 260 B

После

Ширина:  |  Высота:  |  Размер: 134 B

Двоичные данные
webtools/bugzilla/docs/images/tip.gif
Просмотреть файл

Двоичный файл не отображается.
Режим "рядом" Свайп Оверлей

До

Ширина:  |  Высота:  |  Размер: 2.4 KiB

После

Ширина:  |  Высота:  |  Размер: 1.2 KiB

Двоичные данные
webtools/bugzilla/docs/images/warning.gif
Просмотреть файл

Двоичный файл не отображается.
Режим "рядом" Свайп Оверлей

До

Ширина:  |  Высота:  |  Размер: 151 B

После

Ширина:  |  Высота:  |  Размер: 140 B

8
webtools/bugzilla/docs/sgml/administration.sgml
Просмотреть файл

@ -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.

8
webtools/bugzilla/docs/sgml/conventions.sgml
Просмотреть файл

@ -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>

771
webtools/bugzilla/docs/sgml/using.sgml
Просмотреть файл

@ -55,54 +55,20 @@ system against which all others are measured.
<para>
Bugzilla has matured immensely, and now boasts many advanced features. These include:
<itemizedlist>
<listitem>
<para>
integrated, product-based granular security schema
</para>
</listitem>
<listitem>
<para>
inter-bug dependencies and dependency graphing
</para>
</listitem>
<listitem>
<para>
advanced reporting capabilities
</para>
</listitem>
<listitem>
<para>
a robust, stable RDBMS back-end
</para>
</listitem>
<listitem>
<para>
extensive configurability
</para>
</listitem>
<listitem>
<para>
a very well-understood and well-thought-out natural bug resolution protocol
</para>
</listitem>
<listitem>
<para>
email, XML, console, and web interfaces
</para>
</listitem>
<listitem>
<para>
available integration with automated software
configuration management systems, including Perforce and
CVS (through the Bugzilla email interface and
checkin/checkout scripts)
</para>
</listitem>
<listitem>
<para>
too many more features to list
</para>
</listitem>
<listitem><para>Powerful searching</para></listitem>
<listitem><para>User-configurable email notifications of bug changes</para></listitem>
<listitem><para>Full change history</para></listitem>
<listitem><para>Inter-bug dependency tracking and graphing</para></listitem>
<listitem><para>Excellent attachment management</para></listitem>
<listitem><para>Integrated, product-based, granular security schema</para></listitem>
<listitem><para>Fully security-audited, and runs under Perl's taint mode</para></listitem>
<listitem><para>A robust, stable RDBMS back-end</para></listitem>
<listitem><para>Web, XML, email and console interfaces</para></listitem>
<listitem><para>Completely customisable and/or localisable web user interface</para></listitem>
<listitem><para>Extensive configurability</para></listitem>
<listitem><para>Smooth upgrade pathway between versions</para></listitem>
</itemizedlist>
</para>
</section>
@ -178,25 +144,16 @@ system against which all others are measured.
</epigraph>
<para>
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
This section contains information for end-users of Bugzilla.
If you are 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.
</para>
<para>
Throughout this portion of the Guide, we will refer to user
account options available at the Bugzilla test installation,
There is a Bugzilla test installation, called
<ulink url="http://landfill.tequilarista.org/">
landfill.tequilarista.org</ulink>.
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
Landfill</ulink>, which you are welcome to play with.
However, it does not necessarily have all Bugzilla features
enabled, and often runs cutting-edge versions of Bugzilla for
testing, so some things may work slightly differently than
mentioned here.
</para>
@ -207,21 +164,16 @@ system against which all others are measured.
If you want to use Bugzilla, first you
need to create an account. Consult with the administrator
responsible for your installation of Bugzilla for the URL you
should use to access it. If you're test-driving the end-user
Bugzilla experience, use this URL: <ulink
should use to access it. If you're test-driving Bugzilla,
use this URL: <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink>
</para>
<orderedlist>
<listitem>
<para>
Click the "Open a new Bugzilla account" link.
</para>
</listitem>
<listitem>
<para>
Enter your "E-mail address" and "Real Name" (or whatever
name you want to call yourself) in the spaces provided,
then select the "Create Account" button.
Click the <quote>Open a new Bugzilla account</quote> link, enter your
email address and, optionally, your name in the spaces provided,
then click <quote>Create Account</quote>.
</para>
</listitem>
<listitem>
@ -230,308 +182,289 @@ system against which all others are measured.
you provided above, which contains your login name
(generally the same as the email address), and a password
you can use to access your account. This password is
randomly generated, and should be changed at your nearest
opportunity (we'll go into how to do it later).
randomly generated, and can be changed to something more memorable.
</para>
</listitem>
<listitem>
<para>
Click the <quote>Log In</quote> link in the yellow area at
the bottom of the page in your browser, then enter your
<quote>E-mail address</quote> and <quote>Password</quote>
you just received into the spaces provided, and select
the bottom of the page in your browser, enter your
email address and password into the spaces provided, and click
<quote>Login</quote>.
<note>
<para>
If you ever forget your password, you can come back to
this page, enter your <quote>E-mail address</quote>,
then select the <quote>E-mail me a password</quote>
button to have your password mailed to you again so
that you can login.
</para>
</note>
</para>
</listitem>
</orderedlist>
<para>
Congratulations! If you followed these directions, you now
are the proud owner of a user account on
landfill.tequilarista.org (Landfill) or your local Bugzilla
install. You should now see in your browser a page called the
<quote>Bugzilla Query Page</quote>. It may look daunting, but with this
Guide to walk you through it, you will master it in no time.
You are now logged in. Bugzilla uses cookies for authentication, so
(unless your IP address changes) you should not have to log in again.
</para>
</section>
<section id="query">
<title>The Bugzilla Query Page</title>
<section id="bug_page">
<title>Anatomy of a Bug</title>
<para>
The Bugzilla Query Page is the heart and soul of the Bugzilla
user experience. It is the master interface where you can
find any bug report, comment, or patch currently in the
Bugzilla system. We'll go into how to create your own bug
report later on.
The core of Bugzilla is the screen which displays a particular bug.
It's a good place to explain some Bugzilla concepts.
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/show_bug.cgi?id=1">Bug 1 on Landfill</ulink> is a good example. Note that the names of most fields
are hyperlinks; clicking them will take you to context-sensitive
help on that particular field.
</para>
<para>
At this point, let's visit the query page.
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi">
landfill.tequilarista.org/bugzilla-tip/query.cgi</ulink>
</para>
<para>
The first thing you need to notice about the Bugzilla Query
Page is that nearly every box you see on your screen has a
hyperlink nearby, explaining what it is or what it does. Near
the upper-left-hand corner of your browser window you should
see the word <quote>Status</quote> underlined. Select it.
</para>
<para>
Notice the page that popped up? Every underlined word you see
on your screen is a hyperlink that will take you to
context-sensitive help. Click around for a while, and learn
what everything here does. To return to the query interface
after pulling up a help page, use the <quote>Back</quote>
button in your browser.
</para>
<para>
I'm sure that after checking out the online help, you are now
an expert on the Bugzilla Query Page. If, however, you feel
you haven't mastered it yet, let me walk you through making a
few successful queries to find out what there are in the
Bugzilla bug-tracking system itself.
</para>
<orderedlist>
<listitem>
<para>
Ensure you are back on the <quote>Bugzilla Query
Page</quote>. Do nothing in the boxes marked "Status",
"Resolution", "Platform", "OpSys", "Priority", or
"Severity". The default query for "Status" is to find all
bugs that are NEW, ASSIGNED, or REOPENED, which is what we
want. If you don't select anything in the other 5
scrollboxes there, then you are saying that "any of these
are OK"; we're not locking ourselves into only finding
bugs on the "DEC" Platform, or "Windows 95" OpSys
(Operating System). You're smart, I think you have it
figured out.
</para>
<para>
Basically, selecting <emphasis>anything</emphasis> on the
query page narrows your search down. Leaving stuff
unselected, or text boxes unfilled, broadens your search.
</para>
</listitem>
<listitem>
<para>
You see the box immediately below the top six boxes that
contains an "Email" text box, with the words "matching
as", a drop-down selection box, then some checkboxes with
"Assigned To" checked by default? This allows you to
filter your search down based upon email address. Let's
put my email address in there, and see what happens.
</para>
<para>
Type "barnboy@trilobyte.net" in the top Email text box.
</para>
</listitem>
<listitem>
<para>
Let's narrow the search some more. Scroll down until you
find the box with the word "Program" over the top of it.
This is where we can narrow our search down to only
specific products (software programs or product lines) in
our Bugzilla database. Please notice the box is a
<emphasis>scrollbox</emphasis>. Using the down arrow on
the scrollbox, scroll down until you can see an entry
called "Bugzilla". Select this entry.
</para>
</listitem>
<listitem>
<para>
Did you notice that some of the boxes to the right changed
when you selected "Bugzilla"? Every Program (or Product)
has different Versions, Components, and Target Milestones
associated with it. A "Version" is the number of a
software program.
<example>
<title>Some Famous Software Versions</title>
<informalexample>
<orderedlist>
<listitem>
<para>
Do you remember the hype in 1995 when Microsoft
Windows 95(r) was released? It may have been several
years ago, but Microsoft(tm) spent over $300 Million
advertising this new Version of their software.
Three years later, they released Microsoft Windows
98(r), another new version, to great fanfare, and
then in 2000 quietly released Microsoft Windows
ME(Millenium Edition)(r).
</para>
<para>
Software "Versions" help a manufacturer
differentiate their current product from their
previous products. Most do not identify their
products by the year they were released. Instead,
the "original" version of their software will often
be numbered "1.0", with small bug-fix releases on
subsequent tenths of a digit. In most cases, it's
not a decimal number; for instance, often 1.9 is an
<emphasis>older</emphasis> version of the software
than 1.11, but is a <emphasis>newer</emphasis>
version than 1.1.1.
</para>
<para>
In general, a "Version" in Bugzilla should refer to
<emphasis>released</emphasis> products, not products
that have not yet been released to the public.
Forthcoming products are what the Target Milestone
field is for.
</para>
</informalexample>
</example>
</para>
<para>
A "Component" is a piece of a Product.
It may be a standalone program, or some other logical
division of a Product or Program.
Normally, a Component has a single Owner, who is responsible
for overseeing efforts to improve that Component.
<example>
<title>Mozilla's Bugzilla Components</title>
<informalexample>
<para>
Mozilla's "Bugzilla" Product is composed of several pieces (Components):
<emphasis>Product and Component</emphasis>:
Bugs are divided up by Product and Component, with a Product having one
or more Components in it. For example, bugzilla.mozilla.org's
"Bugzilla" Product is composed of several Components:
<simplelist>
<member><emphasis>Administration</emphasis>,
Administration of a bugzilla installation, including
<filename>editcomponents.cgi</filename>,
<filename>editgroups.cgi</filename>,
<filename>editkeywords.cgi</filename>,
<filename>editparams.cgi</filename>,
<filename>editproducts.cgi</filename>,
<filename>editusers.cgi</filename>,
<filename>editversions.cgi,</filename> and
<filename>sanitycheck.cgi</filename>.
</member>
<member><emphasis>Bugzilla-General</emphasis>,
Anything that doesn't fit in the other components, or spans
multiple components.
</member>
<member><emphasis>Creating/Changing Bugs</emphasis>,
Creating, changing, and viewing bugs.
<filename>enter_bug.cgi</filename>,
<filename>post_bug.cgi</filename>,
<filename>show_bug.cgi</filename> and
<filename>process_bug.cgi</filename>.
</member>
<member><emphasis>Documentation</emphasis>,
The bugzilla documentation, including anything in the
<filename>docs/</filename> directory and The Bugzilla Guide
(This document :)
</member>
<member><emphasis>Email</emphasis>,
Anything to do with email sent by Bugzilla.
<filename>processmail</filename>
</member>
<member><emphasis>Installation</emphasis>,
The installation process of Bugzilla. This includes
<filename>checksetup.pl</filename> and whatever else it evolves into.
</member>
<member><emphasis>Query/Buglist</emphasis>,
Anything to do with searching for bugs and viewing the buglists.
<filename>query.cgi</filename> and
<filename>buglist.cgi</filename>
</member>
<member><emphasis>Reporting/Charting</emphasis>,
Getting reports from Bugzilla.
<filename>reports.cgi</filename> and
<filename>duplicates.cgi</filename>
</member>
<member><emphasis>User Accounts</emphasis>,
Anything about managing a user account from the user's perspective.
<filename>userprefs.cgi</filename>, saved queries, creating accounts,
changing passwords, logging in, etc.
</member>
<member><emphasis>User Interface</emphasis>,
General issues having to do with the user interface cosmetics (not
functionality) including cosmetic issues, HTML templates, etc.
</member>
<member><emphasis>Administration</emphasis>,
Administration of a bugzilla installation, including
<filename>editcomponents.cgi</filename>,
<filename>editgroups.cgi</filename>,
<filename>editkeywords.cgi</filename>,
<filename>editparams.cgi</filename>,
<filename>editproducts.cgi</filename>,
<filename>editusers.cgi</filename>,
<filename>editversions.cgi,</filename> and
<filename>sanitycheck.cgi</filename>.
</member>
<member><emphasis>Bugzilla-General</emphasis>,
Anything that doesn't fit in the other components, or spans
multiple components.
</member>
<member><emphasis>Creating/Changing Bugs</emphasis>,
Creating, changing, and viewing bugs.
<filename>enter_bug.cgi</filename>,
<filename>post_bug.cgi</filename>,
<filename>show_bug.cgi</filename> and
<filename>process_bug.cgi</filename>.
</member>
<member><emphasis>Documentation</emphasis>,
The bugzilla documentation, including anything in the
<filename>docs/</filename> directory and The Bugzilla Guide
</member>
<member><emphasis>Email</emphasis>,
Anything to do with email sent by Bugzilla.
<filename>processmail</filename>
</member>
<member><emphasis>Installation</emphasis>,
The installation process of Bugzilla. This includes
<filename>checksetup.pl</filename> and whatever else it evolves into.
</member>
<member><emphasis>Query/Buglist</emphasis>,
Anything to do with searching for bugs and viewing the buglists.
<filename>query.cgi</filename> and
<filename>buglist.cgi</filename>
</member>
<member><emphasis>Reporting/Charting</emphasis>,
Getting reports from Bugzilla.
<filename>reports.cgi</filename> and
<filename>duplicates.cgi</filename>
</member>
<member><emphasis>User Accounts</emphasis>,
Anything about managing a user account from the user's perspective.
<filename>userprefs.cgi</filename>, saved queries, creating accounts,
changing passwords, logging in, etc.
</member>
<member><emphasis>User Interface</emphasis>,
General issues having to do with the user interface cosmetics (not
functionality) including cosmetic issues, HTML templates, etc.
</member>
</simplelist>
</para>
</informalexample>
</example>
</para>
</listitem>
<listitem>
<para>
A "Milestone", or "Target Milestone" is a often a planned
future "Version" of a product. In many cases, though,
Milestones simply represent significant dates for a
developer. Having certain features in your Product is
frequently tied to revenue (money) the developer will
receive if the features work by the time she reaches the
Target Milestone. Target Milestones are a great tool to
organize your time. If someone will pay you $100,000 for
incorporating certain features by a certain date, those
features by that Milestone date become a very high
priority. Milestones tend to be highly malleable
creatures, though, that appear to be in reach but are out
of reach by the time the important day arrives.
</para>
<emphasis>Status and Resolution</emphasis>:
A bug passes through several Statuses in its lifetime, and ends up in the
RESOLVED status, with one of a set of Resolutions (e.g. FIXED, INVALID.)
The different possible
values for Status and Resolution on your installation will be documented
in the context-sensitive help for those items.
</para>
</listitem>
<listitem>
<para>
The Bugzilla Project has set up Milestones for future
Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
Target Milestone can just as easily be a specific date,
code name, or weird alphanumeric combination, like "M19".
<emphasis>Assigned To</emphasis>:
The person responsible for fixing the bug.
</para>
</listitem>
</listitem>
<listitem>
<listitem>
<para>
OK, now let's select the "Bugzilla" component from its scrollbox.
<emphasis>URL</emphasis>:
A URL associated with the bug, if any.
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
Skip down the page a bit -- do you see the "submit query" button?
Select it, and let's run
this query!
<emphasis>Summary</emphasis>:
A one-sentence summary of the problem.
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
Congratulations! You've completed your first Query, and
have before you the Bug List of the author of this Guide,
Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
well, you'll have a cryptic "Zarro Boogs Found" message on
your screen. It is just a happy hacker's way of saying
"Zero Bugs Found". However, I am fairly certain I will
always have some bugs assigned to me that aren't done yet,
so you won't often see that message!
<emphasis>Status Whiteboard</emphasis>: (a.k.a. Whiteboard) A
free-form text area for adding short notes and tags to a bug.
</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>
<emphasis>Keywords</emphasis>:
The administrator can define keywords which you can use to tag and
categorise bugs - e.g. The Mozilla Project has keywords like crash
and regression.
</para>
</listitem>
<listitem>
<para>
<emphasis>Platform and OS</emphasis>:
These indicate the computing environment where the bug was found.
</para>
</listitem>
<listitem>
<para>
<emphasis>Version</emphasis>:
The "Version" field is usually used for versions of a product which have
been released, and is set to indicate which versions of a Component
have the particular problem the bug report is about.
</para>
</listitem>
<listitem>
<para>
<emphasis>Priority</emphasis>:
The bug assignee uses this field to prioritise his or her bugs. It's
a good idea not to change this on other people's bugs.
</para>
</listitem>
<listitem>
<para>
<emphasis>Severity</emphasis>:
This indicates how severe the problem is - from blocker ("application
unusable") to trivial ("minor cosmetic issue"). You can also use this
field to indicate whether a bug is an enhancement request.
</para>
</listitem>
<listitem>
<para>
<emphasis>Target</emphasis>:
(a.k.a. Target Milestone) A future version by which the bug is to be
fixed. e.g. The Bugzilla Project's milestones for future
Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are
not restricted to numbers, thought - you can use any text strings,
such as dates.
</para>
</listitem>
<listitem>
<para>
<emphasis>Reporter</emphasis>:
The person who filed the bug.
</para>
</listitem>
<listitem>
<para>
<emphasis>CC list</emphasis>:
A list of people who get mail when the bug changes.
</para>
</listitem>
<listitem>
<para>
<emphasis>Attachments</emphasis>:
You can attach files (e.g. testcases or patches) to bugs. If there are
any attachments, they are listed in this section.
</para>
</listitem>
<listitem>
<para>
<emphasis>Dependencies</emphasis>:
If this bug cannot be fixed unless other bugs are fixed (depends on), or
this bug stops other bugs being fixed (blocks), their numbers are
recorded here.
</para>
</listitem>
<listitem>
<para>
<emphasis>Votes</emphasis>:
Whether this bug has any votes.
</para>
</listitem>
<listitem>
<para>
<emphasis>Additional Comments</emphasis>:
You can add your two cents to the bug discussion here, if you have
something worthwhile to say.
</para>
</listitem>
</orderedlist>
</section>
<section id="query">
<title>Searching for Bugs</title>
<para>
I encourage you to click the bug numbers in the left-hand
column and examine my bugs. Also notice that if you click the
underlined links near the top of this page, they do not take
you to context-sensitive help here, but instead sort the
columns of bugs on the screen! When you need to sort your bugs
by priority, severity, or the people they are assigned to,
this is a tremendous timesaver.
The Bugzilla Search page is is the interface where you can
find any bug report, comment, or patch currently in the
Bugzilla system. You can play with it here:
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi">
landfill.tequilarista.org/bugzilla-tip/query.cgi</ulink>.
</para>
<para>
The Search page has controls for selecting different possible values
for all of the fields in a bug, as described above. Once you've defined
a search, you can either run it, or save it as a Remembered Query, which
can optionally appear in the footer of your pages.
</para>
<para>
Highly advanced querying is done using Boolean Charts, which have their
own <ulink url="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html">context-sensitive help</ulink>.
</para>
</section>
<section id="list">
<title>Bug Lists</title>
<para>
If you run a search, a list of matching bugs will be returned.
The default search is to return all open bugs on the system -
don't try running this search on a Bugzilla installation with
a lot of bugs!
</para>
<para>
A couple more interesting things about the Bug List page:
The format of the list is configurable. For example, it can be
sorted by clicking the column headings. Other useful features
can be accessed using the links at the bottom of the list:
<simplelist>
<member><emphasis>Change Columns</emphasis>: by selecting
this link, you can show all kinds of information in the
Bug List</member>
<member><emphasis>Long Format</emphasis>: this gives you a large page
with a non-editable summary of the fields of each bug.</member>
<member><emphasis>Change Columns</emphasis>: change the bug
attributes which appear in the list.</member>
<member><emphasis>Change several bugs at once</emphasis>: If
you have sufficient rights to change all the bugs shown in
the Bug List, you can mass-modify them. This is a big
time-saver.</member>
<member><emphasis>Send mail to bug owners</emphasis>: If you
have many related bugs, you can request an update from
every person who owns the bugs in the Bug List asking them
the status.</member>
your account is sufficiently empowered, you can make the same
change to all the bugs in the list - for example, changing their
owner.</member>
<member><emphasis>Send mail to bug owners</emphasis>: Sends mail
to the owners of all bugs on the list.</member>
<member><emphasis>Edit this query</emphasis>: If you didn't
get exactly the results you were looking for, you can
return to the Query page through this link and make small
@ -539,172 +472,54 @@ system against which all others are measured.
accurate results.</member>
</simplelist>
</para>
<note>
<para>
There are many more options to the Bugzilla Query Page and
the Bug List than I have shown you. But this should be
enough for you to learn to get around. I encourage you to
check out the <ulink
url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink> to learn about the Anatomy and Life Cycle of a Bug before continuing.
</para>
</note>
</section>
<section id="bugreports">
<title>Creating and Managing Bug Reports</title>
<title>Filing Bugs</title>
<epigraph>
<para>And all this time, I thought we were taking bugs <emphasis>out</emphasis>...</para>
</epigraph>
<section id="bug-writing">
<title>Writing a Great Bug Report</title>
<para>
Before we plunge into writing your first bug report, I
encourage you to read some bug-writing guidelines. If you
are reading this document as part of a Bugzilla CVS checkout
or un-tarred Bugzilla distribution, you should be able to
read them by clicking <ulink
url="../../bugwritinghelp.html">here</ulink>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">http://www.mozilla.org/quality/bug-writing-guidelines.html</ulink>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</para>
<para>
While you are at it, why not learn how to find previously
reported bugs? Mozilla.org has published a great tutorial
on finding duplicate bugs, available at <ulink
url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>.
</para>
<para>
I realize this was a lot to read. However, understanding
the mentality of writing great bug reports will help us on
the next part!
Years of bug writing experience has been distilled for your reading
pleasure into the <ulink url="http://landfill.tequilarista.org/bugzilla-tip/bugwritinghelp.html">
Bug Writing Guidelines</ulink>.
While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</para>
<para>
The procedure for filing a test bug is as follows:
</para>
<orderedlist>
<listitem>
<para>
Go back to <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink> in your browser.
Go to <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/">Landfill</ulink>
in your browser and click
<ulink
url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink>.
</para>
</listitem>
<listitem>
<para>
Select the <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink> link.
</para>
</listitem>
<listitem>
<para>
Select a product.
</para>
</listitem>
<listitem>
<para>
Now you should be at the "Enter Bug" form. The
"reporter" should have been automatically filled out for
you (or else Bugzilla prompted you to Log In again --
you did keep the email with your username and password,
didn't you?).
</para>
</listitem>
<listitem>
<para>
Select a Component in the scrollbox.
Select a product - any one will do.
</para>
</listitem>
<listitem>
<para>
Fill in the fields.
Bugzilla should have made reasonable guesses, based upon
your browser, for the "Platform" and "OS" drop-down
boxes. If those are wrong, change them -- if you're on
an SGI box running IRIX, we want to know!
boxes. If they are wrong, change them.
</para>
</listitem>
<listitem>
<para>
Fill in the "Assigned To" box with the email address you
provided earlier. This way you don't end up sending
copies of your bug to lots of other people, since it's
just a test bug.
Select "Commit" and send in your bug report.
</para>
</listitem>
<listitem>
<para>
Leave the "CC" text box blank. Fill in the "URL" box
with "http://www.mozilla.org".
</para>
</listitem>
<listitem>
<para>
Enter "The Bugzilla Guide" in the Summary text box, and
place any comments you have on this tutorial, or the
Guide in general, into the Description box.
</para>
</listitem>
</orderedlist>
<para>
Voila! Select "Commit" and send in your bug report! Next
we'll look at resolving bugs.
</para>
</section>
<section id="bug-manage">
<title>Managing your Bug Reports</title>
<para>
OK, you should have a link to the bug you just created near
the top of your page. It should say "Bug XXXX posted", with
a link to the right saying "Back to BUG# XXXX". Select this
link.
</para>
<orderedlist>
<listitem>
<para>
Scroll down a bit on the subsequent page, until you see
the "Resolve bug, changing resolution to (dropdown box).
Normally, you would "Accept bug (change status to
ASSIGNED)", fix it, and then resolve. But in this case,
we're going to short-circuit the process because this
wasn't a real bug. Change the dropdown next to "Resolve
Bug" to "INVALID", make sure the radio button is marked
next to "Resolve Bug", then click "Commit".
</para>
</listitem>
<listitem>
<para>
Hey! It said it couldn't take the change in a big red
box! That's right, you must specify a Comment in order
to make this change. Select the "Back" button in your
browser, add a Comment, then try Resolving the bug with
INVALID status again. This time it should work.
</para>
</listitem>
</orderedlist>
<para>
You have now learned the basics of Bugzilla navigation,
entering a bug, and bug maintenance. I encourage you to
explore these features, and see what you can do with them!
We'll spend no more time on individual Bugs or Queries from
this point on, so you are on your own there.
</para>
<para>
But I'll give a few last hints!
</para>
<para>
There is a <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/help.html">CLUE</ulink> on the Query page that will teach you more how to use the form.
</para>
<para>
If you click the hyperlink on the <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/describecomponents.cgi">Component</ulink> box of the Query page, you will be presented a form that will describe what all the components are.
</para>
<para>
Possibly the most powerful feature of the Query page is the
<ulink
url="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html">Boolean Chart</ulink> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
</para>
<para>
Finally, you can build some nifty <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/reports.cgi">Reports</ulink> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
</para>
</section>
</orderedlist>
</section>
</section>

8
webtools/bugzilla/docs/xml/administration.xml
Просмотреть файл

@ -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.

8
webtools/bugzilla/docs/xml/conventions.xml
Просмотреть файл

@ -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>

771
webtools/bugzilla/docs/xml/using.xml
Просмотреть файл

@ -55,54 +55,20 @@ system against which all others are measured.
<para>
Bugzilla has matured immensely, and now boasts many advanced features. These include:
<itemizedlist>
<listitem>
<para>
integrated, product-based granular security schema
</para>
</listitem>
<listitem>
<para>
inter-bug dependencies and dependency graphing
</para>
</listitem>
<listitem>
<para>
advanced reporting capabilities
</para>
</listitem>
<listitem>
<para>
a robust, stable RDBMS back-end
</para>
</listitem>
<listitem>
<para>
extensive configurability
</para>
</listitem>
<listitem>
<para>
a very well-understood and well-thought-out natural bug resolution protocol
</para>
</listitem>
<listitem>
<para>
email, XML, console, and web interfaces
</para>
</listitem>
<listitem>
<para>
available integration with automated software
configuration management systems, including Perforce and
CVS (through the Bugzilla email interface and
checkin/checkout scripts)
</para>
</listitem>
<listitem>
<para>
too many more features to list
</para>
</listitem>
<listitem><para>Powerful searching</para></listitem>
<listitem><para>User-configurable email notifications of bug changes</para></listitem>
<listitem><para>Full change history</para></listitem>
<listitem><para>Inter-bug dependency tracking and graphing</para></listitem>
<listitem><para>Excellent attachment management</para></listitem>
<listitem><para>Integrated, product-based, granular security schema</para></listitem>
<listitem><para>Fully security-audited, and runs under Perl's taint mode</para></listitem>
<listitem><para>A robust, stable RDBMS back-end</para></listitem>
<listitem><para>Web, XML, email and console interfaces</para></listitem>
<listitem><para>Completely customisable and/or localisable web user interface</para></listitem>
<listitem><para>Extensive configurability</para></listitem>
<listitem><para>Smooth upgrade pathway between versions</para></listitem>
</itemizedlist>
</para>
</section>
@ -178,25 +144,16 @@ system against which all others are measured.
</epigraph>
<para>
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
This section contains information for end-users of Bugzilla.
If you are 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.
</para>
<para>
Throughout this portion of the Guide, we will refer to user
account options available at the Bugzilla test installation,
There is a Bugzilla test installation, called
<ulink url="http://landfill.tequilarista.org/">
landfill.tequilarista.org</ulink>.
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
Landfill</ulink>, which you are welcome to play with.
However, it does not necessarily have all Bugzilla features
enabled, and often runs cutting-edge versions of Bugzilla for
testing, so some things may work slightly differently than
mentioned here.
</para>
@ -207,21 +164,16 @@ system against which all others are measured.
If you want to use Bugzilla, first you
need to create an account. Consult with the administrator
responsible for your installation of Bugzilla for the URL you
should use to access it. If you're test-driving the end-user
Bugzilla experience, use this URL: <ulink
should use to access it. If you're test-driving Bugzilla,
use this URL: <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink>
</para>
<orderedlist>
<listitem>
<para>
Click the "Open a new Bugzilla account" link.
</para>
</listitem>
<listitem>
<para>
Enter your "E-mail address" and "Real Name" (or whatever
name you want to call yourself) in the spaces provided,
then select the "Create Account" button.
Click the <quote>Open a new Bugzilla account</quote> link, enter your
email address and, optionally, your name in the spaces provided,
then click <quote>Create Account</quote>.
</para>
</listitem>
<listitem>
@ -230,308 +182,289 @@ system against which all others are measured.
you provided above, which contains your login name
(generally the same as the email address), and a password
you can use to access your account. This password is
randomly generated, and should be changed at your nearest
opportunity (we'll go into how to do it later).
randomly generated, and can be changed to something more memorable.
</para>
</listitem>
<listitem>
<para>
Click the <quote>Log In</quote> link in the yellow area at
the bottom of the page in your browser, then enter your
<quote>E-mail address</quote> and <quote>Password</quote>
you just received into the spaces provided, and select
the bottom of the page in your browser, enter your
email address and password into the spaces provided, and click
<quote>Login</quote>.
<note>
<para>
If you ever forget your password, you can come back to
this page, enter your <quote>E-mail address</quote>,
then select the <quote>E-mail me a password</quote>
button to have your password mailed to you again so
that you can login.
</para>
</note>
</para>
</listitem>
</orderedlist>
<para>
Congratulations! If you followed these directions, you now
are the proud owner of a user account on
landfill.tequilarista.org (Landfill) or your local Bugzilla
install. You should now see in your browser a page called the
<quote>Bugzilla Query Page</quote>. It may look daunting, but with this
Guide to walk you through it, you will master it in no time.
You are now logged in. Bugzilla uses cookies for authentication, so
(unless your IP address changes) you should not have to log in again.
</para>
</section>
<section id="query">
<title>The Bugzilla Query Page</title>
<section id="bug_page">
<title>Anatomy of a Bug</title>
<para>
The Bugzilla Query Page is the heart and soul of the Bugzilla
user experience. It is the master interface where you can
find any bug report, comment, or patch currently in the
Bugzilla system. We'll go into how to create your own bug
report later on.
The core of Bugzilla is the screen which displays a particular bug.
It's a good place to explain some Bugzilla concepts.
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/show_bug.cgi?id=1">Bug 1 on Landfill</ulink> is a good example. Note that the names of most fields
are hyperlinks; clicking them will take you to context-sensitive
help on that particular field.
</para>
<para>
At this point, let's visit the query page.
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi">
landfill.tequilarista.org/bugzilla-tip/query.cgi</ulink>
</para>
<para>
The first thing you need to notice about the Bugzilla Query
Page is that nearly every box you see on your screen has a
hyperlink nearby, explaining what it is or what it does. Near
the upper-left-hand corner of your browser window you should
see the word <quote>Status</quote> underlined. Select it.
</para>
<para>
Notice the page that popped up? Every underlined word you see
on your screen is a hyperlink that will take you to
context-sensitive help. Click around for a while, and learn
what everything here does. To return to the query interface
after pulling up a help page, use the <quote>Back</quote>
button in your browser.
</para>
<para>
I'm sure that after checking out the online help, you are now
an expert on the Bugzilla Query Page. If, however, you feel
you haven't mastered it yet, let me walk you through making a
few successful queries to find out what there are in the
Bugzilla bug-tracking system itself.
</para>
<orderedlist>
<listitem>
<para>
Ensure you are back on the <quote>Bugzilla Query
Page</quote>. Do nothing in the boxes marked "Status",
"Resolution", "Platform", "OpSys", "Priority", or
"Severity". The default query for "Status" is to find all
bugs that are NEW, ASSIGNED, or REOPENED, which is what we
want. If you don't select anything in the other 5
scrollboxes there, then you are saying that "any of these
are OK"; we're not locking ourselves into only finding
bugs on the "DEC" Platform, or "Windows 95" OpSys
(Operating System). You're smart, I think you have it
figured out.
</para>
<para>
Basically, selecting <emphasis>anything</emphasis> on the
query page narrows your search down. Leaving stuff
unselected, or text boxes unfilled, broadens your search.
</para>
</listitem>
<listitem>
<para>
You see the box immediately below the top six boxes that
contains an "Email" text box, with the words "matching
as", a drop-down selection box, then some checkboxes with
"Assigned To" checked by default? This allows you to
filter your search down based upon email address. Let's
put my email address in there, and see what happens.
</para>
<para>
Type "barnboy@trilobyte.net" in the top Email text box.
</para>
</listitem>
<listitem>
<para>
Let's narrow the search some more. Scroll down until you
find the box with the word "Program" over the top of it.
This is where we can narrow our search down to only
specific products (software programs or product lines) in
our Bugzilla database. Please notice the box is a
<emphasis>scrollbox</emphasis>. Using the down arrow on
the scrollbox, scroll down until you can see an entry
called "Bugzilla". Select this entry.
</para>
</listitem>
<listitem>
<para>
Did you notice that some of the boxes to the right changed
when you selected "Bugzilla"? Every Program (or Product)
has different Versions, Components, and Target Milestones
associated with it. A "Version" is the number of a
software program.
<example>
<title>Some Famous Software Versions</title>
<informalexample>
<orderedlist>
<listitem>
<para>
Do you remember the hype in 1995 when Microsoft
Windows 95(r) was released? It may have been several
years ago, but Microsoft(tm) spent over $300 Million
advertising this new Version of their software.
Three years later, they released Microsoft Windows
98(r), another new version, to great fanfare, and
then in 2000 quietly released Microsoft Windows
ME(Millenium Edition)(r).
</para>
<para>
Software "Versions" help a manufacturer
differentiate their current product from their
previous products. Most do not identify their
products by the year they were released. Instead,
the "original" version of their software will often
be numbered "1.0", with small bug-fix releases on
subsequent tenths of a digit. In most cases, it's
not a decimal number; for instance, often 1.9 is an
<emphasis>older</emphasis> version of the software
than 1.11, but is a <emphasis>newer</emphasis>
version than 1.1.1.
</para>
<para>
In general, a "Version" in Bugzilla should refer to
<emphasis>released</emphasis> products, not products
that have not yet been released to the public.
Forthcoming products are what the Target Milestone
field is for.
</para>
</informalexample>
</example>
</para>
<para>
A "Component" is a piece of a Product.
It may be a standalone program, or some other logical
division of a Product or Program.
Normally, a Component has a single Owner, who is responsible
for overseeing efforts to improve that Component.
<example>
<title>Mozilla's Bugzilla Components</title>
<informalexample>
<para>
Mozilla's "Bugzilla" Product is composed of several pieces (Components):
<emphasis>Product and Component</emphasis>:
Bugs are divided up by Product and Component, with a Product having one
or more Components in it. For example, bugzilla.mozilla.org's
"Bugzilla" Product is composed of several Components:
<simplelist>
<member><emphasis>Administration</emphasis>,
Administration of a bugzilla installation, including
<filename>editcomponents.cgi</filename>,
<filename>editgroups.cgi</filename>,
<filename>editkeywords.cgi</filename>,
<filename>editparams.cgi</filename>,
<filename>editproducts.cgi</filename>,
<filename>editusers.cgi</filename>,
<filename>editversions.cgi,</filename> and
<filename>sanitycheck.cgi</filename>.
</member>
<member><emphasis>Bugzilla-General</emphasis>,
Anything that doesn't fit in the other components, or spans
multiple components.
</member>
<member><emphasis>Creating/Changing Bugs</emphasis>,
Creating, changing, and viewing bugs.
<filename>enter_bug.cgi</filename>,
<filename>post_bug.cgi</filename>,
<filename>show_bug.cgi</filename> and
<filename>process_bug.cgi</filename>.
</member>
<member><emphasis>Documentation</emphasis>,
The bugzilla documentation, including anything in the
<filename>docs/</filename> directory and The Bugzilla Guide
(This document :)
</member>
<member><emphasis>Email</emphasis>,
Anything to do with email sent by Bugzilla.
<filename>processmail</filename>
</member>
<member><emphasis>Installation</emphasis>,
The installation process of Bugzilla. This includes
<filename>checksetup.pl</filename> and whatever else it evolves into.
</member>
<member><emphasis>Query/Buglist</emphasis>,
Anything to do with searching for bugs and viewing the buglists.
<filename>query.cgi</filename> and
<filename>buglist.cgi</filename>
</member>
<member><emphasis>Reporting/Charting</emphasis>,
Getting reports from Bugzilla.
<filename>reports.cgi</filename> and
<filename>duplicates.cgi</filename>
</member>
<member><emphasis>User Accounts</emphasis>,
Anything about managing a user account from the user's perspective.
<filename>userprefs.cgi</filename>, saved queries, creating accounts,
changing passwords, logging in, etc.
</member>
<member><emphasis>User Interface</emphasis>,
General issues having to do with the user interface cosmetics (not
functionality) including cosmetic issues, HTML templates, etc.
</member>
<member><emphasis>Administration</emphasis>,
Administration of a bugzilla installation, including
<filename>editcomponents.cgi</filename>,
<filename>editgroups.cgi</filename>,
<filename>editkeywords.cgi</filename>,
<filename>editparams.cgi</filename>,
<filename>editproducts.cgi</filename>,
<filename>editusers.cgi</filename>,
<filename>editversions.cgi,</filename> and
<filename>sanitycheck.cgi</filename>.
</member>
<member><emphasis>Bugzilla-General</emphasis>,
Anything that doesn't fit in the other components, or spans
multiple components.
</member>
<member><emphasis>Creating/Changing Bugs</emphasis>,
Creating, changing, and viewing bugs.
<filename>enter_bug.cgi</filename>,
<filename>post_bug.cgi</filename>,
<filename>show_bug.cgi</filename> and
<filename>process_bug.cgi</filename>.
</member>
<member><emphasis>Documentation</emphasis>,
The bugzilla documentation, including anything in the
<filename>docs/</filename> directory and The Bugzilla Guide
</member>
<member><emphasis>Email</emphasis>,
Anything to do with email sent by Bugzilla.
<filename>processmail</filename>
</member>
<member><emphasis>Installation</emphasis>,
The installation process of Bugzilla. This includes
<filename>checksetup.pl</filename> and whatever else it evolves into.
</member>
<member><emphasis>Query/Buglist</emphasis>,
Anything to do with searching for bugs and viewing the buglists.
<filename>query.cgi</filename> and
<filename>buglist.cgi</filename>
</member>
<member><emphasis>Reporting/Charting</emphasis>,
Getting reports from Bugzilla.
<filename>reports.cgi</filename> and
<filename>duplicates.cgi</filename>
</member>
<member><emphasis>User Accounts</emphasis>,
Anything about managing a user account from the user's perspective.
<filename>userprefs.cgi</filename>, saved queries, creating accounts,
changing passwords, logging in, etc.
</member>
<member><emphasis>User Interface</emphasis>,
General issues having to do with the user interface cosmetics (not
functionality) including cosmetic issues, HTML templates, etc.
</member>
</simplelist>
</para>
</informalexample>
</example>
</para>
</listitem>
<listitem>
<para>
A "Milestone", or "Target Milestone" is a often a planned
future "Version" of a product. In many cases, though,
Milestones simply represent significant dates for a
developer. Having certain features in your Product is
frequently tied to revenue (money) the developer will
receive if the features work by the time she reaches the
Target Milestone. Target Milestones are a great tool to
organize your time. If someone will pay you $100,000 for
incorporating certain features by a certain date, those
features by that Milestone date become a very high
priority. Milestones tend to be highly malleable
creatures, though, that appear to be in reach but are out
of reach by the time the important day arrives.
</para>
<emphasis>Status and Resolution</emphasis>:
A bug passes through several Statuses in its lifetime, and ends up in the
RESOLVED status, with one of a set of Resolutions (e.g. FIXED, INVALID.)
The different possible
values for Status and Resolution on your installation will be documented
in the context-sensitive help for those items.
</para>
</listitem>
<listitem>
<para>
The Bugzilla Project has set up Milestones for future
Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
Target Milestone can just as easily be a specific date,
code name, or weird alphanumeric combination, like "M19".
<emphasis>Assigned To</emphasis>:
The person responsible for fixing the bug.
</para>
</listitem>
</listitem>
<listitem>
<listitem>
<para>
OK, now let's select the "Bugzilla" component from its scrollbox.
<emphasis>URL</emphasis>:
A URL associated with the bug, if any.
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
Skip down the page a bit -- do you see the "submit query" button?
Select it, and let's run
this query!
<emphasis>Summary</emphasis>:
A one-sentence summary of the problem.
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
Congratulations! You've completed your first Query, and
have before you the Bug List of the author of this Guide,
Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
well, you'll have a cryptic "Zarro Boogs Found" message on
your screen. It is just a happy hacker's way of saying
"Zero Bugs Found". However, I am fairly certain I will
always have some bugs assigned to me that aren't done yet,
so you won't often see that message!
<emphasis>Status Whiteboard</emphasis>: (a.k.a. Whiteboard) A
free-form text area for adding short notes and tags to a bug.
</para>
</listitem>
</orderedlist>
</listitem>
<listitem>
<para>
<emphasis>Keywords</emphasis>:
The administrator can define keywords which you can use to tag and
categorise bugs - e.g. The Mozilla Project has keywords like crash
and regression.
</para>
</listitem>
<listitem>
<para>
<emphasis>Platform and OS</emphasis>:
These indicate the computing environment where the bug was found.
</para>
</listitem>
<listitem>
<para>
<emphasis>Version</emphasis>:
The "Version" field is usually used for versions of a product which have
been released, and is set to indicate which versions of a Component
have the particular problem the bug report is about.
</para>
</listitem>
<listitem>
<para>
<emphasis>Priority</emphasis>:
The bug assignee uses this field to prioritise his or her bugs. It's
a good idea not to change this on other people's bugs.
</para>
</listitem>
<listitem>
<para>
<emphasis>Severity</emphasis>:
This indicates how severe the problem is - from blocker ("application
unusable") to trivial ("minor cosmetic issue"). You can also use this
field to indicate whether a bug is an enhancement request.
</para>
</listitem>
<listitem>
<para>
<emphasis>Target</emphasis>:
(a.k.a. Target Milestone) A future version by which the bug is to be
fixed. e.g. The Bugzilla Project's milestones for future
Bugzilla versions are 2.18, 2.20, 3.0, etc. Milestones are
not restricted to numbers, thought - you can use any text strings,
such as dates.
</para>
</listitem>
<listitem>
<para>
<emphasis>Reporter</emphasis>:
The person who filed the bug.
</para>
</listitem>
<listitem>
<para>
<emphasis>CC list</emphasis>:
A list of people who get mail when the bug changes.
</para>
</listitem>
<listitem>
<para>
<emphasis>Attachments</emphasis>:
You can attach files (e.g. testcases or patches) to bugs. If there are
any attachments, they are listed in this section.
</para>
</listitem>
<listitem>
<para>
<emphasis>Dependencies</emphasis>:
If this bug cannot be fixed unless other bugs are fixed (depends on), or
this bug stops other bugs being fixed (blocks), their numbers are
recorded here.
</para>
</listitem>
<listitem>
<para>
<emphasis>Votes</emphasis>:
Whether this bug has any votes.
</para>
</listitem>
<listitem>
<para>
<emphasis>Additional Comments</emphasis>:
You can add your two cents to the bug discussion here, if you have
something worthwhile to say.
</para>
</listitem>
</orderedlist>
</section>
<section id="query">
<title>Searching for Bugs</title>
<para>
I encourage you to click the bug numbers in the left-hand
column and examine my bugs. Also notice that if you click the
underlined links near the top of this page, they do not take
you to context-sensitive help here, but instead sort the
columns of bugs on the screen! When you need to sort your bugs
by priority, severity, or the people they are assigned to,
this is a tremendous timesaver.
The Bugzilla Search page is is the interface where you can
find any bug report, comment, or patch currently in the
Bugzilla system. You can play with it here:
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi">
landfill.tequilarista.org/bugzilla-tip/query.cgi</ulink>.
</para>
<para>
The Search page has controls for selecting different possible values
for all of the fields in a bug, as described above. Once you've defined
a search, you can either run it, or save it as a Remembered Query, which
can optionally appear in the footer of your pages.
</para>
<para>
Highly advanced querying is done using Boolean Charts, which have their
own <ulink url="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html">context-sensitive help</ulink>.
</para>
</section>
<section id="list">
<title>Bug Lists</title>
<para>
If you run a search, a list of matching bugs will be returned.
The default search is to return all open bugs on the system -
don't try running this search on a Bugzilla installation with
a lot of bugs!
</para>
<para>
A couple more interesting things about the Bug List page:
The format of the list is configurable. For example, it can be
sorted by clicking the column headings. Other useful features
can be accessed using the links at the bottom of the list:
<simplelist>
<member><emphasis>Change Columns</emphasis>: by selecting
this link, you can show all kinds of information in the
Bug List</member>
<member><emphasis>Long Format</emphasis>: this gives you a large page
with a non-editable summary of the fields of each bug.</member>
<member><emphasis>Change Columns</emphasis>: change the bug
attributes which appear in the list.</member>
<member><emphasis>Change several bugs at once</emphasis>: If
you have sufficient rights to change all the bugs shown in
the Bug List, you can mass-modify them. This is a big
time-saver.</member>
<member><emphasis>Send mail to bug owners</emphasis>: If you
have many related bugs, you can request an update from
every person who owns the bugs in the Bug List asking them
the status.</member>
your account is sufficiently empowered, you can make the same
change to all the bugs in the list - for example, changing their
owner.</member>
<member><emphasis>Send mail to bug owners</emphasis>: Sends mail
to the owners of all bugs on the list.</member>
<member><emphasis>Edit this query</emphasis>: If you didn't
get exactly the results you were looking for, you can
return to the Query page through this link and make small
@ -539,172 +472,54 @@ system against which all others are measured.
accurate results.</member>
</simplelist>
</para>
<note>
<para>
There are many more options to the Bugzilla Query Page and
the Bug List than I have shown you. But this should be
enough for you to learn to get around. I encourage you to
check out the <ulink
url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink> to learn about the Anatomy and Life Cycle of a Bug before continuing.
</para>
</note>
</section>
<section id="bugreports">
<title>Creating and Managing Bug Reports</title>
<title>Filing Bugs</title>
<epigraph>
<para>And all this time, I thought we were taking bugs <emphasis>out</emphasis>...</para>
</epigraph>
<section id="bug-writing">
<title>Writing a Great Bug Report</title>
<para>
Before we plunge into writing your first bug report, I
encourage you to read some bug-writing guidelines. If you
are reading this document as part of a Bugzilla CVS checkout
or un-tarred Bugzilla distribution, you should be able to
read them by clicking <ulink
url="../../bugwritinghelp.html">here</ulink>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">http://www.mozilla.org/quality/bug-writing-guidelines.html</ulink>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</para>
<para>
While you are at it, why not learn how to find previously
reported bugs? Mozilla.org has published a great tutorial
on finding duplicate bugs, available at <ulink
url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>.
</para>
<para>
I realize this was a lot to read. However, understanding
the mentality of writing great bug reports will help us on
the next part!
Years of bug writing experience has been distilled for your reading
pleasure into the <ulink url="http://landfill.tequilarista.org/bugzilla-tip/bugwritinghelp.html">
Bug Writing Guidelines</ulink>.
While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</para>
<para>
The procedure for filing a test bug is as follows:
</para>
<orderedlist>
<listitem>
<para>
Go back to <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink> in your browser.
Go to <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/">Landfill</ulink>
in your browser and click
<ulink
url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink>.
</para>
</listitem>
<listitem>
<para>
Select the <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink> link.
</para>
</listitem>
<listitem>
<para>
Select a product.
</para>
</listitem>
<listitem>
<para>
Now you should be at the "Enter Bug" form. The
"reporter" should have been automatically filled out for
you (or else Bugzilla prompted you to Log In again --
you did keep the email with your username and password,
didn't you?).
</para>
</listitem>
<listitem>
<para>
Select a Component in the scrollbox.
Select a product - any one will do.
</para>
</listitem>
<listitem>
<para>
Fill in the fields.
Bugzilla should have made reasonable guesses, based upon
your browser, for the "Platform" and "OS" drop-down
boxes. If those are wrong, change them -- if you're on
an SGI box running IRIX, we want to know!
boxes. If they are wrong, change them.
</para>
</listitem>
<listitem>
<para>
Fill in the "Assigned To" box with the email address you
provided earlier. This way you don't end up sending
copies of your bug to lots of other people, since it's
just a test bug.
Select "Commit" and send in your bug report.
</para>
</listitem>
<listitem>
<para>
Leave the "CC" text box blank. Fill in the "URL" box
with "http://www.mozilla.org".
</para>
</listitem>
<listitem>
<para>
Enter "The Bugzilla Guide" in the Summary text box, and
place any comments you have on this tutorial, or the
Guide in general, into the Description box.
</para>
</listitem>
</orderedlist>
<para>
Voila! Select "Commit" and send in your bug report! Next
we'll look at resolving bugs.
</para>
</section>
<section id="bug-manage">
<title>Managing your Bug Reports</title>
<para>
OK, you should have a link to the bug you just created near
the top of your page. It should say "Bug XXXX posted", with
a link to the right saying "Back to BUG# XXXX". Select this
link.
</para>
<orderedlist>
<listitem>
<para>
Scroll down a bit on the subsequent page, until you see
the "Resolve bug, changing resolution to (dropdown box).
Normally, you would "Accept bug (change status to
ASSIGNED)", fix it, and then resolve. But in this case,
we're going to short-circuit the process because this
wasn't a real bug. Change the dropdown next to "Resolve
Bug" to "INVALID", make sure the radio button is marked
next to "Resolve Bug", then click "Commit".
</para>
</listitem>
<listitem>
<para>
Hey! It said it couldn't take the change in a big red
box! That's right, you must specify a Comment in order
to make this change. Select the "Back" button in your
browser, add a Comment, then try Resolving the bug with
INVALID status again. This time it should work.
</para>
</listitem>
</orderedlist>
<para>
You have now learned the basics of Bugzilla navigation,
entering a bug, and bug maintenance. I encourage you to
explore these features, and see what you can do with them!
We'll spend no more time on individual Bugs or Queries from
this point on, so you are on your own there.
</para>
<para>
But I'll give a few last hints!
</para>
<para>
There is a <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/help.html">CLUE</ulink> on the Query page that will teach you more how to use the form.
</para>
<para>
If you click the hyperlink on the <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/describecomponents.cgi">Component</ulink> box of the Query page, you will be presented a form that will describe what all the components are.
</para>
<para>
Possibly the most powerful feature of the Query page is the
<ulink
url="http://landfill.tequilarista.org/bugzilla-tip/booleanchart.html">Boolean Chart</ulink> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
</para>
<para>
Finally, you can build some nifty <ulink
url="http://landfill.tequilarista.org/bugzilla-tip/reports.cgi">Reports</ulink> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
</para>
</section>
</orderedlist>
</section>
</section>