Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Big checkin of docs to resolve every

Browse Source 
known outstanding doc bug! Yay release.
Still many things to fix. Aren't there always?


git-svn-id: svn://10.0.0.236/trunk@101604 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
barnboy%trilobyte.net
2001-08-22 03:44:35 +00:00
parent 6a8e0d6f5b
commit 305a7218e6
67 changed files with 12582 additions and 9171 deletions
Download Patch File Download Diff File Expand all files Collapse all files

68
mozilla/webtools/bugzilla/docs/README.docs
View File

@@ -38,12 +38,74 @@ point, but for now they are convenient and don't hurt anything.
documentation. Please address comments and questions to the newsgroup:
news://news.mozilla.org/netscape/public/mozilla/webtools .
==========
HOW TO SET UP YOUR OWN SGML EDITING ENVIRONMENT:
==========
Trying to set up an SGML/XML Docbook editing environment the
first time can be a daunting task.
I use Linux-Mandrake, in part, because it has a fully-functional
SGML/XML Docbook editing environment included as part of the
distribution CD's. If you have easier instructions for how to
do this for a particular Linux distribution or platform, please
let the team know at the mailing list: mozilla-webtools@mozilla.org.
The following text is taken nearly verbatim from
http://bugzilla.mozilla.org/show_bug.cgi?id=95970, where I gave
these instructions to someone who wanted the greater manageability
maintaining a document in Docbook brings:
This is just off the top of my head, but here goes. Note some of these may
NOT be necessary, but I don't think they hurt anything by being installed.
rpms:
openjade
jadetex
docbook-dtd41-sgml
docbook-style-dsssl
docbook-dtd31-sgml
docbook-style-dsssl-doc
xemacs
psgml
sgml-tools
sgml-common
Set up environment:
in your .bashrc add this line (after installing above RPMS):
export SGML_CATALOG_FILES=/etc/sgml/catalog
Download "ldp.dsl" from the Resources page on linuxdoc.org. This is the
stylesheet I use to get the HTML and text output. It works well, and has a
nice, consistent look with the rest of the linuxdoc documents. You'll have to
adjust the paths in ldp.dsl at the top of the file to reflect the actual
locations of your docbook catalog files. I created a directory,
/usr/share/sgml/docbook/ldp, and put the ldp.dsl file there. I then edited
ldp.dsl and changed two lines near the top:
<!ENTITY docbook.dsl SYSTEM "../dsssl-stylesheets-1.62/html/docbook.dsl" CDATA
dsssl>
...and...
<!ENTITY docbook.dsl SYSTEM "../dsssl-stylesheets-1.62/print/docbook.dsl" CDATA
dsssl>
Note the difference is the top one points to the HTML docbook stylesheet,
and the next one points to the PRINT docbook stylesheet.
You know, this sure looks awful involved. Anyway, once you have this in
place, add to your .bashrc:
export LDP_HOME=/usr/share/sgml/docbook/ldp
I suggest xemacs for editing your SGML/XML Docbook documents. The darn
thing just works, and generally includes PSGML mode by default. You can
download psgml at http://www.sourceforge.net/projects/psgml.
==========
NOTES:
==========
Here are the commands I use to maintain this documentation.
You MUST have DocBook 4.1 set up correctly in order for this to work,
but there's only a single REMARK tag that's incompatible with 3.1.
Maybe I'll downgrade to DocBook 3.1 to make your life easier...
You MUST have DocBook 4.1 set up correctly in order for this to work.
Substitute your own path to "ldp.dsl" for "$LDP_HOME".

5785
mozilla/webtools/bugzilla/docs/html/Bugzilla-Guide.html
View File

File diff suppressed because it is too large Load Diff

13
mozilla/webtools/bugzilla/docs/html/aboutthisguide.html
View File

@@ -81,16 +81,15 @@ NAME="ABOUTTHISGUIDE"
document you see today.
</P
><P
> Despite the lack of updates, Bugzilla is simply the best piece
of bug-tracking software the world has ever seen. This document
is intended to be the comprehensive guide to the installation,
administration, maintenance, and use of the Bugzilla
bug-tracking system.
> Bugzilla is simply the best piece of bug-tracking software the
world has ever seen. This document is intended to be the
comprehensive guide to the installation, administration,
maintenance, and use of the Bugzilla bug-tracking system.
</P
><P
> This release of the Bugzilla Guide is the
<EM
>2.14.0</EM
>2.14</EM
> release. It is so named that it
may match the current version of Bugzilla. The numbering
tradition stems from that used for many free software projects,
@@ -120,7 +119,7 @@ TARGET="_top"
of Bugzilla, as of this writing (August 10, 2001) is 2.14; if
something were seriously wrong with that edition of the Guide,
subsequent releases would receive an additional dotted-decimal
digit to indicate the update (2.14.0.1, 2.14.0.2, etc.).
digit to indicate the update (2.14.1, 2.14.2, etc.).
Got it? Good.
</P
><P

19
mozilla/webtools/bugzilla/docs/html/administration.html
View File

@@ -177,11 +177,20 @@ COLOR="RED"
do with it?
</FONT
><P
> So you followed the installation instructions to the letter, and
just logged into bugzilla with your super-duper god account and
you are sitting at the query screen. Yet, you have nothing to
query. Your first act of business needs to be to setup the
operating parameters for bugzilla.
> So you followed <SPAN
CLASS="QUOTE"
>"<A
HREF="installation.html"
>Bugzilla Installation</A
>"</SPAN
> to the
letter, and logged into Bugzilla for the very first time with your
super-duper god account. You sit, contentedly staring at the
Bugzilla Query Screen, the worst of the whole mad business of
installing this terrific program behind you. It seems, though, you
have nothing yet to query! Your first act of business should be to
setup the operating parameters for Bugzilla so you can get busy
getting data into your bug tracker.
</P
></DIV
><DIV

18
mozilla/webtools/bugzilla/docs/html/bonsai.html
View File

@@ -74,7 +74,23 @@ NAME="BONSAI"
>5.1. Bonsai</A
></H1
><P
>We need Bonsai integration information.</P
>Bonsai is a web-based tool for managing <A
HREF="cvs.html"
>CVS, the Concurrent Versioning System</A
>
. Using Bonsai, administrators can control open/closed status
of trees, query a fast relational database back-end for change,
branch, and comment information, and view changes made since the
last time the tree was closed. These kinds of changes cause the
engineer responsible to be <SPAN
CLASS="QUOTE"
>"on the hook"</SPAN
> (include
cool URL link here for Hook policies at mozilla.org). Bonsai
also includes gateways to <A
HREF="tinderbox.html"
>Tinderbox, the Mozilla automated build management system</A
> and Bugzilla </P
></DIV
><DIV
CLASS="NAVFOOTER"

2
mozilla/webtools/bugzilla/docs/html/cmdline.html
View File

@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="CMDLINE"
>D.2. Command-line Bugzilla Queries</A
>D.3. Command-line Bugzilla Queries</A
></H1
><P
> Users can query Bugzilla from the command line using this suite

2
mozilla/webtools/bugzilla/docs/html/conventions.html
View File

@@ -79,7 +79,7 @@ NAME="CONVENTIONS"
><DIV
CLASS="INFORMALTABLE"
><A
NAME="AEN135"
NAME="AEN129"
></A
><P
></P

2
mozilla/webtools/bugzilla/docs/html/copyright.html
View File

@@ -74,7 +74,7 @@ NAME="COPYRIGHT"
>1.2. Copyright Information</A
></H1
><A
NAME="AEN76"
NAME="AEN70"
></A
><TABLE
BORDER="0"

18
mozilla/webtools/bugzilla/docs/html/cvs.html
View File

@@ -74,7 +74,23 @@ NAME="CVS"
>5.2. CVS</A
></H1
><P
>CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</P
>CVS integration is best accomplished, at this point, using
the Bugzilla Email Gateway. There have been some files
submitted to allow greater CVS integration, but we need to make
certain that Bugzilla is not tied into one particular software
management package.</P
><P
> Follow the instructions in the FAQ for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to
your Bugzilla e-mail gateway with the subject of <SPAN
CLASS="QUOTE"
>"[Bug
XXXX]"</SPAN
>, and you can have CVS check-in comments append
to your Bugzilla bug. If you have your check-in script include
an @resolution field, you can even change the Bugzilla bug
state.
</P
></DIV
><DIV
CLASS="NAVFOOTER"

4
mozilla/webtools/bugzilla/docs/html/dbdoc.html
View File

@@ -137,7 +137,7 @@ CLASS="SECTION"
><H2
CLASS="SECTION"
><A
NAME="AEN2089"
NAME="AEN2217"
>C.2.1. Bugzilla Database Basics</A
></H2
><P
@@ -260,7 +260,7 @@ CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="AEN2118"
NAME="AEN2246"
>C.2.1.1. Bugzilla Database Tables</A
></H3
><P

2134
mozilla/webtools/bugzilla/docs/html/faq.html
View File

File diff suppressed because it is too large Load Diff

9
mozilla/webtools/bugzilla/docs/html/future.html
View File

@@ -10,7 +10,7 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Tinderbox"
TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"><LINK
REL="NEXT"
TITLE="The Bugzilla FAQ"
@@ -85,11 +85,12 @@ CLASS="SYNOPSIS"
></TR
></TABLE
><P
>The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do
> The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do
not have more information about it right now, and most of what
went into the "future" section is now present. That stuff was
blue-sky a year ago; MattyT should have me a new document
sometime...</P
sometime...
</P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -131,7 +132,7 @@ HREF="faq.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Tinderbox</TD
>Tinderbox/Tinderbox2</TD
><TD
WIDTH="34%"
ALIGN="center"

137
mozilla/webtools/bugzilla/docs/html/geninstall.html
View File

@@ -78,7 +78,7 @@ CLASS="SECTION"
><H2
CLASS="SECTION"
><A
NAME="AEN837"
NAME="AEN916"
>3.5.1. Modifying Your Running System</A
></H2
><P
@@ -111,7 +111,7 @@ CLASS="SECTION"
><H2
CLASS="SECTION"
><A
NAME="AEN844"
NAME="AEN923"
>3.5.2. Upgrading From Previous Versions</A
></H2
><P
@@ -228,33 +228,132 @@ CLASS="SECTION"
><H2
CLASS="SECTION"
><A
NAME="AEN865"
>3.5.4. UNIX Installation Instructions History</A
NAME="MOD_THROTTLE"
>3.5.4. <TT
CLASS="FILENAME"
>mod_throttle</TT
> and Security</A
></H2
><P
> This document was originally adapted from the Bonsai installation
instructions by Terry Weissman &#60;terry@mozilla.org&#62;.
> It is possible for a user, by mistake or on purpose, to access
the database many times in a row which can result in very slow
access speeds for other users. If your Bugzilla installation
is experiencing this problem , you may install the Apache
module <TT
CLASS="FILENAME"
>mod_throttle</TT
> which can limit
connections by ip-address. You may download this module at
<A
HREF="http://www.snert.com/Software/Throttle/"
TARGET="_top"
>http://www.snert.com/Software/Throttle/</A
>. Follow the instructions to install into your Apache install. <EM
>This module only functions with the Apache web server!</EM
>. You may use the <B
CLASS="COMMAND"
>ThrottleClientIP</B
> command provided by this module to accomplish this goal. See the <A
HREF="http://www.snert.com/Software/Throttle/"
TARGET="_top"
>Module Instructions</A
> for more information. </P
></DIV
><DIV
CLASS="SECTION"
><H2
CLASS="SECTION"
><A
NAME="CONTENT_TYPE"
>3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></H2
><P
>It is possible for a Bugzilla to execute malicious
Javascript code. Due to internationalization concerns, we are
unable to incorporate the code changes necessary to fulfill
the CERT advisory requirements mentioned in <A
HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3"
TARGET="_top"
>http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
>. Executing the following code snippet from a UNIX command shell will rectify the problem if your Bugzilla installation is intended for an English-speaking audience. As always, be sure your Bugzilla installation has a good backup before making changes, and I recommend you understand what the script is doing before executing it. </P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \
do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' &#62;$i.tmp; \
mv $i.tmp $i; done
</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
> All this one-liner command does is search for all instances of
<SPAN
CLASS="QUOTE"
>"Content-type: text/html"</SPAN
> and replaces it with
<SPAN
CLASS="QUOTE"
>"Content-Type: text/html; charset=ISO-8859-1"</SPAN
>.
This specification prevents possible Javascript attacks on the
browser, and is suggested for all English-speaking sites. For
non-english-speaking Bugzilla sites, I suggest changing
<SPAN
CLASS="QUOTE"
>"ISO-8859-1"</SPAN
>, above, to <SPAN
CLASS="QUOTE"
>"UTF-8"</SPAN
>.
</P
></DIV
><DIV
CLASS="SECTION"
><H2
CLASS="SECTION"
><A
NAME="AEN964"
>3.5.6. UNIX Installation Instructions History</A
></H2
><P
> This document was originally adapted from the Bonsai
installation instructions by Terry Weissman
&#60;terry@mozilla.org&#62;.
</P
><P
> The February 25, 1999 re-write of this page was done by Ry4an Brase
&#60;ry4an@ry4an.org&#62;, with some edits by Terry Weissman, Bryce Nesbitt,
Martin Pool, &#38; Dan Mosedale (But don't send bug reports to them;
report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi ,
project Webtools, component Bugzilla).
> The February 25, 1999 re-write of this page was done by Ry4an
Brase &#60;ry4an@ry4an.org&#62;, with some edits by Terry
Weissman, Bryce Nesbitt, Martin Pool, &#38; Dan Mosedale (But
don't send bug reports to them; report them using bugzilla, at
http://bugzilla.mozilla.org/enter_bug.cgi , project Webtools,
component Bugzilla).
</P
><P
> This document was heavily modified again Wednesday, March 07 2001 to
reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The
securing MySQL section should be changed to become standard procedure
for Bugzilla installations.
> This document was heavily modified again Wednesday, March 07
2001 to reflect changes for Bugzilla 2.12 release by Matthew
P. Barnson. The securing MySQL section should be changed to
become standard procedure for Bugzilla installations.
</P
><P
> Finally, the README in its entirety was marked up in SGML and included into
the Guide on April 24, 2001 by Matt Barnson. Since that time, it's undergone
extensive modification as Bugzilla grew.
> Finally, the README in its entirety was marked up in SGML and
included into the Guide on April 24, 2001 by Matt Barnson.
Since that time, it's undergone extensive modification as
Bugzilla grew.
</P
><P
> Comments from people using this Guide for the first time are particularly welcome.
> Comments from people using this Guide for the first time are
particularly welcome.
</P
></DIV
></DIV

2
mozilla/webtools/bugzilla/docs/html/gfdl.html
View File

@@ -141,7 +141,7 @@ HREF="gfdl_howto.html"
><P
>Version 1.1, March 2000</P
><A
NAME="AEN2249"
NAME="AEN2416"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"

2
mozilla/webtools/bugzilla/docs/html/gfdl_howto.html
View File

@@ -78,7 +78,7 @@ NAME="GFDL_HOWTO"
a copy of the License in the document and put the following
copyright and license notices just after the title page:</P
><A
NAME="AEN2339"
NAME="AEN2506"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"

304
mozilla/webtools/bugzilla/docs/html/glossary.html
View File

@@ -68,7 +68,7 @@ CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
NAME="AEN2344"
NAME="AEN2511"
>0-9, high ascii</A
></H1
><DL
@@ -110,11 +110,27 @@ NAME="GLOSS_A"
><DL
><DT
><B
>There are no entries for A</B
>Apache</B
></DT
><DD
><P
></P
>In this context, Apache is the web server most
commonly used for serving up
<I
CLASS="GLOSSTERM"
>Bugzilla</I
> pages. Contrary to
popular belief, the apache web server has nothing to do
with the ancient and noble Native American tribe, but
instead derived its name from the fact that it was
<SPAN
CLASS="QUOTE"
>"a patchy"</SPAN
> version of the original
<SPAN
CLASS="ACRONYM"
>NCSA</SPAN
> world-wide-web server.</P
></DD
></DL
></DIV
@@ -179,6 +195,139 @@ CLASS="QUOTE"
> is moderately flexible according to
the needs of the organization using it, though.</P
></DD
><DT
><B
>Bugzilla</B
></DT
><DD
><P
> Bugzilla is the industry-standard bug tracking system. It
is quite popular among Open Source enthusiasts.
</P
></DD
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
NAME="GLOSS_C"
></A
></H1
><DL
><DT
><A
NAME="GLOSS_COMPONENT"
><B
>Component</B
></A
></DT
><DD
><P
> A Component is a subsection of a Product. It should be a
narrow category, tailored to your organization. All
Products must contain at least one Component (and, as a
matter of fact, creating a Product with no Components will
create an error in Bugzilla).
</P
></DD
><DT
><A
NAME="GLOSS_CPAN"
><B
><SPAN
CLASS="ACRONYM"
>CPAN</SPAN
></B
></A
></DT
><DD
><P
><SPAN
CLASS="ACRONYM"
>CPAN</SPAN
> stands for the
<SPAN
CLASS="QUOTE"
>"Comprehensive Perl Archive Network"</SPAN
>. CPAN
maintains a large number of extremely useful
<I
CLASS="GLOSSTERM"
>Perl</I
> modules. By themselves, Perl
modules generally do nothing, but when used as part of a
larger program, they provide much-needed algorithms and
functionality.</P
></DD
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
NAME="GLOSS_D"
>D</A
></H1
><DL
><DT
><B
>daemon</B
></DT
><DD
><P
>A daemon is a computer program which runs in the
background. In general, most daemons are started at boot
time via System V init scripts, or through RC scripts on
BSD-based systems. <I
CLASS="GLOSSTERM"
>mysqld</I
>, the
MySQL server, and <I
CLASS="GLOSSTERM"
>apache</I
>, a web
server, are generally run as daemons.</P
></DD
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
NAME="GLOSS_G"
></A
></H1
><DL
><DT
><B
>Groups</B
></DT
><DD
><P
>The word <SPAN
CLASS="QUOTE"
>"Groups"</SPAN
> has a very special
meaning to Bugzilla. Bugzilla's main security mechanism
comes by lumping users into groups, and assigning those
groups certain privileges to
<I
CLASS="GLOSSTERM"
>Products</I
> and
<I
CLASS="GLOSSTERM"
>Components</I
> in the
<I
CLASS="GLOSSTERM"
>Bugzilla</I
> database.</P
></DD
></DL
></DIV
><DIV
@@ -208,6 +357,33 @@ CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
NAME="GLOSS_M"
>M</A
></H1
><DL
><DT
><B
>mysqld</B
></DT
><DD
><P
>mysqld is the name of the
<I
CLASS="GLOSSTERM"
>daemon</I
> for the MySQL database. In
general, it is invoked automatically through the use of
the System V init scripts on GNU/Linux and AT&#38;T System
V-based systems, such as Solaris and HP/UX, or through the
RC scripts on BSD-based systems.</P
></DD
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
NAME="GLOSS_P"
>P</A
></H1
@@ -226,7 +402,7 @@ NAME="GLOSS_P"
><DIV
CLASS="EXAMPLE"
><A
NAME="AEN2389"
NAME="AEN2602"
></A
><P
><B
@@ -270,6 +446,22 @@ CLASS="QUOTE"
>.</P
></DIV
></DD
><DT
><B
>Perl</B
></DT
><DD
><P
>First written by Larry Wall, Perl is a remarkable
program language. It has the benefits of the flexibility
of an interpreted scripting language (such as shell
script), combined with the speed and power of a compiled
language, such as C. <I
CLASS="GLOSSTERM"
>Bugzilla</I
> is
maintained in Perl.</P
></DD
></DL
></DIV
><DIV
@@ -323,8 +515,11 @@ NAME="GLOSS_R"
></H1
><DL
><DT
><A
NAME="GLOSS_RECURSION"
><B
>Recursion</B
></A
></DT
><DD
><P
@@ -347,13 +542,114 @@ CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
NAME="GLOSS_S"
>S</A
></H1
><DL
><DT
><B
><SPAN
CLASS="ACRONYM"
>SGML</SPAN
></B
></DT
><DD
><P
><SPAN
CLASS="ACRONYM"
>SGML</SPAN
> stands for <SPAN
CLASS="QUOTE"
>"Standard
Generalized Markup Language"</SPAN
>. Created in the
1980's to provide an extensible means to maintain
documentation based upon content instead of presentation,
<SPAN
CLASS="ACRONYM"
>SGML</SPAN
> has withstood the test of time as
a robust, powerful language.
<I
CLASS="GLOSSTERM"
><SPAN
CLASS="ACRONYM"
>XML</SPAN
></I
> is the
<SPAN
CLASS="QUOTE"
>"baby brother"</SPAN
> of SGML; any valid
<SPAN
CLASS="ACRONYM"
>XML</SPAN
> document it, by definition, a valid
<SPAN
CLASS="ACRONYM"
>SGML</SPAN
> document. The document you are
reading is written and maintained in
<SPAN
CLASS="ACRONYM"
>SGML</SPAN
>, and is also valid
<SPAN
CLASS="ACRONYM"
>XML</SPAN
> if you modify the Document Type
Definition.</P
></DD
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
NAME="GLOSS_T"
>T</A
></H1
><DL
><DT
><A
NAME="GLOSS_TARGET_MILESTONE"
><B
>Target Milestone</B
></A
></DT
><DD
><P
> Target Milestones are Product goals. They are
configurable on a per-Product basis. Most software
development houses have a concept of
<SPAN
CLASS="QUOTE"
>"milestones"</SPAN
> where the people funding a
project expect certain functionality on certain dates.
Bugzilla facilitates meeting these milestones by giving
you the ability to declare by which milestone a bug will be
fixed, or an enhancement will be implemented.
</P
></DD
></DL
></DIV
><DIV
CLASS="GLOSSDIV"
><H1
CLASS="GLOSSDIV"
><A
NAME="GLOSS_Z"
>Z</A
></H1
><DL
><DT
><A
NAME="ZARRO-BOOGS-FOUND"
><B
>Zarro Boogs Found</B
></A
></DT
><DD
><P

4
mozilla/webtools/bugzilla/docs/html/granttables.html
View File

@@ -16,7 +16,7 @@ REL="PREVIOUS"
TITLE="MySQL Bugzilla Database Introduction"
HREF="dbdoc.html"><LINK
REL="NEXT"
TITLE="Bugzilla Variants"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"></HEAD
><BODY
CLASS="SECTION"
@@ -335,7 +335,7 @@ HREF="database.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Bugzilla Variants</TD
>Bugzilla Variants and Competitors</TD
></TR
></TABLE
></DIV

581
mozilla/webtools/bugzilla/docs/html/how.html
View File

@@ -16,7 +16,7 @@ REL="PREVIOUS"
TITLE="Why Should We Use Bugzilla?"
HREF="why.html"><LINK
REL="NEXT"
TITLE="What's in it for me?"
TITLE="Where can I find my user preferences?"
HREF="init4me.html"></HEAD
><BODY
CLASS="SECTION"
@@ -98,19 +98,21 @@ VALIGN="TOP"
></TABLE
><P
> Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or administering
a Bugzilla installation, please consult the Installing and Administering
Bugzilla portions of this Guide. This section is principally aimed towards
developing end-user mastery of Bugzilla, so you may fully enjoy the benefits
afforded by using this reliable open-source bug-tracking software.
requires some time. If you are only interested in installing or
administering a Bugzilla installation, please consult the
Installing and Administering Bugzilla portions of this Guide.
This section is principally aimed towards developing end-user
mastery of Bugzilla, so you may fully enjoy the benefits
afforded by using this reliable open-source bug-tracking
software.
</P
><P
> Throughout this portion of the Guide, we will refer to user account
options available at the Bugzilla test installation,
> Throughout this portion of the Guide, we will refer to user
account options available at the Bugzilla test installation,
<A
HREF="http://landfill.tequilarista.org/"
TARGET="_top"
> landfill.tequilarista.org</A
> landfill.tequilarista.org</A
>.
<DIV
CLASS="NOTE"
@@ -133,32 +135,29 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Some people have run into difficulties completing this tutorial. If
you run into problems, please check the updated, online documentation available
at <A
> Some people have run into difficulties completing this
tutorial. If you run into problems, please check the
updated online documentation available at <A
HREF="http://www.trilobyte.net/barnsons/"
TARGET="_top"
>http://www.trilobyte.net/barnsons</A
>.
If you're still stumped, please subscribe to the newsgroup and provide details of exactly
what's stumping you! If enough people complain, I'll have to fix it in the next
version of this Guide. You can subscribe to the newsgroup at
<A
>. If you're still stumped, please subscribe to the newsgroup and provide details of exactly what's stumping you! If enough people complain, I'll have to fix it in the next version of this Guide. You can subscribe to the newsgroup at <A
HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
TARGET="_top"
> news://news.mozilla.org/netscape.public.mozilla.webtools</A
> news://news.mozilla.org/netscape.public.mozilla.webtools</A
>
</P
></TD
></TR
></TABLE
></DIV
>
Although Landfill serves as a great introduction to Bugzilla, it does not offer
all the options you would have as a user on your own installation of Bugzilla,
nor can it do more than serve as a general introduction to Bugzilla. Additionally,
Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
may work slightly differently than mentioned here.
> Although Landfill serves as a great introduction to
Bugzilla, it does not offer all the options you would have as a
user on your own installation of Bugzilla, nor can it do more
than serve as a general introduction to Bugzilla. Additionally,
Landfill often runs cutting-edge versions of Bugzilla for
testing, so some things may work slightly differently than
mentioned here.
</P
><DIV
CLASS="SECTION"
@@ -169,14 +168,14 @@ NAME="MYACCOUNT"
>2.3.1. Create a Bugzilla Account</A
></H2
><P
> First things first! If you want to use Bugzilla, first you need to create
an account. Consult with the administrator responsible for your installation
of Bugzilla for the URL you should use to access it.
If you're test-driving the end-user Bugzilla experience, use this URL:
<A
> First things first! If you want to use Bugzilla, first you
need to create an account. Consult with the administrator
responsible for your installation of Bugzilla for the URL you
should use to access it. If you're test-driving the end-user
Bugzilla experience, use this URL: <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/"
TARGET="_top"
> http://landfill.tequilarista.org/bugzilla-tip/</A
> http://landfill.tequilarista.org/bugzilla-tip/</A
>
</P
><P
@@ -190,23 +189,40 @@ TYPE="1"
></LI
><LI
><P
> Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself)
in the spaces provided, then select the "Create Account" button.
> Enter your "E-mail address" and "Real Name" (or whatever
name you want to call yourself) in the spaces provided,
then select the "Create Account" button.
</P
></LI
><LI
><P
> Within 5-10 minutes, you should receive an email to the address you provided above,
which contains your login name (generally the same as the email address), and
a password you can use to access your account. This password is randomly generated,
and should be changed at your nearest opportunity (we'll go into how to do it later).
> Within moments, you should receive an email to the address
you provided above, which contains your login name
(generally the same as the email address), and a password
you can use to access your account. This password is
randomly generated, and should be changed at your nearest
opportunity (we'll go into how to do it later).
</P
></LI
><LI
><P
> Click the "Log In" link in the yellow area at the bottom of the page in your browser,
then enter your "E-mail address" and "Password" you just received into the spaces provided,
and select "Login".
> Click the <SPAN
CLASS="QUOTE"
>"Log In"</SPAN
> link in the yellow area at
the bottom of the page in your browser, then enter your
<SPAN
CLASS="QUOTE"
>"E-mail address"</SPAN
> and <SPAN
CLASS="QUOTE"
>"Password"</SPAN
>
you just received into the spaces provided, and select
<SPAN
CLASS="QUOTE"
>"Login"</SPAN
>.
<DIV
CLASS="NOTE"
><P
@@ -228,9 +244,17 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> If you ever forget your password, you can come back to this page, enter your
"E-mail address", then select the "E-mail me a password" button to have your password
mailed to you again so that you can login.
> If you ever forget your password, you can come back to
this page, enter your <SPAN
CLASS="QUOTE"
>"E-mail address"</SPAN
>,
then select the <SPAN
CLASS="QUOTE"
>"E-mail me a password"</SPAN
>
button to have your password mailed to you again so
that you can login.
</P
></TD
></TR
@@ -258,11 +282,21 @@ ALT="Caution"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Many modern browsers include an "Auto-Complete" or "Form Fill" feature to
remember the user names and passwords you type in at many sites. Unfortunately,
sometimes they attempt to "guess" what you will put in as your password, and guess
wrong. If you notice a text box is already filled out, please overwrite the contents
of the text box so you can be sure to input the correct information.
> Many modern browsers include an
<SPAN
CLASS="QUOTE"
>"Auto-Complete"</SPAN
> or <SPAN
CLASS="QUOTE"
>"Form
Fill"</SPAN
> feature to remember the user names and
passwords you type in at many sites. Unfortunately,
sometimes they attempt to guess what you will put in
as your password, and guess wrong. If you notice a
text box is already filled out, please overwrite the
contents of the text box so you can be sure to input
the correct information.
</P
></TD
></TR
@@ -273,11 +307,15 @@ VALIGN="TOP"
></LI
></OL
><P
> Congratulations! If you followed these directions, you now are the
proud owner of a user account on landfill.tequilarista.org (Landfill) or
your local Bugzilla install. You should now see in your browser a
page called the "Bugzilla Query Page". It may look daunting, but
with this Guide to walk you through it, you will master it in no time.
> Congratulations! If you followed these directions, you now
are the proud owner of a user account on
landfill.tequilarista.org (Landfill) or your local Bugzilla
install. You should now see in your browser a page called the
<SPAN
CLASS="QUOTE"
>"Bugzilla Query Page"</SPAN
>. It may look daunting, but with this
Guide to walk you through it, you will master it in no time.
</P
></DIV
><DIV
@@ -289,16 +327,27 @@ NAME="QUERY"
>2.3.2. The Bugzilla Query Page</A
></H2
><P
> The Bugzilla Query Page is the heart and soul of Bugzilla. It is the master
interface where you can find any bug report, comment, or patch currently in the Bugzilla
system. We'll go into how to create your own bug report later on.
> The Bugzilla Query Page is the heart and soul of the Bugzilla
user experience. It is the master interface where you can
find any bug report, comment, or patch currently in the
Bugzilla system. We'll go into how to create your own bug
report later on.
</P
><P
> There are efforts underway to simplify query usage. If you have a local installation
of Bugzilla 2.12 or higher, you should have "quicksearch.html" available
to use and simplify your searches. There is also, or shortly will be, a helper
for the query interface, called "queryhelp.cgi". Landfill tends to run the latest code,
so these two utilities should be available there for your perusal.
> There are efforts underway to simplify query usage. If you
have a local installation of Bugzilla 2.12 or higher, you
should have <TT
CLASS="FILENAME"
>quicksearch.html</TT
> available to
use and simplify your searches. There is also a helper for
the query interface, called
<TT
CLASS="FILENAME"
>queryhelp.cgi</TT
>. Landfill tends to run the
latest code, so these two utilities should be available there
for your perusal.
</P
><P
> At this point, please visit the main Bugzilla site,
@@ -309,23 +358,32 @@ TARGET="_top"
>, to see a more fleshed-out query page.
</P
><P
> The first thing you need to notice about the Bugzilla Query Page is that
nearly every box you see on your screen has a hyperlink nearby, explaining what
it is or what it does. Near the upper-left-hand corner of your browser window
you should see the word "Status" underlined. Select it.
> The first thing you need to notice about the Bugzilla Query
Page is that nearly every box you see on your screen has a
hyperlink nearby, explaining what it is or what it does. Near
the upper-left-hand corner of your browser window you should
see the word <SPAN
CLASS="QUOTE"
>"Status"</SPAN
> underlined. Select it.
</P
><P
> Notice the page that popped up? Every underlined word you see on your screen
is a hyperlink that will take you to context-sensitive help.
Click around for a while, and learn what everything here does. To return
to the query interface after pulling up a help page, use the "Back" button in
your browser.
> Notice the page that popped up? Every underlined word you see
on your screen is a hyperlink that will take you to
context-sensitive help. Click around for a while, and learn
what everything here does. To return to the query interface
after pulling up a help page, use the <SPAN
CLASS="QUOTE"
>"Back"</SPAN
>
button in your browser.
</P
><P
> I'm sure that after checking out the online help, you are now an Expert
on the Bugzilla Query Page. If, however, you feel you haven't mastered it yet,
let me walk you through making a few successful queries to find out what there
are in the Bugzilla bug-tracking system itself.
> I'm sure that after checking out the online help, you are now
an expert on the Bugzilla Query Page. If, however, you feel
you haven't mastered it yet, let me walk you through making a
few successful queries to find out what there are in the
Bugzilla bug-tracking system itself.
</P
><P
></P
@@ -333,27 +391,37 @@ TARGET="_top"
TYPE="1"
><LI
><P
> Ensure you are back on the "Bugzilla Query Page"
Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys",
"Priority", or "Severity". The default query for "Status" is to find all bugs that
are NEW, ASSIGNED, or REOPENED, which is what we want. If you don't select anything
in the other 5 scrollboxes there, then you are saying that "any of these are OK";
we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95"
OpSys (Operating System). You're smart, I think you have it figured out.
> Ensure you are back on the <SPAN
CLASS="QUOTE"
>"Bugzilla Query
Page"</SPAN
>. Do nothing in the boxes marked "Status",
"Resolution", "Platform", "OpSys", "Priority", or
"Severity". The default query for "Status" is to find all
bugs that are NEW, ASSIGNED, or REOPENED, which is what we
want. If you don't select anything in the other 5
scrollboxes there, then you are saying that "any of these
are OK"; we're not locking ourselves into only finding
bugs on the "DEC" Platform, or "Windows 95" OpSys
(Operating System). You're smart, I think you have it
figured out.
</P
><P
> Basically, selecting <EM
>anything</EM
> on the query page narrows your search
down. Leaving stuff unselected, or text boxes unfilled, broadens your search!
> on the
query page narrows your search down. Leaving stuff
unselected, or text boxes unfilled, broadens your search.
</P
></LI
><LI
><P
> You see the box immediately below the top six boxes that contains an "Email" text box,
with the words "matching as", a drop-down selection box, then some checkboxes with
"Assigned To" checked by default? This allows you to filter your search down based upon
email address. Let's put my email address in there, and see what happens.
> You see the box immediately below the top six boxes that
contains an "Email" text box, with the words "matching
as", a drop-down selection box, then some checkboxes with
"Assigned To" checked by default? This allows you to
filter your search down based upon email address. Let's
put my email address in there, and see what happens.
</P
><P
> Type "barnboy@trilobyte.net" in the top Email text box.
@@ -361,24 +429,29 @@ TYPE="1"
></LI
><LI
><P
> Let's narrow the search some more. Scroll down until you find the box with the word
"Program" over the top of it. This is where we can narrow our search down to only
specific products (software programs or product lines) in our Bugzilla database.
Please notice the box is a <EM
> Let's narrow the search some more. Scroll down until you
find the box with the word "Program" over the top of it.
This is where we can narrow our search down to only
specific products (software programs or product lines) in
our Bugzilla database. Please notice the box is a
<EM
>scrollbox</EM
>. Using the down arrow on the
scrollbox, scroll down until you can see an entry called "Webtools". Select this entry.
>. Using the down arrow on
the scrollbox, scroll down until you can see an entry
called "Webtools". Select this entry.
</P
></LI
><LI
><P
> Did you notice that some of the boxes to the right changed when you selected "Webtools"?
Every Program (or Product) has different Versions, Components, and Target Milestones associated
with it. A "Version" is the number of a software program.
> Did you notice that some of the boxes to the right changed
when you selected "Webtools"? Every Program (or Product)
has different Versions, Components, and Target Milestones
associated with it. A "Version" is the number of a
software program.
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN297"
NAME="AEN307"
></A
><P
><B
@@ -387,42 +460,45 @@ NAME="AEN297"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN299"
NAME="AEN309"
></A
><P
></P
><P
> Do you remember the hype in 1995 when Microsoft Windows 95(r) was released?
It may have been several years
ago, but Microsoft(tm) spent over $300 Million advertising this new Version of their
software. Three years later, they released Microsoft Windows 98(r),
another new version, to great fanfare, and then in 2000 quietly
released Microsoft Windows ME(Millenium Edition)(r).
> Do you remember the hype in 1995 when Microsoft
Windows 95(r) was released? It may have been several
years ago, but Microsoft(tm) spent over $300 Million
advertising this new Version of their software.
Three years later, they released Microsoft Windows
98(r), another new version, to great fanfare, and
then in 2000 quietly released Microsoft Windows
ME(Millenium Edition)(r).
</P
><P
> Software "Versions" help a manufacturer differentiate
their current product from their
previous products. Most do not identify their products
by the year they were released.
Instead, the "original" version of their software will
often be numbered "1.0", with
small bug-fix releases on subsequent tenths of a digit. In most cases, it's not
a decimal number; for instance, often 1.9 is an <EM
> Software "Versions" help a manufacturer
differentiate their current product from their
previous products. Most do not identify their
products by the year they were released. Instead,
the "original" version of their software will often
be numbered "1.0", with small bug-fix releases on
subsequent tenths of a digit. In most cases, it's
not a decimal number; for instance, often 1.9 is an
<EM
>older</EM
> version
of the software than 1.11,
but is a <EM
> version of the software
than 1.11, but is a <EM
>newer</EM
> version than 1.1.1.
>
version than 1.1.1.
</P
><P
> In general, a "Version" in Bugzilla should refer to
> In general, a "Version" in Bugzilla should refer to
<EM
>released</EM
>
products, not products that have not yet been released
to the public. Forthcoming products
are what the Target Milestone field is for.
> products, not products
that have not yet been released to the public.
Forthcoming products are what the Target Milestone
field is for.
</P
><P
></P
@@ -439,7 +515,7 @@ NAME="AEN299"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN307"
NAME="AEN317"
></A
><P
><B
@@ -448,7 +524,7 @@ NAME="AEN307"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN309"
NAME="AEN319"
></A
><P
></P
@@ -535,26 +611,25 @@ BORDER="0"
>
</P
><P
> A "Milestone", or "Target Milestone" is a often a planned future "Version" of a
product. In many cases, though, Milestones simply represent significant dates for
a developer. Having certain features in your Product is frequently
tied to revenue (money)
the developer will receive if the features work by the time she
reaches the Target Milestone.
Target Milestones are a great tool to organize your time.
If someone will pay you $100,000 for
incorporating certain features by a certain date,
those features by that Milestone date become
a very high priority. Milestones tend to be highly malleable creatures,
though, that appear
to be in reach but are out of reach by the time the important day arrives.
> A "Milestone", or "Target Milestone" is a often a planned
future "Version" of a product. In many cases, though,
Milestones simply represent significant dates for a
developer. Having certain features in your Product is
frequently tied to revenue (money) the developer will
receive if the features work by the time she reaches the
Target Milestone. Target Milestones are a great tool to
organize your time. If someone will pay you $100,000 for
incorporating certain features by a certain date, those
features by that Milestone date become a very high
priority. Milestones tend to be highly malleable
creatures, though, that appear to be in reach but are out
of reach by the time the important day arrives.
</P
><P
> The Bugzilla Project has set up Milestones for future
Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However,
a Target Milestone can just as easily be a specific date,
code name, or weird alphanumeric
combination, like "M19".
> The Bugzilla Project has set up Milestones for future
Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a
Target Milestone can just as easily be a specific date,
code name, or weird alphanumeric combination, like "M19".
</P
></LI
><LI
@@ -571,25 +646,25 @@ BORDER="0"
></LI
><LI
><P
> Congratulations! You've completed your first Query, and have before you the Bug List
of the author of this Guide, Matthew P. Barnson (barnboy@trilobyte.net). If I'm
doing well,
you'll have a cryptic "Zarro Boogs Found" message on your screen. It is just
a happy hacker's way of saying "Zero Bugs Found". However, I am fairly certain I will
> Congratulations! You've completed your first Query, and
have before you the Bug List of the author of this Guide,
Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing
well, you'll have a cryptic "Zarro Boogs Found" message on
your screen. It is just a happy hacker's way of saying
"Zero Bugs Found". However, I am fairly certain I will
always have some bugs assigned to me that aren't done yet,
so you won't often see that message!
</P
></LI
></OL
><P
> I encourage you to click the bug numbers in the left-hand column and examine
my bugs. Also notice that if you click the underlined
links near the top of this page, they do
not take you to context-sensitive help here,
but instead sort the columns of bugs on the screen!
When you need to sort your bugs by priority, severity,
or the people they are assigned to, this
is a tremendous timesaver.
> I encourage you to click the bug numbers in the left-hand
column and examine my bugs. Also notice that if you click the
underlined links near the top of this page, they do not take
you to context-sensitive help here, but instead sort the
columns of bugs on the screen! When you need to sort your bugs
by priority, severity, or the people they are assigned to,
this is a tremendous timesaver.
</P
><P
> A couple more interesting things about the Bug List page:
@@ -602,37 +677,37 @@ BORDER="0"
><TD
><EM
>Change Columns</EM
>:
by selecting this link, you can show all kinds
of information in the Bug List</TD
>: by selecting
this link, you can show all kinds of information in the
Bug List</TD
></TR
><TR
><TD
><EM
>Change several bugs at once</EM
>:
If you have sufficient rights to change all
the bugs shown in the Bug List, you can mass-modify them.
This is a big time-saver.</TD
>: If
you have sufficient rights to change all the bugs shown in
the Bug List, you can mass-modify them. This is a big
time-saver.</TD
></TR
><TR
><TD
><EM
>Send mail to bug owners</EM
>:
If you have many related bugs, you can request
an update from every person who owns the bugs in
the Bug List asking them the status.</TD
>: If you
have many related bugs, you can request an update from
every person who owns the bugs in the Bug List asking them
the status.</TD
></TR
><TR
><TD
><EM
>Edit this query</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
>: 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
></TBODY
></TABLE
@@ -661,17 +736,14 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> There are many more options to the Bugzilla Query Page
and the Bug List than I have shown you.
But this should be enough for you to learn to get around.
I encourage you to check out the
<A
> There are many more options to the Bugzilla Query Page and
the Bug List than I have shown you. But this should be
enough for you to learn to get around. I encourage you to
check out the <A
HREF="http://www.mozilla.org/bugs/"
TARGET="_top"
>Bugzilla Home Page</A
>
to learn about the Anatomy
and Life Cycle of a Bug before continuing.
> to learn about the Anatomy and Life Cycle of a Bug before continuing.
</P
></TD
></TR
@@ -720,30 +792,33 @@ NAME="BUG_WRITING"
>2.3.3.1. Writing a Great Bug Report</A
></H3
><P
> Before we plunge into writing your first bug report, I encourage you to read
<A
> Before we plunge into writing your first bug report, I
encourage you to read some bug-writing guidelines. If you
are reading this document as part of a Bugzilla CVS checkout
or un-tarred Bugzilla distribution, you should be able to
read them by clicking <A
HREF="../../bugwritinghelp.html"
TARGET="_top"
>here</A
>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <A
HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html"
TARGET="_top"
>Mozilla.org's Bug
Writing Guidelines</A
>. While some of the advice is Mozilla-specific, the basic
principles of reporting Reproducible, Specific bugs, isolating the Product you are
using, the Version of the Product, the Component which failed, the Hardware Platform, and
Operating System you were using at the time of the failure go a long way toward ensuring accurate,
responsible fixes for the bug that bit you.
>http://www.mozilla.org/quality/bug-writing-guidelines.html</A
>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you.
</P
><P
> While you are at it, why not learn how to find previously reported bugs? Mozilla.org
has published a great tutorial on finding duplicate bugs, available at
<A
> While you are at it, why not learn how to find previously
reported bugs? Mozilla.org has published a great tutorial
on finding duplicate bugs, available at <A
HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"
TARGET="_top"
> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A
> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A
>.
</P
><P
> I realize this was a lot to read. However, understanding the mentality of writing
great bug reports will help us on the next part!
> I realize this was a lot to read. However, understanding
the mentality of writing great bug reports will help us on
the next part!
</P
><P
></P
@@ -754,18 +829,16 @@ TYPE="1"
> Go back to <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/"
TARGET="_top"
> http://landfill.tequilarista.org/bugzilla-tip/</A
>
in your browser.
> http://landfill.tequilarista.org/bugzilla-tip/</A
> in your browser.
</P
></LI
><LI
><P
> Select the
<A
> Select the <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"
TARGET="_top"
> Enter a new bug report</A
> Enter a new bug report</A
> link.
</P
></LI
@@ -776,11 +849,11 @@ TARGET="_top"
></LI
><LI
><P
> Now you should be at the "Enter Bug" form.
The "reporter" should have been automatically filled out
for you (or else Bugzilla prompted you to Log In again
-- you did keep the email with your username
and password, didn't you?).
> Now you should be at the "Enter Bug" form. The
"reporter" should have been automatically filled out for
you (or else Bugzilla prompted you to Log In again --
you did keep the email with your username and password,
didn't you?).
</P
></LI
><LI
@@ -790,36 +863,37 @@ TARGET="_top"
></LI
><LI
><P
> Bugzilla should have made reasonable guesses, based upon your browser,
for the "Platform" and "OS" drop-down
boxes. If those are wrong, change them -- if you're on an SGI box
running IRIX, we want to know!
> Bugzilla should have made reasonable guesses, based upon
your browser, for the "Platform" and "OS" drop-down
boxes. If those are wrong, change them -- if you're on
an SGI box running IRIX, we want to know!
</P
></LI
><LI
><P
> Fill in the "Assigned To" box with the email address you provided earlier.
This way you don't end up sending copies of your bug to lots of other people,
since it's just a test bug.
> Fill in the "Assigned To" box with the email address you
provided earlier. This way you don't end up sending
copies of your bug to lots of other people, since it's
just a test bug.
</P
></LI
><LI
><P
> Leave the "CC" text box blank.
Fill in the "URL" box with "http://www.mozilla.org".
> Leave the "CC" text box blank. Fill in the "URL" box
with "http://www.mozilla.org".
</P
></LI
><LI
><P
> Enter "The Bugzilla Guide" in the Summary text box,
and place any comments you have on this
tutorial, or the Guide in general, into the Description box.
> Enter "The Bugzilla Guide" in the Summary text box, and
place any comments you have on this tutorial, or the
Guide in general, into the Description box.
</P
></LI
></OL
><P
> Voila! Select "Commit" and send in your bug report!
Next we'll look at resolving bugs.
> Voila! Select "Commit" and send in your bug report! Next
we'll look at resolving bugs.
</P
></DIV
><DIV
@@ -831,10 +905,10 @@ NAME="BUG_MANAGE"
>2.3.3.2. Managing your Bug Reports</A
></H3
><P
> OK, you should have a link to the bug you just created near the top of your page.
It should say
"Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX".
Select this link.
> OK, you should have a link to the bug you just created near
the top of your page. It should say "Bug XXXX posted", with
a link to the right saying "Back to BUG# XXXX". Select this
link.
</P
><P
></P
@@ -842,35 +916,32 @@ NAME="BUG_MANAGE"
TYPE="1"
><LI
><P
> Scroll down a bit on the subsequent page,
until you see the "Resolve bug, changing resolution to (dropdown box).
Normally, you would
"Accept bug (change status to ASSIGNED)", fix it, and then resolve.
But in this case, we're
going to short-circuit the process because this wasn't a real bug.
Change the dropdown next to
"Resolve Bug" to "INVALID", make sure the radio button is
marked next to "Resolve Bug", then
click "Commit".
> Scroll down a bit on the subsequent page, until you see
the "Resolve bug, changing resolution to (dropdown box).
Normally, you would "Accept bug (change status to
ASSIGNED)", fix it, and then resolve. But in this case,
we're going to short-circuit the process because this
wasn't a real bug. Change the dropdown next to "Resolve
Bug" to "INVALID", make sure the radio button is marked
next to "Resolve Bug", then click "Commit".
</P
></LI
><LI
><P
> Hey! It said it couldn't take the change in a big red box!
That's right, you must specify
a Comment in order to make this change. Select the "Back"
button in your browser, add a
Comment, then try Resolving the bug with INVALID status again.
This time it should work.
> Hey! It said it couldn't take the change in a big red
box! That's right, you must specify a Comment in order
to make this change. Select the "Back" button in your
browser, add a Comment, then try Resolving the bug with
INVALID status again. This time it should work.
</P
></LI
></OL
><P
> You have now learned the basics of Bugzilla navigation,
entering a bug, and bug maintenance.
I encourage you to explore these features, and see what you can do with them!
We'll spend no more time on individual Bugs or Queries from this point on, so you are
on your own there.
entering a bug, and bug maintenance. I encourage you to
explore these features, and see what you can do with them!
We'll spend no more time on individual Bugs or Queries from
this point on, so you are on your own there.
</P
><P
> But I'll give a few last hints!
@@ -880,41 +951,29 @@ TYPE="1"
HREF="http://bugzilla.mozilla.org/help.html"
TARGET="_top"
>CLUE</A
>
on the Query page
that will teach you more how to use the form.
> on the Query page that will teach you more how to use the form.
</P
><P
> If you click the hyperlink on the
<A
> If you click the hyperlink on the <A
HREF="http://bugzilla.mozilla.org/describecomponents.cgi"
TARGET="_top"
>Component</A
>
box of the Query page, you will be presented a form that will describe what all
the components are.
> box of the Query page, you will be presented a form that will describe what all the components are.
</P
><P
> Possibly the most powerful feature of the Query page is the
> Possibly the most powerful feature of the Query page is the
<A
HREF="http://bugzilla.mozilla.org/booleanchart.html"
TARGET="_top"
>Boolean Chart</A
> section.
It's a bit confusing to use the first time, but can provide unparalleled
flexibility in your queries,
allowing you to build extremely powerful requests.
> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests.
</P
><P
> Finally, you can build some nifty
<A
> Finally, you can build some nifty <A
HREF="http://bugzilla.mozilla.org/reports.cgi"
TARGET="_top"
>Reports</A
>
using the "Bug Reports" link near the bottom of the query page, and also
available via the "Reports" link
at the footer of each page.
> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page.
</P
></DIV
></DIV
@@ -972,7 +1031,7 @@ HREF="using.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>What's in it for me?</TD
>Where can I find my user preferences?</TD
></TR
></TABLE
></DIV

150
mozilla/webtools/bugzilla/docs/html/index.html
View File

@@ -77,12 +77,6 @@ CLASS="ADDRESS"
></DIV
></DIV
><BR></SPAN
><H4
CLASS="EDITEDBY"
>Edited by</H4
><H3
CLASS="EDITOR"
>I. P. Freely</H3
><DIV
CLASS="REVHISTORY"
><TABLE
@@ -192,7 +186,7 @@ COLSPAN="3"
><DIV
CLASS="ABSTRACT"
><A
NAME="AEN46"
NAME="AEN39"
></A
><P
></P
@@ -213,6 +207,12 @@ NAME="AEN46"
Bugzilla.
</P
><P
> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
ADDITIONS TO THE GUIDE WRITTEN IN HTML!
</P
><P
></P
></DIV
></DIV
@@ -336,7 +336,7 @@ HREF="how.html#BUG_MANAGE"
><DT
>2.4. <A
HREF="init4me.html"
>What's in it for me?</A
>Where can I find my user preferences?</A
></DT
><DD
><DL
@@ -409,12 +409,12 @@ HREF="stepbystep.html"
><DL
><DT
>3.2.1. <A
HREF="stepbystep.html#AEN478"
HREF="stepbystep.html#AEN486"
>Introduction</A
></DT
><DT
>3.2.2. <A
HREF="stepbystep.html#AEN484"
HREF="stepbystep.html#AEN492"
>Installing the Prerequisites</A
></DT
><DT
@@ -429,77 +429,80 @@ HREF="stepbystep.html#INSTALL-PERL"
></DT
><DT
>3.2.5. <A
HREF="stepbystep.html#AEN537"
HREF="stepbystep.html#AEN579"
>DBI Perl Module</A
></DT
><DT
>3.2.6. <A
HREF="stepbystep.html#AEN574"
HREF="stepbystep.html#AEN617"
>Data::Dumper Perl Module</A
></DT
><DT
>3.2.7. <A
HREF="stepbystep.html#AEN578"
HREF="stepbystep.html#AEN622"
>MySQL related Perl Module Collection</A
></DT
><DT
>3.2.8. <A
HREF="stepbystep.html#AEN587"
HREF="stepbystep.html#AEN631"
>TimeDate Perl Module Collection</A
></DT
><DT
>3.2.9. <A
HREF="stepbystep.html#AEN590"
HREF="stepbystep.html#AEN635"
>GD Perl Module (1.8.3)</A
></DT
><DT
>3.2.10. <A
HREF="stepbystep.html#AEN596"
HREF="stepbystep.html#AEN644"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
>3.2.11. <A
HREF="stepbystep.html#AEN599"
HREF="stepbystep.html#AEN648"
>DB_File Perl Module</A
></DT
><DT
>3.2.12. <A
HREF="stepbystep.html#AEN602"
HREF="stepbystep.html#AEN651"
>HTTP Server</A
></DT
><DT
>3.2.13. <A
HREF="stepbystep.html#AEN616"
HREF="stepbystep.html#AEN669"
>Installing the Bugzilla Files</A
></DT
><DT
>3.2.14. <A
HREF="stepbystep.html#AEN636"
HREF="stepbystep.html#AEN696"
>Setting Up the MySQL Database</A
></DT
><DT
>3.2.15. <A
HREF="stepbystep.html#AEN675"
>Tweaking "localconfig"</A
HREF="stepbystep.html#AEN743"
>Tweaking <TT
CLASS="FILENAME"
>localconfig</TT
></A
></DT
><DT
>3.2.16. <A
HREF="stepbystep.html#AEN704"
HREF="stepbystep.html#AEN781"
>Setting Up Maintainers Manually (Optional)</A
></DT
><DT
>3.2.17. <A
HREF="stepbystep.html#AEN713"
HREF="stepbystep.html#AEN792"
>The Whining Cron (Optional)</A
></DT
><DT
>3.2.18. <A
HREF="stepbystep.html#AEN723"
HREF="stepbystep.html#AEN802"
>Bug Graphs (Optional)</A
></DT
><DT
>3.2.19. <A
HREF="stepbystep.html#AEN735"
HREF="stepbystep.html#AEN814"
>Securing MySQL</A
></DT
></DL
@@ -523,12 +526,12 @@ HREF="geninstall.html"
><DL
><DT
>3.5.1. <A
HREF="geninstall.html#AEN837"
HREF="geninstall.html#AEN916"
>Modifying Your Running System</A
></DT
><DT
>3.5.2. <A
HREF="geninstall.html#AEN844"
HREF="geninstall.html#AEN923"
>Upgrading From Previous Versions</A
></DT
><DT
@@ -541,7 +544,20 @@ CLASS="FILENAME"
></DT
><DT
>3.5.4. <A
HREF="geninstall.html#AEN865"
HREF="geninstall.html#MOD_THROTTLE"
><TT
CLASS="FILENAME"
>mod_throttle</TT
> and Security</A
></DT
><DT
>3.5.5. <A
HREF="geninstall.html#CONTENT_TYPE"
>Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></DT
><DT
>3.5.6. <A
HREF="geninstall.html#AEN964"
>UNIX Installation Instructions History</A
></DT
></DL
@@ -694,7 +710,7 @@ HREF="scm.html"
><DT
>5.4. <A
HREF="tinderbox.html"
>Tinderbox</A
>Tinderbox/Tinderbox2</A
></DT
></DL
></DD
@@ -734,14 +750,14 @@ HREF="dbdoc.html"
><DL
><DT
>C.2.1. <A
HREF="dbdoc.html#AEN2089"
HREF="dbdoc.html#AEN2217"
>Bugzilla Database Basics</A
></DT
><DD
><DL
><DT
>C.2.1.1. <A
HREF="dbdoc.html#AEN2118"
HREF="dbdoc.html#AEN2246"
>Bugzilla Database Tables</A
></DT
></DL
@@ -758,7 +774,7 @@ HREF="granttables.html"
><DT
>7. <A
HREF="variants.html"
>Bugzilla Variants</A
>Bugzilla Variants and Competitors</A
></DT
><DD
><DL
@@ -767,6 +783,31 @@ HREF="variants.html"
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
></DT
><DT
>7.2. <A
HREF="variant_fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>7.3. <A
HREF="variant_issuezilla.html"
>Issuezilla</A
></DT
><DT
>7.4. <A
HREF="variant_scarab.html"
>Scarab</A
></DT
><DT
>7.5. <A
HREF="variant_perforce.html"
>Perforce SCM</A
></DT
><DT
>7.6. <A
HREF="variant_sourceforge.html"
>SourceForge</A
></DT
></DL
></DD
><DT
@@ -778,16 +819,24 @@ HREF="patches.html"
><DL
><DT
>D.1. <A
HREF="rewrite.html"
>Apache <TT
CLASS="FILENAME"
>mod_rewrite</TT
> magic</A
></DT
><DT
>D.2. <A
HREF="setperl.html"
>The setperl.csh Utility</A
></DT
><DT
>D.2. <A
>D.3. <A
HREF="cmdline.html"
>Command-line Bugzilla Queries</A
></DT
><DT
>D.3. <A
>D.4. <A
HREF="quicksearch.html"
>The Quicksearch Utility</A
></DT
@@ -879,72 +928,73 @@ CLASS="LOT"
></DT
><DT
>2-1. <A
HREF="how.html#AEN297"
HREF="how.html#AEN307"
>Some Famous Software Versions</A
></DT
><DT
>2-2. <A
HREF="how.html#AEN307"
HREF="how.html#AEN317"
>Mozilla Webtools Components</A
></DT
><DT
>3-1. <A
HREF="stepbystep.html#AEN625"
HREF="stepbystep.html#AEN685"
>Setting up bonsaitools symlink</A
></DT
><DT
>3-2. <A
HREF="stepbystep.html#AEN697"
HREF="stepbystep.html#AEN774"
>Running checksetup.pl as the web user</A
></DT
><DT
>3-3. <A
HREF="win32.html#AEN910"
HREF="win32.html#AEN1012"
>Installing ActivePerl ppd Modules on Microsoft Windows</A
></DT
><DT
>3-4. <A
HREF="win32.html#AEN1084"
>Removing encrypt() for Windows NT installations</A
HREF="win32.html#AEN1180"
>Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</A
></DT
><DT
>4-1. <A
HREF="programadmin.html#AEN1279"
HREF="programadmin.html#AEN1413"
>Creating some Components</A
></DT
><DT
>4-2. <A
HREF="programadmin.html#AEN1308"
HREF="programadmin.html#AEN1442"
>Common Use of Versions</A
></DT
><DT
>4-3. <A
HREF="programadmin.html#AEN1312"
HREF="programadmin.html#AEN1446"
>A Different Use of Versions</A
></DT
><DT
>4-4. <A
HREF="programadmin.html#AEN1340"
HREF="programadmin.html#AEN1474"
>Using SortKey with Target Milestone</A
></DT
><DT
>4-5. <A
HREF="programadmin.html#AEN1376"
HREF="programadmin.html#AEN1510"
>When to Use Group Security</A
></DT
><DT
>4-6. <A
HREF="programadmin.html#AEN1393"
HREF="programadmin.html#AEN1527"
>Creating a New Group</A
></DT
><DT
>D-1. <A
HREF="setperl.html#AEN2193"
HREF="setperl.html#AEN2360"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
HREF="glossary.html#AEN2389"
HREF="glossary.html#AEN2602"
>A Sample Product</A
></DT
></DL

241
mozilla/webtools/bugzilla/docs/html/init4me.html
View File

@@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
>What's in it for me?</TITLE
>Where can I find my user preferences?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="INIT4ME"
>2.4. What's in it for me?</A
>2.4. Where can I find my user preferences?</A
></H1
><TABLE
BORDER="0"
@@ -101,15 +101,13 @@ VALIGN="TOP"
></TR
></TABLE
><P
> Customized User Preferences offer tremendous versatility to
your individual Bugzilla experience.
Let's plunge into what you can do! The first step is to click
the "Edit prefs" link at the footer of each page once you
have logged in to
<A
> Customized User Preferences offer tremendous versatility to your
individual Bugzilla experience. Let's plunge into what you can
do! The first step is to click the "Edit prefs" link at the
footer of each page once you have logged in to <A
HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1"
TARGET="_top"
> Landfill</A
> Landfill</A
>.
</P
><DIV
@@ -122,16 +120,29 @@ NAME="ACCOUNTSETTINGS"
></H2
><P
> On this page, you can change your basic Account Settings,
including your password and full name.
For security reasons, in order to change anything on this page you
must type your <EM
including your password and full name. For security reasons,
in order to change anything on this page you must type your
<EM
>current</EM
>
password into the "Old Password" field.
If you wish to change your password, type the new password you
want into the "New Password" field and again into the "Re-enter
new password" field to ensure
you typed your new password correctly. Select the "Submit" button and you're done!
> password into the <SPAN
CLASS="QUOTE"
>"Old
Password"</SPAN
> field. If you wish to change your
password, type the new password you want into the <SPAN
CLASS="QUOTE"
>"New
Password"</SPAN
> field and again into the <SPAN
CLASS="QUOTE"
>"Re-enter
new password"</SPAN
> field to ensure you typed your new
password correctly. Select the <SPAN
CLASS="QUOTE"
>"Submit"</SPAN
> button
and you are done.
</P
></DIV
><DIV
@@ -150,78 +161,30 @@ CLASS="SECTION"
NAME="NOTIFICATION"
>2.4.2.1. Email Notification</A
></H3
><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 email notification settings described below have been obsoleted in Bugzilla 2.12, and
this section will be replaced with a comprehensive description of the amazing array of
new options at your disposal. However, in the meantime, throw this chunk out the window
and go crazy with goofing around with different notification options.
</P
></TD
></TR
></TABLE
></DIV
><P
> Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
In the drop-down "Notify me of changes to", select one of
<P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
><EM
>All qualifying bugs</EM
>: sends you every change to every bug
where your name is somewhere on it, regardless of who changed it.</TD
></TR
><TR
><TD
><EM
>Only those bugs which I am listed in the CC line</EM
>: prevents
you from receiving mail for which you are the reporter,'
owner, or QA contact. If you are on the CC
list, presumably someone had a <EM
>good</EM
>
reason for you to get the email.</TD
></TR
><TR
><TD
><EM
>All qulifying bugs except those which I change</EM
>:
This is the default, and
a sensible setting. If someone else changes your bugs, you will get emailed,
but if you change bugs
yourself you will receive no notification of the change.</TD
></TR
></TBODY
></TABLE
><P
></P
>
> Here you can reduce or increase the amount of email sent you
from Bugzilla. Although this is referred to as
<SPAN
CLASS="QUOTE"
>"Advanced Email Filtering Options"</SPAN
>, they are,
in fact, the standard email filter set. All of them are
self-explanatory, but you can use the filters in interesting
ways. For instance, some people (notably Quality Assurance
personnel) often only care to receive updates regarding a
bug when the bug changes state, so they can track bugs on
their flow charts and know when it is time to pull the bug
onto a quality assurance platform for inspection. Other
people set up email gateways to
<A
HREF="bonsai.html"
>Bonsai, the Mozilla automated CVS management system</A
> or <A
HREF="tinderbox.html"
>Tinderbox, the Mozilla automated build management system</A
>, and
restrict which types of Bugzilla information are fed to
these systems..
</P
></DIV
><DIV
@@ -253,27 +216,30 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> This option may not be available in all Bugzilla installations, depending upon
the preferences of the systems administrator responsible for the setup of your Bugzilla.
However, if you really want this functionality, ask her to "enable newemailtech
in Params"
and "make it the default for all new users", referring her to the Administration section
of this Guide.
> This option may not be available in all Bugzilla
installations, depending upon the preferences of the
systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality,
ask her to "enable newemailtech in Params" and "make it
the default for all new users", referring her to the
Administration section of this Guide.
</P
></TD
></TR
></TABLE
></DIV
><P
> Disregard the warnings about "experimental and bleeding edge"; the code to handle email
in a cleaner manner than that historically used for Bugzilla is
quite robust and well-tested now.
> Disregard the warnings about "experimental and bleeding
edge"; the code to handle email in a cleaner manner than
that historically used for Bugzilla is quite robust and
well-tested now.
</P
><P
> I recommend you enable the option, "Click here to sign up (and risk any bugs)".
Your email-box
will thank you for it. The fundamental shift in "newemailtech" is away from standard UNIX
"diff" output, which is quite ugly, to a prettier, better laid-out email.
> I recommend you enable the option, "Click here to sign up
(and risk any bugs)". Your email-box will thank you for it.
The fundamental shift in "newemailtech" is away from
standard UNIX "diff" output, which is quite ugly, to a
prettier, better laid-out email.
</P
></DIV
><DIV
@@ -305,20 +271,25 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> This option may not be available in all Bugzilla installations, depending upon
the preferences of the systems administrator responsible for the setup of your Bugzilla.
However, if you really want this functionality, ask her to "enable watchers in Params".
> This option may not be available in all Bugzilla
installations, depending upon the preferences of the
systems administrator responsible for the setup of your
Bugzilla. However, if you really want this functionality,
ask her to "enable watchers in Params".
</P
></TD
></TR
></TABLE
></DIV
><P
> By entering user email names into the "Users to watch" text entry box, delineated by commas,
you can watch bugs of other users. This powerful functionality enables seamless transitions
as developers change projects, managers wish to get in touch with the issues faced by their
direct reports, or users go on vacation. If any of these three situations apply
to you, you will undoubtedly find this feature quite convenient.
> By entering user email names into the "Users to watch" text
entry box, delineated by commas, you can watch bugs of other
users. This powerful functionality enables seamless
transitions as developers change projects, managers wish to
get in touch with the issues faced by their direct reports,
or users go on vacation. If any of these three situations
apply to you, you will undoubtedly find this feature quite
convenient.
</P
></DIV
></DIV
@@ -351,20 +322,24 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> By default, this page is quite barren. However, go explore the Query Page some more; you will
find that you can store numerous queries on the server, so if you regularly run a particular query
it is just a drop-down menu away. On this page of Preferences, if you have many stored
queries you can elect to have them always one-click away!
> By default, this page is quite barren. However, go explore
the Query Page some more; you will find that you can store
numerous queries on the server, so if you regularly run a
particular query it is just a drop-down menu away. On this
page of Preferences, if you have many stored queries you can
elect to have them always one-click away!
</P
></TD
></TR
></TABLE
></DIV
><P
> If you have many stored queries on the server, here you will find individual drop-downs for each
stored query. Each drop-down gives you the option of that query appearing on the footer of every
page in Bugzilla! This gives you powerful one-click access to any complex searches you may set up,
and is an excellent way to impress your boss...
> If you have many stored queries on the server, here you will
find individual drop-downs for each stored query. Each
drop-down gives you the option of that query appearing on the
footer of every page in Bugzilla! This gives you powerful
one-click access to any complex searches you may set up, and
is an excellent way to impress your boss...
</P
><DIV
CLASS="TIP"
@@ -387,13 +362,18 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>By default, the "My Bugs" link appears at the bottom of each page. However, this query
gives you both the bugs you have reported, as well as those you are assigned. One of the most
common uses for this page is to remove the "My Bugs" link, replacing it with two other queries,
commonly called "My Bug Reports" and "My Bugs" (but only referencing bugs assigned to you). This
allows you to distinguish those bugs you have reported from those you are assigned. I commonly
set up complex Boolean queries in the Query page and link them to my footer in this page. When
they are significantly complex, a one-click reference can save hours of work.</P
>By default, the "My Bugs" link appears at the bottom of
each page. However, this query gives you both the bugs you
have reported, as well as those you are assigned. One of
the most common uses for this page is to remove the "My
Bugs" link, replacing it with two other queries, commonly
called "My Bug Reports" and "My Bugs" (but only referencing
bugs assigned to you). This allows you to distinguish those
bugs you have reported from those you are assigned. I
commonly set up complex Boolean queries in the Query page
and link them to my footer in this page. When they are
significantly complex, a one-click reference can save hours
of work.</P
></TD
></TR
></TABLE
@@ -408,11 +388,12 @@ NAME="PERMISSIONSETTINGS"
>2.4.4. Permissions</A
></H2
><P
> This is a purely informative page which outlines your current permissions on
this installation of Bugzilla. If you have permissions to grant certain permissions to
other users, the "other users" link appears on this page as well as the footer.
For more information regarding user administration, please consult the Administration
section of this Guide.
> This is a purely informative page which outlines your current
permissions on this installation of Bugzilla. If you have
permissions to grant certain permissions to other users, the
"other users" link appears on this page as well as the footer.
For more information regarding user administration, please
consult the Administration section of this Guide.
</P
></DIV
></DIV

58
mozilla/webtools/bugzilla/docs/html/installation.html
View File

@@ -90,12 +90,12 @@ HREF="stepbystep.html"
><DL
><DT
>3.2.1. <A
HREF="stepbystep.html#AEN478"
HREF="stepbystep.html#AEN486"
>Introduction</A
></DT
><DT
>3.2.2. <A
HREF="stepbystep.html#AEN484"
HREF="stepbystep.html#AEN492"
>Installing the Prerequisites</A
></DT
><DT
@@ -110,77 +110,80 @@ HREF="stepbystep.html#INSTALL-PERL"
></DT
><DT
>3.2.5. <A
HREF="stepbystep.html#AEN537"
HREF="stepbystep.html#AEN579"
>DBI Perl Module</A
></DT
><DT
>3.2.6. <A
HREF="stepbystep.html#AEN574"
HREF="stepbystep.html#AEN617"
>Data::Dumper Perl Module</A
></DT
><DT
>3.2.7. <A
HREF="stepbystep.html#AEN578"
HREF="stepbystep.html#AEN622"
>MySQL related Perl Module Collection</A
></DT
><DT
>3.2.8. <A
HREF="stepbystep.html#AEN587"
HREF="stepbystep.html#AEN631"
>TimeDate Perl Module Collection</A
></DT
><DT
>3.2.9. <A
HREF="stepbystep.html#AEN590"
HREF="stepbystep.html#AEN635"
>GD Perl Module (1.8.3)</A
></DT
><DT
>3.2.10. <A
HREF="stepbystep.html#AEN596"
HREF="stepbystep.html#AEN644"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
>3.2.11. <A
HREF="stepbystep.html#AEN599"
HREF="stepbystep.html#AEN648"
>DB_File Perl Module</A
></DT
><DT
>3.2.12. <A
HREF="stepbystep.html#AEN602"
HREF="stepbystep.html#AEN651"
>HTTP Server</A
></DT
><DT
>3.2.13. <A
HREF="stepbystep.html#AEN616"
HREF="stepbystep.html#AEN669"
>Installing the Bugzilla Files</A
></DT
><DT
>3.2.14. <A
HREF="stepbystep.html#AEN636"
HREF="stepbystep.html#AEN696"
>Setting Up the MySQL Database</A
></DT
><DT
>3.2.15. <A
HREF="stepbystep.html#AEN675"
>Tweaking "localconfig"</A
HREF="stepbystep.html#AEN743"
>Tweaking <TT
CLASS="FILENAME"
>localconfig</TT
></A
></DT
><DT
>3.2.16. <A
HREF="stepbystep.html#AEN704"
HREF="stepbystep.html#AEN781"
>Setting Up Maintainers Manually (Optional)</A
></DT
><DT
>3.2.17. <A
HREF="stepbystep.html#AEN713"
HREF="stepbystep.html#AEN792"
>The Whining Cron (Optional)</A
></DT
><DT
>3.2.18. <A
HREF="stepbystep.html#AEN723"
HREF="stepbystep.html#AEN802"
>Bug Graphs (Optional)</A
></DT
><DT
>3.2.19. <A
HREF="stepbystep.html#AEN735"
HREF="stepbystep.html#AEN814"
>Securing MySQL</A
></DT
></DL
@@ -204,12 +207,12 @@ HREF="geninstall.html"
><DL
><DT
>3.5.1. <A
HREF="geninstall.html#AEN837"
HREF="geninstall.html#AEN916"
>Modifying Your Running System</A
></DT
><DT
>3.5.2. <A
HREF="geninstall.html#AEN844"
HREF="geninstall.html#AEN923"
>Upgrading From Previous Versions</A
></DT
><DT
@@ -222,7 +225,20 @@ CLASS="FILENAME"
></DT
><DT
>3.5.4. <A
HREF="geninstall.html#AEN865"
HREF="geninstall.html#MOD_THROTTLE"
><TT
CLASS="FILENAME"
>mod_throttle</TT
> and Security</A
></DT
><DT
>3.5.5. <A
HREF="geninstall.html#CONTENT_TYPE"
>Preventing untrusted Bugzilla content from executing malicious Javascript code</A
></DT
><DT
>3.5.6. <A
HREF="geninstall.html#AEN964"
>UNIX Installation Instructions History</A
></DT
></DL

2
mozilla/webtools/bugzilla/docs/html/integration.html
View File

@@ -94,7 +94,7 @@ HREF="scm.html"
><DT
>5.4. <A
HREF="tinderbox.html"
>Tinderbox</A
>Tinderbox/Tinderbox2</A
></DT
></DL
></DIV

2
mozilla/webtools/bugzilla/docs/html/newversions.html
View File

@@ -74,7 +74,7 @@ NAME="NEWVERSIONS"
>1.4. New Versions</A
></H1
><P
> This is the 2.14.0 version of The Bugzilla Guide. If you are
> This is the 2.14 version of The Bugzilla Guide. If you are
reading this from any source other than those below, please
check one of these mirrors to make sure you are reading an
up-to-date version of the Guide.

37
mozilla/webtools/bugzilla/docs/html/patches.html
View File

@@ -10,11 +10,11 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"><LINK
TITLE="SourceForge"
HREF="variant_sourceforge.html"><LINK
REL="NEXT"
TITLE="The setperl.csh Utility"
HREF="setperl.html"></HEAD
TITLE="Apache mod_rewrite magic"
HREF="rewrite.html"></HEAD
><BODY
CLASS="APPENDIX"
BGCOLOR="#FFFFFF"
@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="rhbugzilla.html"
HREF="variant_sourceforge.html"
>Prev</A
></TD
><TD
@@ -54,7 +54,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="setperl.html"
HREF="rewrite.html"
>Next</A
></TD
></TR
@@ -78,21 +78,31 @@ CLASS="TOC"
></DT
><DT
>D.1. <A
HREF="rewrite.html"
>Apache <TT
CLASS="FILENAME"
>mod_rewrite</TT
> magic</A
></DT
><DT
>D.2. <A
HREF="setperl.html"
>The setperl.csh Utility</A
></DT
><DT
>D.2. <A
>D.3. <A
HREF="cmdline.html"
>Command-line Bugzilla Queries</A
></DT
><DT
>D.3. <A
>D.4. <A
HREF="quicksearch.html"
>The Quicksearch Utility</A
></DT
></DL
></DIV
><P
>Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -109,7 +119,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="rhbugzilla.html"
HREF="variant_sourceforge.html"
>Prev</A
></TD
><TD
@@ -125,7 +135,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="setperl.html"
HREF="rewrite.html"
>Next</A
></TD
></TR
@@ -134,7 +144,7 @@ HREF="setperl.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Red Hat Bugzilla</TD
>SourceForge</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -144,7 +154,10 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The setperl.csh Utility</TD
>Apache <TT
CLASS="FILENAME"
>mod_rewrite</TT
> magic</TD
></TR
></TABLE
></DIV

272
mozilla/webtools/bugzilla/docs/html/postinstall-check.html
View File

@@ -74,8 +74,8 @@ NAME="POSTINSTALL-CHECK"
>4.1. Post-Installation Checklist</A
></H1
><P
> After installation, follow the checklist below to ensure that
you have a successful installation. If you do not see a
> After installation, follow the checklist below to help ensure
that you have a successful installation. If you do not see a
recommended setting for a parameter, consider leaving it at the
default while you perform your initial tests on your Bugzilla
setup.
@@ -86,20 +86,34 @@ CLASS="PROCEDURE"
TYPE="1"
><LI
><P
> Bring up "editparams.cgi" in your web browser. For
instance, to edit parameters at mozilla.org, the URL would
be <A
HREF="http://bugzilla.mozilla.org/editparams.cgi"
TARGET="_top"
> http://bugzilla.mozilla.org/editparams.cgi</A
>, also
available under the "edit parameters" link on your query
page.
> Bring up <TT
CLASS="FILENAME"
>editparams.cgi</TT
> in your web
browser. This should be available as the <SPAN
CLASS="QUOTE"
>"edit
parameters"</SPAN
> link from any Bugzilla screen once you
have logged in.
</P
></LI
><LI
><P
> Set "maintainer" to <EM
>The <SPAN
CLASS="QUOTE"
>"maintainer"</SPAN
> is the email address of
the person responsible for maintaining this Bugzilla
installation. The maintainer need not be a valid Bugzilla
user. Error pages, error emails, and administrative mail
will be sent with the maintainer as the return email
address.</P
><P
> Set <SPAN
CLASS="QUOTE"
>"maintainer"</SPAN
> to <EM
>your</EM
> email address.
This allows Bugzilla's error messages to display your email
@@ -108,28 +122,59 @@ TARGET="_top"
></LI
><LI
><P
> Set "urlbase" to the URL reference for your Bugzilla
installation. If your bugzilla query page is at
http://www.foo.com/bugzilla/query.cgi, your url base is
http://www.foo.com/bugzilla/
>The <SPAN
CLASS="QUOTE"
>"urlbase"</SPAN
> parameter defines the fully
qualified domain name and web server path to your Bugzilla
installation.</P
><P
> For example, if your bugzilla query page is
http://www.foo.com/bugzilla/query.cgi, set your
<SPAN
CLASS="QUOTE"
>"urlbase"</SPAN
> is http://www.foo.com/bugzilla/.
</P
></LI
><LI
><P
><SPAN
CLASS="QUOTE"
>"usebuggroups"</SPAN
> dictates whether or not to
implement group-based security for Bugzilla. If set,
Bugzilla bugs can have an associated groupmask defining
which groups of users are allowed to see and edit the
bug.</P
><P
> Set "usebuggroups" to "on" <EM
>only</EM
> if you
need to restrict access to products. I suggest leaving this
parameter <EM
may wish to restrict access to products. I suggest leaving
this parameter <EM
>off</EM
> while initially testing
your Bugzilla.
> while initially
testing your Bugzilla.
</P
></LI
><LI
><P
> Set "usebuggroupsentry" to "on" if you want to restrict
access to products. Once again, if you are simply testing
> <SPAN
CLASS="QUOTE"
>"usebuggroupsentry"</SPAN
>, when set to
<SPAN
CLASS="QUOTE"
>"on"</SPAN
>, requires that all bugs have an associated
groupmask when submitted. This parameter is made for those
installations where product isolation is a necessity.
</P
><P
> Set "usebuggroupsentry" to "on" if you absolutely need to
restrict access to bugs from the moment they are submitted
through resolution. Once again, if you are simply testing
your installation, I suggest against turning this parameter
on; the strict security checking may stop you from being
able to modify your new entries.
@@ -137,6 +182,24 @@ TARGET="_top"
></LI
><LI
><P
> You run into an interesting problem when Bugzilla reaches a
high level of continuous activity. MySQL supports only
table-level write locking. What this means is that if
someone needs to make a change to a bug, they will lock the
entire table until the operation is complete. Locking for
write also blocks reads until the write is complete. The
<SPAN
CLASS="QUOTE"
>"shadowdb"</SPAN
> parameter was designed to get around
this limitation. While only a single user is allowed to
write to a table at a time, reads can continue unimpeded on
a read-only shadow copy of the database. Although your
database size will double, a shadow database can cause an
enormous performance improvement when implemented on
extremely high-traffic Bugzilla databases.
</P
><P
> Set "shadowdb" to "bug_shadowdb" if you will be running a
*very* large installation of Bugzilla. The shadow database
enables many simultaneous users to read and write to the
@@ -163,9 +226,13 @@ ALIGN="LEFT"
VALIGN="TOP"
><P
> Enabling "shadowdb" can adversely affect the stability
of your installation of Bugzilla. You may frequently
need to manually synchronize your databases, or schedule
nightly syncs via "cron"
of your installation of Bugzilla. You should regularly
check that your database is in sync. It is often
advisable to force a shadow database sync nightly via
<SPAN
CLASS="QUOTE"
>"cron"</SPAN
>.
</P
></TD
></TR
@@ -177,7 +244,13 @@ VALIGN="TOP"
> to use
it, and have repeatedly run into the problem it was designed
to solve -- very long wait times while attempting to commit
a change to the database.
a change to the database. Mozilla.org began needing
<SPAN
CLASS="QUOTE"
>"shadowdb"</SPAN
> when they reached around 40,000
Bugzilla users with several hundred Bugzilla bug changes and
comments per day.
</P
><P
> If you use the "shadowdb" option, it is only natural that
@@ -188,6 +261,40 @@ VALIGN="TOP"
></LI
><LI
><P
><SPAN
CLASS="QUOTE"
>"headerhtml"</SPAN
>, <SPAN
CLASS="QUOTE"
>"footerhtml"</SPAN
>,
<SPAN
CLASS="QUOTE"
>"errorhtml"</SPAN
>, <SPAN
CLASS="QUOTE"
>"bannerhtml"</SPAN
>, and
<SPAN
CLASS="QUOTE"
>"blurbhtml"</SPAN
> are all templates which control
display of headers, footers, errors, banners, and additional
data. We could go into some detail regarding the usage of
these, but it is really best just to monkey around with them
a bit to see what they do. I strongly recommend you copy
your <TT
CLASS="FILENAME"
>data/params</TT
> file somewhere safe
before playing with these values, though. If they are
changed dramatically, it may make it impossible for you to
display Bugzilla pages to fix the problem until you have
restored your <TT
CLASS="FILENAME"
>data/params</TT
> file.</P
><P
> If you have custom logos or HTML you must put in place to
fit within your site design guidelines, place the code in
the "headerhtml", "footerhtml", "errorhtml", "bannerhtml",
@@ -216,10 +323,11 @@ VALIGN="TOP"
> The "headerhtml" text box is the HTML printed out
<EM
>before</EM
> any other code on the page.
If you have a special banner, put the code for it in
"bannerhtml". You may want to leave these settings at
the defaults initially.
> any other code on the page,
except the CONTENT-TYPE header sent by the Bugzilla
engine. If you have a special banner, put the code for
it in "bannerhtml". You may want to leave these settings
at the defaults initially.
</P
></TD
></TR
@@ -230,6 +338,14 @@ VALIGN="TOP"
></LI
><LI
><P
><SPAN
CLASS="QUOTE"
>"passwordmail"</SPAN
> is rather simple. Every
time a user creates an account, the text of this parameter
is read as the text to send to the new user along with their
password message.</P
><P
> Add any text you wish to the "passwordmail" parameter box.
For instance, many people choose to use this box to give a
quick training blurb about how to use Bugzilla at your site.
@@ -237,19 +353,48 @@ VALIGN="TOP"
></LI
><LI
><P
> Ensure "newemailtech" is "on". Your users will thank you.
This is the default in the post-2.12 world, and is only an
issue if you are upgrading.
</P
></LI
><LI
><SPAN
CLASS="QUOTE"
>"useqacontact"</SPAN
> allows you to define an
email address for each component, in addition to that of the
default owner, who will be sent carbon copies of incoming
bugs. The critical difference between a QA Contact and an
Owner is that the QA Contact follows the component. If you
reassign a bug from component A to component B, the QA
Contact for that bug will change with the reassignment,
regardless of owner.</P
><P
><SPAN
CLASS="QUOTE"
>"usestatuswhiteboard"</SPAN
> defines whether you
wish to have a free-form, overwritable field associated with
each bug. The advantage of the Status Whiteboard is that it
can be deleted or modified with ease, and provides an
easily-searchable field for indexing some bugs that have
some trait in common. Many people will put <SPAN
CLASS="QUOTE"
>"help
wanted"</SPAN
>, <SPAN
CLASS="QUOTE"
>"stalled"</SPAN
>, or <SPAN
CLASS="QUOTE"
>"waiting
on reply from somebody"</SPAN
> messages into the Status
Whiteboard field so those who peruse the bugs are aware of
their status even more than that which can be indicated by
the Resolution fields.</P
><P
> Do you want to use the QA Contact ("useqacontact") and
status whiteboard ("usestatuswhiteboard") fields? These
fields are useful because they allow for more flexibility,
particularly when you have an existing Quality Assurance
and/or Release Engineering team, but they may not be needed
for smaller installations.
for many smaller installations.
</P
></LI
><LI
@@ -259,14 +404,26 @@ VALIGN="TOP"
they have untouched new bugs. If you do not plan to use
this feature, simply do not set up the whining cron job
described in the installation instructions, or set this
value to "0".
value to "0" (never whine).
</P
></LI
><LI
><P
><SPAN
CLASS="QUOTE"
>"commenton"</SPAN
> fields allow you to dictate
what changes can pass without comment, and which must have a
comment from the person who changed them. Often,
administrators will allow users to add themselves to the CC
list, accept bugs, or change the Status Whiteboard without
adding a comment as to their reasons for the change, yet
require that most other changes come with an
explanation.</P
><P
> Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users resolve,
reassign, or reopen bugs.
reassign, or reopen bugs at the very least.
<DIV
CLASS="NOTE"
><P
@@ -303,11 +460,38 @@ VALIGN="TOP"
></LI
><LI
><P
> Set "supportwatchers" to "On". This feature is helpful for
team leads to monitor progress in their respective areas,
and can offer many other benefits, such as allowing a
developer to pick up a former engineer's bugs without
requiring her to change all the information in the bug.
>The <SPAN
CLASS="QUOTE"
>"supportwatchers"</SPAN
> option can be an
exceptionally powerful tool in the hands of a power Bugzilla
user. By enabling this option, you allow users to receive
email updates whenever other users receive email updates.
This is, of course, subject to the groupset restrictions on
the bug; if the <SPAN
CLASS="QUOTE"
>"watcher"</SPAN
> would not normally be
allowed to view a bug, the watcher cannot get around the
system by setting herself up to watch the bugs of someone
with bugs outside her priveleges. She would still only
receive email updates for those bugs she could normally
view.</P
><P
>For Bugzilla sites which require strong inter-Product
security to prevent snooping, watchers are not a good
idea.</P
><P
> However, for most sites you should set
<SPAN
CLASS="QUOTE"
>"supportwatchers"</SPAN
> to "On". This feature is
helpful for team leads to monitor progress in their
respective areas, and can offer many other benefits, such as
allowing a developer to pick up a former engineer's bugs
without requiring her to change all the information in the
bug.
</P
></LI
></OL

24
mozilla/webtools/bugzilla/docs/html/programadmin.html
View File

@@ -232,7 +232,7 @@ NAME="COMPONENTS"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN1279"
NAME="AEN1413"
></A
><P
><B
@@ -241,7 +241,7 @@ NAME="AEN1279"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN1281"
NAME="AEN1415"
></A
><P
></P
@@ -387,7 +387,7 @@ NAME="VERSIONS"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN1308"
NAME="AEN1442"
></A
><P
><B
@@ -396,7 +396,7 @@ NAME="AEN1308"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN1310"
NAME="AEN1444"
></A
><P
></P
@@ -418,7 +418,7 @@ NAME="AEN1310"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN1312"
NAME="AEN1446"
></A
><P
><B
@@ -427,7 +427,7 @@ NAME="AEN1312"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN1314"
NAME="AEN1448"
></A
><P
></P
@@ -564,7 +564,7 @@ TYPE="1"
><DIV
CLASS="EXAMPLE"
><A
NAME="AEN1340"
NAME="AEN1474"
></A
><P
><B
@@ -573,7 +573,7 @@ NAME="AEN1340"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN1342"
NAME="AEN1476"
></A
><P
></P
@@ -787,7 +787,7 @@ NAME="GROUPS"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN1376"
NAME="AEN1510"
></A
><P
><B
@@ -796,7 +796,7 @@ NAME="AEN1376"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN1378"
NAME="AEN1512"
></A
><P
></P
@@ -913,7 +913,7 @@ TYPE="1"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN1393"
NAME="AEN1527"
></A
><P
><B
@@ -922,7 +922,7 @@ NAME="AEN1393"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN1395"
NAME="AEN1529"
></A
><P
></P

2
mozilla/webtools/bugzilla/docs/html/quicksearch.html
View File

@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="QUICKSEARCH"
>D.3. The Quicksearch Utility</A
>D.4. The Quicksearch Utility</A
></H1
><P
> Quicksearch is a new, experimental feature of the 2.12 release.

191
mozilla/webtools/bugzilla/docs/html/rewrite.html Normal file
View File

@@ -0,0 +1,191 @@
<HTML
><HEAD
><TITLE
>Apache mod_rewrite magic</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="PREVIOUS"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="NEXT"
TITLE="The setperl.csh Utility"
HREF="setperl.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="patches.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="setperl.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="REWRITE"
>D.1. Apache <TT
CLASS="FILENAME"
>mod_rewrite</TT
> magic</A
></H1
><P
>Apache's <TT
CLASS="FILENAME"
>mod_rewrite</TT
> module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</P
><P
></P
><OL
TYPE="1"
><LI
><P
> Make it so if someone types
<TT
CLASS="COMPUTEROUTPUT"
>http://www.foo.com/12345</TT
>,
Bugzilla spits back
http://www.foo.com/show_bug.cgi?id=12345. Try setting up
your VirtualHost section for Bugzilla with a rule like
this:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>&#60;VirtualHost 12.34.56.78&#62;
RewriteEngine On
RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
&#60;/VirtualHost&#62;
</PRE
></FONT
></TD
></TR
></TABLE
></LI
><LI
><P
>There are many, many more things you can do with
mod_rewrite. As time goes on, I will include many more in
the Guide. For now, though, please refer to the mod_rewrite
documentation at <A
HREF="http://www.apache.org"
TARGET="_top"
>http://www.apache.org</A
></P
></LI
></OL
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="patches.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="setperl.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="patches.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The setperl.csh Utility</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

89
mozilla/webtools/bugzilla/docs/html/rhbugzilla.html
View File

@@ -10,14 +10,14 @@ REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Bugzilla Variants"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="NEXT"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD
TITLE="Loki Bugzilla (Fenris)"
HREF="variant_fenris.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
@@ -51,13 +51,13 @@ HREF="variants.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants</TD
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="patches.html"
HREF="variant_fenris.html"
>Next</A
></TD
></TR
@@ -74,65 +74,20 @@ NAME="RHBUGZILLA"
>7.1. Red Hat Bugzilla</A
></H1
><P
> Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
on the planet.
One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
database, as well as MySQL.
Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
<A
NAME="AEN2143"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
CLASS="LITERALLAYOUT"
> &nbsp;&nbsp;Hello.&nbsp;I&nbsp;apologize&nbsp;that&nbsp;I&nbsp;am&nbsp;getting&nbsp;back&nbsp;to&nbsp;you&nbsp;so&nbsp;late.&nbsp;It&nbsp;has&nbsp;been&nbsp;difficult&nbsp;to&nbsp;keep<br>
up&nbsp;with&nbsp;email&nbsp;this&nbsp;past&nbsp;week.&nbsp;I&nbsp;have&nbsp;checked&nbsp;out&nbsp;your&nbsp;updated&nbsp;documentation&nbsp;and&nbsp;I&nbsp;will<br>
have&nbsp;to&nbsp;say&nbsp;very&nbsp;good&nbsp;work.&nbsp;A&nbsp;few&nbsp;notes&nbsp;and&nbsp;additions&nbsp;as&nbsp;follows.<br>
<br>
(ed:&nbsp;from&nbsp;the&nbsp;FAQ)<br>
&#62;For&nbsp;the&nbsp;record,&nbsp;we&nbsp;are&nbsp;not&nbsp;using&nbsp;any&nbsp;template&nbsp;type&nbsp;implementation&nbsp;for&nbsp;the&nbsp;cosmetic&nbsp;changes&nbsp;<br>
&#62;maded&nbsp;to&nbsp;Bugzilla.&nbsp;It&nbsp;is&nbsp;just&nbsp;alot&nbsp;of&nbsp;html&nbsp;changes&nbsp;in&nbsp;the&nbsp;code&nbsp;itself.&nbsp;I&nbsp;admit&nbsp;I&nbsp;may&nbsp;have&nbsp;<br>
&#62;gotten&nbsp;a&nbsp;little&nbsp;carried&nbsp;away&nbsp;with&nbsp;it&nbsp;but&nbsp;the&nbsp;corporate&nbsp;types&nbsp;asked&nbsp;for&nbsp;a&nbsp;more&nbsp;standardized&nbsp;<br>
&#62;interface&nbsp;to&nbsp;match&nbsp;up&nbsp;with&nbsp;other&nbsp;projects&nbsp;relating&nbsp;to&nbsp;Red&nbsp;Hat&nbsp;web&nbsp;sites.&nbsp;A&nbsp;lot&nbsp;of&nbsp;other&nbsp;web&nbsp;<br>
&#62;based&nbsp;internal&nbsp;tools&nbsp;I&nbsp;am&nbsp;working&nbsp;on&nbsp;also&nbsp;look&nbsp;like&nbsp;Bugzilla.&nbsp;<br>
<br>
<br>
This&nbsp;should&nbsp;probably&nbsp;be&nbsp;changed&nbsp;since&nbsp;we&nbsp;are&nbsp;now&nbsp;in&nbsp;fact&nbsp;using&nbsp;Text::Template&nbsp;for&nbsp;most<br>
of&nbsp;the&nbsp;html&nbsp;rendering.&nbsp;You&nbsp;actually&nbsp;state&nbsp;this&nbsp;later&nbsp;in&nbsp;your&nbsp;numbered&nbsp;list.<br>
<br>
Also&nbsp;number&nbsp;6&nbsp;contradicts&nbsp;number&nbsp;8&nbsp;where&nbsp;number&nbsp;6&nbsp;would&nbsp;be&nbsp;the&nbsp;most&nbsp;up&nbsp;to&nbsp;date&nbsp;status<br>
on&nbsp;the&nbsp;Oracle&nbsp;port.<br>
<br>
Additional&nbsp;Information:<br>
-----------------------------<br>
1.&nbsp;Comments&nbsp;are&nbsp;now&nbsp;stored&nbsp;in&nbsp;varchar&nbsp;fields&nbsp;of&nbsp;4k&nbsp;in&nbsp;size&nbsp;each.&nbsp;If&nbsp;the&nbsp;comment&nbsp;is&nbsp;more<br>
than&nbsp;4k&nbsp;it&nbsp;is&nbsp;broken&nbsp;up&nbsp;into&nbsp;chunks&nbsp;and&nbsp;given&nbsp;a&nbsp;sort&nbsp;number&nbsp;so&nbsp;each&nbsp;comment&nbsp;can&nbsp;be&nbsp;re<br>
assembled&nbsp;in&nbsp;the&nbsp;correct&nbsp;order.&nbsp;This&nbsp;was&nbsp;done&nbsp;because&nbsp;originally&nbsp;I&nbsp;was&nbsp;storing&nbsp;the&nbsp;comments<br>
in&nbsp;a&nbsp;long&nbsp;datatype&nbsp;which&nbsp;unfortunately&nbsp;cannot&nbsp;be&nbsp;indexed&nbsp;or&nbsp;joined&nbsp;with&nbsp;another&nbsp;table.&nbsp;This<br>
cause&nbsp;the&nbsp;search&nbsp;of&nbsp;text&nbsp;within&nbsp;the&nbsp;long&nbsp;description&nbsp;to&nbsp;be&nbsp;disabled&nbsp;for&nbsp;a&nbsp;long&nbsp;time.&nbsp;That<br>
is&nbsp;now&nbsp;working&nbsp;and&nbsp;is&nbsp;nto&nbsp;showing&nbsp;any&nbsp;noticeble&nbsp;performance&nbsp;hit&nbsp;that&nbsp;I&nbsp;can&nbsp;tell.&nbsp;<br>
<br>
2.&nbsp;Work&nbsp;is&nbsp;being&nbsp;started&nbsp;on&nbsp;internationalizing&nbsp;the&nbsp;Bugzilla&nbsp;source&nbsp;we&nbsp;have&nbsp;to&nbsp;allow&nbsp;our<br>
Japanese&nbsp;customers&nbsp;to&nbsp;enter&nbsp;bug&nbsp;reports&nbsp;into&nbsp;a&nbsp;single&nbsp;bugzilla&nbsp;system.&nbsp;This&nbsp;will&nbsp;probably<br>
be&nbsp;done&nbsp;by&nbsp;using&nbsp;the&nbsp;nvarchar&nbsp;data&nbsp;types&nbsp;supported&nbsp;by&nbsp;Oracle&nbsp;which&nbsp;allows&nbsp;storage&nbsp;of<br>
double&nbsp;byte&nbsp;characters&nbsp;and&nbsp;also&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;Accept-Language&nbsp;in&nbsp;the&nbsp;http&nbsp;header&nbsp;for&nbsp;<br>
detection&nbsp;by&nbsp;Bugilla&nbsp;of&nbsp;which&nbsp;language&nbsp;to&nbsp;render.<br>
<br>
3.&nbsp;Of&nbsp;course&nbsp;even&nbsp;more&nbsp;cosmetic&nbsp;changes.&nbsp;It&nbsp;is&nbsp;difficult&nbsp;to&nbsp;keep&nbsp;up&nbsp;with&nbsp;the&nbsp;ever&nbsp;<br>
changing&nbsp;faces&nbsp;of&nbsp;www.redhat.com.<br>
<br>
4.&nbsp;Some&nbsp;convenience&nbsp;enhancements&nbsp;in&nbsp;the&nbsp;administration&nbsp;utilities.&nbsp;And&nbsp;more&nbsp;integration<br>
with&nbsp;other&nbsp;internal/external&nbsp;Red&nbsp;Hat&nbsp;web&nbsp;sites.<br>
<br>
I&nbsp;hope&nbsp;this&nbsp;information&nbsp;may&nbsp;prove&nbsp;helpful&nbsp;for&nbsp;your&nbsp;documentation.&nbsp;Please&nbsp;contact<br>
me&nbsp;if&nbsp;you&nbsp;have&nbsp;any&nbsp;more&nbsp;question&nbsp;or&nbsp;I&nbsp;can&nbsp;do&nbsp;anything&nbsp;else.<br>
<br>
Regards<br>
</P
></BLOCKQUOTE
>
> Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
the ability to work with Oracle, MySQL, and PostGreSQL databases
serving as the back-end, instead of just MySQL. Dave Lawrence
has worked very hard to keep Red Hat Bugzilla up-to-date, and
many people prefer the snappier-looking page layout of Red Hat
Bugzilla to the default Mozilla-standard formatting.
</P
><P
>URL: <A
HREF="http://bugzilla.redhat.com/bugzilla/"
TARGET="_top"
>http://bugzilla.redhat.com/bugzilla/</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"
@@ -165,7 +120,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="patches.html"
HREF="variant_fenris.html"
>Next</A
></TD
></TR
@@ -174,7 +129,7 @@ HREF="patches.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Bugzilla Variants</TD
>Bugzilla Variants and Competitors</TD
><TD
WIDTH="34%"
ALIGN="center"
@@ -187,7 +142,7 @@ HREF="variants.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Useful Patches and Utilities for Bugzilla</TD
>Loki Bugzilla (Fenris)</TD
></TR
></TABLE
></DIV

42
mozilla/webtools/bugzilla/docs/html/scm.html
View File

@@ -16,7 +16,7 @@ REL="PREVIOUS"
TITLE="CVS"
HREF="cvs.html"><LINK
REL="NEXT"
TITLE="Tinderbox"
TITLE="Tinderbox/Tinderbox2"
HREF="tinderbox.html"></HEAD
><BODY
CLASS="SECTION"
@@ -74,36 +74,28 @@ NAME="SCM"
>5.3. Perforce SCM</A
></H1
><P
> You can find the project page for Bugzilla and Teamtrack Perforce integration at:
<A
> You can find the project page for Bugzilla and Teamtrack
Perforce integration (p4dti) at: <A
HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top"
> http://www.ravenbrook.com/project/p4dti</A
>. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public Depot"
p4dti page at <A
> http://www.ravenbrook.com/project/p4dti</A
> . <SPAN
CLASS="QUOTE"
>"p4dti"</SPAN
> is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at <A
HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
TARGET="_top"
> http://public.perforce.com/public/perforce/p4dti/index.html</A
> http://public.perforce.com/public/perforce/p4dti/index.html</A
>.
</P
><P
> Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
patches for 2.12 will be out shortly. Check the project page regularly for updates, or
take the given patches and patch it manually. p4dti is designed to support multiple defect
trackers, and maintains its own documentation for it. Please consult the pages linked
above for further information.
</P
><P
> Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
have synchronization problems, the easiest way to avoid them is to only put the bug
information, comments, etc. into Bugzilla, and not into the Perforce change records.
They will link anyway; merely reference the bug ID fixed in your change description,
and put a comment into Bugzilla
giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
question.
> Integration of Perforce with Bugzilla, once patches are applied,
is seamless. Perforce replication information will appear below
the comments of each bug. Be certain you have a matching set of
patches for the Bugzilla version you are installing. p4dti is
designed to support multiple defect trackers, and maintains its
own documentation for it. Please consult the pages linked above
for further information.
</P
></DIV
><DIV
@@ -159,7 +151,7 @@ HREF="integration.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Tinderbox</TD
>Tinderbox/Tinderbox2</TD
></TR
></TABLE
></DIV

17
mozilla/webtools/bugzilla/docs/html/setperl.html
View File

@@ -13,8 +13,8 @@ REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="PREVIOUS"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
TITLE="Apache mod_rewrite magic"
HREF="rewrite.html"><LINK
REL="NEXT"
TITLE="Command-line Bugzilla Queries"
HREF="cmdline.html"></HEAD
@@ -44,7 +44,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="patches.html"
HREF="rewrite.html"
>Prev</A
></TD
><TD
@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="SETPERL"
>D.1. The setperl.csh Utility</A
>D.2. The setperl.csh Utility</A
></H1
><P
> You can use the "setperl.csh" utility to quickly and
@@ -216,7 +216,7 @@ CLASS="COMMAND"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN2193"
NAME="AEN2360"
></A
><P
><B
@@ -258,7 +258,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="patches.html"
HREF="rewrite.html"
>Prev</A
></TD
><TD
@@ -283,7 +283,10 @@ HREF="cmdline.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Useful Patches and Utilities for Bugzilla</TD
>Apache <TT
CLASS="FILENAME"
>mod_rewrite</TT
> magic</TD
><TD
WIDTH="34%"
ALIGN="center"

990
mozilla/webtools/bugzilla/docs/html/stepbystep.html
View File

File diff suppressed because it is too large Load Diff

6
mozilla/webtools/bugzilla/docs/html/tinderbox.html
View File

@@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
>Tinderbox</TITLE
>Tinderbox/Tinderbox2</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
@@ -71,10 +71,10 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="TINDERBOX"
>5.4. Tinderbox</A
>5.4. Tinderbox/Tinderbox2</A
></H1
><P
>We need Tinderbox integration information</P
>We need Tinderbox integration information.</P
></DIV
><DIV
CLASS="NAVFOOTER"

53
mozilla/webtools/bugzilla/docs/html/useradmin.html
View File

@@ -137,6 +137,15 @@ CLASS="PROMPT"
login name)"; </B
>
</P
><P
>Yes, that is <EM
>fourteen</EM
>
<SPAN
CLASS="QUOTE"
>"f"</SPAN
>'s. A whole lot of f-ing going on if you
want to create a new administator.</P
></TD
></TR
></TABLE
@@ -245,13 +254,16 @@ VALIGN="TOP"
right-hand side of the text entry box. You can match
what you type as a case-insensitive substring (the
default) of all users on your system, a case-sensitive
regular expression (please see the "man regexp" manual
page for details on regular expression syntax), or a
<EM
regular expression (please see the <B
CLASS="COMMAND"
>man
regexp</B
> manual page for details on regular
expression syntax), or a <EM
>reverse</EM
> regular expression match,
where every user name which does NOT match the regular
expression is selected.
>
regular expression match, where every user name which
does NOT match the regular expression is selected.
</P
></TD
></TR
@@ -294,10 +306,17 @@ VALIGN="TOP"
>not</EM
>
send an email informing them of their username and
password. In general, it is preferable to log out and
use the "New Account" button to create users, as it
will pre-populate all the required fields and also
notify the user of her account name and password.
password. While useful for creating dummy accounts
(watchers which shuttle mail to another system, for
instance, or email addresses which are a mailing
list), in general it is preferable to log out and use
the <SPAN
CLASS="QUOTE"
>"New Account"</SPAN
> button to create users,
as it will pre-populate all the required fields and
also notify the user of her account name and
password.
</P
></TD
></TR
@@ -346,6 +365,15 @@ VALIGN="TOP"
> Don't disable your own administrative account, or you
will hate life!
</P
><P
>At this time, <SPAN
CLASS="QUOTE"
>"Disabled Text"</SPAN
> does not
prevent a user from using the email interface. If you
have the email interface enabled, they can still
continue to submit bugs and comments that way. We need
a patch to fix this.</P
></TD
></TR
></TABLE
@@ -419,9 +447,8 @@ VALIGN="TOP"
><P
> <EM
>Password</EM
>: You will only see
asterisks in versions of Bugzilla newer than 2.10 or
early 2.11. You can change the user password here.
>: You can change the user
password here. It is normal to only see asterisks.
</P
></LI
><LI

4
mozilla/webtools/bugzilla/docs/html/using.html
View File

@@ -86,7 +86,7 @@ VALIGN="TOP"
><I
><P
><I
>What, Why, How, &#38; What's in it for me?</I
>What, Why, How, &#38; Where?</I
></P
></I
></TD
@@ -150,7 +150,7 @@ HREF="how.html#BUG_MANAGE"
><DT
>2.4. <A
HREF="init4me.html"
>What's in it for me?</A
>Where can I find my user preferences?</A
></DT
><DD
><DL

16
mozilla/webtools/bugzilla/docs/html/usingbz-conc.html
View File

@@ -13,7 +13,7 @@ REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
REL="PREVIOUS"
TITLE="What's in it for me?"
TITLE="Where can I find my user preferences?"
HREF="init4me.html"><LINK
REL="NEXT"
TITLE="Installation"
@@ -74,16 +74,14 @@ NAME="USINGBZ-CONC"
>2.5. Using Bugzilla-Conclusion</A
></H1
><P
> Thank you for reading through this portion of the Bugzilla Guide. I anticipate
it may not yet meet the needs of all readers. If you have additional comments or
corrections to make, please submit your contributions to the
<A
> Thank you for reading through this portion of the Bugzilla
Guide. I anticipate it may not yet meet the needs of all
readers. If you have additional comments or corrections to
make, please submit your contributions to the <A
HREF="mailto://mozilla-webtools@mozilla.org"
TARGET="_top"
>mozilla-webtools</A
>
mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools
newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org
> mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org
</P
></DIV
><DIV
@@ -126,7 +124,7 @@ HREF="installation.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>What's in it for me?</TD
>Where can I find my user preferences?</TD
><TD
WIDTH="34%"
ALIGN="center"

142
mozilla/webtools/bugzilla/docs/html/variant_fenris.html Normal file
View File

@@ -0,0 +1,142 @@
<HTML
><HEAD
><TITLE
>Loki Bugzilla (Fenris)</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"><LINK
REL="NEXT"
TITLE="Issuezilla"
HREF="variant_issuezilla.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="rhbugzilla.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant_issuezilla.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="VARIANT_FENRIS"
>7.2. Loki Bugzilla (Fenris)</A
></H1
><P
>Fenris can be found at <A
HREF="http://fenris.lokigames.com/"
TARGET="_top"
>http://fenris.lokigames.com</A
>. It is a fork from Bugzilla.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="rhbugzilla.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant_issuezilla.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Red Hat Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Issuezilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

153
mozilla/webtools/bugzilla/docs/html/variant_issuezilla.html Normal file
View File

@@ -0,0 +1,153 @@
<HTML
><HEAD
><TITLE
>Issuezilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Loki Bugzilla (Fenris)"
HREF="variant_fenris.html"><LINK
REL="NEXT"
TITLE="Scarab"
HREF="variant_scarab.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variant_fenris.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant_scarab.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="VARIANT_ISSUEZILLA"
>7.3. Issuezilla</A
></H1
><P
>Issuezilla is another fork from Bugzilla, and seems nearly
as popular as the Red Hat Bugzilla fork. Some Issuezilla team
members are regular contributors to the Bugzilla mailing
list/newsgroup. Issuezilla is not the primary focus of
bug-tracking at tigris.org, however. Their Java-based
bug-tracker, <A
HREF="variant_scarab.html"
>Scarab, a newfangled Java-based issue tracker</A
>, is under heavy development
and looks promising!</P
><P
>URL: <A
HREF="http://issuezilla.tigris.org/servlets/ProjectHome"
TARGET="_top"
>http://issuezilla.tigris.org/servlets/ProjectHome</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant_fenris.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant_scarab.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Loki Bugzilla (Fenris)</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Scarab</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

148
mozilla/webtools/bugzilla/docs/html/variant_perforce.html Normal file
View File

@@ -0,0 +1,148 @@
<HTML
><HEAD
><TITLE
>Perforce SCM</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Scarab"
HREF="variant_scarab.html"><LINK
REL="NEXT"
TITLE="SourceForge"
HREF="variant_sourceforge.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variant_scarab.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant_sourceforge.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="VARIANT_PERFORCE"
>7.5. Perforce SCM</A
></H1
><P
>Although Perforce isn't really a bug tracker, it can be used
as such through the <SPAN
CLASS="QUOTE"
>"jobs"</SPAN
> functionality.</P
><P
><A
HREF="http://www.perforce.com/perforce/technotes/note052.html"
TARGET="_top"
>http://www.perforce.com/perforce/technotes/note052.html</A
>http://www.perforce.com/perforce/technotes/note052.html</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant_scarab.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant_sourceforge.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Scarab</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>SourceForge</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

148
mozilla/webtools/bugzilla/docs/html/variant_scarab.html Normal file
View File

@@ -0,0 +1,148 @@
<HTML
><HEAD
><TITLE
>Scarab</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Issuezilla"
HREF="variant_issuezilla.html"><LINK
REL="NEXT"
TITLE="Perforce SCM"
HREF="variant_perforce.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variant_issuezilla.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="variant_perforce.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="VARIANT_SCARAB"
>7.4. Scarab</A
></H1
><P
>Scarab is a promising new bug-tracking system built using
Java Serlet technology. As of this writing, no source code has
been released as a package, but you can obtain the code from
CVS.
</P
><P
>URL: <A
HREF="http://scarab.tigris.org/"
TARGET="_top"
>http://scarab.tigris.org</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant_issuezilla.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="variant_perforce.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Issuezilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Perforce SCM</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

148
mozilla/webtools/bugzilla/docs/html/variant_sourceforge.html Normal file
View File

@@ -0,0 +1,148 @@
<HTML
><HEAD
><TITLE
>SourceForge</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants and Competitors"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Perforce SCM"
HREF="variant_perforce.html"><LINK
REL="NEXT"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variant_perforce.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants and Competitors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="patches.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="VARIANT_SOURCEFORGE"
>7.6. SourceForge</A
></H1
><P
>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the
Internet than strictly a bug tracker, but if you're hunting for
bug-tracking for your open project, it may be just what the
software engineer ordered!</P
><P
>URL: <A
HREF="http://www.sourceforge.net"
TARGET="_top"
>http://www.sourceforge.net</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variant_perforce.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="patches.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Perforce SCM</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Useful Patches and Utilities for Bugzilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

79
mozilla/webtools/bugzilla/docs/html/variants.html
View File

@@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
>Bugzilla Variants</TITLE
>Bugzilla Variants and Competitors</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
@@ -67,39 +67,56 @@ CLASS="CHAPTER"
><H1
><A
NAME="VARIANTS"
>Chapter 7. Bugzilla Variants</A
>Chapter 7. Bugzilla Variants and Competitors</A
></H1
><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
> I <EM
>know</EM
> there are more variants than just RedHat Bugzilla out there.
Please help me get information about them, their project status, and benefits there
might be in using them or in using their code in main-tree Bugzilla.
</P
></TD
></TR
></TABLE
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>7.1. <A
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
></DT
><DT
>7.2. <A
HREF="variant_fenris.html"
>Loki Bugzilla (Fenris)</A
></DT
><DT
>7.3. <A
HREF="variant_issuezilla.html"
>Issuezilla</A
></DT
><DT
>7.4. <A
HREF="variant_scarab.html"
>Scarab</A
></DT
><DT
>7.5. <A
HREF="variant_perforce.html"
>Perforce SCM</A
></DT
><DT
>7.6. <A
HREF="variant_sourceforge.html"
>SourceForge</A
></DT
></DL
></DIV
><P
>I created this section to answer questions about Bugzilla
competitors and variants, then found a wonderful site which covers
an awful lot of what I wanted to discuss. Rather than quote it in
its entirety, I'll simply refer you here: <A
HREF="http://linas.org/linux/pm.html"
TARGET="_top"
>http://linas.org/linux/pm.html</A
></P
></DIV
><DIV
CLASS="NAVFOOTER"

42
mozilla/webtools/bugzilla/docs/html/whatis.html
View File

@@ -130,8 +130,10 @@ system against which all others are measured.
></LI
><LI
><P
> available integration with automated software configuration management systems, including
Perforce and CVS
> available integration with automated software
configuration management systems, including Perforce and
CVS (through the Bugzilla email interface and
checkin/checkout scripts)
</P
></LI
><LI
@@ -143,25 +145,33 @@ system against which all others are measured.
>
</P
><P
> Despite its current robustness and popularity, however, Bugzilla
faces some near-term challenges, such as reliance on a single database, a lack of
abstraction of the user interface and program logic, verbose email bug
notifications, a powerful but daunting query interface, little reporting configurability,
problems with extremely large queries, some unsupportable bug resolution options,
no internationalization, and dependence on some nonstandard libraries.
> Despite its current robustness and popularity, Bugzilla faces
some near-term challenges, such as reliance on a single
database, a lack of abstraction of the user interface and
program logic, verbose email bug notifications, a powerful but
daunting query interface, little reporting configurability,
problems with extremely large queries, some unsupportable bug
resolution options, little internationalization (although non-US
character sets are accepted for comments), and dependence on
some nonstandard libraries.
</P
><P
> Some recent headway has been made on the query front, however. If you are using the latest
version of Bugzilla, you should see a "simple search" form on the default front page of
your Bugzilla install. Type in two or three search terms and you should pull up some
relevant information. This is also available as "queryhelp.cgi".
> Some recent headway has been made on the query front, however.
If you are using the latest version of Bugzilla, you should see
a <SPAN
CLASS="QUOTE"
>"simple search"</SPAN
> form on the default front page of
your Bugzilla install. Type in two or three search terms and
you should pull up some relevant information. This is also
available as "queryhelp.cgi".
</P
><P
> Despite these small problems, Bugzilla is very hard to beat. It is under <EM
> Despite these small problems, Bugzilla is very hard to beat. It
is under <EM
>very</EM
>
active development to address the current issues, and a long-awaited overhaul in the form
of Bugzilla 3.0 is expected sometime later this year.
> active development to address
the current issues, and continually gains new features.
</P
></DIV
><DIV

73
mozilla/webtools/bugzilla/docs/html/why.html
View File

@@ -97,23 +97,25 @@ VALIGN="TOP"
></TR
></TABLE
><P
> For many years, defect-tracking software has remained principally the domain
of large software development houses. Even then, most shops never bothered
with bug-tracking software, and instead simply relied on shared lists and
email to monitor the status of defects. This procedure is error-prone and
tends to cause those bugs judged least significant by developers to be
> For many years, defect-tracking software has remained
principally the domain of large software development houses.
Even then, most shops never bothered with bug-tracking software,
and instead simply relied on shared lists and email to monitor
the status of defects. This procedure is error-prone and tends
to cause those bugs judged least significant by developers to be
dropped or ignored.
</P
><P
> These days, many companies are finding that integrated defect-tracking
systems reduce downtime, increase productivity, and raise customer
satisfaction with their systems. Along with full disclosure, an open
bug-tracker allows manufacturers to keep in touch with their clients
and resellers, to communicate about problems effectively throughout
the data management chain. Many corporations have also discovered that
defect-tracking helps reduce costs by providing IT support accountability,
telephone support knowledge bases, and a common, well-understood system
for accounting for unusual system or software issues.
> These days, many companies are finding that integrated
defect-tracking systems reduce downtime, increase productivity,
and raise customer satisfaction with their systems. Along with
full disclosure, an open bug-tracker allows manufacturers to
keep in touch with their clients and resellers, to communicate
about problems effectively throughout the data management chain.
Many corporations have also discovered that defect-tracking
helps reduce costs by providing IT support accountability,
telephone support knowledge bases, and a common, well-understood
system for accounting for unusual system or software issues.
</P
><P
> But why should <EM
@@ -121,28 +123,35 @@ VALIGN="TOP"
> use Bugzilla?
</P
><P
> Bugzilla is very adaptable to various situations. Known uses currently
include IT support queues, Systems Administration deployment management,
chip design and development problem tracking (both pre-and-post fabrication),
and software and hardware bug tracking for luminaries such as Redhat, Loki software,
Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
configuration management and replication problems
> Bugzilla is very adaptable to various situations. Known uses
currently include IT support queues, Systems Administration
deployment management, chip design and development problem
tracking (both pre-and-post fabrication), and software and
hardware bug tracking for luminaries such as Redhat, Loki
software, Linux-Mandrake, and VA Systems. Combined with systems
such as CVS, Bonsai, or Perforce SCM, Bugzilla provides a
powerful, easy-to-use solution to configuration management and
replication problems
</P
><P
> Bugzilla can dramatically increase the productivity and accountability
of individual employees by providing a documented workflow and positive
feedback for good performance. How many times do you wake up in the
morning, remembering that you were supposed to do *something* today,
but you just can't quite remember? Put it in Bugzilla, and you have a record
of it from which you can extrapolate milestones, predict product versions
for integration, and by using Bugzilla's e-mail integration features
be able to follow the discussion trail that led to critical decisions.
> Bugzilla can dramatically increase the productivity and
accountability of individual employees by providing a documented
workflow and positive feedback for good performance. How many
times do you wake up in the morning, remembering that you were
supposed to do <EM
>something</EM
> today, but you
just can't quite remember? Put it in Bugzilla, and you have a
record of it from which you can extrapolate milestones, predict
product versions for integration, and by using Bugzilla's e-mail
integration features be able to follow the discussion trail that
led to critical decisions.
</P
><P
> Ultimately, Bugzilla puts the power in your hands to improve your value
to your employer or business while providing a usable framework for your natural
attention to detail and knowledge store to flourish.
> Ultimately, Bugzilla puts the power in your hands to improve
your value to your employer or business while providing a usable
framework for your natural attention to detail and knowledge
store to flourish.
</P
></DIV
><DIV

358
mozilla/webtools/bugzilla/docs/html/win32.html
View File

@@ -126,7 +126,7 @@ VALIGN="TOP"
of the
<A
HREF="installation.html"
>Chapter 3</A
>Bugzilla Installation</A
> section while performing your
Win32 installation.
</P
@@ -137,13 +137,14 @@ HREF="installation.html"
be a <EM
>very</EM
> skilled Windows Systems
Administrator with both strong troubleshooting abilities and
a high tolerance for pain. Bugzilla on NT requires hacking
source code and implementing some advanced utilities. What
follows is the recommended installation procedure for Win32;
additional suggestions are provided in <A
Administrator with strong troubleshooting abilities, a high
tolerance for pain, and moderate perl skills. Bugzilla on NT
requires hacking source code and implementing some advanced
utilities. What follows is the recommended installation
procedure for Win32; additional suggestions are provided in
<A
HREF="faq.html"
>The Bugzilla FAQ</A
>Appendix A</A
>.
</P
></TD
@@ -159,9 +160,23 @@ TYPE="1"
> Install <A
HREF="http://www.apache.org/"
TARGET="_top"
>Apache Web Server</A
>Apache Web
Server</A
> for Windows, and copy the Bugzilla files
somewhere Apache can serve them. Please follow all the
instructions referenced in <A
HREF="installation.html"
>Bugzilla Installation</A
>
for Windows.
regarding your Apache configuration, particularly
instructions regarding the <SPAN
CLASS="QUOTE"
>"AddHandler"</SPAN
>
parameter and <SPAN
CLASS="QUOTE"
>"ExecCGI"</SPAN
>.
</P
><DIV
CLASS="NOTE"
@@ -184,13 +199,13 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> You may also use Internet Information Server or Personal Web
Server for this purpose. However, setup is slightly more
difficult. If ActivePerl doesn't seem to handle your file
associations correctly (for .cgi and .pl files), please
consult <A
> You may also use Internet Information Server or Personal
Web Server for this purpose. However, setup is quite
different. If ActivePerl doesn't seem to handle your
file associations correctly (for .cgi and .pl files),
please consult <A
HREF="faq.html"
>The Bugzilla FAQ</A
>Appendix A</A
>.
</P
><P
@@ -286,7 +301,7 @@ CLASS="COMMAND"
><DIV
CLASS="EXAMPLE"
><A
NAME="AEN910"
NAME="AEN1012"
></A
><P
><B
@@ -526,13 +541,63 @@ CLASS="FILENAME"
this line:
</P
><P
> "my $webservergid = getgrnam($my_webservergroup); "
> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>my $webservergid = getgrnam($my_webservergroup);
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
> to
</P
><P
> "my $webservergid = $my_webservergroup; "
> <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>my $webservergid = $my_webservergroup;
</PRE
></FONT
></TD
></TR
></TABLE
>
or the name of the group you wish to own the files explicitly:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>my $webservergid = 'Administrators'
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
></LI
><LI
@@ -841,7 +906,31 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The code above needs testing as well to make sure it is correct.</P
> Some have found success using the commercial product,
<SPAN
CLASS="PRODUCTNAME"
>Windmail</SPAN
>.
You could try replacing your sendmail calls with:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t &#62; mail.log";
</PRE
></FONT
></TD
></TR
></TABLE
>
or something to that effect.
</P
></TD
></TR
></TABLE
@@ -1002,9 +1091,9 @@ ALT="Note"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> This step is completely optional if you are using IIS or
another web server which only decides on an interpreter
based upon the file extension (.pl), rather than the
> This step is optional if you are using IIS or another
web server which only decides on an interpreter based
upon the file extension (.pl), rather than the
<SPAN
CLASS="QUOTE"
>"shebang"</SPAN
@@ -1102,10 +1191,11 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> If you are using IIS 5.0 or higher, you must add cgi
> If you are using IIS or Personal Web Server, you must add cgi
relationships to Properties -&#62; Home directory (tab) -&#62;
Application Settings (section) -&#62; Configuration (button),
such as: <TABLE
such as:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
@@ -1164,18 +1254,17 @@ VALIGN="TOP"
><P
> From Andrew Pearson:
<A
NAME="AEN1062"
NAME="AEN1169"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> "You can make Bugzilla work with Personal Web Server for
Windows 98 and higher, as well as for IIS 4.0. Microsoft has
information available at
<A
HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"
> You can make Bugzilla work with Personal Web Server for
Windows 98 and higher, as well as for IIS 4.0.
Microsoft has information available at <A
HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"
TARGET="_top"
> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A
> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A
>
</P
><P
@@ -1225,79 +1314,25 @@ ALT="Tip"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</P
><A
NAME="AEN1072"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> Hi - I am updating bugzilla to 2.12 so I can tell you what I did (after I
deleted the current dir and copied the files in).
</P
><P
> In checksetup.pl, I did the following...
</P
><DIV
CLASS="PROCEDURE"
><OL
TYPE="1"
><LI
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>my $webservergid = getgrnam($my_webservergroup);
</PRE
></FONT
></TD
></TR
></TABLE
><P
>to</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>my $webservergid = 'Administrators'
</PRE
></FONT
></TD
></TR
></TABLE
></LI
><LI
><P
> I then ran checksetup.pl
</P
></LI
><LI
><P
> I removed all the encrypt()
<DIV
> If attempting to run Bugzilla 2.12 or older, you will need
to remove encrypt() calls from the Perl source. This is
<EM
>not necessary</EM
> for Bugzilla 2.13 and
later.
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN1084"
NAME="AEN1180"
></A
><P
><B
>Example 3-4. Removing encrypt() for Windows NT installations</B
>Example 3-4. Removing encrypt() for Windows NT Bugzilla version
2.12 or earlier</B
></P
><P
> Replace this:
<TABLE
> Replace this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
@@ -1307,17 +1342,17 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn();
</PRE
>
SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn();
</PRE
></FONT
></TD
></TR
></TABLE
>
with this:
<TABLE
with this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
@@ -1327,125 +1362,18 @@ WIDTH="100%"
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>my $enteredcryptpwd = $enteredpwd
</PRE
>
my $enteredcryptpwd = $enteredpwd
</PRE
></FONT
></TD
></TR
></TABLE
>
in cgi.pl.
</P
in cgi.pl.
</P
></DIV
>
</P
></LI
><LI
><P
> I renamed processmail to processmail.pl
</P
></LI
><LI
><P
> I altered the sendmail statements to windmail:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="PROGRAMLISTING"
>
open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t &#62; mail.log";
</PRE
></FONT
></TD
></TR
></TABLE
>
</P
><P
> The quotes around the dir is for the spaces. mail.log is for the output
</P
></LI
></OL
></DIV
></BLOCKQUOTE
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> This was some late breaking information from Jan Evert. Sorry for the lack of formatting.
</P
><P
CLASS="LITERALLAYOUT"
>I'm&nbsp;busy&nbsp;installing&nbsp;bugzilla&nbsp;on&nbsp;a&nbsp;WinNT&nbsp;machine&nbsp;and&nbsp;I&nbsp;thought&nbsp;I'd&nbsp;notify&nbsp;you<br>
at&nbsp;this&nbsp;moment&nbsp;of&nbsp;the&nbsp;commments&nbsp;I&nbsp;have&nbsp;to&nbsp;section&nbsp;2.2.1&nbsp;of&nbsp;the&nbsp;bugzilla<br>
guide&nbsp;(at&nbsp;http://www.trilobyte.net/barnsons/html/).<br>
<br>
Step&nbsp;1:<br>
I've&nbsp;used&nbsp;apache,&nbsp;installation&nbsp;is&nbsp;really&nbsp;straightforward.<br>
After&nbsp;reading&nbsp;the&nbsp;Unix&nbsp;installation&nbsp;instructions,&nbsp;I&nbsp;found&nbsp;that&nbsp;it&nbsp;is<br>
necessary&nbsp;to&nbsp;add&nbsp;the&nbsp;ExecCGI&nbsp;option&nbsp;to&nbsp;the&nbsp;bugzilla&nbsp;directory.&nbsp;Also&nbsp;the<br>
'AddHandler'&nbsp;line&nbsp;for&nbsp;.cgi&nbsp;is&nbsp;by&nbsp;default&nbsp;commented&nbsp;out.<br>
<br>
Step&nbsp;3:&nbsp;although&nbsp;just&nbsp;a&nbsp;detail,&nbsp;'ppm&nbsp;install&nbsp;&#60;module%gt;'&nbsp;will&nbsp;also&nbsp;work<br>
(without&nbsp;.ppd).&nbsp;And,&nbsp;it&nbsp;can&nbsp;also&nbsp;download&nbsp;these&nbsp;automatically&nbsp;from<br>
ActiveState.<br>
<br>
Step&nbsp;4:&nbsp;although&nbsp;I&nbsp;have&nbsp;cygwin&nbsp;installed,&nbsp;it&nbsp;seems&nbsp;that&nbsp;it&nbsp;is&nbsp;not&nbsp;necessary.<br>
On&nbsp;my&nbsp;machine&nbsp;cygwin&nbsp;is&nbsp;not&nbsp;in&nbsp;the&nbsp;PATH&nbsp;and&nbsp;everything&nbsp;seems&nbsp;to&nbsp;work&nbsp;as<br>
expected.<br>
However,&nbsp;I've&nbsp;not&nbsp;used&nbsp;everything&nbsp;yet.<br>
<br>
Step&nbsp;6:&nbsp;the&nbsp;'bugs_password'&nbsp;given&nbsp;in&nbsp;SQL&nbsp;command&nbsp;d&nbsp;needs&nbsp;to&nbsp;be&nbsp;edited&nbsp;into<br>
localconfig&nbsp;later&nbsp;on&nbsp;(Step&nbsp;7)&nbsp;if&nbsp;the&nbsp;password&nbsp;is&nbsp;not&nbsp;empty.&nbsp;I've&nbsp;also&nbsp;edited<br>
it&nbsp;into&nbsp;globals.pl,&nbsp;but&nbsp;I'm&nbsp;not&nbsp;sure&nbsp;that&nbsp;is&nbsp;needed.&nbsp;In&nbsp;both&nbsp;places,&nbsp;the<br>
variable&nbsp;is&nbsp;named&nbsp;db_pass.<br>
<br>
Step&nbsp;8:&nbsp;all&nbsp;the&nbsp;sendmail&nbsp;replacements&nbsp;mentioned&nbsp;are&nbsp;not&nbsp;as&nbsp;simple&nbsp;as<br>
described&nbsp;there.&nbsp;Since&nbsp;I&nbsp;am&nbsp;not&nbsp;familiar&nbsp;(yet)&nbsp;with&nbsp;perl,&nbsp;I&nbsp;don't&nbsp;have&nbsp;any<br>
mail&nbsp;working&nbsp;yet.<br>
<br>
Step&nbsp;9:&nbsp;in&nbsp;globals.pl&nbsp;the&nbsp;encrypt()&nbsp;call&nbsp;can&nbsp;be&nbsp;replaced&nbsp;by&nbsp;just&nbsp;the<br>
unencrypted&nbsp;password.&nbsp;In&nbsp;CGI.pl,&nbsp;the&nbsp;complete&nbsp;SQL&nbsp;command&nbsp;can&nbsp;be&nbsp;removed.<br>
<br>
Step&nbsp;11:&nbsp;I've&nbsp;only&nbsp;changed&nbsp;the&nbsp;#!&nbsp;lines&nbsp;in&nbsp;*.cgi.&nbsp;I&nbsp;haven't&nbsp;noticed&nbsp;problems<br>
with&nbsp;the&nbsp;system()&nbsp;call&nbsp;yet.<br>
There&nbsp;seem&nbsp;to&nbsp;be&nbsp;only&nbsp;four&nbsp;system()&nbsp;called&nbsp;programs:&nbsp;processmail.pl&nbsp;(handled<br>
by&nbsp;step&nbsp;10),&nbsp;syncshadowdb&nbsp;(which&nbsp;should&nbsp;probably&nbsp;get&nbsp;the&nbsp;same&nbsp;treatment&nbsp;as<br>
processmail.pl),&nbsp;diff&nbsp;and&nbsp;mysqldump.&nbsp;The&nbsp;last&nbsp;one&nbsp;is&nbsp;only&nbsp;needed&nbsp;with&nbsp;the<br>
shadowdb&nbsp;feature&nbsp;(which&nbsp;I&nbsp;don't&nbsp;use).<br>
<br>
There&nbsp;seems&nbsp;to&nbsp;be&nbsp;one&nbsp;step&nbsp;missing:&nbsp;copying&nbsp;the&nbsp;bugzilla&nbsp;files&nbsp;somehwere<br>
that&nbsp;apache&nbsp;can&nbsp;serve&nbsp;them.<br>
<br>
Just&nbsp;noticed&nbsp;the&nbsp;updated&nbsp;guide...&nbsp;Brian's&nbsp;comment&nbsp;is&nbsp;new.&nbsp;His&nbsp;first&nbsp;comment<br>
will&nbsp;work,&nbsp;but&nbsp;opens&nbsp;up&nbsp;a&nbsp;huge&nbsp;security&nbsp;hole.<br>
</P
></TD
></TR

17
mozilla/webtools/bugzilla/docs/sgml/Bugzilla-Guide.sgml
View File

@@ -23,7 +23,7 @@
<!ENTITY bz-ver "2.14">
<!ENTITY bz-cvs-ver "2.15">
<!ENTITY bzg-date "August 10, 2001">
<!ENTITY bzg-ver "2.14.0">
<!ENTITY bzg-ver "2.14">
<!ENTITY bzg-cvs-ver "2.15.0">
<!ENTITY bzg-auth "Matthew P. Barnson">
<!ENTITY bzg-auth-email "<email>barnboy@NOSPAM.trilobyte.net</email>">
@@ -137,15 +137,6 @@ try to avoid clutter and feel free to waste space in the code to make it more re
</affiliation>
</collab>
<editor>
<firstname>I.</firstname>
<surname>Freely</surname>
<othername>P.</othername>
<affiliation>
<address><email>ipfreely@freely.eye-p.net</email></address>
</affiliation>
</editor>
</authorgroup>
<abstract>
@@ -165,6 +156,12 @@ try to avoid clutter and feel free to waste space in the code to make it more re
professional on operating system upon which you install
Bugzilla.
</para>
<para>
THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
ADDITIONS TO THE GUIDE WRITTEN IN HTML!
</para>
</abstract>

9
mozilla/webtools/bugzilla/docs/sgml/about.sgml
View File

@@ -14,11 +14,10 @@
document you see today.
</para>
<para>
Despite the lack of updates, Bugzilla is simply the best piece
of bug-tracking software the world has ever seen. This document
is intended to be the comprehensive guide to the installation,
administration, maintenance, and use of the Bugzilla
bug-tracking system.
Bugzilla is simply the best piece of bug-tracking software the
world has ever seen. This document is intended to be the
comprehensive guide to the installation, administration,
maintenance, and use of the Bugzilla bug-tracking system.
</para>
<para>
This release of the Bugzilla Guide is the

220
mozilla/webtools/bugzilla/docs/sgml/administration.sgml
View File

@@ -8,18 +8,21 @@
</subtitle>
<para>
So you followed the installation instructions to the letter, and
just logged into bugzilla with your super-duper god account and
you are sitting at the query screen. Yet, you have nothing to
query. Your first act of business needs to be to setup the
operating parameters for bugzilla.
So you followed <quote><xref linkend="installation"></quote> to the
letter, and logged into Bugzilla for the very first time with your
super-duper god account. You sit, contentedly staring at the
Bugzilla Query Screen, the worst of the whole mad business of
installing this terrific program behind you. It seems, though, you
have nothing yet to query! Your first act of business should be to
setup the operating parameters for Bugzilla so you can get busy
getting data into your bug tracker.
</para>
<section id="postinstall-check">
<title>Post-Installation Checklist</title>
<para>
After installation, follow the checklist below to ensure that
you have a successful installation. If you do not see a
After installation, follow the checklist below to help ensure
that you have a successful installation. If you do not see a
recommended setting for a parameter, consider leaving it at the
default while you perform your initial tests on your Bugzilla
setup.
@@ -30,47 +33,80 @@
<procedure>
<step>
<para>
Bring up "editparams.cgi" in your web browser. For
instance, to edit parameters at mozilla.org, the URL would
be <ulink url="http://bugzilla.mozilla.org/editparams.cgi">
http://bugzilla.mozilla.org/editparams.cgi</ulink>, also
available under the "edit parameters" link on your query
page.
Bring up <filename>editparams.cgi</filename> in your web
browser. This should be available as the <quote>edit
parameters</quote> link from any Bugzilla screen once you
have logged in.
</para>
</step>
<step>
<para>The <quote>maintainer</quote> is the email address of
the person responsible for maintaining this Bugzilla
installation. The maintainer need not be a valid Bugzilla
user. Error pages, error emails, and administrative mail
will be sent with the maintainer as the return email
address.</para>
<para>
Set "maintainer" to <emphasis>your</emphasis> email address.
Set <quote>maintainer</quote> to <emphasis>your</emphasis> email address.
This allows Bugzilla's error messages to display your email
address and allow people to contact you for help.
</para>
</step>
<step>
<para>The <quote>urlbase</quote> parameter defines the fully
qualified domain name and web server path to your Bugzilla
installation.</para>
<para>
Set "urlbase" to the URL reference for your Bugzilla
installation. If your bugzilla query page is at
http://www.foo.com/bugzilla/query.cgi, your url base is
http://www.foo.com/bugzilla/
For example, if your bugzilla query page is
http://www.foo.com/bugzilla/query.cgi, set your
<quote>urlbase</quote> is http://www.foo.com/bugzilla/.
</para>
</step>
<step>
<para><quote>usebuggroups</quote> dictates whether or not to
implement group-based security for Bugzilla. If set,
Bugzilla bugs can have an associated groupmask defining
which groups of users are allowed to see and edit the
bug.</para>
<para>
Set "usebuggroups" to "on" <emphasis>only</emphasis> if you
need to restrict access to products. I suggest leaving this
parameter <emphasis>off</emphasis> while initially testing
your Bugzilla.
may wish to restrict access to products. I suggest leaving
this parameter <emphasis>off</emphasis> while initially
testing your Bugzilla.
</para>
</step>
<step>
<para>
Set "usebuggroupsentry" to "on" if you want to restrict
access to products. Once again, if you are simply testing
<quote>usebuggroupsentry</quote>, when set to
<quote>on</quote>, requires that all bugs have an associated
groupmask when submitted. This parameter is made for those
installations where product isolation is a necessity.
</para>
<para>
Set "usebuggroupsentry" to "on" if you absolutely need to
restrict access to bugs from the moment they are submitted
through resolution. Once again, if you are simply testing
your installation, I suggest against turning this parameter
on; the strict security checking may stop you from being
able to modify your new entries.
</para>
</step>
<step>
<para>
You run into an interesting problem when Bugzilla reaches a
high level of continuous activity. MySQL supports only
table-level write locking. What this means is that if
someone needs to make a change to a bug, they will lock the
entire table until the operation is complete. Locking for
write also blocks reads until the write is complete. The
<quote>shadowdb</quote> parameter was designed to get around
this limitation. While only a single user is allowed to
write to a table at a time, reads can continue unimpeded on
a read-only shadow copy of the database. Although your
database size will double, a shadow database can cause an
enormous performance improvement when implemented on
extremely high-traffic Bugzilla databases.
</para>
<para>
Set "shadowdb" to "bug_shadowdb" if you will be running a
*very* large installation of Bugzilla. The shadow database
@@ -79,15 +115,19 @@
<note>
<para>
Enabling "shadowdb" can adversely affect the stability
of your installation of Bugzilla. You may frequently
need to manually synchronize your databases, or schedule
nightly syncs via "cron"
of your installation of Bugzilla. You should regularly
check that your database is in sync. It is often
advisable to force a shadow database sync nightly via
<quote>cron</quote>.
</para>
</note> Once again, in testing you should avoid this option
-- use it if or when you <emphasis>need</emphasis> to use
it, and have repeatedly run into the problem it was designed
to solve -- very long wait times while attempting to commit
a change to the database.
a change to the database. Mozilla.org began needing
<quote>shadowdb</quote> when they reached around 40,000
Bugzilla users with several hundred Bugzilla bug changes and
comments per day.
</para>
<para>
If you use the "shadowdb" option, it is only natural that
@@ -97,6 +137,18 @@
</para>
</step>
<step>
<para><quote>headerhtml</quote>, <quote>footerhtml</quote>,
<quote>errorhtml</quote>, <quote>bannerhtml</quote>, and
<quote>blurbhtml</quote> are all templates which control
display of headers, footers, errors, banners, and additional
data. We could go into some detail regarding the usage of
these, but it is really best just to monkey around with them
a bit to see what they do. I strongly recommend you copy
your <filename>data/params</filename> file somewhere safe
before playing with these values, though. If they are
changed dramatically, it may make it impossible for you to
display Bugzilla pages to fix the problem until you have
restored your <filename>data/params</filename> file.</para>
<para>
If you have custom logos or HTML you must put in place to
fit within your site design guidelines, place the code in
@@ -105,15 +157,20 @@
<note>
<para>
The "headerhtml" text box is the HTML printed out
<emphasis>before</emphasis> any other code on the page.
If you have a special banner, put the code for it in
"bannerhtml". You may want to leave these settings at
the defaults initially.
<emphasis>before</emphasis> any other code on the page,
except the CONTENT-TYPE header sent by the Bugzilla
engine. If you have a special banner, put the code for
it in "bannerhtml". You may want to leave these settings
at the defaults initially.
</para>
</note>
</para>
</step>
<step>
<para><quote>passwordmail</quote> is rather simple. Every
time a user creates an account, the text of this parameter
is read as the text to send to the new user along with their
password message.</para>
<para>
Add any text you wish to the "passwordmail" parameter box.
For instance, many people choose to use this box to give a
@@ -121,20 +178,32 @@
</para>
</step>
<step>
<para>
Ensure "newemailtech" is "on". Your users will thank you.
This is the default in the post-2.12 world, and is only an
issue if you are upgrading.
</para>
</step>
<step>
<para><quote>useqacontact</quote> allows you to define an
email address for each component, in addition to that of the
default owner, who will be sent carbon copies of incoming
bugs. The critical difference between a QA Contact and an
Owner is that the QA Contact follows the component. If you
reassign a bug from component A to component B, the QA
Contact for that bug will change with the reassignment,
regardless of owner.</para>
<para><quote>usestatuswhiteboard</quote> defines whether you
wish to have a free-form, overwritable field associated with
each bug. The advantage of the Status Whiteboard is that it
can be deleted or modified with ease, and provides an
easily-searchable field for indexing some bugs that have
some trait in common. Many people will put <quote>help
wanted</quote>, <quote>stalled</quote>, or <quote>waiting
on reply from somebody</quote> messages into the Status
Whiteboard field so those who peruse the bugs are aware of
their status even more than that which can be indicated by
the Resolution fields.</para>
<para>
Do you want to use the QA Contact ("useqacontact") and
status whiteboard ("usestatuswhiteboard") fields? These
fields are useful because they allow for more flexibility,
particularly when you have an existing Quality Assurance
and/or Release Engineering team, but they may not be needed
for smaller installations.
for many smaller installations.
</para>
</step>
<step>
@@ -144,14 +213,22 @@
they have untouched new bugs. If you do not plan to use
this feature, simply do not set up the whining cron job
described in the installation instructions, or set this
value to "0".
value to "0" (never whine).
</para>
</step>
<step>
<para><quote>commenton</quote> fields allow you to dictate
what changes can pass without comment, and which must have a
comment from the person who changed them. Often,
administrators will allow users to add themselves to the CC
list, accept bugs, or change the Status Whiteboard without
adding a comment as to their reasons for the change, yet
require that most other changes come with an
explanation.</para>
<para>
Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users resolve,
reassign, or reopen bugs.
reassign, or reopen bugs at the very least.
<note>
<para>
It is generally far better to require a developer
@@ -164,12 +241,28 @@
</para>
</step>
<step>
<para>The <quote>supportwatchers</quote> option can be an
exceptionally powerful tool in the hands of a power Bugzilla
user. By enabling this option, you allow users to receive
email updates whenever other users receive email updates.
This is, of course, subject to the groupset restrictions on
the bug; if the <quote>watcher</quote> would not normally be
allowed to view a bug, the watcher cannot get around the
system by setting herself up to watch the bugs of someone
with bugs outside her priveleges. She would still only
receive email updates for those bugs she could normally
view.</para>
<para>For Bugzilla sites which require strong inter-Product
security to prevent snooping, watchers are not a good
idea.</para>
<para>
Set "supportwatchers" to "On". This feature is helpful for
team leads to monitor progress in their respective areas,
and can offer many other benefits, such as allowing a
developer to pick up a former engineer's bugs without
requiring her to change all the information in the bug.
However, for most sites you should set
<quote>supportwatchers</quote> to "On". This feature is
helpful for team leads to monitor progress in their
respective areas, and can offer many other benefits, such as
allowing a developer to pick up a former engineer's bugs
without requiring her to change all the information in the
bug.
</para>
</step>
</procedure>
@@ -205,6 +298,9 @@
groupset=0x7ffffffffffffff where login_name = "(user's
login name)"; </command>
</para>
<para>Yes, that is <emphasis>fourteen</emphasis>
<quote>f</quote>'s. A whole lot of f-ing going on if you
want to create a new administator.</para>
</tip>
</section>
@@ -269,11 +365,11 @@
right-hand side of the text entry box. You can match
what you type as a case-insensitive substring (the
default) of all users on your system, a case-sensitive
regular expression (please see the "man regexp" manual
page for details on regular expression syntax), or a
<emphasis>reverse</emphasis> regular expression match,
where every user name which does NOT match the regular
expression is selected.
regular expression (please see the <command>man
regexp</command> manual page for details on regular
expression syntax), or a <emphasis>reverse</emphasis>
regular expression match, where every user name which
does NOT match the regular expression is selected.
</para>
</tip>
</listitem>
@@ -292,10 +388,14 @@
<para>
Adding a user this way will <emphasis>not</emphasis>
send an email informing them of their username and
password. In general, it is preferable to log out and
use the "New Account" button to create users, as it
will pre-populate all the required fields and also
notify the user of her account name and password.
password. While useful for creating dummy accounts
(watchers which shuttle mail to another system, for
instance, or email addresses which are a mailing
list), in general it is preferable to log out and use
the <quote>New Account</quote> button to create users,
as it will pre-populate all the required fields and
also notify the user of her account name and
password.
</para>
</note>
</listitem>
@@ -317,6 +417,11 @@
Don't disable your own administrative account, or you
will hate life!
</para>
<para>At this time, <quote>Disabled Text</quote> does not
prevent a user from using the email interface. If you
have the email interface enabled, they can still
continue to submit bugs and comments that way. We need
a patch to fix this.</para>
</warning>
</para>
</section>
@@ -350,9 +455,8 @@
</listitem>
<listitem>
<para>
<emphasis>Password</emphasis>: You will only see
asterisks in versions of Bugzilla newer than 2.10 or
early 2.11. You can change the user password here.
<emphasis>Password</emphasis>: You can change the user
password here. It is normal to only see asterisks.
</para>
</listitem>
<listitem>

1509
mozilla/webtools/bugzilla/docs/sgml/faq.sgml
View File

File diff suppressed because it is too large Load Diff

6
mozilla/webtools/bugzilla/docs/sgml/future.sgml
View File

@@ -3,11 +3,13 @@
<chapter id="future">
<title>The Future of Bugzilla</title>
<synopsis>Bugzilla's Future. Much of this is the present, now.</synopsis>
<para>The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do
<para>
The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do
not have more information about it right now, and most of what
went into the "future" section is now present. That stuff was
blue-sky a year ago; MattyT should have me a new document
sometime...</para>
sometime...
</para>
</chapter>
<!-- Keep this comment at the end of the file

156
mozilla/webtools/bugzilla/docs/sgml/glossary.sgml
View File

@@ -26,9 +26,16 @@
<glossdiv id="gloss_a">
<title>A</title>
<glossentry>
<glossterm>There are no entries for A</glossterm>
<glossterm>Apache</glossterm>
<glossdef>
<para></para>
<para>In this context, Apache is the web server most
commonly used for serving up
<glossterm>Bugzilla</glossterm> pages. Contrary to
popular belief, the apache web server has nothing to do
with the ancient and noble Native American tribe, but
instead derived its name from the fact that it was
<quote>a patchy</quote> version of the original
<acronym>NCSA</acronym> world-wide-web server.</para>
</glossdef>
</glossentry>
</glossdiv>
@@ -70,8 +77,77 @@
the needs of the organization using it, though.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bugzilla</glossterm>
<glossdef>
<para>
Bugzilla is the industry-standard bug tracking system. It
is quite popular among Open Source enthusiasts.
</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_c">
<title></title>
<glossentry id="gloss_component">
<glossterm>Component</glossterm>
<glossdef>
<para>
A Component is a subsection of a Product. It should be a
narrow category, tailored to your organization. All
Products must contain at least one Component (and, as a
matter of fact, creating a Product with no Components will
create an error in Bugzilla).
</para>
</glossdef>
</glossentry>
<glossentry id="gloss_cpan">
<glossterm><acronym>CPAN</acronym></glossterm>
<glossdef>
<para><acronym>CPAN</acronym> stands for the
<quote>Comprehensive Perl Archive Network</quote>. CPAN
maintains a large number of extremely useful
<glossterm>Perl</glossterm> modules. By themselves, Perl
modules generally do nothing, but when used as part of a
larger program, they provide much-needed algorithms and
functionality.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_d">
<title>D</title>
<glossentry>
<glossterm>daemon</glossterm>
<glossdef>
<para>A daemon is a computer program which runs in the
background. In general, most daemons are started at boot
time via System V init scripts, or through RC scripts on
BSD-based systems. <glossterm>mysqld</glossterm>, the
MySQL server, and <glossterm>apache</glossterm>, a web
server, are generally run as daemons.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_g">
<title></title>
<glossentry>
<glossterm>Groups</glossterm>
<glossdef>
<para>The word <quote>Groups</quote> has a very special
meaning to Bugzilla. Bugzilla's main security mechanism
comes by lumping users into groups, and assigning those
groups certain privileges to
<glossterm>Products</glossterm> and
<glossterm>Components</glossterm> in the
<glossterm>Bugzilla</glossterm> database.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_i">
<title>I</title>
<glossentry id="gloss_infiniteloop">
@@ -81,7 +157,22 @@
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_m">
<title>M</title>
<glossentry>
<glossterm>mysqld</glossterm>
<glossdef>
<para>mysqld is the name of the
<glossterm>daemon</glossterm> for the MySQL database. In
general, it is invoked automatically through the use of
the System V init scripts on GNU/Linux and AT&amp;T System
V-based systems, such as Solaris and HP/UX, or through the
RC scripts on BSD-based systems.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_p">
<title>P</title>
<glossentry>
@@ -108,6 +199,17 @@
</example>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Perl</glossterm>
<glossdef>
<para>First written by Larry Wall, Perl is a remarkable
program language. It has the benefits of the flexibility
of an interpreted scripting language (such as shell
script), combined with the speed and power of a compiled
language, such as C. <glossterm>Bugzilla</glossterm> is
maintained in Perl.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_q">
@@ -129,8 +231,8 @@
<glossdiv id="gloss_r">
<title>R</title>
<glossentry>
<glossterm id="gloss_recursion">Recursion</glossterm>
<glossentry id="gloss_recursion" xreflabel="Recursion">
<glossterm>Recursion</glossterm>
<glossdef>
<para>The property of a function looking back at itself for
something. <quote>GNU</quote>, for instance, stands for
@@ -140,10 +242,52 @@
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_s">
<title>S</title>
<glossentry>
<glossterm><acronym>SGML</acronym></glossterm>
<glossdef>
<para><acronym>SGML</acronym> stands for <quote>Standard
Generalized Markup Language</quote>. Created in the
1980's to provide an extensible means to maintain
documentation based upon content instead of presentation,
<acronym>SGML</acronym> has withstood the test of time as
a robust, powerful language.
<glossterm><acronym>XML</acronym></glossterm> is the
<quote>baby brother</quote> of SGML; any valid
<acronym>XML</acronym> document it, by definition, a valid
<acronym>SGML</acronym> document. The document you are
reading is written and maintained in
<acronym>SGML</acronym>, and is also valid
<acronym>XML</acronym> if you modify the Document Type
Definition.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_t">
<title>T</title>
<glossentry id="gloss_target_milestone" xreflabel="Target Milestone">
<glossterm>Target Milestone</glossterm>
<glossdef>
<para>
Target Milestones are Product goals. They are
configurable on a per-Product basis. Most software
development houses have a concept of
<quote>milestones</quote> where the people funding a
project expect certain functionality on certain dates.
Bugzilla facilitates meeting these milestones by giving
you the ability to declare by which milestone a bug will be
fixed, or an enhancement will be implemented.
</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_z">
<title>Z</title>
<glossentry>
<glossentry id="zarro-boogs-found" xreflabel="Zarro Boogs Found">
<glossterm>Zarro Boogs Found</glossterm>
<glossdef>
<para>This is the cryptic response sent by Bugzilla when a

959
mozilla/webtools/bugzilla/docs/sgml/installation.sgml
View File

File diff suppressed because it is too large Load Diff

70
mozilla/webtools/bugzilla/docs/sgml/integration.sgml
View File

@@ -5,49 +5,59 @@
<chapter id="integration">
<title>Integrating Bugzilla with Third-Party Tools</title>
<section id="bonsai">
<section id="bonsai" xreflabel="Bonsai, the Mozilla automated CVS management system">
<title>Bonsai</title>
<para>We need Bonsai integration information.</para>
<para>Bonsai is a web-based tool for managing <xref
linkend="cvs">
. Using Bonsai, administrators can control open/closed status
of trees, query a fast relational database back-end for change,
branch, and comment information, and view changes made since the
last time the tree was closed. These kinds of changes cause the
engineer responsible to be <quote>on the hook</quote> (include
cool URL link here for Hook policies at mozilla.org). Bonsai
also includes gateways to <xref
linkend="tinderbox"> and Bugzilla </para>
</section>
<section id="cvs">
<section id="cvs" xreflabel="CVS, the Concurrent Versioning System">
<title>CVS</title>
<para>CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</para>
<para>CVS integration is best accomplished, at this point, using
the Bugzilla Email Gateway. There have been some files
submitted to allow greater CVS integration, but we need to make
certain that Bugzilla is not tied into one particular software
management package.</para>
<para>
Follow the instructions in the FAQ for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to
your Bugzilla e-mail gateway with the subject of <quote>[Bug
XXXX]</quote>, and you can have CVS check-in comments append
to your Bugzilla bug. If you have your check-in script include
an @resolution field, you can even change the Bugzilla bug
state.
</para>
</section>
<section id="scm">
<section id="scm" xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS">
<title>Perforce SCM</title>
<para>
You can find the project page for Bugzilla and Teamtrack Perforce integration at:
<ulink url="http://www.ravenbrook.com/project/p4dti/">
http://www.ravenbrook.com/project/p4dti</ulink>. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public Depot"
p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
You can find the project page for Bugzilla and Teamtrack
Perforce integration (p4dti) at: <ulink
url="http://www.ravenbrook.com/project/p4dti/"> http://www.ravenbrook.com/project/p4dti</ulink> . <quote>p4dti</quote> is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html"> http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
</para>
<para>
Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
patches for 2.12 will be out shortly. Check the project page regularly for updates, or
take the given patches and patch it manually. p4dti is designed to support multiple defect
trackers, and maintains its own documentation for it. Please consult the pages linked
above for further information.
</para>
<para>
Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
have synchronization problems, the easiest way to avoid them is to only put the bug
information, comments, etc. into Bugzilla, and not into the Perforce change records.
They will link anyway; merely reference the bug ID fixed in your change description,
and put a comment into Bugzilla
giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
question.
Integration of Perforce with Bugzilla, once patches are applied,
is seamless. Perforce replication information will appear below
the comments of each bug. Be certain you have a matching set of
patches for the Bugzilla version you are installing. p4dti is
designed to support multiple defect trackers, and maintains its
own documentation for it. Please consult the pages linked above
for further information.
</para>
</section>
<section id="tinderbox">
<title>Tinderbox</title>
<para>We need Tinderbox integration information</para>
<section id="tinderbox" xreflabel="Tinderbox, the Mozilla automated build management system">
<title>Tinderbox/Tinderbox2</title>
<para>We need Tinderbox integration information.</para>
</section>
</chapter>

34
mozilla/webtools/bugzilla/docs/sgml/patches.sgml
View File

@@ -3,6 +3,40 @@
<appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla">
<title>Useful Patches and Utilities for Bugzilla</title>
<para>Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</para>
<section id="rewrite" xreflabel="Apache mod_rewrite magic">
<title>Apache <filename>mod_rewrite</filename> magic</title>
<para>Apache's <filename>mod_rewrite</filename> module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</para>
<orderedlist>
<listitem>
<para>
Make it so if someone types
<computeroutput>http://www.foo.com/12345</computeroutput>,
Bugzilla spits back
http://www.foo.com/show_bug.cgi?id=12345. Try setting up
your VirtualHost section for Bugzilla with a rule like
this:</para>
<programlisting>
<![CDATA[
<VirtualHost 12.34.56.78>
RewriteEngine On
RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
</VirtualHost>
]]>
</programlisting>
</listitem>
<listitem>
<para>There are many, many more things you can do with
mod_rewrite. As time goes on, I will include many more in
the Guide. For now, though, please refer to the mod_rewrite
documentation at <ulink
url="http://www.apache.org">http://www.apache.org</ulink></para>
</listitem>
</orderedlist>
</section>
<section id="setperl" xreflabel="The setperl.csh Utility">
<title>The setperl.csh Utility</title>
<para> You can use the "setperl.csh" utility to quickly and

807
mozilla/webtools/bugzilla/docs/sgml/using.sgml
View File

File diff suppressed because it is too large Load Diff

129
mozilla/webtools/bugzilla/docs/sgml/variants.sgml
View File

@@ -1,72 +1,77 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">-->
<chapter id="variants">
<title>Bugzilla Variants</title>
<note>
<para>
I <emphasis>know</emphasis> there are more variants than just RedHat Bugzilla out there.
Please help me get information about them, their project status, and benefits there
might be in using them or in using their code in main-tree Bugzilla.
</para>
</note>
<chapter id="variants" xreflabel="Bugzilla Variants and Competitors">
<title>Bugzilla Variants and Competitors</title>
<para>I created this section to answer questions about Bugzilla
competitors and variants, then found a wonderful site which covers
an awful lot of what I wanted to discuss. Rather than quote it in
its entirety, I'll simply refer you here: <ulink
url="http://linas.org/linux/pm.html">http://linas.org/linux/pm.html</ulink></para>
<section id="rhbugzilla">
<section id="rhbugzilla" xreflabel="Red Hat Bugzilla">
<title>Red Hat Bugzilla</title>
<para>
Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
on the planet.
One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
database, as well as MySQL.
Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
<blockquote>
<literallayout>
Hello. I apologize that I am getting back to you so late. It has been difficult to keep
up with email this past week. I have checked out your updated documentation and I will
have to say very good work. A few notes and additions as follows.
(ed: from the FAQ)
>For the record, we are not using any template type implementation for the cosmetic changes
>maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have
>gotten a little carried away with it but the corporate types asked for a more standardized
>interface to match up with other projects relating to Red Hat web sites. A lot of other web
>based internal tools I am working on also look like Bugzilla.
This should probably be changed since we are now in fact using Text::Template for most
of the html rendering. You actually state this later in your numbered list.
Also number 6 contradicts number 8 where number 6 would be the most up to date status
on the Oracle port.
Additional Information:
-----------------------------
1. Comments are now stored in varchar fields of 4k in size each. If the comment is more
than 4k it is broken up into chunks and given a sort number so each comment can be re
assembled in the correct order. This was done because originally I was storing the comments
in a long datatype which unfortunately cannot be indexed or joined with another table. This
cause the search of text within the long description to be disabled for a long time. That
is now working and is nto showing any noticeble performance hit that I can tell.
2. Work is being started on internationalizing the Bugzilla source we have to allow our
Japanese customers to enter bug reports into a single bugzilla system. This will probably
be done by using the nvarchar data types supported by Oracle which allows storage of
double byte characters and also the use of the Accept-Language in the http header for
detection by Bugilla of which language to render.
3. Of course even more cosmetic changes. It is difficult to keep up with the ever
changing faces of www.redhat.com.
4. Some convenience enhancements in the administration utilities. And more integration
with other internal/external Red Hat web sites.
I hope this information may prove helpful for your documentation. Please contact
me if you have any more question or I can do anything else.
Regards
</literallayout>
</blockquote>
Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
the ability to work with Oracle, MySQL, and PostGreSQL databases
serving as the back-end, instead of just MySQL. Dave Lawrence
has worked very hard to keep Red Hat Bugzilla up-to-date, and
many people prefer the snappier-looking page layout of Red Hat
Bugzilla to the default Mozilla-standard formatting.
</para>
<para>URL: <ulink
url="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</ulink></para>
</section>
<section id="variant_fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris">
<title>Loki Bugzilla (Fenris)</title>
<para>Fenris can be found at <ulink
url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para>
</section>
<section id="variant_issuezilla" xreflabel="Issuezilla">
<title>Issuezilla</title>
<para>Issuezilla is another fork from Bugzilla, and seems nearly
as popular as the Red Hat Bugzilla fork. Some Issuezilla team
members are regular contributors to the Bugzilla mailing
list/newsgroup. Issuezilla is not the primary focus of
bug-tracking at tigris.org, however. Their Java-based
bug-tracker, <xref linkend="variant_scarab">, is under heavy development
and looks promising!</para>
<para>URL: <ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">http://issuezilla.tigris.org/servlets/ProjectHome</ulink></para>
</section>
<section id="variant_scarab" xreflabel="Scarab, a newfangled Java-based issue tracker">
<title>Scarab</title>
<para>Scarab is a promising new bug-tracking system built using
Java Serlet technology. As of this writing, no source code has
been released as a package, but you can obtain the code from
CVS.
</para>
<para>URL: <ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink></para>
</section>
<section id="variant_perforce" xreflabel="Using Perforce to track bugs">
<title>Perforce SCM</title>
<para>Although Perforce isn't really a bug tracker, it can be used
as such through the <quote>jobs</quote> functionality.</para>
<para><ulink
url="http://www.perforce.com/perforce/technotes/note052.html"></ulink>http://www.perforce.com/perforce/technotes/note052.html</para>
</section>
<section id="variant_sourceforge" xreflabel="SourceForge">
<title>SourceForge</title>
<para>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the
Internet than strictly a bug tracker, but if you're hunting for
bug-tracking for your open project, it may be just what the
software engineer ordered!</para>
<para>URL: <ulink
url="http://www.sourceforge.net">http://www.sourceforge.net</ulink></para>
</section>
</chapter>
<!-- Keep this comment at the end of the file

1336
mozilla/webtools/bugzilla/docs/txt/Bugzilla-Guide.txt
View File

File diff suppressed because it is too large Load Diff

17
mozilla/webtools/bugzilla/docs/xml/Bugzilla-Guide.xml
View File

@@ -23,7 +23,7 @@
<!ENTITY bz-ver "2.14">
<!ENTITY bz-cvs-ver "2.15">
<!ENTITY bzg-date "August 10, 2001">
<!ENTITY bzg-ver "2.14.0">
<!ENTITY bzg-ver "2.14">
<!ENTITY bzg-cvs-ver "2.15.0">
<!ENTITY bzg-auth "Matthew P. Barnson">
<!ENTITY bzg-auth-email "<email>barnboy@NOSPAM.trilobyte.net</email>">
@@ -137,15 +137,6 @@ try to avoid clutter and feel free to waste space in the code to make it more re
</affiliation>
</collab>
<editor>
<firstname>I.</firstname>
<surname>Freely</surname>
<othername>P.</othername>
<affiliation>
<address><email>ipfreely@freely.eye-p.net</email></address>
</affiliation>
</editor>
</authorgroup>
<abstract>
@@ -165,6 +156,12 @@ try to avoid clutter and feel free to waste space in the code to make it more re
professional on operating system upon which you install
Bugzilla.
</para>
<para>
THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
ADDITIONS TO THE GUIDE WRITTEN IN HTML!
</para>
</abstract>

9
mozilla/webtools/bugzilla/docs/xml/about.xml
View File

@@ -14,11 +14,10 @@
document you see today.
</para>
<para>
Despite the lack of updates, Bugzilla is simply the best piece
of bug-tracking software the world has ever seen. This document
is intended to be the comprehensive guide to the installation,
administration, maintenance, and use of the Bugzilla
bug-tracking system.
Bugzilla is simply the best piece of bug-tracking software the
world has ever seen. This document is intended to be the
comprehensive guide to the installation, administration,
maintenance, and use of the Bugzilla bug-tracking system.
</para>
<para>
This release of the Bugzilla Guide is the

220
mozilla/webtools/bugzilla/docs/xml/administration.xml
View File

@@ -8,18 +8,21 @@
</subtitle>
<para>
So you followed the installation instructions to the letter, and
just logged into bugzilla with your super-duper god account and
you are sitting at the query screen. Yet, you have nothing to
query. Your first act of business needs to be to setup the
operating parameters for bugzilla.
So you followed <quote><xref linkend="installation"></quote> to the
letter, and logged into Bugzilla for the very first time with your
super-duper god account. You sit, contentedly staring at the
Bugzilla Query Screen, the worst of the whole mad business of
installing this terrific program behind you. It seems, though, you
have nothing yet to query! Your first act of business should be to
setup the operating parameters for Bugzilla so you can get busy
getting data into your bug tracker.
</para>
<section id="postinstall-check">
<title>Post-Installation Checklist</title>
<para>
After installation, follow the checklist below to ensure that
you have a successful installation. If you do not see a
After installation, follow the checklist below to help ensure
that you have a successful installation. If you do not see a
recommended setting for a parameter, consider leaving it at the
default while you perform your initial tests on your Bugzilla
setup.
@@ -30,47 +33,80 @@
<procedure>
<step>
<para>
Bring up "editparams.cgi" in your web browser. For
instance, to edit parameters at mozilla.org, the URL would
be <ulink url="http://bugzilla.mozilla.org/editparams.cgi">
http://bugzilla.mozilla.org/editparams.cgi</ulink>, also
available under the "edit parameters" link on your query
page.
Bring up <filename>editparams.cgi</filename> in your web
browser. This should be available as the <quote>edit
parameters</quote> link from any Bugzilla screen once you
have logged in.
</para>
</step>
<step>
<para>The <quote>maintainer</quote> is the email address of
the person responsible for maintaining this Bugzilla
installation. The maintainer need not be a valid Bugzilla
user. Error pages, error emails, and administrative mail
will be sent with the maintainer as the return email
address.</para>
<para>
Set "maintainer" to <emphasis>your</emphasis> email address.
Set <quote>maintainer</quote> to <emphasis>your</emphasis> email address.
This allows Bugzilla's error messages to display your email
address and allow people to contact you for help.
</para>
</step>
<step>
<para>The <quote>urlbase</quote> parameter defines the fully
qualified domain name and web server path to your Bugzilla
installation.</para>
<para>
Set "urlbase" to the URL reference for your Bugzilla
installation. If your bugzilla query page is at
http://www.foo.com/bugzilla/query.cgi, your url base is
http://www.foo.com/bugzilla/
For example, if your bugzilla query page is
http://www.foo.com/bugzilla/query.cgi, set your
<quote>urlbase</quote> is http://www.foo.com/bugzilla/.
</para>
</step>
<step>
<para><quote>usebuggroups</quote> dictates whether or not to
implement group-based security for Bugzilla. If set,
Bugzilla bugs can have an associated groupmask defining
which groups of users are allowed to see and edit the
bug.</para>
<para>
Set "usebuggroups" to "on" <emphasis>only</emphasis> if you
need to restrict access to products. I suggest leaving this
parameter <emphasis>off</emphasis> while initially testing
your Bugzilla.
may wish to restrict access to products. I suggest leaving
this parameter <emphasis>off</emphasis> while initially
testing your Bugzilla.
</para>
</step>
<step>
<para>
Set "usebuggroupsentry" to "on" if you want to restrict
access to products. Once again, if you are simply testing
<quote>usebuggroupsentry</quote>, when set to
<quote>on</quote>, requires that all bugs have an associated
groupmask when submitted. This parameter is made for those
installations where product isolation is a necessity.
</para>
<para>
Set "usebuggroupsentry" to "on" if you absolutely need to
restrict access to bugs from the moment they are submitted
through resolution. Once again, if you are simply testing
your installation, I suggest against turning this parameter
on; the strict security checking may stop you from being
able to modify your new entries.
</para>
</step>
<step>
<para>
You run into an interesting problem when Bugzilla reaches a
high level of continuous activity. MySQL supports only
table-level write locking. What this means is that if
someone needs to make a change to a bug, they will lock the
entire table until the operation is complete. Locking for
write also blocks reads until the write is complete. The
<quote>shadowdb</quote> parameter was designed to get around
this limitation. While only a single user is allowed to
write to a table at a time, reads can continue unimpeded on
a read-only shadow copy of the database. Although your
database size will double, a shadow database can cause an
enormous performance improvement when implemented on
extremely high-traffic Bugzilla databases.
</para>
<para>
Set "shadowdb" to "bug_shadowdb" if you will be running a
*very* large installation of Bugzilla. The shadow database
@@ -79,15 +115,19 @@
<note>
<para>
Enabling "shadowdb" can adversely affect the stability
of your installation of Bugzilla. You may frequently
need to manually synchronize your databases, or schedule
nightly syncs via "cron"
of your installation of Bugzilla. You should regularly
check that your database is in sync. It is often
advisable to force a shadow database sync nightly via
<quote>cron</quote>.
</para>
</note> Once again, in testing you should avoid this option
-- use it if or when you <emphasis>need</emphasis> to use
it, and have repeatedly run into the problem it was designed
to solve -- very long wait times while attempting to commit
a change to the database.
a change to the database. Mozilla.org began needing
<quote>shadowdb</quote> when they reached around 40,000
Bugzilla users with several hundred Bugzilla bug changes and
comments per day.
</para>
<para>
If you use the "shadowdb" option, it is only natural that
@@ -97,6 +137,18 @@
</para>
</step>
<step>
<para><quote>headerhtml</quote>, <quote>footerhtml</quote>,
<quote>errorhtml</quote>, <quote>bannerhtml</quote>, and
<quote>blurbhtml</quote> are all templates which control
display of headers, footers, errors, banners, and additional
data. We could go into some detail regarding the usage of
these, but it is really best just to monkey around with them
a bit to see what they do. I strongly recommend you copy
your <filename>data/params</filename> file somewhere safe
before playing with these values, though. If they are
changed dramatically, it may make it impossible for you to
display Bugzilla pages to fix the problem until you have
restored your <filename>data/params</filename> file.</para>
<para>
If you have custom logos or HTML you must put in place to
fit within your site design guidelines, place the code in
@@ -105,15 +157,20 @@
<note>
<para>
The "headerhtml" text box is the HTML printed out
<emphasis>before</emphasis> any other code on the page.
If you have a special banner, put the code for it in
"bannerhtml". You may want to leave these settings at
the defaults initially.
<emphasis>before</emphasis> any other code on the page,
except the CONTENT-TYPE header sent by the Bugzilla
engine. If you have a special banner, put the code for
it in "bannerhtml". You may want to leave these settings
at the defaults initially.
</para>
</note>
</para>
</step>
<step>
<para><quote>passwordmail</quote> is rather simple. Every
time a user creates an account, the text of this parameter
is read as the text to send to the new user along with their
password message.</para>
<para>
Add any text you wish to the "passwordmail" parameter box.
For instance, many people choose to use this box to give a
@@ -121,20 +178,32 @@
</para>
</step>
<step>
<para>
Ensure "newemailtech" is "on". Your users will thank you.
This is the default in the post-2.12 world, and is only an
issue if you are upgrading.
</para>
</step>
<step>
<para><quote>useqacontact</quote> allows you to define an
email address for each component, in addition to that of the
default owner, who will be sent carbon copies of incoming
bugs. The critical difference between a QA Contact and an
Owner is that the QA Contact follows the component. If you
reassign a bug from component A to component B, the QA
Contact for that bug will change with the reassignment,
regardless of owner.</para>
<para><quote>usestatuswhiteboard</quote> defines whether you
wish to have a free-form, overwritable field associated with
each bug. The advantage of the Status Whiteboard is that it
can be deleted or modified with ease, and provides an
easily-searchable field for indexing some bugs that have
some trait in common. Many people will put <quote>help
wanted</quote>, <quote>stalled</quote>, or <quote>waiting
on reply from somebody</quote> messages into the Status
Whiteboard field so those who peruse the bugs are aware of
their status even more than that which can be indicated by
the Resolution fields.</para>
<para>
Do you want to use the QA Contact ("useqacontact") and
status whiteboard ("usestatuswhiteboard") fields? These
fields are useful because they allow for more flexibility,
particularly when you have an existing Quality Assurance
and/or Release Engineering team, but they may not be needed
for smaller installations.
for many smaller installations.
</para>
</step>
<step>
@@ -144,14 +213,22 @@
they have untouched new bugs. If you do not plan to use
this feature, simply do not set up the whining cron job
described in the installation instructions, or set this
value to "0".
value to "0" (never whine).
</para>
</step>
<step>
<para><quote>commenton</quote> fields allow you to dictate
what changes can pass without comment, and which must have a
comment from the person who changed them. Often,
administrators will allow users to add themselves to the CC
list, accept bugs, or change the Status Whiteboard without
adding a comment as to their reasons for the change, yet
require that most other changes come with an
explanation.</para>
<para>
Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users resolve,
reassign, or reopen bugs.
reassign, or reopen bugs at the very least.
<note>
<para>
It is generally far better to require a developer
@@ -164,12 +241,28 @@
</para>
</step>
<step>
<para>The <quote>supportwatchers</quote> option can be an
exceptionally powerful tool in the hands of a power Bugzilla
user. By enabling this option, you allow users to receive
email updates whenever other users receive email updates.
This is, of course, subject to the groupset restrictions on
the bug; if the <quote>watcher</quote> would not normally be
allowed to view a bug, the watcher cannot get around the
system by setting herself up to watch the bugs of someone
with bugs outside her priveleges. She would still only
receive email updates for those bugs she could normally
view.</para>
<para>For Bugzilla sites which require strong inter-Product
security to prevent snooping, watchers are not a good
idea.</para>
<para>
Set "supportwatchers" to "On". This feature is helpful for
team leads to monitor progress in their respective areas,
and can offer many other benefits, such as allowing a
developer to pick up a former engineer's bugs without
requiring her to change all the information in the bug.
However, for most sites you should set
<quote>supportwatchers</quote> to "On". This feature is
helpful for team leads to monitor progress in their
respective areas, and can offer many other benefits, such as
allowing a developer to pick up a former engineer's bugs
without requiring her to change all the information in the
bug.
</para>
</step>
</procedure>
@@ -205,6 +298,9 @@
groupset=0x7ffffffffffffff where login_name = "(user's
login name)"; </command>
</para>
<para>Yes, that is <emphasis>fourteen</emphasis>
<quote>f</quote>'s. A whole lot of f-ing going on if you
want to create a new administator.</para>
</tip>
</section>
@@ -269,11 +365,11 @@
right-hand side of the text entry box. You can match
what you type as a case-insensitive substring (the
default) of all users on your system, a case-sensitive
regular expression (please see the "man regexp" manual
page for details on regular expression syntax), or a
<emphasis>reverse</emphasis> regular expression match,
where every user name which does NOT match the regular
expression is selected.
regular expression (please see the <command>man
regexp</command> manual page for details on regular
expression syntax), or a <emphasis>reverse</emphasis>
regular expression match, where every user name which
does NOT match the regular expression is selected.
</para>
</tip>
</listitem>
@@ -292,10 +388,14 @@
<para>
Adding a user this way will <emphasis>not</emphasis>
send an email informing them of their username and
password. In general, it is preferable to log out and
use the "New Account" button to create users, as it
will pre-populate all the required fields and also
notify the user of her account name and password.
password. While useful for creating dummy accounts
(watchers which shuttle mail to another system, for
instance, or email addresses which are a mailing
list), in general it is preferable to log out and use
the <quote>New Account</quote> button to create users,
as it will pre-populate all the required fields and
also notify the user of her account name and
password.
</para>
</note>
</listitem>
@@ -317,6 +417,11 @@
Don't disable your own administrative account, or you
will hate life!
</para>
<para>At this time, <quote>Disabled Text</quote> does not
prevent a user from using the email interface. If you
have the email interface enabled, they can still
continue to submit bugs and comments that way. We need
a patch to fix this.</para>
</warning>
</para>
</section>
@@ -350,9 +455,8 @@
</listitem>
<listitem>
<para>
<emphasis>Password</emphasis>: You will only see
asterisks in versions of Bugzilla newer than 2.10 or
early 2.11. You can change the user password here.
<emphasis>Password</emphasis>: You can change the user
password here. It is normal to only see asterisks.
</para>
</listitem>
<listitem>

1509
mozilla/webtools/bugzilla/docs/xml/faq.xml
View File

File diff suppressed because it is too large Load Diff

156
mozilla/webtools/bugzilla/docs/xml/glossary.xml
View File

@@ -26,9 +26,16 @@
<glossdiv id="gloss_a">
<title>A</title>
<glossentry>
<glossterm>There are no entries for A</glossterm>
<glossterm>Apache</glossterm>
<glossdef>
<para></para>
<para>In this context, Apache is the web server most
commonly used for serving up
<glossterm>Bugzilla</glossterm> pages. Contrary to
popular belief, the apache web server has nothing to do
with the ancient and noble Native American tribe, but
instead derived its name from the fact that it was
<quote>a patchy</quote> version of the original
<acronym>NCSA</acronym> world-wide-web server.</para>
</glossdef>
</glossentry>
</glossdiv>
@@ -70,8 +77,77 @@
the needs of the organization using it, though.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bugzilla</glossterm>
<glossdef>
<para>
Bugzilla is the industry-standard bug tracking system. It
is quite popular among Open Source enthusiasts.
</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_c">
<title></title>
<glossentry id="gloss_component">
<glossterm>Component</glossterm>
<glossdef>
<para>
A Component is a subsection of a Product. It should be a
narrow category, tailored to your organization. All
Products must contain at least one Component (and, as a
matter of fact, creating a Product with no Components will
create an error in Bugzilla).
</para>
</glossdef>
</glossentry>
<glossentry id="gloss_cpan">
<glossterm><acronym>CPAN</acronym></glossterm>
<glossdef>
<para><acronym>CPAN</acronym> stands for the
<quote>Comprehensive Perl Archive Network</quote>. CPAN
maintains a large number of extremely useful
<glossterm>Perl</glossterm> modules. By themselves, Perl
modules generally do nothing, but when used as part of a
larger program, they provide much-needed algorithms and
functionality.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_d">
<title>D</title>
<glossentry>
<glossterm>daemon</glossterm>
<glossdef>
<para>A daemon is a computer program which runs in the
background. In general, most daemons are started at boot
time via System V init scripts, or through RC scripts on
BSD-based systems. <glossterm>mysqld</glossterm>, the
MySQL server, and <glossterm>apache</glossterm>, a web
server, are generally run as daemons.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_g">
<title></title>
<glossentry>
<glossterm>Groups</glossterm>
<glossdef>
<para>The word <quote>Groups</quote> has a very special
meaning to Bugzilla. Bugzilla's main security mechanism
comes by lumping users into groups, and assigning those
groups certain privileges to
<glossterm>Products</glossterm> and
<glossterm>Components</glossterm> in the
<glossterm>Bugzilla</glossterm> database.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_i">
<title>I</title>
<glossentry id="gloss_infiniteloop">
@@ -81,7 +157,22 @@
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_m">
<title>M</title>
<glossentry>
<glossterm>mysqld</glossterm>
<glossdef>
<para>mysqld is the name of the
<glossterm>daemon</glossterm> for the MySQL database. In
general, it is invoked automatically through the use of
the System V init scripts on GNU/Linux and AT&amp;T System
V-based systems, such as Solaris and HP/UX, or through the
RC scripts on BSD-based systems.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_p">
<title>P</title>
<glossentry>
@@ -108,6 +199,17 @@
</example>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Perl</glossterm>
<glossdef>
<para>First written by Larry Wall, Perl is a remarkable
program language. It has the benefits of the flexibility
of an interpreted scripting language (such as shell
script), combined with the speed and power of a compiled
language, such as C. <glossterm>Bugzilla</glossterm> is
maintained in Perl.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_q">
@@ -129,8 +231,8 @@
<glossdiv id="gloss_r">
<title>R</title>
<glossentry>
<glossterm id="gloss_recursion">Recursion</glossterm>
<glossentry id="gloss_recursion" xreflabel="Recursion">
<glossterm>Recursion</glossterm>
<glossdef>
<para>The property of a function looking back at itself for
something. <quote>GNU</quote>, for instance, stands for
@@ -140,10 +242,52 @@
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_s">
<title>S</title>
<glossentry>
<glossterm><acronym>SGML</acronym></glossterm>
<glossdef>
<para><acronym>SGML</acronym> stands for <quote>Standard
Generalized Markup Language</quote>. Created in the
1980's to provide an extensible means to maintain
documentation based upon content instead of presentation,
<acronym>SGML</acronym> has withstood the test of time as
a robust, powerful language.
<glossterm><acronym>XML</acronym></glossterm> is the
<quote>baby brother</quote> of SGML; any valid
<acronym>XML</acronym> document it, by definition, a valid
<acronym>SGML</acronym> document. The document you are
reading is written and maintained in
<acronym>SGML</acronym>, and is also valid
<acronym>XML</acronym> if you modify the Document Type
Definition.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_t">
<title>T</title>
<glossentry id="gloss_target_milestone" xreflabel="Target Milestone">
<glossterm>Target Milestone</glossterm>
<glossdef>
<para>
Target Milestones are Product goals. They are
configurable on a per-Product basis. Most software
development houses have a concept of
<quote>milestones</quote> where the people funding a
project expect certain functionality on certain dates.
Bugzilla facilitates meeting these milestones by giving
you the ability to declare by which milestone a bug will be
fixed, or an enhancement will be implemented.
</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_z">
<title>Z</title>
<glossentry>
<glossentry id="zarro-boogs-found" xreflabel="Zarro Boogs Found">
<glossterm>Zarro Boogs Found</glossterm>
<glossdef>
<para>This is the cryptic response sent by Bugzilla when a

959
mozilla/webtools/bugzilla/docs/xml/installation.xml
View File

File diff suppressed because it is too large Load Diff

70
mozilla/webtools/bugzilla/docs/xml/integration.xml
View File

@@ -5,49 +5,59 @@
<chapter id="integration">
<title>Integrating Bugzilla with Third-Party Tools</title>
<section id="bonsai">
<section id="bonsai" xreflabel="Bonsai, the Mozilla automated CVS management system">
<title>Bonsai</title>
<para>We need Bonsai integration information.</para>
<para>Bonsai is a web-based tool for managing <xref
linkend="cvs">
. Using Bonsai, administrators can control open/closed status
of trees, query a fast relational database back-end for change,
branch, and comment information, and view changes made since the
last time the tree was closed. These kinds of changes cause the
engineer responsible to be <quote>on the hook</quote> (include
cool URL link here for Hook policies at mozilla.org). Bonsai
also includes gateways to <xref
linkend="tinderbox"> and Bugzilla </para>
</section>
<section id="cvs">
<section id="cvs" xreflabel="CVS, the Concurrent Versioning System">
<title>CVS</title>
<para>CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</para>
<para>CVS integration is best accomplished, at this point, using
the Bugzilla Email Gateway. There have been some files
submitted to allow greater CVS integration, but we need to make
certain that Bugzilla is not tied into one particular software
management package.</para>
<para>
Follow the instructions in the FAQ for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to
your Bugzilla e-mail gateway with the subject of <quote>[Bug
XXXX]</quote>, and you can have CVS check-in comments append
to your Bugzilla bug. If you have your check-in script include
an @resolution field, you can even change the Bugzilla bug
state.
</para>
</section>
<section id="scm">
<section id="scm" xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS">
<title>Perforce SCM</title>
<para>
You can find the project page for Bugzilla and Teamtrack Perforce integration at:
<ulink url="http://www.ravenbrook.com/project/p4dti/">
http://www.ravenbrook.com/project/p4dti</ulink>. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public Depot"
p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
You can find the project page for Bugzilla and Teamtrack
Perforce integration (p4dti) at: <ulink
url="http://www.ravenbrook.com/project/p4dti/"> http://www.ravenbrook.com/project/p4dti</ulink> . <quote>p4dti</quote> is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html"> http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
</para>
<para>
Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
patches for 2.12 will be out shortly. Check the project page regularly for updates, or
take the given patches and patch it manually. p4dti is designed to support multiple defect
trackers, and maintains its own documentation for it. Please consult the pages linked
above for further information.
</para>
<para>
Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
have synchronization problems, the easiest way to avoid them is to only put the bug
information, comments, etc. into Bugzilla, and not into the Perforce change records.
They will link anyway; merely reference the bug ID fixed in your change description,
and put a comment into Bugzilla
giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
question.
Integration of Perforce with Bugzilla, once patches are applied,
is seamless. Perforce replication information will appear below
the comments of each bug. Be certain you have a matching set of
patches for the Bugzilla version you are installing. p4dti is
designed to support multiple defect trackers, and maintains its
own documentation for it. Please consult the pages linked above
for further information.
</para>
</section>
<section id="tinderbox">
<title>Tinderbox</title>
<para>We need Tinderbox integration information</para>
<section id="tinderbox" xreflabel="Tinderbox, the Mozilla automated build management system">
<title>Tinderbox/Tinderbox2</title>
<para>We need Tinderbox integration information.</para>
</section>
</chapter>

34
mozilla/webtools/bugzilla/docs/xml/patches.xml
View File

@@ -3,6 +3,40 @@
<appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla">
<title>Useful Patches and Utilities for Bugzilla</title>
<para>Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</para>
<section id="rewrite" xreflabel="Apache mod_rewrite magic">
<title>Apache <filename>mod_rewrite</filename> magic</title>
<para>Apache's <filename>mod_rewrite</filename> module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</para>
<orderedlist>
<listitem>
<para>
Make it so if someone types
<computeroutput>http://www.foo.com/12345</computeroutput>,
Bugzilla spits back
http://www.foo.com/show_bug.cgi?id=12345. Try setting up
your VirtualHost section for Bugzilla with a rule like
this:</para>
<programlisting>
<![CDATA[
<VirtualHost 12.34.56.78>
RewriteEngine On
RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R]
</VirtualHost>
]]>
</programlisting>
</listitem>
<listitem>
<para>There are many, many more things you can do with
mod_rewrite. As time goes on, I will include many more in
the Guide. For now, though, please refer to the mod_rewrite
documentation at <ulink
url="http://www.apache.org">http://www.apache.org</ulink></para>
</listitem>
</orderedlist>
</section>
<section id="setperl" xreflabel="The setperl.csh Utility">
<title>The setperl.csh Utility</title>
<para> You can use the "setperl.csh" utility to quickly and

807
mozilla/webtools/bugzilla/docs/xml/using.xml
View File

File diff suppressed because it is too large Load Diff

129
mozilla/webtools/bugzilla/docs/xml/variants.xml
View File

@@ -1,72 +1,77 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">-->
<chapter id="variants">
<title>Bugzilla Variants</title>
<note>
<para>
I <emphasis>know</emphasis> there are more variants than just RedHat Bugzilla out there.
Please help me get information about them, their project status, and benefits there
might be in using them or in using their code in main-tree Bugzilla.
</para>
</note>
<chapter id="variants" xreflabel="Bugzilla Variants and Competitors">
<title>Bugzilla Variants and Competitors</title>
<para>I created this section to answer questions about Bugzilla
competitors and variants, then found a wonderful site which covers
an awful lot of what I wanted to discuss. Rather than quote it in
its entirety, I'll simply refer you here: <ulink
url="http://linas.org/linux/pm.html">http://linas.org/linux/pm.html</ulink></para>
<section id="rhbugzilla">
<section id="rhbugzilla" xreflabel="Red Hat Bugzilla">
<title>Red Hat Bugzilla</title>
<para>
Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
on the planet.
One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
database, as well as MySQL.
Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
<blockquote>
<literallayout>
Hello. I apologize that I am getting back to you so late. It has been difficult to keep
up with email this past week. I have checked out your updated documentation and I will
have to say very good work. A few notes and additions as follows.
(ed: from the FAQ)
>For the record, we are not using any template type implementation for the cosmetic changes
>maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have
>gotten a little carried away with it but the corporate types asked for a more standardized
>interface to match up with other projects relating to Red Hat web sites. A lot of other web
>based internal tools I am working on also look like Bugzilla.
This should probably be changed since we are now in fact using Text::Template for most
of the html rendering. You actually state this later in your numbered list.
Also number 6 contradicts number 8 where number 6 would be the most up to date status
on the Oracle port.
Additional Information:
-----------------------------
1. Comments are now stored in varchar fields of 4k in size each. If the comment is more
than 4k it is broken up into chunks and given a sort number so each comment can be re
assembled in the correct order. This was done because originally I was storing the comments
in a long datatype which unfortunately cannot be indexed or joined with another table. This
cause the search of text within the long description to be disabled for a long time. That
is now working and is nto showing any noticeble performance hit that I can tell.
2. Work is being started on internationalizing the Bugzilla source we have to allow our
Japanese customers to enter bug reports into a single bugzilla system. This will probably
be done by using the nvarchar data types supported by Oracle which allows storage of
double byte characters and also the use of the Accept-Language in the http header for
detection by Bugilla of which language to render.
3. Of course even more cosmetic changes. It is difficult to keep up with the ever
changing faces of www.redhat.com.
4. Some convenience enhancements in the administration utilities. And more integration
with other internal/external Red Hat web sites.
I hope this information may prove helpful for your documentation. Please contact
me if you have any more question or I can do anything else.
Regards
</literallayout>
</blockquote>
Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
the ability to work with Oracle, MySQL, and PostGreSQL databases
serving as the back-end, instead of just MySQL. Dave Lawrence
has worked very hard to keep Red Hat Bugzilla up-to-date, and
many people prefer the snappier-looking page layout of Red Hat
Bugzilla to the default Mozilla-standard formatting.
</para>
<para>URL: <ulink
url="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</ulink></para>
</section>
<section id="variant_fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris">
<title>Loki Bugzilla (Fenris)</title>
<para>Fenris can be found at <ulink
url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para>
</section>
<section id="variant_issuezilla" xreflabel="Issuezilla">
<title>Issuezilla</title>
<para>Issuezilla is another fork from Bugzilla, and seems nearly
as popular as the Red Hat Bugzilla fork. Some Issuezilla team
members are regular contributors to the Bugzilla mailing
list/newsgroup. Issuezilla is not the primary focus of
bug-tracking at tigris.org, however. Their Java-based
bug-tracker, <xref linkend="variant_scarab">, is under heavy development
and looks promising!</para>
<para>URL: <ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">http://issuezilla.tigris.org/servlets/ProjectHome</ulink></para>
</section>
<section id="variant_scarab" xreflabel="Scarab, a newfangled Java-based issue tracker">
<title>Scarab</title>
<para>Scarab is a promising new bug-tracking system built using
Java Serlet technology. As of this writing, no source code has
been released as a package, but you can obtain the code from
CVS.
</para>
<para>URL: <ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink></para>
</section>
<section id="variant_perforce" xreflabel="Using Perforce to track bugs">
<title>Perforce SCM</title>
<para>Although Perforce isn't really a bug tracker, it can be used
as such through the <quote>jobs</quote> functionality.</para>
<para><ulink
url="http://www.perforce.com/perforce/technotes/note052.html"></ulink>http://www.perforce.com/perforce/technotes/note052.html</para>
</section>
<section id="variant_sourceforge" xreflabel="SourceForge">
<title>SourceForge</title>
<para>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the
Internet than strictly a bug tracker, but if you're hunting for
bug-tracking for your open project, it may be just what the
software engineer ordered!</para>
<para>URL: <ulink
url="http://www.sourceforge.net">http://www.sourceforge.net</ulink></para>
</section>
</chapter>
<!-- Keep this comment at the end of the file