Skip to content

bugzilla
bugzilla
Commit 96a0037a authored by gerv%gerv.net's avatar gerv%gerv.net
Browse files
Options

Another pre-2.17.7 rev.

parent cb5afb1e
Hide whitespace changes
Inline Side-by-side
Showing with 1200 additions and 1334 deletions
docs/html/Bugzilla-Guide.html
View file @ 96a0037a
......@@ -155,46 +155,51 @@ HREF="#using"
><DL
><DT
>3.1. <A
HREF="#using-intro"
>Introduction</A
></DT
><DT
>3.2. <A
HREF="#myaccount"
>Create a Bugzilla Account</A
></DT
><DT
>3.2. <A
>3.3. <A
HREF="#bug_page"
>Anatomy of a Bug</A
></DT
><DT
>3.3. <A
>3.4. <A
HREF="#query"
>Searching for Bugs</A
></DT
><DT
>3.4. <A
>3.5. <A
HREF="#list"
>Bug Lists</A
></DT
><DT
>3.5. <A
>3.6. <A
HREF="#bugreports"
>Filing Bugs</A
></DT
><DT
>3.6. <A
>3.7. <A
HREF="#patchviewer"
>Patch Viewer</A
></DT
><DT
>3.7. <A
>3.8. <A
HREF="#hintsandtips"
>Hints and Tips</A
></DT
><DT
>3.8. <A
>3.9. <A
HREF="#userpreferences"
>User Preferences</A
></DT
><DT
>3.9. <A
>3.10. <A
HREF="#reporting"
>Reports</A
></DT
......@@ -598,25 +603,23 @@ NAME="newversions"
</P
><P
>&#13; The newest version of this guide can always be found at <A
>&#13; The latest version of this guide can always be found at <A
HREF="http://www.bugzilla.org"
TARGET="_top"
>http://www.bugzilla.org</A
>; however, you should read the version
which came with the Bugzilla release you are using.
</P
><P
>&#13; The latest version of this document can always be checked out via CVS.
Please follow the <A
>, or checked out via CVS.
(Please follow the <A
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"
>Mozilla CVS</A
>
instructions and check out the <TT
>Mozilla
CVS</A
> instructions and check out the
<TT
CLASS="filename"
>mozilla/webtools/bugzilla/docs/</TT
>
subtree.
subtree.) However, you should read the version
which came with the Bugzilla release you are using.
</P
><P
>&#13; The Bugzilla Guide is currently only available in English.
......@@ -648,7 +651,7 @@ NAME="credits"
><P
>&#13; Last but not least, all the members of the
<A
HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
TARGET="_top"
>&#13; netscape.public.mozilla.webtools</A
>
......@@ -669,7 +672,7 @@ NAME="conventions"
><DIV
CLASS="informaltable"
><A
NAME="AEN73"
NAME="AEN72"
></A
><P
></P
......@@ -693,7 +696,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Warnings</TD
>Warning</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -767,7 +770,7 @@ VALIGN="TOP"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Notes</TD
>Note</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -841,7 +844,7 @@ VALIGN="TOP"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>File and directory names</TD
>File or directory name</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -855,7 +858,7 @@ CLASS="filename"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Commands to be typed</TD
>Command to be typed</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -869,7 +872,7 @@ CLASS="command"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Applications names</TD
>Application name</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -883,12 +886,7 @@ CLASS="application"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
>
of users command under bash shell</TD
>&#13; Normal user's prompt under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -898,12 +896,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
>
of root users command under bash shell</TD
>&#13; Root user's prompt under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -913,12 +906,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
>
of user command under tcsh shell</TD
>&#13; Normal user's prompt under tcsh shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -1040,23 +1028,15 @@ NAME="why-tracking"
></A
>2.2. Why use a bug-tracking system?</H1
><P
>For many years, defect-tracking software was principally
the domain of large software development houses. Most smaller shops
simply relied on
shared lists and email to monitor the status of defects. This procedure
was error-prone and tended to cause those bugs judged least significant by
developers to be dropped or ignored.</P
>Those who do not use a bug-tracking system tend to rely on
shared lists, email, spreadsheets and/or Post-It notes to monitor the
status of defects. This procedure
is usually error-prone and tends to cause those bugs judged least
significant by developers to be dropped or ignored.</P
><P
>Integrated
defect-tracking systems reduce downtime, increase productivity, and raise
customer satisfaction with their systems. Along with full disclosure, an
open bug-tracker allows you to keep in touch with your clients
and resellers, to communicate about problems effectively throughout the
data management chain. Many corporations have also discovered that
defect-tracking helps reduce costs by providing IT support
accountability, telephone support knowledge bases, and a common,
well-understood method for accounting for unusual system or software
issues.</P
>Integrated defect-tracking systems make sure that nothing gets
swept under the carpet; they provide a method of creating, storing,
arranging and processing defect reports and enhancement requests.</P
></DIV
><DIV
CLASS="section"
......@@ -1067,7 +1047,8 @@ NAME="why-bugzilla"
></A
>2.3. Why use Bugzilla?</H1
><P
>Bugzilla boasts many advanced features. These include:
>Bugzilla is the leading open-source/free software bug tracking
system. It boasts many advanced features, including:
<P
></P
><UL
......@@ -1105,12 +1086,12 @@ NAME="why-bugzilla"
></LI
><LI
><P
>Web, XML, email and console interfaces</P
>Completely customisable and/or localisable web user
interface</P
></LI
><LI
><P
>Completely customisable and/or localisable web user
interface</P
>Additional XML, email and console interfaces</P
></LI
><LI
><P
......@@ -1145,8 +1126,7 @@ HREF="http://www.perforce.com"
TARGET="_top"
>Perforce SCM</A
>, Bugzilla
provides a powerful, easy-to-use solution to configuration management and
replication problems.</P
provides a powerful, easy-to-use configuration management solution.</P
></DIV
></DIV
><DIV
......@@ -1156,18 +1136,27 @@ CLASS="chapter"
NAME="using"
></A
>Chapter 3. Using Bugzilla</H1
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="using-intro"
></A
>3.1. Introduction</H1
><P
>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
<A
There is a Bugzilla test installation, called
<A
HREF="http://landfill.bugzilla.org/bugzilla-tip/"
TARGET="_top"
>Landfill</A
>,
which you are welcome to play with (if it's up.)
However, it does not necessarily
have all Bugzilla features enabled, and runs an up-to-the-minute version,
so some things may not quite work as this document describes.</P
which you are welcome to play with (if it's up.)
However, it does not necessarily
have all Bugzilla features enabled, and runs an up-to-the-minute version,
so some things may not quite work as this document describes.</P
></DIV
><DIV
CLASS="section"
><HR><H1
......@@ -1175,7 +1164,7 @@ CLASS="section"
><A
NAME="myaccount"
></A
>3.1. Create a Bugzilla Account</H1
>3.2. Create a Bugzilla Account</H1
><P
>If you want to use Bugzilla, first you need to create an account.
Consult with the administrator responsible for your installation of
......@@ -1245,7 +1234,7 @@ CLASS="section"
><A
NAME="bug_page"
></A
>3.2. Anatomy of a Bug</H1
>3.3. Anatomy of a Bug</H1
><P
>The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
......@@ -1512,7 +1501,7 @@ CLASS="section"
><A
NAME="query"
></A
>3.3. Searching for Bugs</H1
>3.4. Searching for Bugs</H1
><P
>The Bugzilla Search page is is the interface where you can find
any bug report, comment, or patch currently in the Bugzilla system. You
......@@ -1542,7 +1531,7 @@ CLASS="section"
><A
NAME="list"
></A
>3.4. Bug Lists</H1
>3.5. Bug Lists</H1
><P
>If you run a search, a list of matching bugs will be returned.
</P
......@@ -1567,6 +1556,15 @@ BORDER="0"
><TR
><TD
>&#13; <EM
>CSV:</EM
>
get the buglist as comma-separated values, for import into e.g.
a spreadsheet.</TD
></TR
><TR
><TD
>&#13; <EM
>Change Columns:</EM
>
......@@ -1593,13 +1591,23 @@ BORDER="0"
><TR
><TD
>&#13; <EM
>Edit this query:</EM
>Edit Search:</EM
>
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 revisions
to the query you just made so you get more accurate results.</TD
></TR
><TR
><TD
>&#13; <EM
>Remember Search As:</EM
>
You can give a search a name and remember it; a link will appear
in your page footer giving you quick access to run it again later.
</TD
></TR
></TBODY
></TABLE
><P
......@@ -1614,7 +1622,7 @@ CLASS="section"
><A
NAME="bugreports"
></A
>3.5. Filing Bugs</H1
>3.6. Filing Bugs</H1
><P
>Years of bug writing experience has been distilled for your
reading pleasure into the
......@@ -1666,6 +1674,22 @@ TARGET="_top"
>Select "Commit" and send in your bug report.</P
></LI
></OL
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</P
><P
>&#13; You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</P
><P
>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</P
></DIV
><DIV
CLASS="section"
......@@ -1674,7 +1698,7 @@ CLASS="section"
><A
NAME="patchviewer"
></A
>3.6. Patch Viewer</H1
>3.7. Patch Viewer</H1
><P
>Viewing and reviewing patches in Bugzilla is often difficult due to
lack of context, improper format and the inherent readability issues that
......@@ -1732,7 +1756,7 @@ CLASS="section"
><A
NAME="patchviewer_view"
></A
>3.6.1. Viewing Patches in Patch Viewer</H2
>3.7.1. Viewing Patches in Patch Viewer</H2
><P
>The main way to view a patch in patch viewer is to click on the
"Diff" link next to a patch in the Attachments list on a bug. You may
......@@ -1746,7 +1770,7 @@ CLASS="section"
><A
NAME="patchviewer_diff"
></A
>3.6.2. Seeing the Difference Between Two Patches</H2
>3.7.2. Seeing the Difference Between Two Patches</H2
><P
>To see the difference between two patches, you must first view the
newer patch in Patch Viewer. Then select the older patch from the
......@@ -1761,7 +1785,7 @@ CLASS="section"
><A
NAME="patchviewer_context"
></A
>3.6.3. Getting More Context in a Patch</H2
>3.7.3. Getting More Context in a Patch</H2
><P
>To get more context in a patch, you put a number in the textbox at
the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
......@@ -1777,7 +1801,7 @@ CLASS="section"
><A
NAME="patchviewer_collapse"
></A
>3.6.4. Collapsing and Expanding Sections of a Patch</H2
>3.7.4. Collapsing and Expanding Sections of a Patch</H2
><P
>To view only a certain set of files in a patch (for example, if a
patch is absolutely huge and you want to only review part of it at a
......@@ -1793,7 +1817,7 @@ CLASS="section"
><A
NAME="patchviewer_link"
></A
>3.6.5. Linking to a Section of a Patch</H2
>3.7.5. Linking to a Section of a Patch</H2
><P
>To link to a section of a patch (for example, if you want to be
able to give someone a URL to show them which part you are talking
......@@ -1808,7 +1832,7 @@ CLASS="section"
><A
NAME="patchviewer_bonsai_lxr"
></A
>3.6.6. Going to Bonsai and LXR</H2
>3.7.6. Going to Bonsai and LXR</H2
><P
>To go to Bonsai to get blame for the lines you are interested in,
you can click the "Lines XX-YY" link on the section header you are
......@@ -1826,7 +1850,7 @@ CLASS="section"
><A
NAME="patchviewer_unified_diff"
></A
>3.6.7. Creating a Unified Diff</H2
>3.7.7. Creating a Unified Diff</H2
><P
>If the patch is not in a format that you like, you can turn it
into a unified diff format by clicking the "Raw Unified" link at the top
......@@ -1840,7 +1864,7 @@ CLASS="section"
><A
NAME="hintsandtips"
></A
>3.7. Hints and Tips</H1
>3.8. Hints and Tips</H1
><P
>This section distills some Bugzilla tips and best practices
that have been developed.</P
......@@ -1849,9 +1873,9 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN358"
NAME="AEN363"
></A
>3.7.1. Autolinkification</H2
>3.8.1. Autolinkification</H2
><P
>Bugzilla comments are plain text - so typing &#60;U&#62; will
produce less-than, U, greater-than rather than underlined text.
......@@ -1920,7 +1944,7 @@ CLASS="section"
><A
NAME="quicksearch"
></A
>3.7.2. Quicksearch</H2
>3.8.2. Quicksearch</H2
><P
>Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
......@@ -1953,7 +1977,7 @@ CLASS="section"
><A
NAME="commenting"
></A
>3.7.3. Comments</H2
>3.8.3. Comments</H2
><P
>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
......@@ -1977,7 +2001,7 @@ CLASS="section"
><A
NAME="attachments"
></A
>3.7.4. Attachments</H2
>3.8.4. Attachments</H2
><P
>&#13; Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it doesn't
......@@ -1996,31 +2020,6 @@ NAME="attachments"
out of the bug.
</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN388"
></A
>3.7.5. Filing Bugs</H2
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</P
><P
>&#13; You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</P
><P
>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</P
></DIV
></DIV
><DIV
CLASS="section"
......@@ -2029,7 +2028,7 @@ CLASS="section"
><A
NAME="userpreferences"
></A
>3.8. User Preferences</H1
>3.9. User Preferences</H1
><P
>Once you have logged in, you can customise various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
......@@ -2041,7 +2040,7 @@ CLASS="section"
><A
NAME="accountsettings"
></A
>3.8.1. Account Settings</H2
>3.9.1. Account Settings</H2
><P
>On this tab, you can change your basic account information,
including your password, email address and real name. For security
......@@ -2066,7 +2065,7 @@ CLASS="section"
><A
NAME="emailsettings"
></A
>3.8.2. Email Settings</H2
>3.9.2. Email Settings</H2
><P
>On this tab you can reduce or increase the amount of email sent
you from Bugzilla, opting in our out depending on your relationship to
......@@ -2121,7 +2120,7 @@ CLASS="section"
><A
NAME="permissionsettings"
></A
>3.8.3. Permissions</H2
>3.9.3. Permissions</H2
><P
>This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
......@@ -2136,7 +2135,7 @@ CLASS="section"
><A
NAME="reporting"
></A
>3.9. Reports</H1
>3.10. Reports</H1
><P
><EM
>To be written</EM
......@@ -2170,7 +2169,8 @@ CLASS="productname"
<A
HREF="#os-specific"
>Section 4.4</A
>, so be sure to check out that section before
>, so unless you are on Linux,
be sure to check out that section before
you start your installation.
</P
><DIV
......@@ -2228,7 +2228,8 @@ ALIGN="LEFT"
VALIGN="TOP"
><P
>While installing Bugzilla, it is a good idea to ensure that there
is some kind of firewall between you and the rest of the Internet
is some kind of configurable firewall between you and the rest of the
Internet
as your machine may be insecure for periods during the install. Many
installation steps require an active Internet connection to complete,
but you must take care to ensure that at no point is your machine
......@@ -2240,19 +2241,18 @@ VALIGN="TOP"
><P
>This guide assumes that you already have your operating system
installed, network configured, and have administrative access to the
shell on the machine you are installing Bugzilla onto. It is possible to
install and run Bugzilla without administrative access, but you have to
machine onto which you are installing Bugzilla. It is possible to
install and run Bugzilla itself without administrative access, but you
have to
either make sure all the required software is installed or get somebody
with administrative access to install it for you.
</P
><P
>&#13; You are strongly recommended to make a backup of your system
before installing Bugzilla and at regular intervals thereafter.
before installing Bugzilla (and at regular intervals thereafter :-).
</P
><P
>The listing below is a basic step-by-step list. More information
can be found in the sections below. Minimum versions will be
included in parenthesis where appropriate.
>Here's a basic step-by-step list:
</P
><DIV
CLASS="procedure"
......@@ -2264,7 +2264,7 @@ TYPE="1"
HREF="#install-perl"
>Install Perl</A
>
(5.6)
(5.6.0 or above)
</P
></LI
><LI
......@@ -2273,7 +2273,7 @@ HREF="#install-perl"
HREF="#install-mysql"
>Install MySQL</A
>
(3.23.41)
(3.23.41 or above)
</P
></LI
><LI
......@@ -2320,17 +2320,18 @@ NAME="install-perl"
>4.1.1. Perl</H2
><P
>Any machine that doesn't have Perl on it is a sad machine indeed.
Perl can be got in source form from <A
If your OS doesn't come with it, Perl can be got in source form
from <A
HREF="http://www.perl.com"
TARGET="_top"
>http://www.perl.com</A
>.
There are also binary versions available for many platforms, most of which
are linked to from perl.com.
Although Bugzilla runs with perl 5.6,
Although Bugzilla runs with perl 5.6.0,
it's a good idea to be up to the very latest version
if you can when running Bugzilla. As of this writing, that is Perl
version 5.8.</P
version 5.8.2.</P
></DIV
><DIV
CLASS="section"
......@@ -2341,7 +2342,8 @@ NAME="install-mysql"
></A
>4.1.2. MySQL</H2
><P
>Visit the MySQL homepage at
>If your OS doesn't come with it or provide official packages,
visit the MySQL homepage at
<A
HREF="http://www.mysql.com"
TARGET="_top"
......@@ -2440,7 +2442,7 @@ set-variable = max_allowed_packet=1M
>If you are running Bugzilla and MySQL on the same machine, you may
also wish to utilize the <TT
CLASS="option"
>skip-networking</TT
>--skip-networking</TT
> option as
mentioned in <A
HREF="#security-mysql"
......@@ -2454,7 +2456,7 @@ CLASS="section"
><A
NAME="install-setupdatabase"
></A
>4.1.2.1. Configuring MySQL</H3
>4.1.2.1. Adding a user to MySQL</H3
><P
>This first thing you'll want to do is make sure you've given the
<SPAN
......@@ -2464,7 +2466,8 @@ CLASS="QUOTE"
<A
HREF="#security-mysql"
>Section 4.5.2</A
>. For clarity, these instructions will
>. Then, you need to add a user for
Bugzilla to use. For clarity, these instructions will
assume that your MySQL user for Bugzilla will be <SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
......@@ -2507,14 +2510,14 @@ VALIGN="TOP"
CLASS="QUOTE"
>"bugs"</SPAN
> for both the user and
database name.
database name. Don't use it for the password, though...
</P
></TD
></TR
></TABLE
></DIV
><P
>Next, we use an SQL <B
>We use an SQL <B
CLASS="command"
>GRANT</B
> command to create a
......@@ -2522,8 +2525,7 @@ CLASS="command"
CLASS="QUOTE"
>"bugs_user"</SPAN
>
user, and grant sufficient permissions for checksetup.pl, which we'll
use later, to work its magic. This also restricts the
user. This also restricts the
<SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
......@@ -2593,7 +2595,12 @@ CLASS="computeroutput"
<TT
CLASS="computeroutput"
>CREATE TEMPORARY TABLES</TT
> permissions.
> permissions,
so add them to the list in the
<TT
CLASS="computeroutput"
>GRANT</TT
> command.
</P
></TD
></TR
......@@ -2703,32 +2710,30 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you symlink the bugzilla directory into your Apache's HTML
>If you symlink the bugzilla directory into your Apache's
<TT
CLASS="filename"
>html</TT
>
hierarchy, you may receive
<SPAN
CLASS="errorname"
>Forbidden</SPAN
>
errors unless you add the
<SPAN
CLASS="QUOTE"
>"FollowSymLinks"</SPAN
<TT
CLASS="filename"
>FollowSymLinks</TT
>
directive to the &#60;Directory&#62; entry for the HTML root
in httpd.conf.</P
directive to the <TT
CLASS="filename"
>&#60;Directory&#62;</TT
> entry for
the HTML root directory in httpd.conf.</P
></TD
></TR
></TABLE
></DIV
><P
>Once all the files are in a web accessible directory, make that
directory writable by your webserver's user. This is a temporary step
until you run the post-install
<TT
CLASS="filename"
>checksetup.pl</TT
>
script, which locks down your installation.</P
><DIV
CLASS="caution"
><P
......@@ -2765,6 +2770,166 @@ CLASS="option"
></TR
></TABLE
></DIV
><P
>Once all the files are in a web accessible directory, make that
directory writable by your webserver's user. This is a temporary step
until you run the post-install
<TT
CLASS="filename"
>checksetup.pl</TT
>
script, which locks down your installation.</P
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN522"
></A
>4.1.5. <TT
CLASS="filename"
>checksetup.pl</TT
></H2
><P
>Next, run the magic checksetup.pl script.
This is designed to check whether you have all of the right
Perl modules in the correct
versions, and that Bugzilla is generally set up correctly.
</P
><P
>&#13; Eventually,
it will make sure Bugzilla files and directories have reasonable
permissions, set up the
<TT
CLASS="filename"
>data</TT
>
directory, and create all the MySQL tables. But the first time you
run it, it's highly likely to tell you that you are missing a few
Perl modules. Make a note of which ones they are, and then proceed to
the next section to install them.
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;<TT
CLASS="prompt"
>bash#</TT
> ./checksetup.pl
</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13; The first time you run it with all the correct modules installed,
it will create a file called
<TT
CLASS="filename"
>localconfig</TT
>.</P
><P
>This file contains a variety of settings you may need to tweak
including how Bugzilla should connect to the MySQL database.</P
><P
>The connection settings include:
<P
></P
><OL
TYPE="1"
><LI
><P
>server's host: just use
<SPAN
CLASS="QUOTE"
>"localhost"</SPAN
>
if the MySQL server is local</P
></LI
><LI
><P
>database name:
<SPAN
CLASS="QUOTE"
>"bugs_db"</SPAN
>
if you're following these directions</P
></LI
><LI
><P
>MySQL username:
<SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
>
if you're following these directions</P
></LI
><LI
><P
>Password for the
<SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
>
MySQL account; (<SPAN
CLASS="QUOTE"
>"bugs_password"</SPAN
> above)</P
></LI
></OL
>
</P
><P
>Edit the file to change these. Once you are happy with the
settings, <TT
CLASS="filename"
>su</TT
> to the user
your web server runs as, and re-run
<TT
CLASS="filename"
>checksetup.pl</TT
>. (Note: on some security-conscious
systems, you may need to change the login shell for the webserver
account before you can do this.)
On this second run, it will create the database and an administrator
account for which you will be prompted to provide information.</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
>The checksetup.pl script is designed so that you can run it at
any time without causing harm. You should run it after any upgrade to
Bugzilla.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
......@@ -2773,7 +2938,15 @@ CLASS="section"
><A
NAME="install-perlmodules"
></A
>4.1.5. Perl Modules</H2
>4.1.6. Perl Modules</H2
><P
>Don't be intimidated by this long list of modules. See
<A
HREF="#install-modules-bundle-bugzilla"
>Section 4.1.6.1</A
> for a way of
installing all the ones you need with a single command.
</P
><P
>Perl modules can be found using
<A
......@@ -2789,8 +2962,7 @@ HREF="#gloss-ppm"
CLASS="glossterm"
>PPM</I
></A
> on Win32. The root servers
have a real tendency to bog down, so please use mirrors.
> on Win32.
</P
><P
>Good instuctions can be found for using each of these services on
......@@ -3010,15 +3182,6 @@ HREF="#install-modules-bundle-bugzilla"
><LI
><P
>&#13; <A
HREF="#install-modules-appconfig"
>AppConfig</A
>
(1.52)
</P
></LI
><LI
><P
>&#13; <A
HREF="#install-modules-cgi"
>CGI</A
>
......@@ -3028,15 +3191,6 @@ HREF="#install-modules-cgi"
><LI
><P
>&#13; <A
HREF="#install-modules-data-dumper"
>Data::Dumper</A
>
(any)
</P
></LI
><LI
><P
>&#13; <A
HREF="#install-modules-date-format"
>Date::Format</A
>
......@@ -3178,7 +3332,7 @@ CLASS="section"
><A
NAME="install-modules-bundle-bugzilla"
></A
>4.1.5.1. Bundle::Bugzilla</H3
>4.1.6.1. Bundle::Bugzilla</H3
><P
>If you are running at least perl 5.6.1, you can save yourself a lot
of time by using Bundle::Bugzilla. This bundle contains every module
......@@ -3255,22 +3409,9 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-modules-appconfig"
></A
>4.1.5.2. AppConfig (1.52)</H3
><P
>Dependency for Template Toolkit. We probably don't need to
specifically check for it anymore.
</P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-modules-cgi"
></A
>4.1.5.3. CGI (2.88)</H3
>4.1.6.2. CGI (2.88)</H3
><P
>The CGI module parses form elements and cookies and does many
other usefule things. It come as a part of recent perl distributions, but
......@@ -3301,43 +3442,9 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-modules-data-dumper"
></A
>4.1.5.4. Data::Dumper (any)</H3
><P
>The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
sub-releases of Perl 5.004, but a re-installation just to be sure it's
available won't hurt anything.
</P
><P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/Data-Dumper/"
TARGET="_top"
>http://search.cpan.org/dist/Data-Dumper/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/Data-Dumper.zip"
TARGET="_top"
>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/Data-Dumper.zip</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://www.perldoc.com/perl5.8.0/lib/Data/Dumper.html"
TARGET="_top"
>http://www.perldoc.com/perl5.8.0/lib/Data/Dumper.html</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="install-modules-date-format"
></A
>4.1.5.5. TimeDate modules (2.21)</H3
>4.1.6.3. TimeDate modules (2.21)</H3
><P
>Many of the more common date/time/calendar related Perl modules
have been grouped into a bundle similar to the MySQL modules bundle.
......@@ -3372,7 +3479,7 @@ CLASS="section"
><A
NAME="install-modules-dbi"
></A
>4.1.5.6. DBI (1.32)</H3
>4.1.6.4. DBI (1.32)</H3
><P
>The DBI module is a generic Perl module used the
MySQL-related modules. As long as your Perl installation was done
......@@ -3406,7 +3513,7 @@ CLASS="section"
><A
NAME="install-modules-dbd-mysql"
></A
>4.1.5.7. MySQL-related modules</H3
>4.1.6.5. MySQL-related modules</H3
><P
>The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
......@@ -3451,7 +3558,7 @@ CLASS="section"
><A
NAME="install-file-spec"
></A
>4.1.5.8. File::Spec (0.82)</H3
>4.1.6.6. File::Spec (0.82)</H3
><P
>File::Spec is a perl module that allows file operations, such as
generating full path names, to work cross platform.
......@@ -3483,7 +3590,7 @@ CLASS="section"
><A
NAME="install-modules-file-temp"
></A
>4.1.5.9. File::Temp (any)</H3
>4.1.6.7. File::Temp (any)</H3
><P
>File::Temp is used to generate a temporary filename that is
guaranteed to be unique. It comes as a standard part of perl
......@@ -3515,7 +3622,7 @@ CLASS="section"
><A
NAME="install-modules-template"
></A
>4.1.5.10. Template Toolkit (2.08)</H3
>4.1.6.8. Template Toolkit (2.08)</H3
><P
>When you install Template Toolkit, you'll get asked various
questions about features to enable. The defaults are fine, except
......@@ -3549,7 +3656,7 @@ CLASS="section"
><A
NAME="install-modules-text-wrap"
></A
>4.1.5.11. Text::Wrap (2001.0131)</H3
>4.1.6.9. Text::Wrap (2001.0131)</H3
><P
>Text::Wrap is designed to proved intelligent text wrapping.
</P
......@@ -3575,14 +3682,10 @@ CLASS="section"
><A
NAME="install-modules-gd"
></A
>4.1.5.12. GD (1.20) [optional]</H3
>4.1.6.10. GD (1.20) [optional]</H3
><P
>The GD library was written by Thomas Boutell a long while ago to
programmatically generate images in C. Since then it's become the
defacto standard for programmatic image construction. The Perl bindings
to it found in the GD library are used on millions of web pages to
generate graphs on the fly. That's what Bugzilla will be using it for
so you must install it if you want any of the graphing to work.</P
>You need the GD library if you want any of the graphing to work.
</P
><DIV
CLASS="note"
><P
......@@ -3685,7 +3788,7 @@ CLASS="section"
><A
NAME="install-modules-chart-base"
></A
>4.1.5.13. Chart::Base (0.99c) [optional]</H3
>4.1.6.11. Chart::Base (0.99c) [optional]</H3
><P
>The Chart module provides Bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
......@@ -3714,7 +3817,7 @@ CLASS="section"
><A
NAME="install-modules-xml-parser"
></A
>4.1.5.14. XML::Parser (any) [Optional]</H3
>4.1.6.12. XML::Parser (any) [optional]</H3
><P
>XML::Parser is used by the <TT
CLASS="filename"
......@@ -3749,7 +3852,7 @@ CLASS="section"
><A
NAME="install-modules-gd-graph"
></A
>4.1.5.15. GD::Graph (any) [Optional]</H3
>4.1.6.13. GD::Graph (any) [optional]</H3
><P
>In addition to GD listed above, the reporting interface of Bugzilla
needs to have the GD::Graph module installed.
......@@ -3781,7 +3884,7 @@ CLASS="section"
><A
NAME="install-modules-gd-text-align"
></A
>4.1.5.16. GD::Text::Align (any) [Optional]</H3
>4.1.6.14. GD::Text::Align (any) [optional]</H3
><P
>GD::Text::Align, as the name implies, is used to draw aligned
strings of text. It is needed by the reporting interface.
......@@ -3813,7 +3916,7 @@ CLASS="section"
><A
NAME="install-modules-mime-parser"
></A
>4.1.5.17. MIME::Parser (any) [Optional]</H3
>4.1.6.15. MIME::Parser (any) [optional]</H3
><P
>MIME::Parser is only needed if you want to use the e-mail interface
located in the <TT
......@@ -3848,7 +3951,7 @@ CLASS="section"
><A
NAME="install-modules-patchreader"
></A
>4.1.5.18. PatchReader (0.9.1) [Optional]</H3
>4.1.6.16. PatchReader (0.9.1) [optional]</H3
><P
>PatchReader is only needed if you want to use Patch Viewer, a
Bugzilla feature to format patches in a pretty HTML fashion. There are a
......@@ -3884,154 +3987,15 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN748"
NAME="AEN768"
></A
>4.1.6. <TT
CLASS="filename"
>checksetup.pl</TT
></H2
><P
>Next, run the magic checksetup.pl script.
This is designed to make sure your perl modules are the correct
version and your MySQL database and other
configuration options are consistent with the Bugzilla CGI files.
It will make sure Bugzilla files and directories have reasonable
permissions, set up the
<TT
CLASS="filename"
>data</TT
>
directory, and create all the MySQL tables.
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;<TT
CLASS="prompt"
>bash#</TT
> ./checksetup.pl
</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13; The first time you run it, it will create a file called
<TT
CLASS="filename"
>localconfig</TT
>.</P
><P
>This file contains a variety of settings you may need to tweak
including how Bugzilla should connect to the MySQL database.</P
><P
>The connection settings include:
<P
></P
><OL
TYPE="1"
><LI
><P
>server's host: just use
<SPAN
CLASS="QUOTE"
>"localhost"</SPAN
>
if the MySQL server is local</P
></LI
><LI
><P
>database name:
<SPAN
CLASS="QUOTE"
>"bugs_db"</SPAN
>
if you're following these directions</P
></LI
><LI
><P
>MySQL username:
<SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
>
if you're following these directions</P
></LI
><LI
>4.1.7. Configuring Bugzilla</H2
><P
>Password for the
<SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
>
MySQL account; (<SPAN
CLASS="QUOTE"
>"bugs_password"</SPAN
> above)</P
></LI
></OL
>
>&#13; Once checksetup.pl has run successfully, Bugzilla should start up.
Proceed to the correct URL and log in with the administrator account
you defined in the last checksetup.pl run.
</P
><P
>Once you are happy with the settings,
<TT
CLASS="filename"
>su</TT
> to the user
your web server runs as, and re-run
<TT
CLASS="filename"
>checksetup.pl</TT
>. (Note: on some security-conscious
systems, you may need to change the login shell for the webserver
account before you can do this.)
On this second run, it will create the database and an administrator
account for which you will be prompted to provide information.</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
>The checksetup.pl script is designed so that you can run it at
any time without causing harm. You should run it after any upgrade to
Bugzilla.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN778"
></A
>4.1.7. Configuring Bugzilla</H2
><P
>&#13; You should run through the parameters on the Edit Parameters page
(link in the footer) and set them all to appropriate values.
They key parameters are documented in <A
......@@ -4452,7 +4416,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN852"
NAME="AEN843"
></A
>4.3.1. Dependency Charts</H2
><P
......@@ -4516,7 +4480,7 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN867"
NAME="AEN858"
></A
>4.3.2. Bug Graphs</H2
><P
......@@ -4575,7 +4539,7 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN880"
NAME="AEN871"
></A
>4.3.3. The Whining Cron</H2
><P
......@@ -5091,7 +5055,7 @@ NAME="win32-perlmodules"
>Bugzilla on Windows requires the same perl modules found in
<A
HREF="#install-perlmodules"
>Section 4.1.5</A
>Section 4.1.6</A
>. The main difference is that
windows uses <A
HREF="#gloss-ppm"
......@@ -6290,7 +6254,7 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN1215"
NAME="AEN1206"
></A
>4.6.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
......@@ -6315,7 +6279,7 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN1220"
NAME="AEN1211"
></A
>4.6.2. DBD::Sponge::db prepare failed</H2
><P
......@@ -8247,7 +8211,7 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN1597"
NAME="AEN1588"
></A
>6.1.1. What to Edit</H2
><P
......@@ -8399,7 +8363,7 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN1620"
NAME="AEN1611"
></A
>6.1.2. How To Edit Templates</H2
><DIV
......@@ -8479,7 +8443,7 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN1630"
NAME="AEN1621"
></A
>6.1.3. Template Formats</H2
><P
......@@ -8541,7 +8505,7 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN1643"
NAME="AEN1634"
></A
>6.1.4. Particular Templates</H2
><P
......@@ -9039,7 +9003,7 @@ CLASS="section"
><HR><H2
CLASS="section"
><A
NAME="AEN1719"
NAME="AEN1710"
></A
>6.4.1. Bugzilla Database Basics</H2
><P
......@@ -9153,7 +9117,7 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="AEN1746"
NAME="AEN1737"
></A
>6.4.1.1. Bugzilla Database Tables</H3
><P
......@@ -11428,7 +11392,7 @@ CLASS="answer"
><P
>&#13; Microsoft has some advice on this matter, as well:
<A
NAME="AEN2062"
NAME="AEN2053"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -12049,7 +12013,7 @@ NAME="gfdl"
><P
>Version 1.1, March 2000</P
><A
NAME="AEN2192"
NAME="AEN2183"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -12512,7 +12476,7 @@ NAME="gfdl-howto"
of the License in the document and put the following copyright and
license notices just after the title page:</P
><A
NAME="AEN2282"
NAME="AEN2273"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -12549,7 +12513,7 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="AEN2287"
NAME="AEN2278"
></A
>0-9, high ascii</H1
><DL
......@@ -13413,7 +13377,7 @@ NAME="gloss-zarro"
Terry had the following to say:
</P
><A
NAME="AEN2522"
NAME="AEN2513"
></A
><TABLE
BORDER="0"
......
docs/html/bug_page.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="bug_page"
></A
>3.2. Anatomy of a Bug</H1
>3.3. Anatomy of a Bug</H1
><P
>The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
......
docs/html/bugreports.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="bugreports"
></A
>3.5. Filing Bugs</H1
>3.6. Filing Bugs</H1
><P
>Years of bug writing experience has been distilled for your
reading pleasure into the
......@@ -129,6 +129,22 @@ TARGET="_top"
>Select "Commit" and send in your bug report.</P
></LI
></OL
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</P
><P
>&#13; You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</P
><P
>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/conventions.html
View file @ 96a0037a
......@@ -83,7 +83,7 @@ NAME="conventions"
><DIV
CLASS="informaltable"
><A
NAME="AEN73"
NAME="AEN72"
></A
><P
></P
......@@ -107,7 +107,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Warnings</TD
>Warning</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -181,7 +181,7 @@ VALIGN="TOP"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Notes</TD
>Note</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -255,7 +255,7 @@ VALIGN="TOP"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>File and directory names</TD
>File or directory name</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -269,7 +269,7 @@ CLASS="filename"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Commands to be typed</TD
>Command to be typed</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -283,7 +283,7 @@ CLASS="command"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Applications names</TD
>Application name</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -297,12 +297,7 @@ CLASS="application"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
>
of users command under bash shell</TD
>&#13; Normal user's prompt under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -312,12 +307,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
>
of root users command under bash shell</TD
>&#13; Root user's prompt under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -327,12 +317,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
>
of user command under tcsh shell</TD
>&#13; Normal user's prompt under tcsh shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......
docs/html/credits.html
View file @ 96a0037a
......@@ -90,7 +90,7 @@ NAME="credits"
><P
>&#13; Last but not least, all the members of the
<A
HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
TARGET="_top"
>&#13; netscape.public.mozilla.webtools</A
>
......
docs/html/cust-templates.html
View file @ 96a0037a
......@@ -97,7 +97,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1597"
NAME="AEN1588"
></A
>6.1.1. What to Edit</H2
><P
......@@ -249,7 +249,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1620"
NAME="AEN1611"
></A
>6.1.2. How To Edit Templates</H2
><DIV
......@@ -329,7 +329,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1630"
NAME="AEN1621"
></A
>6.1.3. Template Formats</H2
><P
......@@ -391,7 +391,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1643"
NAME="AEN1634"
></A
>6.1.4. Particular Templates</H2
><P
......
docs/html/customization.html
View file @ 96a0037a
......@@ -90,22 +90,22 @@ HREF="cust-templates.html"
><DL
><DT
>6.1.1. <A
HREF="cust-templates.html#AEN1597"
HREF="cust-templates.html#AEN1588"
>What to Edit</A
></DT
><DT
>6.1.2. <A
HREF="cust-templates.html#AEN1620"
HREF="cust-templates.html#AEN1611"
>How To Edit Templates</A
></DT
><DT
>6.1.3. <A
HREF="cust-templates.html#AEN1630"
HREF="cust-templates.html#AEN1621"
>Template Formats</A
></DT
><DT
>6.1.4. <A
HREF="cust-templates.html#AEN1643"
HREF="cust-templates.html#AEN1634"
>Particular Templates</A
></DT
><DT
......
docs/html/dbdoc.html
View file @ 96a0037a
......@@ -137,7 +137,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1719"
NAME="AEN1710"
></A
>6.4.1. Bugzilla Database Basics</H2
><P
......@@ -251,7 +251,7 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN1746"
NAME="AEN1737"
></A
>6.4.1.1. Bugzilla Database Tables</H3
><P
......
docs/html/extraconfig.html
View file @ 96a0037a
......@@ -83,7 +83,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN852"
NAME="AEN843"
></A
>4.3.1. Dependency Charts</H2
><P
......@@ -147,7 +147,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN867"
NAME="AEN858"
></A
>4.3.2. Bug Graphs</H2
><P
......@@ -206,7 +206,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN880"
NAME="AEN871"
></A
>4.3.3. The Whining Cron</H2
><P
......
docs/html/faq.html
View file @ 96a0037a
......@@ -1974,7 +1974,7 @@ CLASS="answer"
><P
>&#13; Microsoft has some advice on this matter, as well:
<A
NAME="AEN2062"
NAME="AEN2053"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......
docs/html/gfdl-howto.html
View file @ 96a0037a
......@@ -83,7 +83,7 @@ NAME="gfdl-howto"
of the License in the document and put the following copyright and
license notices just after the title page:</P
><A
NAME="AEN2282"
NAME="AEN2273"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......
docs/html/gfdl.html
View file @ 96a0037a
......@@ -146,7 +146,7 @@ HREF="gfdl-howto.html"
><P
>Version 1.1, March 2000</P
><A
NAME="AEN2192"
NAME="AEN2183"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......
docs/html/glossary.html
View file @ 96a0037a
......@@ -72,7 +72,7 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="AEN2287"
NAME="AEN2278"
></A
>0-9, high ascii</H1
><DL
......@@ -936,7 +936,7 @@ NAME="gloss-zarro"
Terry had the following to say:
</P
><A
NAME="AEN2522"
NAME="AEN2513"
></A
><TABLE
BORDER="0"
......
docs/html/hintsandtips.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="hintsandtips"
></A
>3.7. Hints and Tips</H1
>3.8. Hints and Tips</H1
><P
>This section distills some Bugzilla tips and best practices
that have been developed.</P
......@@ -86,9 +86,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN358"
NAME="AEN363"
></A
>3.7.1. Autolinkification</H2
>3.8.1. Autolinkification</H2
><P
>Bugzilla comments are plain text - so typing &#60;U&#62; will
produce less-than, U, greater-than rather than underlined text.
......@@ -157,7 +157,7 @@ CLASS="section"
><A
NAME="quicksearch"
></A
>3.7.2. Quicksearch</H2
>3.8.2. Quicksearch</H2
><P
>Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
......@@ -190,7 +190,7 @@ CLASS="section"
><A
NAME="commenting"
></A
>3.7.3. Comments</H2
>3.8.3. Comments</H2
><P
>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
......@@ -214,7 +214,7 @@ CLASS="section"
><A
NAME="attachments"
></A
>3.7.4. Attachments</H2
>3.8.4. Attachments</H2
><P
>&#13; Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it doesn't
......@@ -233,31 +233,6 @@ NAME="attachments"
out of the bug.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN388"
></A
>3.7.5. Filing Bugs</H2
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</P
><P
>&#13; You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</P
><P
>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/index.html
View file @ 96a0037a
......@@ -158,46 +158,51 @@ HREF="using.html"
><DL
><DT
>3.1. <A
HREF="using-intro.html"
>Introduction</A
></DT
><DT
>3.2. <A
HREF="myaccount.html"
>Create a Bugzilla Account</A
></DT
><DT
>3.2. <A
>3.3. <A
HREF="bug_page.html"
>Anatomy of a Bug</A
></DT
><DT
>3.3. <A
>3.4. <A
HREF="query.html"
>Searching for Bugs</A
></DT
><DT
>3.4. <A
>3.5. <A
HREF="list.html"
>Bug Lists</A
></DT
><DT
>3.5. <A
>3.6. <A
HREF="bugreports.html"
>Filing Bugs</A
></DT
><DT
>3.6. <A
>3.7. <A
HREF="patchviewer.html"
>Patch Viewer</A
></DT
><DT
>3.7. <A
>3.8. <A
HREF="hintsandtips.html"
>Hints and Tips</A
></DT
><DT
>3.8. <A
>3.9. <A
HREF="userpreferences.html"
>User Preferences</A
></DT
><DT
>3.9. <A
>3.10. <A
HREF="reporting.html"
>Reports</A
></DT
......
docs/html/installation.html
View file @ 96a0037a
......@@ -110,20 +110,20 @@ HREF="stepbystep.html#install-bzfiles"
></DT
><DT
>4.1.5. <A
HREF="stepbystep.html#install-perlmodules"
>Perl Modules</A
></DT
><DT
>4.1.6. <A
HREF="stepbystep.html#AEN748"
HREF="stepbystep.html#AEN522"
><TT
CLASS="filename"
>checksetup.pl</TT
></A
></DT
><DT
>4.1.6. <A
HREF="stepbystep.html#install-perlmodules"
>Perl Modules</A
></DT
><DT
>4.1.7. <A
HREF="stepbystep.html#AEN778"
HREF="stepbystep.html#AEN768"
>Configuring Bugzilla</A
></DT
></DL
......@@ -167,17 +167,17 @@ HREF="extraconfig.html"
><DL
><DT
>4.3.1. <A
HREF="extraconfig.html#AEN852"
HREF="extraconfig.html#AEN843"
>Dependency Charts</A
></DT
><DT
>4.3.2. <A
HREF="extraconfig.html#AEN867"
HREF="extraconfig.html#AEN858"
>Bug Graphs</A
></DT
><DT
>4.3.3. <A
HREF="extraconfig.html#AEN880"
HREF="extraconfig.html#AEN871"
>The Whining Cron</A
></DT
><DT
......@@ -276,12 +276,12 @@ HREF="troubleshooting.html"
><DL
><DT
>4.6.1. <A
HREF="troubleshooting.html#AEN1215"
HREF="troubleshooting.html#AEN1206"
>Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
></DT
><DT
>4.6.2. <A
HREF="troubleshooting.html#AEN1220"
HREF="troubleshooting.html#AEN1211"
>DBD::Sponge::db prepare failed</A
></DT
><DT
......
docs/html/list.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="list"
></A
>3.4. Bug Lists</H1
>3.5. Bug Lists</H1
><P
>If you run a search, a list of matching bugs will be returned.
</P
......@@ -102,6 +102,15 @@ BORDER="0"
><TR
><TD
>&#13; <EM
>CSV:</EM
>
get the buglist as comma-separated values, for import into e.g.
a spreadsheet.</TD
></TR
><TR
><TD
>&#13; <EM
>Change Columns:</EM
>
......@@ -128,13 +137,23 @@ BORDER="0"
><TR
><TD
>&#13; <EM
>Edit this query:</EM
>Edit Search:</EM
>
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 revisions
to the query you just made so you get more accurate results.</TD
></TR
><TR
><TD
>&#13; <EM
>Remember Search As:</EM
>
You can give a search a name and remember it; a link will appear
in your page footer giving you quick access to run it again later.
</TD
></TR
></TBODY
></TABLE
><P
......
docs/html/myaccount.html
View file @ 96a0037a
......@@ -14,8 +14,8 @@ REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
REL="PREVIOUS"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
TITLE="Introduction"
HREF="using-intro.html"><LINK
REL="NEXT"
TITLE="Anatomy of a Bug"
HREF="bug_page.html"></HEAD
......@@ -47,7 +47,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="using.html"
HREF="using-intro.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="myaccount"
></A
>3.1. Create a Bugzilla Account</H1
>3.2. Create a Bugzilla Account</H1
><P
>If you want to use Bugzilla, first you need to create an account.
Consult with the administrator responsible for your installation of
......@@ -156,7 +156,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="using.html"
HREF="using-intro.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -184,7 +184,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Using Bugzilla</TD
>Introduction</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/newversions.html
View file @ 96a0037a
......@@ -87,25 +87,23 @@ NAME="newversions"
</P
><P
>&#13; The newest version of this guide can always be found at <A
>&#13; The latest version of this guide can always be found at <A
HREF="http://www.bugzilla.org"
TARGET="_top"
>http://www.bugzilla.org</A
>; however, you should read the version
which came with the Bugzilla release you are using.
</P
><P
>&#13; The latest version of this document can always be checked out via CVS.
Please follow the <A
>, or checked out via CVS.
(Please follow the <A
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"
>Mozilla CVS</A
>
instructions and check out the <TT
>Mozilla
CVS</A
> instructions and check out the
<TT
CLASS="filename"
>mozilla/webtools/bugzilla/docs/</TT
>
subtree.
subtree.) However, you should read the version
which came with the Bugzilla release you are using.
</P
><P
>&#13; The Bugzilla Guide is currently only available in English.
......
docs/html/os-specific.html
View file @ 96a0037a
......@@ -152,7 +152,7 @@ NAME="win32-perlmodules"
>Bugzilla on Windows requires the same perl modules found in
<A
HREF="stepbystep.html#install-perlmodules"
>Section 4.1.5</A
>Section 4.1.6</A
>. The main difference is that
windows uses <A
HREF="glossary.html#gloss-ppm"
......
docs/html/patchviewer.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="patchviewer"
></A
>3.6. Patch Viewer</H1
>3.7. Patch Viewer</H1
><P
>Viewing and reviewing patches in Bugzilla is often difficult due to
lack of context, improper format and the inherent readability issues that
......@@ -135,7 +135,7 @@ CLASS="section"
><A
NAME="patchviewer_view"
></A
>3.6.1. Viewing Patches in Patch Viewer</H2
>3.7.1. Viewing Patches in Patch Viewer</H2
><P
>The main way to view a patch in patch viewer is to click on the
"Diff" link next to a patch in the Attachments list on a bug. You may
......@@ -149,7 +149,7 @@ CLASS="section"
><A
NAME="patchviewer_diff"
></A
>3.6.2. Seeing the Difference Between Two Patches</H2
>3.7.2. Seeing the Difference Between Two Patches</H2
><P
>To see the difference between two patches, you must first view the
newer patch in Patch Viewer. Then select the older patch from the
......@@ -164,7 +164,7 @@ CLASS="section"
><A
NAME="patchviewer_context"
></A
>3.6.3. Getting More Context in a Patch</H2
>3.7.3. Getting More Context in a Patch</H2
><P
>To get more context in a patch, you put a number in the textbox at
the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
......@@ -180,7 +180,7 @@ CLASS="section"
><A
NAME="patchviewer_collapse"
></A
>3.6.4. Collapsing and Expanding Sections of a Patch</H2
>3.7.4. Collapsing and Expanding Sections of a Patch</H2
><P
>To view only a certain set of files in a patch (for example, if a
patch is absolutely huge and you want to only review part of it at a
......@@ -196,7 +196,7 @@ CLASS="section"
><A
NAME="patchviewer_link"
></A
>3.6.5. Linking to a Section of a Patch</H2
>3.7.5. Linking to a Section of a Patch</H2
><P
>To link to a section of a patch (for example, if you want to be
able to give someone a URL to show them which part you are talking
......@@ -211,7 +211,7 @@ CLASS="section"
><A
NAME="patchviewer_bonsai_lxr"
></A
>3.6.6. Going to Bonsai and LXR</H2
>3.7.6. Going to Bonsai and LXR</H2
><P
>To go to Bonsai to get blame for the lines you are interested in,
you can click the "Lines XX-YY" link on the section header you are
......@@ -229,7 +229,7 @@ CLASS="section"
><A
NAME="patchviewer_unified_diff"
></A
>3.6.7. Creating a Unified Diff</H2
>3.7.7. Creating a Unified Diff</H2
><P
>If the patch is not in a format that you like, you can turn it
into a unified diff format by clicking the "Raw Unified" link at the top
......
docs/html/query.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="query"
></A
>3.3. Searching for Bugs</H1
>3.4. Searching for Bugs</H1
><P
>The Bugzilla Search page is is the interface where you can find
any bug report, comment, or patch currently in the Bugzilla system. You
......
docs/html/reporting.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="reporting"
></A
>3.9. Reports</H1
>3.10. Reports</H1
><P
><EM
>To be written</EM
......
docs/html/stepbystep.html
View file @ 96a0037a
......@@ -90,7 +90,8 @@ CLASS="productname"
<A
HREF="os-specific.html"
>Section 4.4</A
>, so be sure to check out that section before
>, so unless you are on Linux,
be sure to check out that section before
you start your installation.
</P
><DIV
......@@ -148,7 +149,8 @@ ALIGN="LEFT"
VALIGN="TOP"
><P
>While installing Bugzilla, it is a good idea to ensure that there
is some kind of firewall between you and the rest of the Internet
is some kind of configurable firewall between you and the rest of the
Internet
as your machine may be insecure for periods during the install. Many
installation steps require an active Internet connection to complete,
but you must take care to ensure that at no point is your machine
......@@ -160,19 +162,18 @@ VALIGN="TOP"
><P
>This guide assumes that you already have your operating system
installed, network configured, and have administrative access to the
shell on the machine you are installing Bugzilla onto. It is possible to
install and run Bugzilla without administrative access, but you have to
machine onto which you are installing Bugzilla. It is possible to
install and run Bugzilla itself without administrative access, but you
have to
either make sure all the required software is installed or get somebody
with administrative access to install it for you.
</P
><P
>&#13; You are strongly recommended to make a backup of your system
before installing Bugzilla and at regular intervals thereafter.
before installing Bugzilla (and at regular intervals thereafter :-).
</P
><P
>The listing below is a basic step-by-step list. More information
can be found in the sections below. Minimum versions will be
included in parenthesis where appropriate.
>Here's a basic step-by-step list:
</P
><DIV
CLASS="procedure"
......@@ -184,7 +185,7 @@ TYPE="1"
HREF="stepbystep.html#install-perl"
>Install Perl</A
>
(5.6)
(5.6.0 or above)
</P
></LI
><LI
......@@ -193,7 +194,7 @@ HREF="stepbystep.html#install-perl"
HREF="stepbystep.html#install-mysql"
>Install MySQL</A
>
(3.23.41)
(3.23.41 or above)
</P
></LI
><LI
......@@ -240,17 +241,18 @@ NAME="install-perl"
>4.1.1. Perl</H2
><P
>Any machine that doesn't have Perl on it is a sad machine indeed.
Perl can be got in source form from <A
If your OS doesn't come with it, Perl can be got in source form
from <A
HREF="http://www.perl.com"
TARGET="_top"
>http://www.perl.com</A
>.
There are also binary versions available for many platforms, most of which
are linked to from perl.com.
Although Bugzilla runs with perl 5.6,
Although Bugzilla runs with perl 5.6.0,
it's a good idea to be up to the very latest version
if you can when running Bugzilla. As of this writing, that is Perl
version 5.8.</P
version 5.8.2.</P
></DIV
><DIV
CLASS="section"
......@@ -261,7 +263,8 @@ NAME="install-mysql"
></A
>4.1.2. MySQL</H2
><P
>Visit the MySQL homepage at
>If your OS doesn't come with it or provide official packages,
visit the MySQL homepage at
<A
HREF="http://www.mysql.com"
TARGET="_top"
......@@ -360,7 +363,7 @@ set-variable = max_allowed_packet=1M
>If you are running Bugzilla and MySQL on the same machine, you may
also wish to utilize the <TT
CLASS="option"
>skip-networking</TT
>--skip-networking</TT
> option as
mentioned in <A
HREF="security.html#security-mysql"
......@@ -374,7 +377,7 @@ CLASS="section"
><A
NAME="install-setupdatabase"
></A
>4.1.2.1. Configuring MySQL</H3
>4.1.2.1. Adding a user to MySQL</H3
><P
>This first thing you'll want to do is make sure you've given the
<SPAN
......@@ -384,7 +387,8 @@ CLASS="QUOTE"
<A
HREF="security.html#security-mysql"
>Section 4.5.2</A
>. For clarity, these instructions will
>. Then, you need to add a user for
Bugzilla to use. For clarity, these instructions will
assume that your MySQL user for Bugzilla will be <SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
......@@ -427,14 +431,14 @@ VALIGN="TOP"
CLASS="QUOTE"
>"bugs"</SPAN
> for both the user and
database name.
database name. Don't use it for the password, though...
</P
></TD
></TR
></TABLE
></DIV
><P
>Next, we use an SQL <B
>We use an SQL <B
CLASS="command"
>GRANT</B
> command to create a
......@@ -442,8 +446,7 @@ CLASS="command"
CLASS="QUOTE"
>"bugs_user"</SPAN
>
user, and grant sufficient permissions for checksetup.pl, which we'll
use later, to work its magic. This also restricts the
user. This also restricts the
<SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
......@@ -513,7 +516,12 @@ CLASS="computeroutput"
<TT
CLASS="computeroutput"
>CREATE TEMPORARY TABLES</TT
> permissions.
> permissions,
so add them to the list in the
<TT
CLASS="computeroutput"
>GRANT</TT
> command.
</P
></TD
></TR
......@@ -623,32 +631,30 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you symlink the bugzilla directory into your Apache's HTML
>If you symlink the bugzilla directory into your Apache's
<TT
CLASS="filename"
>html</TT
>
hierarchy, you may receive
<SPAN
CLASS="errorname"
>Forbidden</SPAN
>
errors unless you add the
<SPAN
CLASS="QUOTE"
>"FollowSymLinks"</SPAN
<TT
CLASS="filename"
>FollowSymLinks</TT
>
directive to the &#60;Directory&#62; entry for the HTML root
in httpd.conf.</P
directive to the <TT
CLASS="filename"
>&#60;Directory&#62;</TT
> entry for
the HTML root directory in httpd.conf.</P
></TD
></TR
></TABLE
></DIV
><P
>Once all the files are in a web accessible directory, make that
directory writable by your webserver's user. This is a temporary step
until you run the post-install
<TT
CLASS="filename"
>checksetup.pl</TT
>
script, which locks down your installation.</P
><DIV
CLASS="caution"
><P
......@@ -685,6 +691,166 @@ CLASS="option"
></TR
></TABLE
></DIV
><P
>Once all the files are in a web accessible directory, make that
directory writable by your webserver's user. This is a temporary step
until you run the post-install
<TT
CLASS="filename"
>checksetup.pl</TT
>
script, which locks down your installation.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN522"
></A
>4.1.5. <TT
CLASS="filename"
>checksetup.pl</TT
></H2
><P
>Next, run the magic checksetup.pl script.
This is designed to check whether you have all of the right
Perl modules in the correct
versions, and that Bugzilla is generally set up correctly.
</P
><P
>&#13; Eventually,
it will make sure Bugzilla files and directories have reasonable
permissions, set up the
<TT
CLASS="filename"
>data</TT
>
directory, and create all the MySQL tables. But the first time you
run it, it's highly likely to tell you that you are missing a few
Perl modules. Make a note of which ones they are, and then proceed to
the next section to install them.
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;<TT
CLASS="prompt"
>bash#</TT
> ./checksetup.pl
</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13; The first time you run it with all the correct modules installed,
it will create a file called
<TT
CLASS="filename"
>localconfig</TT
>.</P
><P
>This file contains a variety of settings you may need to tweak
including how Bugzilla should connect to the MySQL database.</P
><P
>The connection settings include:
<P
></P
><OL
TYPE="1"
><LI
><P
>server's host: just use
<SPAN
CLASS="QUOTE"
>"localhost"</SPAN
>
if the MySQL server is local</P
></LI
><LI
><P
>database name:
<SPAN
CLASS="QUOTE"
>"bugs_db"</SPAN
>
if you're following these directions</P
></LI
><LI
><P
>MySQL username:
<SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
>
if you're following these directions</P
></LI
><LI
><P
>Password for the
<SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
>
MySQL account; (<SPAN
CLASS="QUOTE"
>"bugs_password"</SPAN
> above)</P
></LI
></OL
>
</P
><P
>Edit the file to change these. Once you are happy with the
settings, <TT
CLASS="filename"
>su</TT
> to the user
your web server runs as, and re-run
<TT
CLASS="filename"
>checksetup.pl</TT
>. (Note: on some security-conscious
systems, you may need to change the login shell for the webserver
account before you can do this.)
On this second run, it will create the database and an administrator
account for which you will be prompted to provide information.</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
>The checksetup.pl script is designed so that you can run it at
any time without causing harm. You should run it after any upgrade to
Bugzilla.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
......@@ -693,7 +859,15 @@ CLASS="section"
><A
NAME="install-perlmodules"
></A
>4.1.5. Perl Modules</H2
>4.1.6. Perl Modules</H2
><P
>Don't be intimidated by this long list of modules. See
<A
HREF="stepbystep.html#install-modules-bundle-bugzilla"
>Section 4.1.6.1</A
> for a way of
installing all the ones you need with a single command.
</P
><P
>Perl modules can be found using
<A
......@@ -709,8 +883,7 @@ HREF="glossary.html#gloss-ppm"
CLASS="glossterm"
>PPM</I
></A
> on Win32. The root servers
have a real tendency to bog down, so please use mirrors.
> on Win32.
</P
><P
>Good instuctions can be found for using each of these services on
......@@ -930,15 +1103,6 @@ HREF="stepbystep.html#install-modules-bundle-bugzilla"
><LI
><P
>&#13; <A
HREF="stepbystep.html#install-modules-appconfig"
>AppConfig</A
>
(1.52)
</P
></LI
><LI
><P
>&#13; <A
HREF="stepbystep.html#install-modules-cgi"
>CGI</A
>
......@@ -948,15 +1112,6 @@ HREF="stepbystep.html#install-modules-cgi"
><LI
><P
>&#13; <A
HREF="stepbystep.html#install-modules-data-dumper"
>Data::Dumper</A
>
(any)
</P
></LI
><LI
><P
>&#13; <A
HREF="stepbystep.html#install-modules-date-format"
>Date::Format</A
>
......@@ -1098,7 +1253,7 @@ CLASS="section"
><A
NAME="install-modules-bundle-bugzilla"
></A
>4.1.5.1. Bundle::Bugzilla</H3
>4.1.6.1. Bundle::Bugzilla</H3
><P
>If you are running at least perl 5.6.1, you can save yourself a lot
of time by using Bundle::Bugzilla. This bundle contains every module
......@@ -1175,22 +1330,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="install-modules-appconfig"
></A
>4.1.5.2. AppConfig (1.52)</H3
><P
>Dependency for Template Toolkit. We probably don't need to
specifically check for it anymore.
</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="install-modules-cgi"
></A
>4.1.5.3. CGI (2.88)</H3
>4.1.6.2. CGI (2.88)</H3
><P
>The CGI module parses form elements and cookies and does many
other usefule things. It come as a part of recent perl distributions, but
......@@ -1221,43 +1363,9 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="install-modules-data-dumper"
></A
>4.1.5.4. Data::Dumper (any)</H3
><P
>The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
sub-releases of Perl 5.004, but a re-installation just to be sure it's
available won't hurt anything.
</P
><P
CLASS="literallayout"
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CPAN&nbsp;Download&nbsp;Page:&nbsp;<A
HREF="http://search.cpan.org/dist/Data-Dumper/"
TARGET="_top"
>http://search.cpan.org/dist/Data-Dumper/</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PPM&nbsp;Download&nbsp;Link:&nbsp;<A
HREF="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/Data-Dumper.zip"
TARGET="_top"
>http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/Data-Dumper.zip</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Documentation:&nbsp;<A
HREF="http://www.perldoc.com/perl5.8.0/lib/Data/Dumper.html"
TARGET="_top"
>http://www.perldoc.com/perl5.8.0/lib/Data/Dumper.html</A
><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="install-modules-date-format"
></A
>4.1.5.5. TimeDate modules (2.21)</H3
>4.1.6.3. TimeDate modules (2.21)</H3
><P
>Many of the more common date/time/calendar related Perl modules
have been grouped into a bundle similar to the MySQL modules bundle.
......@@ -1292,7 +1400,7 @@ CLASS="section"
><A
NAME="install-modules-dbi"
></A
>4.1.5.6. DBI (1.32)</H3
>4.1.6.4. DBI (1.32)</H3
><P
>The DBI module is a generic Perl module used the
MySQL-related modules. As long as your Perl installation was done
......@@ -1326,7 +1434,7 @@ CLASS="section"
><A
NAME="install-modules-dbd-mysql"
></A
>4.1.5.7. MySQL-related modules</H3
>4.1.6.5. MySQL-related modules</H3
><P
>The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
......@@ -1371,7 +1479,7 @@ CLASS="section"
><A
NAME="install-file-spec"
></A
>4.1.5.8. File::Spec (0.82)</H3
>4.1.6.6. File::Spec (0.82)</H3
><P
>File::Spec is a perl module that allows file operations, such as
generating full path names, to work cross platform.
......@@ -1403,7 +1511,7 @@ CLASS="section"
><A
NAME="install-modules-file-temp"
></A
>4.1.5.9. File::Temp (any)</H3
>4.1.6.7. File::Temp (any)</H3
><P
>File::Temp is used to generate a temporary filename that is
guaranteed to be unique. It comes as a standard part of perl
......@@ -1435,7 +1543,7 @@ CLASS="section"
><A
NAME="install-modules-template"
></A
>4.1.5.10. Template Toolkit (2.08)</H3
>4.1.6.8. Template Toolkit (2.08)</H3
><P
>When you install Template Toolkit, you'll get asked various
questions about features to enable. The defaults are fine, except
......@@ -1469,7 +1577,7 @@ CLASS="section"
><A
NAME="install-modules-text-wrap"
></A
>4.1.5.11. Text::Wrap (2001.0131)</H3
>4.1.6.9. Text::Wrap (2001.0131)</H3
><P
>Text::Wrap is designed to proved intelligent text wrapping.
</P
......@@ -1495,14 +1603,10 @@ CLASS="section"
><A
NAME="install-modules-gd"
></A
>4.1.5.12. GD (1.20) [optional]</H3
><P
>The GD library was written by Thomas Boutell a long while ago to
programmatically generate images in C. Since then it's become the
defacto standard for programmatic image construction. The Perl bindings
to it found in the GD library are used on millions of web pages to
generate graphs on the fly. That's what Bugzilla will be using it for
so you must install it if you want any of the graphing to work.</P
>4.1.6.10. GD (1.20) [optional]</H3
><P
>You need the GD library if you want any of the graphing to work.
</P
><DIV
CLASS="note"
><P
......@@ -1605,7 +1709,7 @@ CLASS="section"
><A
NAME="install-modules-chart-base"
></A
>4.1.5.13. Chart::Base (0.99c) [optional]</H3
>4.1.6.11. Chart::Base (0.99c) [optional]</H3
><P
>The Chart module provides Bugzilla with on-the-fly charting
abilities. It can be installed in the usual fashion after it has been
......@@ -1634,7 +1738,7 @@ CLASS="section"
><A
NAME="install-modules-xml-parser"
></A
>4.1.5.14. XML::Parser (any) [Optional]</H3
>4.1.6.12. XML::Parser (any) [optional]</H3
><P
>XML::Parser is used by the <TT
CLASS="filename"
......@@ -1669,7 +1773,7 @@ CLASS="section"
><A
NAME="install-modules-gd-graph"
></A
>4.1.5.15. GD::Graph (any) [Optional]</H3
>4.1.6.13. GD::Graph (any) [optional]</H3
><P
>In addition to GD listed above, the reporting interface of Bugzilla
needs to have the GD::Graph module installed.
......@@ -1701,7 +1805,7 @@ CLASS="section"
><A
NAME="install-modules-gd-text-align"
></A
>4.1.5.16. GD::Text::Align (any) [Optional]</H3
>4.1.6.14. GD::Text::Align (any) [optional]</H3
><P
>GD::Text::Align, as the name implies, is used to draw aligned
strings of text. It is needed by the reporting interface.
......@@ -1733,7 +1837,7 @@ CLASS="section"
><A
NAME="install-modules-mime-parser"
></A
>4.1.5.17. MIME::Parser (any) [Optional]</H3
>4.1.6.15. MIME::Parser (any) [optional]</H3
><P
>MIME::Parser is only needed if you want to use the e-mail interface
located in the <TT
......@@ -1768,7 +1872,7 @@ CLASS="section"
><A
NAME="install-modules-patchreader"
></A
>4.1.5.18. PatchReader (0.9.1) [Optional]</H3
>4.1.6.16. PatchReader (0.9.1) [optional]</H3
><P
>PatchReader is only needed if you want to use Patch Viewer, a
Bugzilla feature to format patches in a pretty HTML fashion. There are a
......@@ -1804,154 +1908,15 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN748"
NAME="AEN768"
></A
>4.1.6. <TT
CLASS="filename"
>checksetup.pl</TT
></H2
><P
>Next, run the magic checksetup.pl script.
This is designed to make sure your perl modules are the correct
version and your MySQL database and other
configuration options are consistent with the Bugzilla CGI files.
It will make sure Bugzilla files and directories have reasonable
permissions, set up the
<TT
CLASS="filename"
>data</TT
>
directory, and create all the MySQL tables.
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="screen"
>&#13;<TT
CLASS="prompt"
>bash#</TT
> ./checksetup.pl
</PRE
></FONT
></TD
></TR
></TABLE
><P
>&#13; The first time you run it, it will create a file called
<TT
CLASS="filename"
>localconfig</TT
>.</P
><P
>This file contains a variety of settings you may need to tweak
including how Bugzilla should connect to the MySQL database.</P
><P
>The connection settings include:
<P
></P
><OL
TYPE="1"
><LI
><P
>server's host: just use
<SPAN
CLASS="QUOTE"
>"localhost"</SPAN
>
if the MySQL server is local</P
></LI
><LI
><P
>database name:
<SPAN
CLASS="QUOTE"
>"bugs_db"</SPAN
>
if you're following these directions</P
></LI
><LI
><P
>MySQL username:
<SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
>
if you're following these directions</P
></LI
><LI
>4.1.7. Configuring Bugzilla</H2
><P
>Password for the
<SPAN
CLASS="QUOTE"
>"bugs_user"</SPAN
>
MySQL account; (<SPAN
CLASS="QUOTE"
>"bugs_password"</SPAN
> above)</P
></LI
></OL
>
>&#13; Once checksetup.pl has run successfully, Bugzilla should start up.
Proceed to the correct URL and log in with the administrator account
you defined in the last checksetup.pl run.
</P
><P
>Once you are happy with the settings,
<TT
CLASS="filename"
>su</TT
> to the user
your web server runs as, and re-run
<TT
CLASS="filename"
>checksetup.pl</TT
>. (Note: on some security-conscious
systems, you may need to change the login shell for the webserver
account before you can do this.)
On this second run, it will create the database and an administrator
account for which you will be prompted to provide information.</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
>The checksetup.pl script is designed so that you can run it at
any time without causing harm. You should run it after any upgrade to
Bugzilla.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN778"
></A
>4.1.7. Configuring Bugzilla</H2
><P
>&#13; You should run through the parameters on the Edit Parameters page
(link in the footer) and set them all to appropriate values.
They key parameters are documented in <A
......
docs/html/troubleshooting.html
View file @ 96a0037a
......@@ -87,7 +87,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1215"
NAME="AEN1206"
></A
>4.6.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
......@@ -112,7 +112,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1220"
NAME="AEN1211"
></A
>4.6.2. DBD::Sponge::db prepare failed</H2
><P
......
docs/html/userpreferences.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="userpreferences"
></A
>3.8. User Preferences</H1
>3.9. User Preferences</H1
><P
>Once you have logged in, you can customise various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
......@@ -89,7 +89,7 @@ CLASS="section"
><A
NAME="accountsettings"
></A
>3.8.1. Account Settings</H2
>3.9.1. Account Settings</H2
><P
>On this tab, you can change your basic account information,
including your password, email address and real name. For security
......@@ -114,7 +114,7 @@ CLASS="section"
><A
NAME="emailsettings"
></A
>3.8.2. Email Settings</H2
>3.9.2. Email Settings</H2
><P
>On this tab you can reduce or increase the amount of email sent
you from Bugzilla, opting in our out depending on your relationship to
......@@ -169,7 +169,7 @@ CLASS="section"
><A
NAME="permissionsettings"
></A
>3.8.3. Permissions</H2
>3.9.3. Permissions</H2
><P
>This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
......
docs/html/using.html
View file @ 96a0037a
......@@ -14,8 +14,8 @@ REL="PREVIOUS"
TITLE="Why use Bugzilla?"
HREF="why-bugzilla.html"><LINK
REL="NEXT"
TITLE="Create a Bugzilla Account"
HREF="myaccount.html"></HEAD
TITLE="Introduction"
HREF="using-intro.html"></HEAD
><BODY
CLASS="chapter"
BGCOLOR="#FFFFFF"
......@@ -58,7 +58,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="myaccount.html"
HREF="using-intro.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -83,150 +83,138 @@ CLASS="TOC"
></DT
><DT
>3.1. <A
HREF="using-intro.html"
>Introduction</A
></DT
><DT
>3.2. <A
HREF="myaccount.html"
>Create a Bugzilla Account</A
></DT
><DT
>3.2. <A
>3.3. <A
HREF="bug_page.html"
>Anatomy of a Bug</A
></DT
><DT
>3.3. <A
>3.4. <A
HREF="query.html"
>Searching for Bugs</A
></DT
><DT
>3.4. <A
>3.5. <A
HREF="list.html"
>Bug Lists</A
></DT
><DT
>3.5. <A
>3.6. <A
HREF="bugreports.html"
>Filing Bugs</A
></DT
><DT
>3.6. <A
>3.7. <A
HREF="patchviewer.html"
>Patch Viewer</A
></DT
><DD
><DL
><DT
>3.6.1. <A
>3.7.1. <A
HREF="patchviewer.html#patchviewer_view"
>Viewing Patches in Patch Viewer</A
></DT
><DT
>3.6.2. <A
>3.7.2. <A
HREF="patchviewer.html#patchviewer_diff"
>Seeing the Difference Between Two Patches</A
></DT
><DT
>3.6.3. <A
>3.7.3. <A
HREF="patchviewer.html#patchviewer_context"
>Getting More Context in a Patch</A
></DT
><DT
>3.6.4. <A
>3.7.4. <A
HREF="patchviewer.html#patchviewer_collapse"
>Collapsing and Expanding Sections of a Patch</A
></DT
><DT
>3.6.5. <A
>3.7.5. <A
HREF="patchviewer.html#patchviewer_link"
>Linking to a Section of a Patch</A
></DT
><DT
>3.6.6. <A
>3.7.6. <A
HREF="patchviewer.html#patchviewer_bonsai_lxr"
>Going to Bonsai and LXR</A
></DT
><DT
>3.6.7. <A
>3.7.7. <A
HREF="patchviewer.html#patchviewer_unified_diff"
>Creating a Unified Diff</A
></DT
></DL
></DD
><DT
>3.7. <A
>3.8. <A
HREF="hintsandtips.html"
>Hints and Tips</A
></DT
><DD
><DL
><DT
>3.7.1. <A
HREF="hintsandtips.html#AEN358"
>3.8.1. <A
HREF="hintsandtips.html#AEN363"
>Autolinkification</A
></DT
><DT
>3.7.2. <A
>3.8.2. <A
HREF="hintsandtips.html#quicksearch"
>Quicksearch</A
></DT
><DT
>3.7.3. <A
>3.8.3. <A
HREF="hintsandtips.html#commenting"
>Comments</A
></DT
><DT
>3.7.4. <A
>3.8.4. <A
HREF="hintsandtips.html#attachments"
>Attachments</A
></DT
><DT
>3.7.5. <A
HREF="hintsandtips.html#AEN388"
>Filing Bugs</A
></DT
></DL
></DD
><DT
>3.8. <A
>3.9. <A
HREF="userpreferences.html"
>User Preferences</A
></DT
><DD
><DL
><DT
>3.8.1. <A
>3.9.1. <A
HREF="userpreferences.html#accountsettings"
>Account Settings</A
></DT
><DT
>3.8.2. <A
>3.9.2. <A
HREF="userpreferences.html#emailsettings"
>Email Settings</A
></DT
><DT
>3.8.3. <A
>3.9.3. <A
HREF="userpreferences.html#permissionsettings"
>Permissions</A
></DT
></DL
></DD
><DT
>3.9. <A
>3.10. <A
HREF="reporting.html"
>Reports</A
></DT
></DL
></DIV
><P
>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
<A
HREF="http://landfill.bugzilla.org/bugzilla-tip/"
TARGET="_top"
>Landfill</A
>,
which you are welcome to play with (if it's up.)
However, it does not necessarily
have all Bugzilla features enabled, and runs an up-to-the-minute version,
so some things may not quite work as this document describes.</P
></DIV
><DIV
CLASS="NAVFOOTER"
......@@ -262,7 +250,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="myaccount.html"
HREF="using-intro.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -282,7 +270,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Create a Bugzilla Account</TD
>Introduction</TD
></TR
></TABLE
></DIV
......
docs/html/why-bugzilla.html
View file @ 96a0037a
......@@ -79,7 +79,8 @@ NAME="why-bugzilla"
></A
>2.3. Why use Bugzilla?</H1
><P
>Bugzilla boasts many advanced features. These include:
>Bugzilla is the leading open-source/free software bug tracking
system. It boasts many advanced features, including:
<P
></P
><UL
......@@ -117,12 +118,12 @@ NAME="why-bugzilla"
></LI
><LI
><P
>Web, XML, email and console interfaces</P
>Completely customisable and/or localisable web user
interface</P
></LI
><LI
><P
>Completely customisable and/or localisable web user
interface</P
>Additional XML, email and console interfaces</P
></LI
><LI
><P
......@@ -157,8 +158,7 @@ HREF="http://www.perforce.com"
TARGET="_top"
>Perforce SCM</A
>, Bugzilla
provides a powerful, easy-to-use solution to configuration management and
replication problems.</P
provides a powerful, easy-to-use configuration management solution.</P
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/why-tracking.html
View file @ 96a0037a
......@@ -79,23 +79,15 @@ NAME="why-tracking"
></A
>2.2. Why use a bug-tracking system?</H1
><P
>For many years, defect-tracking software was principally
the domain of large software development houses. Most smaller shops
simply relied on
shared lists and email to monitor the status of defects. This procedure
was error-prone and tended to cause those bugs judged least significant by
developers to be dropped or ignored.</P
>Those who do not use a bug-tracking system tend to rely on
shared lists, email, spreadsheets and/or Post-It notes to monitor the
status of defects. This procedure
is usually error-prone and tends to cause those bugs judged least
significant by developers to be dropped or ignored.</P
><P
>Integrated
defect-tracking systems reduce downtime, increase productivity, and raise
customer satisfaction with their systems. Along with full disclosure, an
open bug-tracker allows you to keep in touch with your clients
and resellers, to communicate about problems effectively throughout the
data management chain. Many corporations have also discovered that
defect-tracking helps reduce costs by providing IT support
accountability, telephone support knowledge bases, and a common,
well-understood method for accounting for unusual system or software
issues.</P
>Integrated defect-tracking systems make sure that nothing gets
swept under the carpet; they provide a method of creating, storing,
arranging and processing defect reports and enhancement requests.</P
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/pdf/Bugzilla-Guide.pdf
View file @ 96a0037a
This source diff could not be displayed because it is too large. You can view the blob instead.
docs/txt/Bugzilla-Guide.txt
View file @ 96a0037a
......@@ -31,15 +31,16 @@ The Bugzilla Team
3. Using Bugzilla
3.1. Create a Bugzilla Account
3.2. Anatomy of a Bug
3.3. Searching for Bugs
3.4. Bug Lists
3.5. Filing Bugs
3.6. Patch Viewer
3.7. Hints and Tips
3.8. User Preferences
3.9. Reports
3.1. Introduction
3.2. Create a Bugzilla Account
3.3. Anatomy of a Bug
3.4. Searching for Bugs
3.5. Bug Lists
3.6. Filing Bugs
3.7. Patch Viewer
3.8. Hints and Tips
3.9. User Preferences
3.10. Reports
4. Installation
......@@ -153,13 +154,11 @@ Chapter 1. About This Guide
match the current version of Bugzilla. This version of the guide, like
its associated Bugzilla version, is a development version.
The newest version of this guide can always be found at
http://www.bugzilla.org; however, you should read the version which
came with the Bugzilla release you are using.
The latest version of this document can always be checked out via CVS.
Please follow the Mozilla CVS instructions and check out the
mozilla/webtools/bugzilla/docs/ subtree.
The latest version of this guide can always be found at
http://www.bugzilla.org, or checked out via CVS. (Please follow the
Mozilla CVS instructions and check out the
mozilla/webtools/bugzilla/docs/ subtree.) However, you should read the
version which came with the Bugzilla release you are using.
The Bugzilla Guide is currently only available in English. If you
would like to volunteer to translate it, please contact Dave Miller.
......@@ -187,7 +186,7 @@ Chapter 1. About This Guide
This document uses the following conventions:
Descriptions Appearance
Warnings
Warning
Caution
......@@ -197,7 +196,7 @@ Chapter 1. About This Guide
Tip
Would you like a breath mint?
Notes
Note
Note
......@@ -207,12 +206,12 @@ Chapter 1. About This Guide
Warning
Read this or the cat gets it.
File and directory names filename
Commands to be typed command
Applications names application
Prompt of users command under bash shell bash$
Prompt of root users command under bash shell bash#
Prompt of user command under tcsh shell tcsh$
File or directory name filename
Command to be typed command
Application name application
Normal user's prompt under bash shell bash$
Root user's prompt under bash shell bash#
Normal user's prompt under tcsh shell tcsh$
Environment variables VARIABLE
Term found in the glossary Bugzilla
Code example
......@@ -238,26 +237,21 @@ Chapter 2. Introduction
2.2. Why use a bug-tracking system?
For many years, defect-tracking software was principally the domain of
large software development houses. Most smaller shops simply relied on
shared lists and email to monitor the status of defects. This
procedure was error-prone and tended to cause those bugs judged least
significant by developers to be dropped or ignored.
Those who do not use a bug-tracking system tend to rely on shared
lists, email, spreadsheets and/or Post-It notes to monitor the status
of defects. This procedure is usually error-prone and tends to cause
those bugs judged least significant by developers to be dropped or
ignored.
Integrated defect-tracking systems reduce downtime, increase
productivity, and raise customer satisfaction with their systems.
Along with full disclosure, an open bug-tracker allows you to keep in
touch with your clients and resellers, to communicate about problems
effectively throughout the data management chain. Many corporations
have also discovered that defect-tracking helps reduce costs by
providing IT support accountability, telephone support knowledge
bases, and a common, well-understood method for accounting for unusual
system or software issues.
Integrated defect-tracking systems make sure that nothing gets swept
under the carpet; they provide a method of creating, storing,
arranging and processing defect reports and enhancement requests.
_________________________________________________________________
2.3. Why use Bugzilla?
Bugzilla boasts many advanced features. These include:
Bugzilla is the leading open-source/free software bug tracking system.
It boasts many advanced features, including:
* Powerful searching
* User-configurable email notifications of bug changes
......@@ -267,8 +261,8 @@ Chapter 2. Introduction
* Integrated, product-based, granular security schema
* Fully security-audited, and runs under Perl's taint mode
* A robust, stable RDBMS back-end
* Web, XML, email and console interfaces
* Completely customisable and/or localisable web user interface
* Additional XML, email and console interfaces
* Extensive configurability
* Smooth upgrade pathway between versions
......@@ -278,12 +272,13 @@ Chapter 2. Introduction
pre-and-post fabrication), and software and hardware bug tracking for
luminaries such as Redhat, NASA, Linux-Mandrake, and VA Systems.
Combined with systems such as CVS, Bonsai, or Perforce SCM, Bugzilla
provides a powerful, easy-to-use solution to configuration management
and replication problems.
provides a powerful, easy-to-use configuration management solution.
_________________________________________________________________
Chapter 3. Using Bugzilla
3.1. Introduction
This section contains information for end-users of Bugzilla. There is
a Bugzilla test installation, called Landfill, which you are welcome
to play with (if it's up.) However, it does not necessarily have all
......@@ -291,7 +286,7 @@ Chapter 3. Using Bugzilla
some things may not quite work as this document describes.
_________________________________________________________________
3.1. Create a Bugzilla Account
3.2. Create a Bugzilla Account
If you want to use Bugzilla, first you need to create an account.
Consult with the administrator responsible for your installation of
......@@ -315,7 +310,7 @@ Chapter 3. Using Bugzilla
changes, you should not have to log in again.
_________________________________________________________________
3.2. Anatomy of a Bug
3.3. Anatomy of a Bug
The core of Bugzilla is the screen which displays a particular bug.
It's a good place to explain some Bugzilla concepts. Bug 1 on Landfill
......@@ -391,7 +386,7 @@ Chapter 3. Using Bugzilla
discussion here, if you have something worthwhile to say.
_________________________________________________________________
3.3. Searching for Bugs
3.4. Searching for Bugs
The Bugzilla Search page is is the interface where you can find any
bug report, comment, or patch currently in the Bugzilla system. You
......@@ -411,7 +406,7 @@ Chapter 3. Using Bugzilla
Charts help link on the Search page for more information.
_________________________________________________________________
3.4. Bug Lists
3.5. Bug Lists
If you run a search, a list of matching bugs will be returned.
......@@ -421,19 +416,23 @@ Chapter 3. Using Bugzilla
Long Format: this gives you a large page with a non-editable summary
of the fields of each bug.
CSV: get the buglist as comma-separated values, for import into e.g. a
spreadsheet.
Change Columns: change the bug attributes which appear in the list.
Change several bugs at once: If your account is sufficiently
empowered, you can make the same change to all the bugs in the list -
for example, changing their owner.
Send mail to bug owners: Sends mail to the owners of all bugs on the
list.
Edit this query: 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 revisions to the query you just made so you get more
accurate results.
Edit Search: 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
revisions to the query you just made so you get more accurate results.
Remember Search As: You can give a search a name and remember it; a
link will appear in your page footer giving you quick access to run it
again later.
_________________________________________________________________
3.5. Filing Bugs
3.6. Filing Bugs
Years of bug writing experience has been distilled for your reading
pleasure into the Bug Writing Guidelines. While some of the advice is
......@@ -452,9 +451,21 @@ Chapter 3. Using Bugzilla
based upon your browser, for the "Platform" and "OS" drop-down
boxes. If they are wrong, change them.
4. Select "Commit" and send in your bug report.
Try to make sure that everything said in the summary is also said in
the first comment. Summaries are often updated and this will ensure
your original information is easily accessible.
You do not need to put "any" or similar strings in the URL field. If
there is no specific URL associated with the bug, leave this field
blank.
If you feel a bug you filed was incorrectly marked as a DUPLICATE of
another, please question it in your bug, not the bug it was duped to.
Feel free to CC the person who duped it if they are not already CCed.
_________________________________________________________________
3.6. Patch Viewer
3.7. Patch Viewer
Viewing and reviewing patches in Bugzilla is often difficult due to
lack of context, improper format and the inherent readability issues
......@@ -476,7 +487,7 @@ Chapter 3. Using Bugzilla
format it came from
_________________________________________________________________
3.6.1. Viewing Patches in Patch Viewer
3.7.1. Viewing Patches in Patch Viewer
The main way to view a patch in patch viewer is to click on the "Diff"
link next to a patch in the Attachments list on a bug. You may also do
......@@ -484,7 +495,7 @@ Chapter 3. Using Bugzilla
button in the Edit Attachment screen.
_________________________________________________________________
3.6.2. Seeing the Difference Between Two Patches
3.7.2. Seeing the Difference Between Two Patches
To see the difference between two patches, you must first view the
newer patch in Patch Viewer. Then select the older patch from the
......@@ -493,7 +504,7 @@ Chapter 3. Using Bugzilla
new or changed in the newer patch.
_________________________________________________________________
3.6.3. Getting More Context in a Patch
3.7.3. Getting More Context in a Patch
To get more context in a patch, you put a number in the textbox at the
top of Patch Viewer ("Patch / File / [textbox]") and hit enter. This
......@@ -503,7 +514,7 @@ Chapter 3. Using Bugzilla
against files that were diffed using "cvs diff".
_________________________________________________________________
3.6.4. Collapsing and Expanding Sections of a Patch
3.7.4. Collapsing and Expanding Sections of a Patch
To view only a certain set of files in a patch (for example, if a
patch is absolutely huge and you want to only review part of it at a
......@@ -513,7 +524,7 @@ Chapter 3. Using Bugzilla
the top of the page.
_________________________________________________________________
3.6.5. Linking to a Section of a Patch
3.7.5. Linking to a Section of a Patch
To link to a section of a patch (for example, if you want to be able
to give someone a URL to show them which part you are talking about)
......@@ -522,7 +533,7 @@ Chapter 3. Using Bugzilla
Location in Mozilla works as well.)
_________________________________________________________________
3.6.6. Going to Bonsai and LXR
3.7.6. Going to Bonsai and LXR
To go to Bonsai to get blame for the lines you are interested in, you
can click the "Lines XX-YY" link on the section header you are
......@@ -534,20 +545,20 @@ Chapter 3. Using Bugzilla
numbers are likely to rot).
_________________________________________________________________
3.6.7. Creating a Unified Diff
3.7.7. Creating a Unified Diff
If the patch is not in a format that you like, you can turn it into a
unified diff format by clicking the "Raw Unified" link at the top of
the page.
_________________________________________________________________
3.7. Hints and Tips
3.8. Hints and Tips
This section distills some Bugzilla tips and best practices that have
been developed.
_________________________________________________________________
3.7.1. Autolinkification
3.8.1. Autolinkification
Bugzilla comments are plain text - so typing <U> will produce
less-than, U, greater-than rather than underlined text. However,
......@@ -570,7 +581,7 @@ Chapter 3. Using Bugzilla
convenience of others.
_________________________________________________________________
3.7.2. Quicksearch
3.8.2. Quicksearch
Quicksearch is a single-text-box query tool which uses metacharacters
to indicate what is to be searched. For example, typing "foo|bar" into
......@@ -582,7 +593,7 @@ Chapter 3. Using Bugzilla
Help link which details how to use it.
_________________________________________________________________
3.7.3. Comments
3.8.3. Comments
If you are changing the fields on a bug, only comment if either you
have something pertinent to say, or Bugzilla requires it. Otherwise,
......@@ -598,7 +609,7 @@ Chapter 3. Using Bugzilla
art creations are not.
_________________________________________________________________
3.7.4. Attachments
3.8.4. Attachments
Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it
......@@ -614,29 +625,14 @@ Chapter 3. Using Bugzilla
way, the test case works immediately out of the bug.
_________________________________________________________________
3.7.5. Filing Bugs
Try to make sure that everything said in the summary is also said in
the first comment. Summaries are often updated and this will ensure
your original information is easily accessible.
You do not need to put "any" or similar strings in the URL field. If
there is no specific URL associated with the bug, leave this field
blank.
If you feel a bug you filed was incorrectly marked as a DUPLICATE of
another, please question it in your bug, not the bug it was duped to.
Feel free to CC the person who duped it if they are not already CCed.
_________________________________________________________________
3.8. User Preferences
3.9. User Preferences
Once you have logged in, you can customise various aspects of Bugzilla
via the "Edit prefs" link in the page footer. The preferences are
split into three tabs:
_________________________________________________________________
3.8.1. Account Settings
3.9.1. Account Settings
On this tab, you can change your basic account information, including
your password, email address and real name. For security reasons, in
......@@ -647,7 +643,7 @@ Chapter 3. Using Bugzilla
change. This helps to prevent account hijacking.
_________________________________________________________________
3.8.2. Email Settings
3.9.2. Email Settings
On this tab you can reduce or increase the amount of email sent you
from Bugzilla, opting in our out depending on your relationship to the
......@@ -671,7 +667,7 @@ Chapter 3. Using Bugzilla
installations. If you can't see it, ask your administrator.
_________________________________________________________________
3.8.3. Permissions
3.9.3. Permissions
This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
......@@ -679,7 +675,7 @@ Chapter 3. Using Bugzilla
administration functions.
_________________________________________________________________
3.9. Reports
3.10. Reports
To be written
_________________________________________________________________
......@@ -692,8 +688,8 @@ Chapter 4. Installation
operating systems including almost all Unix clones and Microsoft
Windows. Many operating systems have utilities that make installation
easier or quirks that make it harder. We have tried to collect that
information in Section 4.4, so be sure to check out that section
before you start your installation.
information in Section 4.4, so unless you are on Linux, be sure to
check out that section before you start your installation.
Note
......@@ -704,27 +700,25 @@ Chapter 4. Installation
Warning
While installing Bugzilla, it is a good idea to ensure that there is
some kind of firewall between you and the rest of the Internet as your
machine may be insecure for periods during the install. Many
installation steps require an active Internet connection to complete,
but you must take care to ensure that at no point is your machine
vulnerable to an attack.
some kind of configurable firewall between you and the rest of the
Internet as your machine may be insecure for periods during the
install. Many installation steps require an active Internet connection
to complete, but you must take care to ensure that at no point is your
machine vulnerable to an attack.
This guide assumes that you already have your operating system
installed, network configured, and have administrative access to the
shell on the machine you are installing Bugzilla onto. It is possible
to install and run Bugzilla without administrative access, but you
machine onto which you are installing Bugzilla. It is possible to
install and run Bugzilla itself without administrative access, but you
have to either make sure all the required software is installed or get
somebody with administrative access to install it for you.
You are strongly recommended to make a backup of your system before
installing Bugzilla and at regular intervals thereafter.
installing Bugzilla (and at regular intervals thereafter :-).
The listing below is a basic step-by-step list. More information can
be found in the sections below. Minimum versions will be included in
parenthesis where appropriate.
1. Install Perl (5.6)
2. Install MySQL (3.23.41)
Here's a basic step-by-step list:
1. Install Perl (5.6.0 or above)
2. Install MySQL (3.23.41 or above)
3. Install a Webserver
4. Put Bugzilla in the Webspace
5. Install Perl Modules
......@@ -733,18 +727,20 @@ Chapter 4. Installation
4.1.1. Perl
Any machine that doesn't have Perl on it is a sad machine indeed. Perl
can be got in source form from http://www.perl.com. There are also
binary versions available for many platforms, most of which are linked
to from perl.com. Although Bugzilla runs with perl 5.6, it's a good
idea to be up to the very latest version if you can when running
Bugzilla. As of this writing, that is Perl version 5.8.
Any machine that doesn't have Perl on it is a sad machine indeed. If
your OS doesn't come with it, Perl can be got in source form from
http://www.perl.com. There are also binary versions available for many
platforms, most of which are linked to from perl.com. Although
Bugzilla runs with perl 5.6.0, it's a good idea to be up to the very
latest version if you can when running Bugzilla. As of this writing,
that is Perl version 5.8.2.
_________________________________________________________________
4.1.2. MySQL
Visit the MySQL homepage at http://www.mysql.com to grab and install
the latest stable release of the server.
If your OS doesn't come with it or provide official packages, visit
the MySQL homepage at http://www.mysql.com to grab and install the
latest stable release of the server.
Note
......@@ -771,29 +767,30 @@ Chapter 4. Installation
set-variable = max_allowed_packet=1M
If you are running Bugzilla and MySQL on the same machine, you may
also wish to utilize the skip-networking option as mentioned in
also wish to utilize the --skip-networking option as mentioned in
Section 4.5.2 for the added security.
_________________________________________________________________
4.1.2.1. Configuring MySQL
4.1.2.1. Adding a user to MySQL
This first thing you'll want to do is make sure you've given the
"root" user a password as suggested in Section 4.5.2. For clarity,
these instructions will assume that your MySQL user for Bugzilla will
be "bugs_user", the database will be called "bugs_db" and the password
for the "bugs_user" user is "bugs_password". You should, of course,
substitute the values you intend to use for your site.
"root" user a password as suggested in Section 4.5.2. Then, you need
to add a user for Bugzilla to use. For clarity, these instructions
will assume that your MySQL user for Bugzilla will be "bugs_user", the
database will be called "bugs_db" and the password for the "bugs_user"
user is "bugs_password". You should, of course, substitute the values
you intend to use for your site.
Note
Most people use "bugs" for both the user and database name.
Most people use "bugs" for both the user and database name. Don't use
it for the password, though...
Next, we use an SQL GRANT command to create a "bugs_user" user, and
grant sufficient permissions for checksetup.pl, which we'll use later,
to work its magic. This also restricts the "bugs_user" user to
operations within a database called "bugs_db", and only allows the
account to connect from "localhost". Modify it to reflect your setup
if you will be connecting from another machine or as a different user.
We use an SQL GRANT command to create a "bugs_user" user. This also
restricts the "bugs_user" user to operations within a database called
"bugs_db", and only allows the account to connect from "localhost".
Modify it to reflect your setup if you will be connecting from another
machine or as a different user.
mysql> GRANT SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,
DROP,REFERENCES ON bugs_db.* TO bugs_user@localhost
IDENTIFIED BY 'bugs_password';
......@@ -802,7 +799,8 @@ set-variable = max_allowed_packet=1M
Note
If you are using MySQL 4, the bugs user also needs to be granted the
LOCK TABLES and CREATE TEMPORARY TABLES permissions.
LOCK TABLES and CREATE TEMPORARY TABLES permissions, so add them to
the list in the GRANT command.
_________________________________________________________________
4.1.3. HTTP Server
......@@ -830,28 +828,71 @@ set-variable = max_allowed_packet=1M
Tip
If you symlink the bugzilla directory into your Apache's HTML
If you symlink the bugzilla directory into your Apache's html
hierarchy, you may receive Forbidden errors unless you add the
"FollowSymLinks" directive to the <Directory> entry for the HTML root
in httpd.conf.
FollowSymLinks directive to the <Directory> entry for the HTML root
directory in httpd.conf.
Caution
The default Bugzilla distribution is not designed to be placed in a
cgi-bin directory (this includes any directory which is configured
using the ScriptAlias directive of Apache).
Once all the files are in a web accessible directory, make that
directory writable by your webserver's user. This is a temporary step
until you run the post-install checksetup.pl script, which locks down
your installation.
_________________________________________________________________
Caution
4.1.5. checksetup.pl
The default Bugzilla distribution is not designed to be placed in a
cgi-bin directory (this includes any directory which is configured
using the ScriptAlias directive of Apache).
Next, run the magic checksetup.pl script. This is designed to check
whether you have all of the right Perl modules in the correct
versions, and that Bugzilla is generally set up correctly.
Eventually, it will make sure Bugzilla files and directories have
reasonable permissions, set up the data directory, and create all the
MySQL tables. But the first time you run it, it's highly likely to
tell you that you are missing a few Perl modules. Make a note of which
ones they are, and then proceed to the next section to install them.
bash# ./checksetup.pl
The first time you run it with all the correct modules installed, it
will create a file called localconfig.
This file contains a variety of settings you may need to tweak
including how Bugzilla should connect to the MySQL database.
The connection settings include:
1. server's host: just use "localhost" if the MySQL server is local
2. database name: "bugs_db" if you're following these directions
3. MySQL username: "bugs_user" if you're following these directions
4. Password for the "bugs_user" MySQL account; ("bugs_password"
above)
Edit the file to change these. Once you are happy with the settings,
su to the user your web server runs as, and re-run checksetup.pl.
(Note: on some security-conscious systems, you may need to change the
login shell for the webserver account before you can do this.) On this
second run, it will create the database and an administrator account
for which you will be prompted to provide information.
Note
The checksetup.pl script is designed so that you can run it at any
time without causing harm. You should run it after any upgrade to
Bugzilla.
_________________________________________________________________
4.1.5. Perl Modules
4.1.6. Perl Modules
Don't be intimidated by this long list of modules. See Section 4.1.6.1
for a way of installing all the ones you need with a single command.
Perl modules can be found using CPAN on Unix based systems or PPM on
Win32. The root servers have a real tendency to bog down, so please
use mirrors.
Win32.
Good instuctions can be found for using each of these services on
their respective websites. The basics can be found in Example 4-1 for
......@@ -892,16 +933,14 @@ bash# make install
Perl Modules (minimum version):
1. Bundle::Bugzilla (Will allow you to skip the rest)
2. AppConfig (1.52)
3. CGI (2.88)
4. Data::Dumper (any)
5. Date::Format (2.21)
6. DBI (1.32)
7. DBD::mysql (2.1010)
8. File::Spec (0.82)
9. File::Temp (any)
10. Template Toolkit (2.08)
11. Text::Wrap (2001.0131)
2. CGI (2.88)
3. Date::Format (2.21)
4. DBI (1.32)
5. DBD::mysql (2.1010)
6. File::Spec (0.82)
7. File::Temp (any)
8. Template Toolkit (2.08)
9. Text::Wrap (2001.0131)
and, optionally:
......@@ -914,7 +953,7 @@ bash# make install
7. PatchReader (0.9.1) for pretty HTML view of patches
_________________________________________________________________
4.1.5.1. Bundle::Bugzilla
4.1.6.1. Bundle::Bugzilla
If you are running at least perl 5.6.1, you can save yourself a lot of
time by using Bundle::Bugzilla. This bundle contains every module
......@@ -937,13 +976,7 @@ cpan>
you'll have to go through a series of configuration steps.
_________________________________________________________________
4.1.5.2. AppConfig (1.52)
Dependency for Template Toolkit. We probably don't need to
specifically check for it anymore.
_________________________________________________________________
4.1.5.3. CGI (2.88)
4.1.6.2. CGI (2.88)
The CGI module parses form elements and cookies and does many other
usefule things. It come as a part of recent perl distributions, but
......@@ -955,21 +988,7 @@ cpan>
Documentation: http://www.perldoc.com/perl5.8.0/lib/CGI.html
_________________________________________________________________
4.1.5.4. Data::Dumper (any)
The Data::Dumper module provides data structure persistence for Perl
(similar to Java's serialization). It comes with later sub-releases of
Perl 5.004, but a re-installation just to be sure it's available won't
hurt anything.
CPAN Download Page: http://search.cpan.org/dist/Data-Dumper/
PPM Download Link: http://ppm.activestate.com/PPMPackages/zips
/6xx-builds-only/Data-Dumper.zip
Documentation: http://www.perldoc.com/perl5.8.0/lib/Data/Dumpe
r.html
_________________________________________________________________
4.1.5.5. TimeDate modules (2.21)
4.1.6.3. TimeDate modules (2.21)
Many of the more common date/time/calendar related Perl modules have
been grouped into a bundle similar to the MySQL modules bundle. This
......@@ -984,7 +1003,7 @@ cpan>
ormat.pm
_________________________________________________________________
4.1.5.6. DBI (1.32)
4.1.6.4. DBI (1.32)
The DBI module is a generic Perl module used the MySQL-related
modules. As long as your Perl installation was done correctly the DBI
......@@ -997,7 +1016,7 @@ cpan>
Documentation: http://dbi.perl.org/doc/
_________________________________________________________________
4.1.5.7. MySQL-related modules
4.1.6.5. MySQL-related modules
The Perl/MySQL interface requires a few mutually-dependent Perl
modules. These modules are grouped together into the the
......@@ -1022,7 +1041,7 @@ cpan>
ysql.pod
_________________________________________________________________
4.1.5.8. File::Spec (0.82)
4.1.6.6. File::Spec (0.82)
File::Spec is a perl module that allows file operations, such as
generating full path names, to work cross platform.
......@@ -1034,7 +1053,7 @@ cpan>
html
_________________________________________________________________
4.1.5.9. File::Temp (any)
4.1.6.7. File::Temp (any)
File::Temp is used to generate a temporary filename that is guaranteed
to be unique. It comes as a standard part of perl
......@@ -1046,7 +1065,7 @@ cpan>
html
_________________________________________________________________
4.1.5.10. Template Toolkit (2.08)
4.1.6.8. Template Toolkit (2.08)
When you install Template Toolkit, you'll get asked various questions
about features to enable. The defaults are fine, except that it is
......@@ -1060,7 +1079,7 @@ cpan>
Documentation: http://www.template-toolkit.org/docs.html
_________________________________________________________________
4.1.5.11. Text::Wrap (2001.0131)
4.1.6.9. Text::Wrap (2001.0131)
Text::Wrap is designed to proved intelligent text wrapping.
......@@ -1070,15 +1089,9 @@ cpan>
html
_________________________________________________________________
4.1.5.12. GD (1.20) [optional]
4.1.6.10. GD (1.20) [optional]
The GD library was written by Thomas Boutell a long while ago to
programmatically generate images in C. Since then it's become the
defacto standard for programmatic image construction. The Perl
bindings to it found in the GD library are used on millions of web
pages to generate graphs on the fly. That's what Bugzilla will be
using it for so you must install it if you want any of the graphing to
work.
You need the GD library if you want any of the graphing to work.
Note
......@@ -1099,7 +1112,7 @@ cpan>
Documentation: http://stein.cshl.org/WWW/software/GD/
_________________________________________________________________
4.1.5.13. Chart::Base (0.99c) [optional]
4.1.6.11. Chart::Base (0.99c) [optional]
The Chart module provides Bugzilla with on-the-fly charting abilities.
It can be installed in the usual fashion after it has been fetched
......@@ -1111,7 +1124,7 @@ cpan>
/6xx-builds-only/Chart.zip
_________________________________________________________________
4.1.5.14. XML::Parser (any) [Optional]
4.1.6.12. XML::Parser (any) [optional]
XML::Parser is used by the importxml.pl script. You only need it if
you are going to be importing bugs (such as for bug moving).
......@@ -1123,7 +1136,7 @@ cpan>
.html
_________________________________________________________________
4.1.5.15. GD::Graph (any) [Optional]
4.1.6.13. GD::Graph (any) [optional]
In addition to GD listed above, the reporting interface of Bugzilla
needs to have the GD::Graph module installed.
......@@ -1134,7 +1147,7 @@ cpan>
Documentation: http://search.cpan.org/dist/GDGraph/Graph.pm
_________________________________________________________________
4.1.5.16. GD::Text::Align (any) [Optional]
4.1.6.14. GD::Text::Align (any) [optional]
GD::Text::Align, as the name implies, is used to draw aligned strings
of text. It is needed by the reporting interface.
......@@ -1146,7 +1159,7 @@ cpan>
gn.pm
_________________________________________________________________
4.1.5.17. MIME::Parser (any) [Optional]
4.1.6.15. MIME::Parser (any) [optional]
MIME::Parser is only needed if you want to use the e-mail interface
located in the contrib directory.
......@@ -1158,7 +1171,7 @@ cpan>
/Parser.pm
_________________________________________________________________
4.1.5.18. PatchReader (0.9.1) [Optional]
4.1.6.16. PatchReader (0.9.1) [optional]
PatchReader is only needed if you want to use Patch Viewer, a Bugzilla
feature to format patches in a pretty HTML fashion. There are a number
......@@ -1176,45 +1189,12 @@ cpan>
html
_________________________________________________________________
4.1.6. checksetup.pl
Next, run the magic checksetup.pl script. This is designed to make
sure your perl modules are the correct version and your MySQL database
and other configuration options are consistent with the Bugzilla CGI
files. It will make sure Bugzilla files and directories have
reasonable permissions, set up the data directory, and create all the
MySQL tables.
bash# ./checksetup.pl
The first time you run it, it will create a file called localconfig.
This file contains a variety of settings you may need to tweak
including how Bugzilla should connect to the MySQL database.
The connection settings include:
1. server's host: just use "localhost" if the MySQL server is local
2. database name: "bugs_db" if you're following these directions
3. MySQL username: "bugs_user" if you're following these directions
4. Password for the "bugs_user" MySQL account; ("bugs_password"
above)
Once you are happy with the settings, su to the user your web server
runs as, and re-run checksetup.pl. (Note: on some security-conscious
systems, you may need to change the login shell for the webserver
account before you can do this.) On this second run, it will create
the database and an administrator account for which you will be
prompted to provide information.
Note
The checksetup.pl script is designed so that you can run it at any
time without causing harm. You should run it after any upgrade to
Bugzilla.
_________________________________________________________________
4.1.7. Configuring Bugzilla
Once checksetup.pl has run successfully, Bugzilla should start up.
Proceed to the correct URL and log in with the administrator account
you defined in the last checksetup.pl run.
You should run through the parameters on the Edit Parameters page
(link in the footer) and set them all to appropriate values. They key
parameters are documented in Section 5.1.
......@@ -1536,7 +1516,7 @@ Javascript code
4.4.1.2. Perl Modules on Win32
Bugzilla on Windows requires the same perl modules found in Section
4.1.5. The main difference is that windows uses PPM instead of CPAN.
4.1.6. The main difference is that windows uses PPM instead of CPAN.
C:\perl> ppm <module name>
Note
......
docs/xml/Bugzilla-Guide.xml
View file @ 96a0037a
......@@ -40,11 +40,11 @@
<!ENTITY bz "http://www.bugzilla.org/">
<!ENTITY bzg-bugs "<ulink url='http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation'>Bugzilla Documentation</ulink>">
<!ENTITY mysql "http://www.mysql.com/">
<!ENTITY newest-perl-ver "5.8">
<!ENTITY newest-perl-ver "5.8.2">
<!-- For minimum versions -->
<!ENTITY min-mysql-ver "3.23.41">
<!ENTITY min-perl-ver "5.6">
<!ENTITY min-perl-ver "5.6.0">
<!ENTITY min-template-ver "2.08">
<!ENTITY min-file-temp-ver "any">
<!ENTITY min-appconfig-ver "1.52">
......
docs/xml/about.xml
View file @ 96a0037a
......@@ -67,17 +67,15 @@
]]>
</para>
<para>
The newest version of this guide can always be found at <ulink
url="http://www.bugzilla.org"/>; however, you should read the version
The latest version of this guide can always be found at <ulink
url="http://www.bugzilla.org"/>, or checked out via CVS.
(Please follow the <ulink url="http://www.mozilla.org/cvs.html">Mozilla
CVS</ulink> instructions and check out the
<filename>mozilla/webtools/bugzilla/docs/</filename>
subtree.) However, you should read the version
which came with the Bugzilla release you are using.
</para>
<para>
The latest version of this document can always be checked out via CVS.
Please follow the <ulink url="http://www.mozilla.org/cvs.html">Mozilla CVS</ulink>
instructions and check out the <filename>mozilla/webtools/bugzilla/docs/</filename>
subtree.
</para>
<para>
The Bugzilla Guide is currently only available in English.
If you would like to volunteer to translate it, please contact
<ulink url="mailto:justdave@syndicomm.com">Dave Miller</ulink>.
......@@ -116,7 +114,7 @@
<para>
Last but not least, all the members of the
<ulink url="news://news.mozilla.org/netscape/public/mozilla/webtools">
<ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">
netscape.public.mozilla.webtools</ulink>
newsgroup. Without your discussions, insight, suggestions, and patches,
this could never have happened.
......
docs/xml/conventions.xml
View file @ 96a0037a
......@@ -20,7 +20,7 @@
<tbody>
<row>
<entry>Warnings</entry>
<entry>Warning</entry>
<entry>
<caution>
......@@ -40,7 +40,7 @@
</row>
<row>
<entry>Notes</entry>
<entry>Note</entry>
<entry>
<note>
......@@ -60,7 +60,7 @@
</row>
<row>
<entry>File and directory names</entry>
<entry>File or directory name</entry>
<entry>
<filename>filename</filename>
......@@ -68,7 +68,7 @@
</row>
<row>
<entry>Commands to be typed</entry>
<entry>Command to be typed</entry>
<entry>
<command>command</command>
......@@ -76,7 +76,7 @@
</row>
<row>
<entry>Applications names</entry>
<entry>Application name</entry>
<entry>
<application>application</application>
......@@ -85,27 +85,21 @@
<row>
<entry>
<foreignphrase>Prompt</foreignphrase>
of users command under bash shell</entry>
Normal user's prompt under bash shell</entry>
<entry>bash$</entry>
</row>
<row>
<entry>
<foreignphrase>Prompt</foreignphrase>
of root users command under bash shell</entry>
Root user's prompt under bash shell</entry>
<entry>bash#</entry>
</row>
<row>
<entry>
<foreignphrase>Prompt</foreignphrase>
of user command under tcsh shell</entry>
Normal user's prompt under tcsh shell</entry>
<entry>tcsh$</entry>
</row>
......
docs/xml/installation.xml
View file @ 96a0037a
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> -->
<!-- $Id: installation.xml,v 1.56 2004/01/15 22:34:35 gerv%gerv.net Exp $ -->
<!-- $Id: installation.xml,v 1.57 2004/01/15 23:54:39 gerv%gerv.net Exp $ -->
<chapter id="installation">
<title>Installation</title>
......@@ -11,7 +11,8 @@
<productname class="registered">Microsoft Windows</productname>. Many
operating systems have utilities that make installation easier or quirks
that make it harder. We have tried to collect that information in
<xref linkend="os-specific"/>, so be sure to check out that section before
<xref linkend="os-specific"/>, so unless you are on Linux,
be sure to check out that section before
you start your installation.
</para>
......@@ -25,7 +26,8 @@
<warning>
<para>While installing Bugzilla, it is a good idea to ensure that there
is some kind of firewall between you and the rest of the Internet
is some kind of configurable firewall between you and the rest of the
Internet
as your machine may be insecure for periods during the install. Many
installation steps require an active Internet connection to complete,
but you must take care to ensure that at no point is your machine
......@@ -34,31 +36,30 @@
<para>This guide assumes that you already have your operating system
installed, network configured, and have administrative access to the
shell on the machine you are installing Bugzilla onto. It is possible to
install and run Bugzilla without administrative access, but you have to
machine onto which you are installing Bugzilla. It is possible to
install and run Bugzilla itself without administrative access, but you
have to
either make sure all the required software is installed or get somebody
with administrative access to install it for you.
</para>
<para>
You are strongly recommended to make a backup of your system
before installing Bugzilla and at regular intervals thereafter.
before installing Bugzilla (and at regular intervals thereafter :-).
</para>
<para>The listing below is a basic step-by-step list. More information
can be found in the sections below. Minimum versions will be
included in parenthesis where appropriate.
<para>Here's a basic step-by-step list:
</para>
<procedure>
<step>
<para><link linkend="install-perl">Install Perl</link>
(&min-perl-ver;)
(&min-perl-ver; or above)
</para>
</step>
<step>
<para><link linkend="install-mysql">Install MySQL</link>
(&min-mysql-ver;)
(&min-mysql-ver; or above)
</para>
</step>
<step>
......@@ -83,7 +84,8 @@
<title>Perl</title>
<para>Any machine that doesn't have Perl on it is a sad machine indeed.
Perl can be got in source form from <ulink url="http://www.perl.com"/>.
If your OS doesn't come with it, Perl can be got in source form
from <ulink url="http://www.perl.com"/>.
There are also binary versions available for many platforms, most of which
are linked to from perl.com.
Although Bugzilla runs with perl &min-perl-ver;,
......@@ -95,7 +97,8 @@
<section id="install-mysql">
<title>MySQL</title>
<para>Visit the MySQL homepage at
<para>If your OS doesn't come with it or provide official packages,
visit the MySQL homepage at
<ulink url="http://www.mysql.com"/>
to grab and install the latest stable release of the server.
</para>
......@@ -136,16 +139,17 @@ set-variable = max_allowed_packet=1M
</figure>
<para>If you are running Bugzilla and MySQL on the same machine, you may
also wish to utilize the <option>skip-networking</option> option as
also wish to utilize the <option>--skip-networking</option> option as
mentioned in <xref linkend="security-mysql"/> for the added security.
</para>
<section id="install-setupdatabase">
<title>Configuring MySQL</title>
<title>Adding a user to MySQL</title>
<para>This first thing you'll want to do is make sure you've given the
<quote>root</quote> user a password as suggested in
<xref linkend="security-mysql"/>. For clarity, these instructions will
<xref linkend="security-mysql"/>. Then, you need to add a user for
Bugzilla to use. For clarity, these instructions will
assume that your MySQL user for Bugzilla will be <quote>bugs_user</quote>,
the database will be called <quote>bugs_db</quote> and the password for
the <quote>bugs_user</quote> user is <quote>bugs_password</quote>. You
......@@ -154,14 +158,13 @@ set-variable = max_allowed_packet=1M
<note>
<para>Most people use <quote>bugs</quote> for both the user and
database name.
database name. Don't use it for the password, though...
</para>
</note>
<para>Next, we use an SQL <command>GRANT</command> command to create a
<para>We use an SQL <command>GRANT</command> command to create a
<quote>bugs_user</quote>
user, and grant sufficient permissions for checksetup.pl, which we'll
use later, to work its magic. This also restricts the
user. This also restricts the
<quote>bugs_user</quote>
user to operations within a database called
<quote>bugs_db</quote>, and only allows the account to connect from
......@@ -179,7 +182,9 @@ set-variable = max_allowed_packet=1M
<note>
<para>If you are using MySQL 4, the bugs user also needs to be granted
the <computeroutput>LOCK TABLES</computeroutput> and
<computeroutput>CREATE TEMPORARY TABLES</computeroutput> permissions.
<computeroutput>CREATE TEMPORARY TABLES</computeroutput> permissions,
so add them to the list in the
<computeroutput>GRANT</computeroutput> command.
</para>
</note>
</section>
......@@ -217,21 +222,16 @@ set-variable = max_allowed_packet=1M
directory.</para>
<tip>
<para>If you symlink the bugzilla directory into your Apache's HTML
<para>If you symlink the bugzilla directory into your Apache's
<filename>html</filename>
hierarchy, you may receive
<errorname>Forbidden</errorname>
errors unless you add the
<quote>FollowSymLinks</quote>
directive to the &lt;Directory&gt; entry for the HTML root
in httpd.conf.</para>
<filename>FollowSymLinks</filename>
directive to the <filename>&lt;Directory&gt;</filename> entry for
the HTML root directory in httpd.conf.</para>
</tip>
<para>Once all the files are in a web accessible directory, make that
directory writable by your webserver's user. This is a temporary step
until you run the post-install
<filename>checksetup.pl</filename>
script, which locks down your installation.</para>
<caution>
<para>The default Bugzilla distribution is not designed to be placed
in a <filename class="directory">cgi-bin</filename> directory (this
......@@ -239,15 +239,104 @@ set-variable = max_allowed_packet=1M
<option>ScriptAlias</option> directive of Apache).
</para>
</caution>
<para>Once all the files are in a web accessible directory, make that
directory writable by your webserver's user. This is a temporary step
until you run the post-install
<filename>checksetup.pl</filename>
script, which locks down your installation.</para>
</section>
<section>
<title>
<filename>checksetup.pl</filename>
</title>
<para>Next, run the magic checksetup.pl script.
This is designed to check whether you have all of the right
Perl modules in the correct
versions, and that Bugzilla is generally set up correctly.
</para>
<para>
Eventually,
it will make sure Bugzilla files and directories have reasonable
permissions, set up the
<filename>data</filename>
directory, and create all the MySQL tables. But the first time you
run it, it's highly likely to tell you that you are missing a few
Perl modules. Make a note of which ones they are, and then proceed to
the next section to install them.
</para>
<screen>
<prompt>bash#</prompt> ./checksetup.pl
</screen>
<para>
The first time you run it with all the correct modules installed,
it will create a file called
<filename>localconfig</filename>.</para>
<para>This file contains a variety of settings you may need to tweak
including how Bugzilla should connect to the MySQL database.</para>
<para>The connection settings include:
<orderedlist>
<listitem>
<para>server's host: just use
<quote>localhost</quote>
if the MySQL server is local</para>
</listitem>
<listitem>
<para>database name:
<quote>bugs_db</quote>
if you're following these directions</para>
</listitem>
<listitem>
<para>MySQL username:
<quote>bugs_user</quote>
if you're following these directions</para>
</listitem>
<listitem>
<para>Password for the
<quote>bugs_user</quote>
MySQL account; (<quote>bugs_password</quote> above)</para>
</listitem>
</orderedlist>
</para>
<para>Edit the file to change these. Once you are happy with the
settings, <filename>su</filename> to the user
your web server runs as, and re-run
<filename>checksetup.pl</filename>. (Note: on some security-conscious
systems, you may need to change the login shell for the webserver
account before you can do this.)
On this second run, it will create the database and an administrator
account for which you will be prompted to provide information.</para>
<note>
<para>The checksetup.pl script is designed so that you can run it at
any time without causing harm. You should run it after any upgrade to
Bugzilla.</para>
</note>
</section>
<section id="install-perlmodules">
<title>Perl Modules</title>
<para>Don't be intimidated by this long list of modules. See
<xref linkend="install-modules-bundle-bugzilla"/> for a way of
installing all the ones you need with a single command.
</para>
<para>Perl modules can be found using
<glossterm linkend="gloss-cpan">CPAN</glossterm> on Unix based systems or
<glossterm linkend="gloss-ppm">PPM</glossterm> on Win32. The root servers
have a real tendency to bog down, so please use mirrors.
<glossterm linkend="gloss-ppm">PPM</glossterm> on Win32.
</para>
<para>Good instuctions can be found for using each of these services on
......@@ -310,7 +399,6 @@ set-variable = max_allowed_packet=1M
<para>Perl Modules (minimum version):
<orderedlist>
<!-- TODO: Don't think we actually care about AppConfig anymore -->
<listitem>
<para>
<link linkend="install-modules-bundle-bugzilla">Bundle::Bugzilla</link>
......@@ -320,13 +408,6 @@ set-variable = max_allowed_packet=1M
<listitem>
<para>
<link linkend="install-modules-appconfig">AppConfig</link>
(&min-appconfig-ver;)
</para>
</listitem>
<listitem>
<para>
<link linkend="install-modules-cgi">CGI</link>
(&min-cgi-ver;)
</para>
......@@ -334,13 +415,6 @@ set-variable = max_allowed_packet=1M
<listitem>
<para>
<link linkend="install-modules-data-dumper">Data::Dumper</link>
(&min-data-dumper-ver;)
</para>
</listitem>
<listitem>
<para>
<link linkend="install-modules-date-format">Date::Format</link>
(&min-date-format-ver;)
</para>
......@@ -477,14 +551,6 @@ ReadLine support enabled
</calloutlist>
</section>
<section id="install-modules-appconfig">
<title>AppConfig (&min-appconfig-ver;)</title>
<para>Dependency for Template Toolkit. We probably don't need to
specifically check for it anymore.
</para>
</section>
<section id="install-modules-cgi">
<title>CGI (&min-cgi-ver;)</title>
......@@ -500,22 +566,6 @@ ReadLine support enabled
</literallayout>
</section>
<section id="install-modules-data-dumper">
<title>Data::Dumper (&min-data-dumper-ver;)</title>
<para>The Data::Dumper module provides data structure persistence for
Perl (similar to Java's serialization). It comes with later
sub-releases of Perl 5.004, but a re-installation just to be sure it's
available won't hurt anything.
</para>
<literallayout>
CPAN Download Page: <ulink url="http://search.cpan.org/dist/Data-Dumper/"/>
PPM Download Link: <ulink url="http://ppm.activestate.com/PPMPackages/zips/6xx-builds-only/Data-Dumper.zip"/>
Documentation: <ulink url="http://www.perldoc.com/perl5.8.0/lib/Data/Dumper.html"/>
</literallayout>
</section>
<section id="install-modules-date-format">
<title>TimeDate modules (&min-date-format-ver;)</title>
......@@ -637,12 +687,8 @@ ReadLine support enabled
<section id="install-modules-gd">
<title>GD (&min-gd-ver;) [optional]</title>
<para>The GD library was written by Thomas Boutell a long while ago to
programmatically generate images in C. Since then it's become the
defacto standard for programmatic image construction. The Perl bindings
to it found in the GD library are used on millions of web pages to
generate graphs on the fly. That's what Bugzilla will be using it for
so you must install it if you want any of the graphing to work.</para>
<para>You need the GD library if you want any of the graphing to work.
</para>
<note>
<para>The Perl GD library requires some other libraries that may or
......@@ -687,7 +733,7 @@ ReadLine support enabled
</section>
<section id="install-modules-xml-parser">
<title>XML::Parser (&min-xml-parser-ver;) [Optional]</title>
<title>XML::Parser (&min-xml-parser-ver;) [optional]</title>
<para>XML::Parser is used by the <filename>importxml.pl</filename>
script. You only need it if you are going to be importing bugs (such as
......@@ -704,7 +750,7 @@ ReadLine support enabled
</section>
<section id="install-modules-gd-graph">
<title>GD::Graph (&min-gd-graph-ver;) [Optional]</title>
<title>GD::Graph (&min-gd-graph-ver;) [optional]</title>
<para>In addition to GD listed above, the reporting interface of Bugzilla
needs to have the GD::Graph module installed.
......@@ -718,7 +764,7 @@ ReadLine support enabled
</section>
<section id="install-modules-gd-text-align">
<title>GD::Text::Align (&min-gd-text-align-ver;) [Optional]</title>
<title>GD::Text::Align (&min-gd-text-align-ver;) [optional]</title>
<para>GD::Text::Align, as the name implies, is used to draw aligned
strings of text. It is needed by the reporting interface.
......@@ -732,7 +778,7 @@ ReadLine support enabled
</section>
<section id="install-modules-mime-parser">
<title>MIME::Parser (&min-mime-parser-ver;) [Optional]</title>
<title>MIME::Parser (&min-mime-parser-ver;) [optional]</title>
<para>MIME::Parser is only needed if you want to use the e-mail interface
located in the <filename class="directory">contrib</filename> directory.
......@@ -746,7 +792,7 @@ ReadLine support enabled
</section>
<section id="install-modules-patchreader">
<title>PatchReader (&min-patchreader-ver;) [Optional]</title>
<title>PatchReader (&min-patchreader-ver;) [optional]</title>
<para>PatchReader is only needed if you want to use Patch Viewer, a
Bugzilla feature to format patches in a pretty HTML fashion. There are a
......@@ -767,77 +813,13 @@ ReadLine support enabled
<section>
<title>
<filename>checksetup.pl</filename>
</title>
<para>Next, run the magic checksetup.pl script.
This is designed to make sure your perl modules are the correct
version and your MySQL database and other
configuration options are consistent with the Bugzilla CGI files.
It will make sure Bugzilla files and directories have reasonable
permissions, set up the
<filename>data</filename>
directory, and create all the MySQL tables.
</para>
<screen>
<prompt>bash#</prompt> ./checksetup.pl
</screen>
<title>Configuring Bugzilla</title>
<para>
The first time you run it, it will create a file called
<filename>localconfig</filename>.</para>
<para>This file contains a variety of settings you may need to tweak
including how Bugzilla should connect to the MySQL database.</para>
<para>The connection settings include:
<orderedlist>
<listitem>
<para>server's host: just use
<quote>localhost</quote>
if the MySQL server is local</para>
</listitem>
<listitem>
<para>database name:
<quote>bugs_db</quote>
if you're following these directions</para>
</listitem>
<listitem>
<para>MySQL username:
<quote>bugs_user</quote>
if you're following these directions</para>
</listitem>
<listitem>
<para>Password for the
<quote>bugs_user</quote>
MySQL account; (<quote>bugs_password</quote> above)</para>
</listitem>
</orderedlist>
Once checksetup.pl has run successfully, Bugzilla should start up.
Proceed to the correct URL and log in with the administrator account
you defined in the last checksetup.pl run.
</para>
<para>Once you are happy with the settings,
<filename>su</filename> to the user
your web server runs as, and re-run
<filename>checksetup.pl</filename>. (Note: on some security-conscious
systems, you may need to change the login shell for the webserver
account before you can do this.)
On this second run, it will create the database and an administrator
account for which you will be prompted to provide information.</para>
<note>
<para>The checksetup.pl script is designed so that you can run it at
any time without causing harm. You should run it after any upgrade to
Bugzilla.</para>
</note>
</section>
<section>
<title>Configuring Bugzilla</title>
<para>
You should run through the parameters on the Edit Parameters page
(link in the footer) and set them all to appropriate values.
......
docs/xml/introduction.xml
View file @ 96a0037a
......@@ -17,30 +17,23 @@
<section id="why-tracking">
<title>Why use a bug-tracking system?</title>
<para>For many years, defect-tracking software was principally
the domain of large software development houses. Most smaller shops
simply relied on
shared lists and email to monitor the status of defects. This procedure
was error-prone and tended to cause those bugs judged least significant by
developers to be dropped or ignored.</para>
<para>Integrated
defect-tracking systems reduce downtime, increase productivity, and raise
customer satisfaction with their systems. Along with full disclosure, an
open bug-tracker allows you to keep in touch with your clients
and resellers, to communicate about problems effectively throughout the
data management chain. Many corporations have also discovered that
defect-tracking helps reduce costs by providing IT support
accountability, telephone support knowledge bases, and a common,
well-understood method for accounting for unusual system or software
issues.</para>
<para>Those who do not use a bug-tracking system tend to rely on
shared lists, email, spreadsheets and/or Post-It notes to monitor the
status of defects. This procedure
is usually error-prone and tends to cause those bugs judged least
significant by developers to be dropped or ignored.</para>
<para>Integrated defect-tracking systems make sure that nothing gets
swept under the carpet; they provide a method of creating, storing,
arranging and processing defect reports and enhancement requests.</para>
</section>
<section id="why-bugzilla">
<title>Why use Bugzilla?</title>
<para>Bugzilla boasts many advanced features. These include:
<para>Bugzilla is the leading open-source/free software bug tracking
system. It boasts many advanced features, including:
<itemizedlist>
<listitem>
<para>Powerful searching</para>
......@@ -75,12 +68,12 @@
</listitem>
<listitem>
<para>Web, XML, email and console interfaces</para>
<para>Completely customisable and/or localisable web user
interface</para>
</listitem>
<listitem>
<para>Completely customisable and/or localisable web user
interface</para>
<para>Additional XML, email and console interfaces</para>
</listitem>
<listitem>
......@@ -102,8 +95,7 @@
<ulink url="http://www.cvshome.org">CVS</ulink>,
<ulink url="http://www.mozilla.org/bonsai.html">Bonsai</ulink>, or
<ulink url="http://www.perforce.com">Perforce SCM</ulink>, Bugzilla
provides a powerful, easy-to-use solution to configuration management and
replication problems.</para>
provides a powerful, easy-to-use configuration management solution.</para>
</section>
</chapter>
......
docs/xml/using.xml
View file @ 96a0037a
......@@ -3,14 +3,17 @@
<chapter id="using">
<title>Using Bugzilla</title>
<para>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
<ulink url="http://landfill.bugzilla.org/bugzilla-tip/">Landfill</ulink>,
which you are welcome to play with (if it's up.)
However, it does not necessarily
have all Bugzilla features enabled, and runs an up-to-the-minute version,
so some things may not quite work as this document describes.</para>
<section id="using-intro">
<title>Introduction</title>
<para>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
<ulink url="http://landfill.bugzilla.org/bugzilla-tip/">Landfill</ulink>,
which you are welcome to play with (if it's up.)
However, it does not necessarily
have all Bugzilla features enabled, and runs an up-to-the-minute version,
so some things may not quite work as this document describes.</para>
</section>
<section id="myaccount">
<title>Create a Bugzilla Account</title>
......@@ -296,6 +299,12 @@
of each bug.</member>
<member>
<emphasis>CSV:</emphasis>
get the buglist as comma-separated values, for import into e.g.
a spreadsheet.</member>
<member>
<emphasis>Change Columns:</emphasis>
change the bug attributes which appear in the list.</member>
......@@ -313,11 +322,18 @@
Sends mail to the owners of all bugs on the list.</member>
<member>
<emphasis>Edit this query:</emphasis>
<emphasis>Edit Search:</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 revisions
to the query you just made so you get more accurate results.</member>
<member>
<emphasis>Remember Search As:</emphasis>
You can give a search a name and remember it; a link will appear
in your page footer giving you quick access to run it again later.
</member>
</simplelist>
</para>
</section>
......@@ -365,6 +381,24 @@
<para>Select "Commit" and send in your bug report.</para>
</listitem>
</orderedlist>
<para>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</para>
<para>
You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</para>
<para>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</para>
</section>
<section id="patchviewer">
......@@ -552,27 +586,6 @@
out of the bug.
</para>
</section>
<section>
<title>Filing Bugs</title>
<para>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</para>
<para>
You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</para>
<para>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</para>
</section>
</section>
<section id="userpreferences">
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment