Skip to content

bugzilla
bugzilla
Commit d819eae3 authored by barnboy%trilobyte.net's avatar barnboy%trilobyte.net
Browse files
Options

Checkin for 2.14 release. Still some problems; this cannot yet

be used for 2.14 documentation due to inconsistencies.
parent 83103061
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 1644 additions and 694 deletions
docs/sgml/Bugzilla-Guide.sgml
View file @ d819eae3
<!DOCTYPE BOOK PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!-- Include macros -->
<!ENTITY about SYSTEM "about.sgml">
......@@ -17,99 +17,156 @@
<!ENTITY patches SYSTEM "patches.sgml">
<!ENTITY variants SYSTEM "variants.sgml">
<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
<!ENTITY revhistory SYSTEM "revhistory.sgml">
<!ENTITY bz "http://www.mozilla.org/projects/bugzilla">
<!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-cvs-ver "2.15.0">
<!ENTITY bzg-auth "Matthew P. Barnson">
<!ENTITY bzg-auth-email "<email>barnboy@NOSPAM.trilobyte.net</email>">
<!ENTITY mysql "http://www.mysql.com/">
<!ENTITY perl-ver "5.6.1">
]>
<!-- Coding standards for this document
1. Preface new or modified sections with a comment stating who
modified it and when; please also use the "authorinitials" tag.
2. There is no "two".
3. Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc.
4. Use Entities to include files for new chapters in Bugzilla-Guide.sgml.
5. Ensure all documents compile cleanly to HTML after modification.
The errors "DTD Declaration not allowed here" and "DTDDECL catalog types not supported"
are normal errors to be expected when compiling the whole guide.
6. Try to index important terms wherever possible.
7. Follow coding standards at http://www.linuxdoc.org.
8. All tags should be lowercase (needsfix)
9. Code being submitted for review should use the
"review" tag. Documentation on this is available at
http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
under section 4.9.4, "Making notes on the text while it's being written".
<!-- Coding standards for this document
10. Please use sensible spacing. The comments at the very end of each Guide
file define reasonable defaults for PSGML mode in EMACS.
Double-indent tags, use double spacing whenever possible,
try to avoid clutter and feel free to waste space in the code to make it more readable.
* Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc.
* Use Entities to include files for new chapters in Bugzilla-Guide.sgml.
* Try to use Entities for frequently-used passages of text as well.
* Ensure all documents compile cleanly to HTML after modification.
The warning, "DTDDECL catalog types not supported" is normal.
* Try to index important terms wherever possible.
* Use "glossterm" whenever you introduce a new term.
* Follow coding standards at http://www.linuxdoc.org, and
check out the KDE guidelines (they are nice, too)
http://i18n.kde.org/doc/markup.html
* All tags should be lowercase (needsfix)
* Please use sensible spacing. The comments at the very end of each
file define reasonable defaults for PSGML mode in EMACS.
Double-indent tags, use double spacing whenever possible, and
try to avoid clutter and feel free to waste space in the code to make it more readable.
-->
<BOOK ID="index">
<book id="index">
<!-- Header -->
<BOOKINFO>
<TITLE>The Bugzilla Guide</TITLE>
<PUBDATE>2001-04-25</PUBDATE>
<AUTHOR>
<FIRSTNAME>Matthew</FIRSTNAME>
<OTHERNAME>P.</OTHERNAME>
<SURNAME>Barnson</SURNAME>
<affiliation>
<address><email>barnboy@trilobyte.net</email></address>
</affiliation>
</AUTHOR>
<ABSTRACT>
<PARA>This is the documentation for Bugzilla, the Mozilla bug-tracking system.</PARA>
</ABSTRACT>
<REVHISTORY>
<REVISION>
<REVNUMBER>v2.11</REVNUMBER>
<DATE>20 December 2000</DATE>
<AUTHORINITIALS>MPB</AUTHORINITIALS>
<REVREMARK>Converted the README, FAQ, and DATABASE information into SGML
docbook format.</REVREMARK>
</REVISION>
<bookinfo>
<title>The Bugzilla Guide</title>
<pubdate>2001-04-25</pubdate>
<revhistory>
<revision>
<revnumber>v2.11</revnumber>
<date>20 December 2000</date>
<authorinitials>MPB</authorinitials>
<revremark>
Converted the README, FAQ, and DATABASE information into
SGML docbook format.
</revremark>
</revision>
<revision>
<revnumber>2.11.1</revnumber>
<date>06 March 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Took way too long to revise this for 2.12 release.
Updated FAQ to use qandaset tags instead of literallayout,
cleaned up administration section, added User Guide section,
miscellaneous FAQ updates and third-party integration information.
From this point on all new tags are lowercase in preparation for the
2.13 release of the Guide in XML format instead of SGML.
Took way too long to revise this for 2.12 release. Updated
FAQ to use qandaset tags instead of literallayout, cleaned
up administration section, added User Guide section,
miscellaneous FAQ updates and third-party integration
information. From this point on all new tags are lowercase
in preparation for the 2.13 release of the Guide in XML
format instead of SGML.
</revremark>
</revision>
<revision>
<revnumber>2.12.0</revnumber>
<date>24 April 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
moving bugs from one keyword to another, clarified possible problems with the Landfill
tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
README into the UNIX installation section, and changed the README to indicate the deprecated
status. Things I know need work: Used "simplelist" a lot, where I should have used
"procedure" to tag things. Need to lowercase all tags to be XML compliant.
Things fixed this release: Elaborated on queryhelp
interface, added FAQ regarding moving bugs from one keyword
to another, clarified possible problems with the Landfill
tutorial, fixed a boatload of typos and unclear sentence
structures. Incorporated the README into the UNIX
installation section, and changed the README to indicate the
deprecated status. Things I know need work: Used
"simplelist" a lot, where I should have used "procedure" to
tag things. Need to lowercase all tags to be XML compliant.
</revremark>
</revision>
</REVHISTORY>
<revision>
<revnumber>2.14.0</revnumber>
<date>07 August 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Attempted to integrate relevant portions of the UNIX and
Windows installation instructions, moved some data from FAQ
to Install, removed references to README from text, added
Mac OS X install instructions, fixed a bunch
of tpyos (Mark Harig), linked text that referenced other
parts of the Guide, and nuked the old MySQL permissions
section.
</revremark>
</revision>
</revhistory>
<authorgroup>
<author>
<firstname>Matthew</firstname>
<othername>P.</othername>
<surname>Barnson</surname>
<affiliation>
<address><email>barnboy@NOSPAM.trilobyte.net</email></address>
</affiliation>
</author>
<collab>
<collabname>Zach Lipton</collabname>
<affiliation>
<address><email>zach@NOSPAM.zachlipton.com</email></address>
</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>
<para>
This is the documentation for Bugzilla, the Mozilla
bug-tracking system.
</para>
<para>
Bugzilla is an enterprise-class set of software utilities
that, when used together, power issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
While it is easy to use and quite flexible, it is very
difficult for a novice to install and maintain. Although we
have provided step-by-step directions, Bugzilla is not always
easy to get working. Please be sure the person responsible
for installing and maintaining this software is a qualified
professional on operating system upon which you install
Bugzilla.
</para>
</abstract>
<KEYWORDSET>
<KEYWORD>Bugzilla</KEYWORD>
......@@ -127,15 +184,15 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- About This Guide -->
&about;
<!-- Using Bugzilla -->
&using;
<!-- Installing Bugzilla -->
&installation;
<!-- Administering Bugzilla -->
&administration;
<!-- Using Bugzilla -->
&using;
<!-- Integrating Bugzilla with Third-Party Tools -->
&integration;
......@@ -166,31 +223,26 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- Index -->
&index;
</BOOK>
</book>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/conventions.sgml
View file @ d819eae3
......@@ -89,23 +89,28 @@
</informaltable>
</section>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:upper
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/dbschema.mysql 0 → 100644
View file @ d819eae3
# MySQL dump 7.1
#
# Host: localhost Database: bugs
#--------------------------------------------------------
# Server version 3.22.32
#
# Table structure for table 'attachments'
#
CREATE TABLE attachments (
attach_id mediumint(9) DEFAULT '0' NOT NULL auto_increment,
bug_id mediumint(9) DEFAULT '0' NOT NULL,
creation_ts timestamp(14),
description mediumtext NOT NULL,
mimetype mediumtext NOT NULL,
ispatch tinyint(4),
filename mediumtext NOT NULL,
thedata longblob NOT NULL,
submitter_id mediumint(9) DEFAULT '0' NOT NULL,
PRIMARY KEY (attach_id)
);
create index index_41 on attachments (bug_id);
create index index_42 on attachments (creation_ts);
#
# Table structure for table 'bugs'
#
CREATE TABLE bugs (
bug_id mediumint(9) DEFAULT '0' NOT NULL auto_increment,
groupset bigint(20) DEFAULT '0' NOT NULL,
assigned_to mediumint(9) DEFAULT '0' NOT NULL,
bug_file_loc text,
bug_severity enum DEFAULT 'blocker' NOT NULL,
bug_status enum DEFAULT 'UNCONFIRMED' NOT NULL,
creation_ts datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
delta_ts timestamp(14),
short_desc mediumtext,
op_sys enum DEFAULT 'All' NOT NULL,
priority enum DEFAULT 'P1' NOT NULL,
product varchar(64) DEFAULT '' NOT NULL,
rep_platform enum,
reporter mediumint(9) DEFAULT '0' NOT NULL,
version varchar(16) DEFAULT '' NOT NULL,
component varchar(50) DEFAULT '' NOT NULL,
resolution enum DEFAULT '' NOT NULL,
target_milestone varchar(20) DEFAULT '---' NOT NULL,
qa_contact mediumint(9) DEFAULT '0' NOT NULL,
status_whiteboard mediumtext NOT NULL,
votes mediumint(9) DEFAULT '0' NOT NULL,
keywords mediumtext NOT NULL,
lastdiffed datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
everconfirmed tinyint(4) DEFAULT '0' NOT NULL,
PRIMARY KEY (bug_id)
);
create index index_7 on bugs (assigned_to);
create index index_8 on bugs (creation_ts);
create index index_9 on bugs (delta_ts);
create index index_10 on bugs (bug_severity);
create index index_11 on bugs (bug_status);
create index index_12 on bugs (op_sys);
create index index_13 on bugs (priority);
create index index_14 on bugs (product);
create index index_15 on bugs (reporter);
create index index_16 on bugs (version);
create index index_17 on bugs (component);
create index index_18 on bugs (resolution);
create index index_19 on bugs (target_milestone);
create index index_20 on bugs (qa_contact);
create index index_21 on bugs (votes);
#
# Table structure for table 'bugs_activity'
#
CREATE TABLE bugs_activity (
bug_id mediumint(9) DEFAULT '0' NOT NULL,
who mediumint(9) DEFAULT '0' NOT NULL,
bug_when datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
fieldid mediumint(9) DEFAULT '0' NOT NULL,
oldvalue tinytext,
newvalue tinytext
);
create index index_43 on bugs_activity (bug_id);
create index index_44 on bugs_activity (bug_when);
create index index_45 on bugs_activity (fieldid);
#
# Table structure for table 'cc'
#
CREATE TABLE cc (
bug_id mediumint(9) DEFAULT '0' NOT NULL,
who mediumint(9) DEFAULT '0' NOT NULL
);
create index index_31 on cc (who);
create unique index index_32 on cc (bug_id,who);
#
# Table structure for table 'components'
#
CREATE TABLE components (
value tinytext,
program varchar(64),
initialowner tinytext NOT NULL,
initialqacontact tinytext NOT NULL,
description mediumtext NOT NULL
);
#
# Table structure for table 'dependencies'
#
CREATE TABLE dependencies (
blocked mediumint(9) DEFAULT '0' NOT NULL,
dependson mediumint(9) DEFAULT '0' NOT NULL
);
create index index_34 on dependencies (blocked);
create index index_35 on dependencies (dependson);
#
# Table structure for table 'duplicates'
#
CREATE TABLE duplicates (
dupe_of mediumint(9) DEFAULT '0' NOT NULL,
dupe mediumint(9) DEFAULT '0' NOT NULL,
PRIMARY KEY (dupe)
);
#
# Table structure for table 'fielddefs'
#
CREATE TABLE fielddefs (
fieldid mediumint(9) DEFAULT '0' NOT NULL auto_increment,
name varchar(64) DEFAULT '' NOT NULL,
description mediumtext NOT NULL,
mailhead tinyint(4) DEFAULT '0' NOT NULL,
sortkey smallint(6) DEFAULT '0' NOT NULL,
PRIMARY KEY (fieldid)
);
create unique index index_28 on fielddefs (name);
create index index_29 on fielddefs (sortkey);
#
# Table structure for table 'groups'
#
CREATE TABLE groups (
bit bigint(20) DEFAULT '0' NOT NULL,
name varchar(255) DEFAULT '' NOT NULL,
description text NOT NULL,
isbuggroup tinyint(4) DEFAULT '0' NOT NULL,
userregexp tinytext NOT NULL
);
create unique index index_3 on groups (bit);
create unique index index_4 on groups (name);
#
# Table structure for table 'keyworddefs'
#
CREATE TABLE keyworddefs (
id smallint(6) DEFAULT '0' NOT NULL,
name varchar(64) DEFAULT '' NOT NULL,
description mediumtext,
PRIMARY KEY (id)
);
create unique index index_33 on keyworddefs (name);
#
# Table structure for table 'keywords'
#
CREATE TABLE keywords (
bug_id mediumint(9) DEFAULT '0' NOT NULL,
keywordid smallint(6) DEFAULT '0' NOT NULL
);
create index index_39 on keywords (keywordid);
create unique index index_40 on keywords (bug_id, keywordid);
#
# Table structure for table 'logincookies'
#
CREATE TABLE logincookies (
cookie mediumint(9) DEFAULT '0' NOT NULL auto_increment,
userid mediumint(9) DEFAULT '0' NOT NULL,
cryptpassword varchar(64),
hostname varchar(128),
lastused timestamp(14),
PRIMARY KEY (cookie)
);
create index index_30 on logincookies (lastused);
#
# Table structure for table 'longdescs'
#
CREATE TABLE longdescs (
bug_id mediumint(9) DEFAULT '0' NOT NULL,
who mediumint(9) DEFAULT '0' NOT NULL,
bug_when datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
thetext mediumtext
);
create index index_22 on longdescs (bug_id);
create index index_23 on longdescs (bug_when);
#
# Table structure for table 'milestones'
#
CREATE TABLE milestones (
value varchar(20) DEFAULT '' NOT NULL,
product varchar(64) DEFAULT '' NOT NULL,
sortkey smallint(6) DEFAULT '0' NOT NULL,
);
create unique index index_24 on milestones (product, value);
#
# Table structure for table 'namedqueries'
#
CREATE TABLE namedqueries (
userid mediumint(9) DEFAULT '0' NOT NULL,
name varchar(64) DEFAULT '' NOT NULL,
watchfordiffs tinyint(4) DEFAULT '0' NOT NULL,
linkinfooter tinyint(4) DEFAULT '0' NOT NULL,
query mediumtext NOT NULL
);
create unique index index_25 on namedqueries (userid, name);
create index index_26 on namedqueries (watchfordiffs);
#
# Table structure for table 'products'
#
CREATE TABLE products (
product varchar(64),
description mediumtext,
milestoneurl tinytext NOT NULL,
disallownew tinyint(4) DEFAULT '0' NOT NULL,
votesperuser smallint(6) DEFAULT '0' NOT NULL,
maxvotesperbug smallint(6) DEFAULT '10000' NOT NULL,
votestoconfirm smallint(6) DEFAULT '0' NOT NULL,
defaultmilestone varchar(20) DEFAULT '---' NOT NULL
);
#
# Table structure for table 'profiles'
#
CREATE TABLE profiles (
userid mediumint(9) DEFAULT '0' NOT NULL auto_increment,
login_name varchar(255) DEFAULT '' NOT NULL,
password varchar(16),
cryptpassword varchar(64),
realname varchar(255),
groupset bigint(20) DEFAULT '0' NOT NULL,
emailnotification enum DEFAULT 'ExcludeSelfChanges' NOT NULL,
disabledtext mediumtext NOT NULL,
newemailtech tinyint(4) DEFAULT '0' NOT NULL,
mybugslink tinyint(4) DEFAULT '1' NOT NULL,
blessgroupset bigint(20) DEFAULT '0' NOT NULL,
PRIMARY KEY (userid)
);
create unique index index_27 on profiles (login_name);
#
# Table structure for table 'profiles_activity'
#
CREATE TABLE profiles_activity (
userid mediumint(9) DEFAULT '0' NOT NULL,
who mediumint(9) DEFAULT '0' NOT NULL,
profiles_when datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
fieldid mediumint(9) DEFAULT '0' NOT NULL,
oldvalue tinytext,
newvalue tinytext
);
create index index_0 on profiles_activity (userid);
create index index_1 on profiles_activity (profiles_when);
create index index_2 on profiles_activity (fieldid);
#
# Table structure for table 'shadowlog'
#
CREATE TABLE shadowlog (
id int(11) DEFAULT '0' NOT NULL auto_increment,
ts timestamp(14),
reflected tinyint(4) DEFAULT '0' NOT NULL,
command mediumtext NOT NULL,
PRIMARY KEY (id)
);
create index index_38 on shadowlog (reflected);
#
# Table structure for table 'versions'
#
CREATE TABLE versions (
value tinytext,
program varchar(64) DEFAULT '' NOT NULL
);
#
# Table structure for table 'votes'
#
CREATE TABLE votes (
who mediumint(9) DEFAULT '0' NOT NULL,
bug_id mediumint(9) DEFAULT '0' NOT NULL,
count smallint(6) DEFAULT '0' NOT NULL
);
create index index_5 on votes (who);
create index index_6 on votes (bug_id);
#
# Table structure for table 'watch'
#
CREATE TABLE watch (
watcher mediumint(9) DEFAULT '0' NOT NULL,
watched mediumint(9) DEFAULT '0' NOT NULL
);
create index index_36 on watch (watched);
create unique index index_37 on watch (watcher, watched);
docs/sgml/faq.sgml
View file @ d819eae3
This source diff could not be displayed because it is too large. You can view the blob instead.
docs/sgml/gfdl.sgml
View file @ d819eae3
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="gfdl">
<title>GNU Free Documentation License</title>
......@@ -450,19 +450,25 @@ of this license document, but changing it is not allowed.</para>
</sect1>
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:nil
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-parent-document: ("Bugzilla-Guide.sgml" "appendix")
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-local-catalogs: CATALOG
sgml-validate-command: "nsgmls -s gfdl.sgml"
ispell-skip-sgml: t
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/glossary.sgml
View file @ d819eae3
<!-- <!DOCTYPE glossary PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<glossary id="glossary">
<glossdiv id="gloss_a">
<title>A</title>
<glossentry>
<glossterm>There are no entries for A</glossterm>
<glossdef>
<para></para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_b">
<title>B</title>
<glossentry>
<glossterm>Bug</glossterm>
<glossdef>
<para>A "Bug" in Bugzilla refers to an issue entered into the database which has an associated number, assignments, comments, etc. Many also refer to a "Ticket" or "Issue"; in this context, they are synonymous.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bug Number</glossterm>
<glossdef>
<para>Each Bugzilla Bug is assigned a number that uniquely identifies that Bug. The Bug associated with a Bug Number can be pulled up via a query, or easily from the very front page by typing the number in the "Find" box.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bug Life Cycle</glossterm>
<glossdef>
<para>A Bug has stages through which it must pass before becoming a "closed bug", including acceptance, resolution, and verification. The "Bug Life Cycle" is moderately flexible according to the needs of the organization using it, though.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_i">
<title>I</title>
<glossentry id="gloss_infiniteloop">
<glossterm>Infinite Loop</glossterm>
<glosssee otherterm="gloss_recursion">
</glossentry>
</glossdiv>
<glossdiv id="gloss_p">
<title>P</title>
<glossentry>
<glossterm id="gloss_product">Product</glossterm>
<glossdef>
<para>A Product is a broad category of types of bugs. In general, there are several Components to a Product. A Product also defines a default Group (used for Bug Security) for all bugs entered into components beneath it.</para>
<example>
<title>A Sample Product</title>
<para>A company sells a software product called "X". They also maintain some older software called "Y", and have a secret project "Z". An effective use of Products might be to create Products "X", "Y", and "Z", each with Components "User Interface", "Database", and "Business Logic". They might also change group permissions so that only those people who are members of Group "Z" can see components and bugs under Product "Z".</para>
</example>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_q">
<title>Q</title>
<glossentry>
<glossterm>Q/A</glossterm>
<glossdef>
<para>"Q/A" is short for "Quality Assurance". In most large software development organizations, there is a team devoted to ensuring the product meets minimum standards before shipping. This team will also generally want to track the progress of bugs over their life cycle, thus the need for the "Q/A Contact" field in a Bug.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_r">
<title>R</title>
<glossentry>
<glossterm id="gloss_recursion">Recursion</glossterm>
<glosssee otherterm="gloss_infiniteloop">
</glossentry>
</glossdiv>
<glossdiv id="gloss_z">
<title>Z</title>
<glossentry>
<glossterm>Zarro Boogs Found</glossterm>
<glossdef>
<para>This is the cryptic response sent by Bugzilla when a query returned no results. It is just a goofy way of saying "Zero Bugs Found".</para>
</glossdef>
</glossentry>
</glossdiv>
</glossary>
<glossary id="glossary">
<glossdiv>
<title>0-9, high ascii</title>
<glossentry>
<glossterm>.htaccess</glossterm>
<glossdef>
<para>
Apache web server, and other NCSA-compliant web servers,
observe the convention of using files in directories
called <filename>.htaccess</filename> files. These
restrict parameters of the web server. In Bugzilla, they
are used to restrict access to certain files which would
otherwise compromise your installation. For instance, the
<filename>localconfig</filename> file contains the
password to your database. If this information were
generally available, and remote access to your database
turned on, you risk corruption of your database by
computer criminals or the curious.
</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_a">
<title>A</title>
<glossentry>
<glossterm>There are no entries for A</glossterm>
<glossdef>
<para></para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_b">
<title>B</title>
<glossentry>
<glossterm>Bug</glossterm>
<glossdef>
<para>
A <quote>Bug</quote> in Bugzilla refers to an issue
entered into the database which has an associated number,
assignments, comments, etc. Some also refer to a
<quote>tickets</quote> or <quote>issues</quote>; in the
context of Bugzilla, they are synonymous.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bug Number</glossterm>
<glossdef>
<para>
Each Bugzilla Bug is assigned a number that uniquely
identifies that Bug. The Bug associated with a Bug Number
can be pulled up via a query, or easily from the very
front page by typing the number in the "Find" box.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bug Life Cycle</glossterm>
<glossdef>
<para>A Bug has stages through which it must pass before
becoming a <quote>closed bug</quote>, including
acceptance, resolution, and verification. The <quote>Bug
Life Cycle</quote> is moderately flexible according to
the needs of the organization using it, though.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_i">
<title>I</title>
<glossentry id="gloss_infiniteloop">
<glossterm>Infinite Loop</glossterm>
<glossdef>
<para>A loop of information that never ends; see recursion.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_p">
<title>P</title>
<glossentry>
<glossterm id="gloss_product">Product</glossterm>
<glossdef>
<para>A Product is a broad category of types of bugs. In
general, there are several Components to a Product. A
Product also defines a default Group (used for Bug
Security) for all bugs entered into components beneath
it.</para>
<example>
<title>A Sample Product</title>
<para>A company sells a software product called
<quote>X</quote>. They also maintain some older
software called <quote>Y</quote>, and have a secret
project <quote>Z</quote>. An effective use of Products
might be to create Products <quote>X</quote>,
<quote>Y</quote>, <quote>Z</quote>, each with Components
of User Interface, Database, and Business Logic. They
might also change group permissions so that only those
people who are members of Group <quote>Z</quote> can see
components and bugs under Product
<quote>Z</quote>.</para>
</example>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_q">
<title>Q</title>
<glossentry>
<glossterm>QA</glossterm>
<glossdef>
<para><quote>QA</quote>, <quote>Q/A</quote>, and
<quote>Q.A.</quote> are short for <quote>Quality
Assurance</quote>. In most large software development
organizations, there is a team devoted to ensuring the
product meets minimum standards before shipping. This
team will also generally want to track the progress of
bugs over their life cycle, thus the need for the
<quote>QA Contact</quote> field in a Bug.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_r">
<title>R</title>
<glossentry>
<glossterm id="gloss_recursion">Recursion</glossterm>
<glossdef>
<para>The property of a function looking back at itself for
something. <quote>GNU</quote>, for instance, stands for
<quote>GNU's Not UNIX</quote>, thus recursing upon itself
for definition. For further clarity, see Infinite
Loop.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_z">
<title>Z</title>
<glossentry>
<glossterm>Zarro Boogs Found</glossterm>
<glossdef>
<para>This is the cryptic response sent by Bugzilla when a
query returned no results. It is just a goofy way of
saying "Zero Bugs Found".</para>
</glossdef>
</glossentry>
</glossdiv>
</glossary>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/index.sgml
View file @ d819eae3
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-always-quote-attributes:t
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/integration.sgml
View file @ d819eae3
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" >
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<!-- Keep these tools listings in alphabetical order please. -MPB -->
......@@ -12,14 +12,13 @@
<section id="cvs">
<title>CVS</title>
<para>We need CVS integration information</para>
<para>CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</para>
</section>
<section id="scm">
<title>Perforce SCM</title>
<para>
Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
You can find the main project page at
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"
......@@ -54,22 +53,25 @@
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/patches.sgml
View file @ d819eae3
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="patches">
<appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla">
<title>Useful Patches and Utilities for Bugzilla</title>
<section id="setperl">
<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 easily
change the path to perl on all your Bugzilla files.
This is a C-shell script; if you do not have "csh" or "tcsh" in the search
path on your system, it will not work!
<para> You can use the "setperl.csh" utility to quickly and
easily change the path to perl on all your Bugzilla files. This
is a C-shell script; if you do not have "csh" or "tcsh" in the
search path on your system, it will not work!
</para>
<procedure>
<step>
......@@ -28,18 +27,15 @@
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
</computeroutput>
<computeroutput> <prompt>bash#</prompt> <command>wget -O
setperl.csh
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command> </computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+x setperl.csh</command>
</computeroutput>
<computeroutput> <prompt>bash#</prompt> <command>chmod
u+x setperl.csh</command> </computeroutput>
</para>
</step>
</substeps>
......@@ -59,10 +55,8 @@
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+x duplicates.cgi</command>
</computeroutput>
<computeroutput> <prompt>bash#</prompt> <command>chmod
u+x duplicates.cgi</command> </computeroutput>
</para>
</step>
<step>
......@@ -80,16 +74,14 @@
Run the script:
</para>
<para>
<computeroutput>
<prompt>bash#</prompt>
<computeroutput> <prompt>bash#</prompt>
<command>./setperl.csh /your/path/to/perl</command>
</computeroutput>
<example>
<title>Using Setperl to set your perl path</title>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.csh /usr/bin/perl</command>
<computeroutput> <prompt>bash#</prompt>
<command>./setperl.csh /usr/bin/perl</command>
</computeroutput>
</para>
</example>
......@@ -101,22 +93,23 @@
<section id="cmdline">
<title>Command-line Bugzilla Queries</title>
<para>
Users can query Bugzilla from the command line using
this suite of utilities.
Users can query Bugzilla from the command line using this suite
of utilities.
</para>
<para>
The query.conf file contains the mapping from options to field
names and comparison types. Quoted option names are "grepped" for, so
it should be easy to edit this file. Comments (#) have no effect; you
must make sure these lines do not contain any quoted "option"
names and comparison types. Quoted option names are "grepped"
for, so it should be easy to edit this file. Comments (#) have
no effect; you must make sure these lines do not contain any
quoted "option"
</para>
<para>
buglist is a shell script which submits a Bugzilla query and writes the
resulting HTML page to stdout. It supports both short options,
(such as "-Afoo" or "-Rbar") and long options (such as
"--assignedto=foo" or "--reporter=bar"). If the first character
of an option is not "-", it is treated as if it were prefixed
with "--default=".
buglist is a shell script which submits a Bugzilla query and
writes the resulting HTML page to stdout. It supports both
short options, (such as "-Afoo" or "-Rbar") and long options
(such as "--assignedto=foo" or "--reporter=bar"). If the first
character of an option is not "-", it is treated as if it were
prefixed with "--default=".
</para>
<para>
The columlist is taken from the COLUMNLIST environment variable.
......@@ -128,10 +121,10 @@
<para>
bugs is a simple shell script which calls buglist and extracts
the bug numbers from the output. Adding the prefix
"http://bugzilla.mozilla.org/buglist.cgi?bug_id="
turns the bug list into a working link if any bugs are found.
Counting bugs is easy. Pipe the results through
<command>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</command>
"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug
list into a working link if any bugs are found. Counting bugs is
easy. Pipe the results through <command>sed -e 's/,/ /g' | wc |
awk '{printf $2 "\n"}'</command>
</para>
<para>
Akkana says she has good results piping buglist output through
......@@ -145,26 +138,23 @@
<substeps>
<step>
<para>
<computeroutput>
<prompt>bash$</prompt>
<command>wget -O query.conf 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</command>
</computeroutput>
<computeroutput> <prompt>bash$</prompt> <command>wget -O
query.conf
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</command> </computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash$</prompt>
<command>wget -O buglist 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</command>
</computeroutput>
<computeroutput> <prompt>bash$</prompt> <command>wget -O
buglist
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</command> </computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>wget -O bugs 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command>
</computeroutput>
<computeroutput> <prompt>bash#</prompt> <command>wget -O
bugs
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command> </computeroutput>
</para>
</step>
</substeps>
......@@ -185,53 +175,64 @@
<title>The Quicksearch Utility</title>
<para>
Quicksearch is a new, experimental feature of the 2.12 release.
It consist of two Javascript files, "quicksearch.js" and "localconfig.js",
and two documentation files, "quicksearch.html" and "quicksearchhack.html"
It consist of two Javascript files, "quicksearch.js" and
"localconfig.js", and two documentation files,
"quicksearch.html" and "quicksearchhack.html"
</para>
<para>
The index.html page has been updated to include the QuickSearch text box.
The index.html page has been updated to include the QuickSearch
text box.
</para>
<para>
To take full advantage of the query power, the Bugzilla maintainer must
edit "localconfig.js" according to the value sets used in the local installation.
To take full advantage of the query power, the Bugzilla
maintainer must edit "localconfig.js" according to the value
sets used in the local installation.
</para>
<para>
Currently, keywords must be hard-coded in localconfig.js. If they are not,
keywords are not automatically recognized. This means, if localconfig.js
is left unconfigured, that searching for a bug with the "foo" keyword
will only find bugs with "foo" in the summary, status whiteboard, product or
component name, but not those with the keyword "foo".
Currently, keywords must be hard-coded in localconfig.js. If
they are not, keywords are not automatically recognized. This
means, if localconfig.js is left unconfigured, that searching
for a bug with the "foo" keyword will only find bugs with "foo"
in the summary, status whiteboard, product or component name,
but not those with the keyword "foo".
</para>
<para>
Workarounds for Bugzilla users:
<simplelist>
<member>search for '!foo' (this will find only bugs with the keyword "foo"</member>
<member>search 'foo,!foo' (equivalent to 'foo OR keyword:foo')</member>
<member>search for '!foo' (this will find only bugs with the
keyword "foo"</member>
<member>search 'foo,!foo' (equivalent to 'foo OR
keyword:foo')</member>
</simplelist>
</para>
<para>
When this tool is ported from client-side JavaScript to server-side Perl,
the requirement for hard-coding keywords can be fixed.
<ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=70907">This bug</ulink>
has details.
When this tool is ported from client-side JavaScript to
server-side Perl, the requirement for hard-coding keywords can
be fixed. <ulink
url="http://bugzilla.mozilla.org/show_bug.cgi?id=70907">This bug</ulink> has details.
</para>
</section>
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/requiredsoftware.sgml
View file @ d819eae3
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="downloadlinks">
<title>Software Download Links</title>
......@@ -15,7 +15,7 @@
http://www.mozilla.org/projects/bugzilla/</ulink>
</para>
<para>
MySQL: <ulink url="http://www.mysql.org/">http://www.mysql.org/</ulink>
MySQL: <ulink url="http://www.mysql.com/">http://www.mysql.com/</ulink>
</para>
<para>
Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink>
......@@ -63,20 +63,24 @@
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/using.sgml
View file @ d819eae3
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<!-- TOC
Chapter: Using Bugzilla
......@@ -38,19 +38,19 @@ Chapter: Using Bugzilla
<section id="whatis">
<title>What is Bugzilla?</title>
<para>
Bugzilla is one example of a class of programs called "Defect Tracking Systems",
or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
groups of developers to keep track of outstanding bugs in their product effectively.
Bugzilla was originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy
bug-tracking database used internally for Netscape Communications. Terry later ported
Bugzilla to
Perl from TCL, and in Perl it remains to this day.
Most commercial defect-tracking software vendors at the
time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla). It
is now the de-facto standard defect-tracking system against which all others are
measured.
Bugzilla is one example of a class of programs called "Defect
Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
Tracking Systems allow individual or groups of developers to keep
track of outstanding bugs in their product effectively. Bugzilla was
originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy bug-tracking database used internally for
Netscape Communications. Terry later ported Bugzilla to Perl from
TCL, and in Perl it remains to this day. Most commercial
defect-tracking software vendors at the time charged enormous
licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser
project, Mozilla). It is now the de-facto standard defect-tracking
system against which all others are measured.
</para>
<para>
Bugzilla has matured immensely, and now boasts many advanced features. These include:
......@@ -87,13 +87,13 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
email, XML, and HTTP APIs
email, XML, console, and HTTP APIs
</para>
</listitem>
<listitem>
<para>
available integration with automated software configuration management systems, including
Perforce and CVS.
Perforce and CVS
</para>
</listitem>
<listitem>
......@@ -137,7 +137,7 @@ Chapter: Using Bugzilla
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
dropped or ignored.
</para>
<para>
These days, many companies are finding that integrated defect-tracking
......@@ -223,12 +223,12 @@ Chapter: Using Bugzilla
<section id="myaccount">
<title>Create a Bugzilla Account</title>
<para>
First thing's first! If you want to use Bugzilla, first you need to create
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:
<ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/">
http://landfill.tequilarista.org/mozilla/bugzilla/</ulink>
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/">
http://landfill.tequilarista.org/bugzilla-tip/</ulink>
</para>
<orderedlist>
<listitem>
......@@ -560,15 +560,15 @@ Chapter: Using Bugzilla
<orderedlist>
<listitem>
<para>
Go back to <ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/">
http://landfill.tequilarista.org/mozilla/bugzilla/</ulink>
Go back to <ulink url="http://landfill.tequilarista.org/bugzilla-tip/">
http://landfill.tequilarista.org/bugzilla-tip/</ulink>
in your browser.
</para>
</listitem>
<listitem>
<para>
Select the
<ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/enter_bug.cgi">
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi">
Enter a new bug report</ulink> link.
</para>
</listitem>
......@@ -716,7 +716,7 @@ Chapter: Using Bugzilla
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
<ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/query.cgi?GoAheadAndLogIn=1">
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1">
Landfill</ulink>.
</para>
<section id="accountsettings">
......@@ -861,17 +861,20 @@ Chapter: Using Bugzilla
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:Bugzilla-Guide\.sgml
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/variants.sgml
View file @ d819eae3
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">-->
<chapter id="variants">
<title>Bugzilla Variants</title>
......@@ -68,20 +68,24 @@ Regards
</para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/Bugzilla-Guide.xml
View file @ d819eae3
<!DOCTYPE BOOK PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!-- Include macros -->
<!ENTITY about SYSTEM "about.sgml">
......@@ -17,99 +17,156 @@
<!ENTITY patches SYSTEM "patches.sgml">
<!ENTITY variants SYSTEM "variants.sgml">
<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
<!ENTITY revhistory SYSTEM "revhistory.sgml">
<!ENTITY bz "http://www.mozilla.org/projects/bugzilla">
<!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-cvs-ver "2.15.0">
<!ENTITY bzg-auth "Matthew P. Barnson">
<!ENTITY bzg-auth-email "<email>barnboy@NOSPAM.trilobyte.net</email>">
<!ENTITY mysql "http://www.mysql.com/">
<!ENTITY perl-ver "5.6.1">
]>
<!-- Coding standards for this document
1. Preface new or modified sections with a comment stating who
modified it and when; please also use the "authorinitials" tag.
2. There is no "two".
3. Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc.
4. Use Entities to include files for new chapters in Bugzilla-Guide.sgml.
5. Ensure all documents compile cleanly to HTML after modification.
The errors "DTD Declaration not allowed here" and "DTDDECL catalog types not supported"
are normal errors to be expected when compiling the whole guide.
6. Try to index important terms wherever possible.
7. Follow coding standards at http://www.linuxdoc.org.
8. All tags should be lowercase (needsfix)
9. Code being submitted for review should use the
"review" tag. Documentation on this is available at
http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
under section 4.9.4, "Making notes on the text while it's being written".
<!-- Coding standards for this document
10. Please use sensible spacing. The comments at the very end of each Guide
file define reasonable defaults for PSGML mode in EMACS.
Double-indent tags, use double spacing whenever possible,
try to avoid clutter and feel free to waste space in the code to make it more readable.
* Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc.
* Use Entities to include files for new chapters in Bugzilla-Guide.sgml.
* Try to use Entities for frequently-used passages of text as well.
* Ensure all documents compile cleanly to HTML after modification.
The warning, "DTDDECL catalog types not supported" is normal.
* Try to index important terms wherever possible.
* Use "glossterm" whenever you introduce a new term.
* Follow coding standards at http://www.linuxdoc.org, and
check out the KDE guidelines (they are nice, too)
http://i18n.kde.org/doc/markup.html
* All tags should be lowercase (needsfix)
* Please use sensible spacing. The comments at the very end of each
file define reasonable defaults for PSGML mode in EMACS.
Double-indent tags, use double spacing whenever possible, and
try to avoid clutter and feel free to waste space in the code to make it more readable.
-->
<BOOK ID="index">
<book id="index">
<!-- Header -->
<BOOKINFO>
<TITLE>The Bugzilla Guide</TITLE>
<PUBDATE>2001-04-25</PUBDATE>
<AUTHOR>
<FIRSTNAME>Matthew</FIRSTNAME>
<OTHERNAME>P.</OTHERNAME>
<SURNAME>Barnson</SURNAME>
<affiliation>
<address><email>barnboy@trilobyte.net</email></address>
</affiliation>
</AUTHOR>
<ABSTRACT>
<PARA>This is the documentation for Bugzilla, the Mozilla bug-tracking system.</PARA>
</ABSTRACT>
<REVHISTORY>
<REVISION>
<REVNUMBER>v2.11</REVNUMBER>
<DATE>20 December 2000</DATE>
<AUTHORINITIALS>MPB</AUTHORINITIALS>
<REVREMARK>Converted the README, FAQ, and DATABASE information into SGML
docbook format.</REVREMARK>
</REVISION>
<bookinfo>
<title>The Bugzilla Guide</title>
<pubdate>2001-04-25</pubdate>
<revhistory>
<revision>
<revnumber>v2.11</revnumber>
<date>20 December 2000</date>
<authorinitials>MPB</authorinitials>
<revremark>
Converted the README, FAQ, and DATABASE information into
SGML docbook format.
</revremark>
</revision>
<revision>
<revnumber>2.11.1</revnumber>
<date>06 March 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Took way too long to revise this for 2.12 release.
Updated FAQ to use qandaset tags instead of literallayout,
cleaned up administration section, added User Guide section,
miscellaneous FAQ updates and third-party integration information.
From this point on all new tags are lowercase in preparation for the
2.13 release of the Guide in XML format instead of SGML.
Took way too long to revise this for 2.12 release. Updated
FAQ to use qandaset tags instead of literallayout, cleaned
up administration section, added User Guide section,
miscellaneous FAQ updates and third-party integration
information. From this point on all new tags are lowercase
in preparation for the 2.13 release of the Guide in XML
format instead of SGML.
</revremark>
</revision>
<revision>
<revnumber>2.12.0</revnumber>
<date>24 April 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
moving bugs from one keyword to another, clarified possible problems with the Landfill
tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
README into the UNIX installation section, and changed the README to indicate the deprecated
status. Things I know need work: Used "simplelist" a lot, where I should have used
"procedure" to tag things. Need to lowercase all tags to be XML compliant.
Things fixed this release: Elaborated on queryhelp
interface, added FAQ regarding moving bugs from one keyword
to another, clarified possible problems with the Landfill
tutorial, fixed a boatload of typos and unclear sentence
structures. Incorporated the README into the UNIX
installation section, and changed the README to indicate the
deprecated status. Things I know need work: Used
"simplelist" a lot, where I should have used "procedure" to
tag things. Need to lowercase all tags to be XML compliant.
</revremark>
</revision>
</REVHISTORY>
<revision>
<revnumber>2.14.0</revnumber>
<date>07 August 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Attempted to integrate relevant portions of the UNIX and
Windows installation instructions, moved some data from FAQ
to Install, removed references to README from text, added
Mac OS X install instructions, fixed a bunch
of tpyos (Mark Harig), linked text that referenced other
parts of the Guide, and nuked the old MySQL permissions
section.
</revremark>
</revision>
</revhistory>
<authorgroup>
<author>
<firstname>Matthew</firstname>
<othername>P.</othername>
<surname>Barnson</surname>
<affiliation>
<address><email>barnboy@NOSPAM.trilobyte.net</email></address>
</affiliation>
</author>
<collab>
<collabname>Zach Lipton</collabname>
<affiliation>
<address><email>zach@NOSPAM.zachlipton.com</email></address>
</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>
<para>
This is the documentation for Bugzilla, the Mozilla
bug-tracking system.
</para>
<para>
Bugzilla is an enterprise-class set of software utilities
that, when used together, power issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
While it is easy to use and quite flexible, it is very
difficult for a novice to install and maintain. Although we
have provided step-by-step directions, Bugzilla is not always
easy to get working. Please be sure the person responsible
for installing and maintaining this software is a qualified
professional on operating system upon which you install
Bugzilla.
</para>
</abstract>
<KEYWORDSET>
<KEYWORD>Bugzilla</KEYWORD>
......@@ -127,15 +184,15 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- About This Guide -->
&about;
<!-- Using Bugzilla -->
&using;
<!-- Installing Bugzilla -->
&installation;
<!-- Administering Bugzilla -->
&administration;
<!-- Using Bugzilla -->
&using;
<!-- Integrating Bugzilla with Third-Party Tools -->
&integration;
......@@ -166,31 +223,26 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- Index -->
&index;
</BOOK>
</book>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/conventions.xml
View file @ d819eae3
......@@ -89,23 +89,28 @@
</informaltable>
</section>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:upper
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/dbschema.mysql 0 → 100644
View file @ d819eae3
# MySQL dump 7.1
#
# Host: localhost Database: bugs
#--------------------------------------------------------
# Server version 3.22.32
#
# Table structure for table 'attachments'
#
CREATE TABLE attachments (
attach_id mediumint(9) DEFAULT '0' NOT NULL auto_increment,
bug_id mediumint(9) DEFAULT '0' NOT NULL,
creation_ts timestamp(14),
description mediumtext NOT NULL,
mimetype mediumtext NOT NULL,
ispatch tinyint(4),
filename mediumtext NOT NULL,
thedata longblob NOT NULL,
submitter_id mediumint(9) DEFAULT '0' NOT NULL,
PRIMARY KEY (attach_id)
);
create index index_41 on attachments (bug_id);
create index index_42 on attachments (creation_ts);
#
# Table structure for table 'bugs'
#
CREATE TABLE bugs (
bug_id mediumint(9) DEFAULT '0' NOT NULL auto_increment,
groupset bigint(20) DEFAULT '0' NOT NULL,
assigned_to mediumint(9) DEFAULT '0' NOT NULL,
bug_file_loc text,
bug_severity enum DEFAULT 'blocker' NOT NULL,
bug_status enum DEFAULT 'UNCONFIRMED' NOT NULL,
creation_ts datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
delta_ts timestamp(14),
short_desc mediumtext,
op_sys enum DEFAULT 'All' NOT NULL,
priority enum DEFAULT 'P1' NOT NULL,
product varchar(64) DEFAULT '' NOT NULL,
rep_platform enum,
reporter mediumint(9) DEFAULT '0' NOT NULL,
version varchar(16) DEFAULT '' NOT NULL,
component varchar(50) DEFAULT '' NOT NULL,
resolution enum DEFAULT '' NOT NULL,
target_milestone varchar(20) DEFAULT '---' NOT NULL,
qa_contact mediumint(9) DEFAULT '0' NOT NULL,
status_whiteboard mediumtext NOT NULL,
votes mediumint(9) DEFAULT '0' NOT NULL,
keywords mediumtext NOT NULL,
lastdiffed datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
everconfirmed tinyint(4) DEFAULT '0' NOT NULL,
PRIMARY KEY (bug_id)
);
create index index_7 on bugs (assigned_to);
create index index_8 on bugs (creation_ts);
create index index_9 on bugs (delta_ts);
create index index_10 on bugs (bug_severity);
create index index_11 on bugs (bug_status);
create index index_12 on bugs (op_sys);
create index index_13 on bugs (priority);
create index index_14 on bugs (product);
create index index_15 on bugs (reporter);
create index index_16 on bugs (version);
create index index_17 on bugs (component);
create index index_18 on bugs (resolution);
create index index_19 on bugs (target_milestone);
create index index_20 on bugs (qa_contact);
create index index_21 on bugs (votes);
#
# Table structure for table 'bugs_activity'
#
CREATE TABLE bugs_activity (
bug_id mediumint(9) DEFAULT '0' NOT NULL,
who mediumint(9) DEFAULT '0' NOT NULL,
bug_when datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
fieldid mediumint(9) DEFAULT '0' NOT NULL,
oldvalue tinytext,
newvalue tinytext
);
create index index_43 on bugs_activity (bug_id);
create index index_44 on bugs_activity (bug_when);
create index index_45 on bugs_activity (fieldid);
#
# Table structure for table 'cc'
#
CREATE TABLE cc (
bug_id mediumint(9) DEFAULT '0' NOT NULL,
who mediumint(9) DEFAULT '0' NOT NULL
);
create index index_31 on cc (who);
create unique index index_32 on cc (bug_id,who);
#
# Table structure for table 'components'
#
CREATE TABLE components (
value tinytext,
program varchar(64),
initialowner tinytext NOT NULL,
initialqacontact tinytext NOT NULL,
description mediumtext NOT NULL
);
#
# Table structure for table 'dependencies'
#
CREATE TABLE dependencies (
blocked mediumint(9) DEFAULT '0' NOT NULL,
dependson mediumint(9) DEFAULT '0' NOT NULL
);
create index index_34 on dependencies (blocked);
create index index_35 on dependencies (dependson);
#
# Table structure for table 'duplicates'
#
CREATE TABLE duplicates (
dupe_of mediumint(9) DEFAULT '0' NOT NULL,
dupe mediumint(9) DEFAULT '0' NOT NULL,
PRIMARY KEY (dupe)
);
#
# Table structure for table 'fielddefs'
#
CREATE TABLE fielddefs (
fieldid mediumint(9) DEFAULT '0' NOT NULL auto_increment,
name varchar(64) DEFAULT '' NOT NULL,
description mediumtext NOT NULL,
mailhead tinyint(4) DEFAULT '0' NOT NULL,
sortkey smallint(6) DEFAULT '0' NOT NULL,
PRIMARY KEY (fieldid)
);
create unique index index_28 on fielddefs (name);
create index index_29 on fielddefs (sortkey);
#
# Table structure for table 'groups'
#
CREATE TABLE groups (
bit bigint(20) DEFAULT '0' NOT NULL,
name varchar(255) DEFAULT '' NOT NULL,
description text NOT NULL,
isbuggroup tinyint(4) DEFAULT '0' NOT NULL,
userregexp tinytext NOT NULL
);
create unique index index_3 on groups (bit);
create unique index index_4 on groups (name);
#
# Table structure for table 'keyworddefs'
#
CREATE TABLE keyworddefs (
id smallint(6) DEFAULT '0' NOT NULL,
name varchar(64) DEFAULT '' NOT NULL,
description mediumtext,
PRIMARY KEY (id)
);
create unique index index_33 on keyworddefs (name);
#
# Table structure for table 'keywords'
#
CREATE TABLE keywords (
bug_id mediumint(9) DEFAULT '0' NOT NULL,
keywordid smallint(6) DEFAULT '0' NOT NULL
);
create index index_39 on keywords (keywordid);
create unique index index_40 on keywords (bug_id, keywordid);
#
# Table structure for table 'logincookies'
#
CREATE TABLE logincookies (
cookie mediumint(9) DEFAULT '0' NOT NULL auto_increment,
userid mediumint(9) DEFAULT '0' NOT NULL,
cryptpassword varchar(64),
hostname varchar(128),
lastused timestamp(14),
PRIMARY KEY (cookie)
);
create index index_30 on logincookies (lastused);
#
# Table structure for table 'longdescs'
#
CREATE TABLE longdescs (
bug_id mediumint(9) DEFAULT '0' NOT NULL,
who mediumint(9) DEFAULT '0' NOT NULL,
bug_when datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
thetext mediumtext
);
create index index_22 on longdescs (bug_id);
create index index_23 on longdescs (bug_when);
#
# Table structure for table 'milestones'
#
CREATE TABLE milestones (
value varchar(20) DEFAULT '' NOT NULL,
product varchar(64) DEFAULT '' NOT NULL,
sortkey smallint(6) DEFAULT '0' NOT NULL,
);
create unique index index_24 on milestones (product, value);
#
# Table structure for table 'namedqueries'
#
CREATE TABLE namedqueries (
userid mediumint(9) DEFAULT '0' NOT NULL,
name varchar(64) DEFAULT '' NOT NULL,
watchfordiffs tinyint(4) DEFAULT '0' NOT NULL,
linkinfooter tinyint(4) DEFAULT '0' NOT NULL,
query mediumtext NOT NULL
);
create unique index index_25 on namedqueries (userid, name);
create index index_26 on namedqueries (watchfordiffs);
#
# Table structure for table 'products'
#
CREATE TABLE products (
product varchar(64),
description mediumtext,
milestoneurl tinytext NOT NULL,
disallownew tinyint(4) DEFAULT '0' NOT NULL,
votesperuser smallint(6) DEFAULT '0' NOT NULL,
maxvotesperbug smallint(6) DEFAULT '10000' NOT NULL,
votestoconfirm smallint(6) DEFAULT '0' NOT NULL,
defaultmilestone varchar(20) DEFAULT '---' NOT NULL
);
#
# Table structure for table 'profiles'
#
CREATE TABLE profiles (
userid mediumint(9) DEFAULT '0' NOT NULL auto_increment,
login_name varchar(255) DEFAULT '' NOT NULL,
password varchar(16),
cryptpassword varchar(64),
realname varchar(255),
groupset bigint(20) DEFAULT '0' NOT NULL,
emailnotification enum DEFAULT 'ExcludeSelfChanges' NOT NULL,
disabledtext mediumtext NOT NULL,
newemailtech tinyint(4) DEFAULT '0' NOT NULL,
mybugslink tinyint(4) DEFAULT '1' NOT NULL,
blessgroupset bigint(20) DEFAULT '0' NOT NULL,
PRIMARY KEY (userid)
);
create unique index index_27 on profiles (login_name);
#
# Table structure for table 'profiles_activity'
#
CREATE TABLE profiles_activity (
userid mediumint(9) DEFAULT '0' NOT NULL,
who mediumint(9) DEFAULT '0' NOT NULL,
profiles_when datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
fieldid mediumint(9) DEFAULT '0' NOT NULL,
oldvalue tinytext,
newvalue tinytext
);
create index index_0 on profiles_activity (userid);
create index index_1 on profiles_activity (profiles_when);
create index index_2 on profiles_activity (fieldid);
#
# Table structure for table 'shadowlog'
#
CREATE TABLE shadowlog (
id int(11) DEFAULT '0' NOT NULL auto_increment,
ts timestamp(14),
reflected tinyint(4) DEFAULT '0' NOT NULL,
command mediumtext NOT NULL,
PRIMARY KEY (id)
);
create index index_38 on shadowlog (reflected);
#
# Table structure for table 'versions'
#
CREATE TABLE versions (
value tinytext,
program varchar(64) DEFAULT '' NOT NULL
);
#
# Table structure for table 'votes'
#
CREATE TABLE votes (
who mediumint(9) DEFAULT '0' NOT NULL,
bug_id mediumint(9) DEFAULT '0' NOT NULL,
count smallint(6) DEFAULT '0' NOT NULL
);
create index index_5 on votes (who);
create index index_6 on votes (bug_id);
#
# Table structure for table 'watch'
#
CREATE TABLE watch (
watcher mediumint(9) DEFAULT '0' NOT NULL,
watched mediumint(9) DEFAULT '0' NOT NULL
);
create index index_36 on watch (watched);
create unique index index_37 on watch (watcher, watched);
docs/xml/faq.xml
View file @ d819eae3
This source diff could not be displayed because it is too large. You can view the blob instead.
docs/xml/gfdl.xml
View file @ d819eae3
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="gfdl">
<title>GNU Free Documentation License</title>
......@@ -450,19 +450,25 @@ of this license document, but changing it is not allowed.</para>
</sect1>
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:nil
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-parent-document: ("Bugzilla-Guide.sgml" "appendix")
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-local-catalogs: CATALOG
sgml-validate-command: "nsgmls -s gfdl.sgml"
ispell-skip-sgml: t
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/glossary.xml
View file @ d819eae3
<!-- <!DOCTYPE glossary PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<glossary id="glossary">
<glossdiv id="gloss_a">
<title>A</title>
<glossentry>
<glossterm>There are no entries for A</glossterm>
<glossdef>
<para></para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_b">
<title>B</title>
<glossentry>
<glossterm>Bug</glossterm>
<glossdef>
<para>A "Bug" in Bugzilla refers to an issue entered into the database which has an associated number, assignments, comments, etc. Many also refer to a "Ticket" or "Issue"; in this context, they are synonymous.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bug Number</glossterm>
<glossdef>
<para>Each Bugzilla Bug is assigned a number that uniquely identifies that Bug. The Bug associated with a Bug Number can be pulled up via a query, or easily from the very front page by typing the number in the "Find" box.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bug Life Cycle</glossterm>
<glossdef>
<para>A Bug has stages through which it must pass before becoming a "closed bug", including acceptance, resolution, and verification. The "Bug Life Cycle" is moderately flexible according to the needs of the organization using it, though.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_i">
<title>I</title>
<glossentry id="gloss_infiniteloop">
<glossterm>Infinite Loop</glossterm>
<glosssee otherterm="gloss_recursion">
</glossentry>
</glossdiv>
<glossdiv id="gloss_p">
<title>P</title>
<glossentry>
<glossterm id="gloss_product">Product</glossterm>
<glossdef>
<para>A Product is a broad category of types of bugs. In general, there are several Components to a Product. A Product also defines a default Group (used for Bug Security) for all bugs entered into components beneath it.</para>
<example>
<title>A Sample Product</title>
<para>A company sells a software product called "X". They also maintain some older software called "Y", and have a secret project "Z". An effective use of Products might be to create Products "X", "Y", and "Z", each with Components "User Interface", "Database", and "Business Logic". They might also change group permissions so that only those people who are members of Group "Z" can see components and bugs under Product "Z".</para>
</example>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_q">
<title>Q</title>
<glossentry>
<glossterm>Q/A</glossterm>
<glossdef>
<para>"Q/A" is short for "Quality Assurance". In most large software development organizations, there is a team devoted to ensuring the product meets minimum standards before shipping. This team will also generally want to track the progress of bugs over their life cycle, thus the need for the "Q/A Contact" field in a Bug.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_r">
<title>R</title>
<glossentry>
<glossterm id="gloss_recursion">Recursion</glossterm>
<glosssee otherterm="gloss_infiniteloop">
</glossentry>
</glossdiv>
<glossdiv id="gloss_z">
<title>Z</title>
<glossentry>
<glossterm>Zarro Boogs Found</glossterm>
<glossdef>
<para>This is the cryptic response sent by Bugzilla when a query returned no results. It is just a goofy way of saying "Zero Bugs Found".</para>
</glossdef>
</glossentry>
</glossdiv>
</glossary>
<glossary id="glossary">
<glossdiv>
<title>0-9, high ascii</title>
<glossentry>
<glossterm>.htaccess</glossterm>
<glossdef>
<para>
Apache web server, and other NCSA-compliant web servers,
observe the convention of using files in directories
called <filename>.htaccess</filename> files. These
restrict parameters of the web server. In Bugzilla, they
are used to restrict access to certain files which would
otherwise compromise your installation. For instance, the
<filename>localconfig</filename> file contains the
password to your database. If this information were
generally available, and remote access to your database
turned on, you risk corruption of your database by
computer criminals or the curious.
</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_a">
<title>A</title>
<glossentry>
<glossterm>There are no entries for A</glossterm>
<glossdef>
<para></para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_b">
<title>B</title>
<glossentry>
<glossterm>Bug</glossterm>
<glossdef>
<para>
A <quote>Bug</quote> in Bugzilla refers to an issue
entered into the database which has an associated number,
assignments, comments, etc. Some also refer to a
<quote>tickets</quote> or <quote>issues</quote>; in the
context of Bugzilla, they are synonymous.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bug Number</glossterm>
<glossdef>
<para>
Each Bugzilla Bug is assigned a number that uniquely
identifies that Bug. The Bug associated with a Bug Number
can be pulled up via a query, or easily from the very
front page by typing the number in the "Find" box.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Bug Life Cycle</glossterm>
<glossdef>
<para>A Bug has stages through which it must pass before
becoming a <quote>closed bug</quote>, including
acceptance, resolution, and verification. The <quote>Bug
Life Cycle</quote> is moderately flexible according to
the needs of the organization using it, though.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_i">
<title>I</title>
<glossentry id="gloss_infiniteloop">
<glossterm>Infinite Loop</glossterm>
<glossdef>
<para>A loop of information that never ends; see recursion.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_p">
<title>P</title>
<glossentry>
<glossterm id="gloss_product">Product</glossterm>
<glossdef>
<para>A Product is a broad category of types of bugs. In
general, there are several Components to a Product. A
Product also defines a default Group (used for Bug
Security) for all bugs entered into components beneath
it.</para>
<example>
<title>A Sample Product</title>
<para>A company sells a software product called
<quote>X</quote>. They also maintain some older
software called <quote>Y</quote>, and have a secret
project <quote>Z</quote>. An effective use of Products
might be to create Products <quote>X</quote>,
<quote>Y</quote>, <quote>Z</quote>, each with Components
of User Interface, Database, and Business Logic. They
might also change group permissions so that only those
people who are members of Group <quote>Z</quote> can see
components and bugs under Product
<quote>Z</quote>.</para>
</example>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_q">
<title>Q</title>
<glossentry>
<glossterm>QA</glossterm>
<glossdef>
<para><quote>QA</quote>, <quote>Q/A</quote>, and
<quote>Q.A.</quote> are short for <quote>Quality
Assurance</quote>. In most large software development
organizations, there is a team devoted to ensuring the
product meets minimum standards before shipping. This
team will also generally want to track the progress of
bugs over their life cycle, thus the need for the
<quote>QA Contact</quote> field in a Bug.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_r">
<title>R</title>
<glossentry>
<glossterm id="gloss_recursion">Recursion</glossterm>
<glossdef>
<para>The property of a function looking back at itself for
something. <quote>GNU</quote>, for instance, stands for
<quote>GNU's Not UNIX</quote>, thus recursing upon itself
for definition. For further clarity, see Infinite
Loop.</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv id="gloss_z">
<title>Z</title>
<glossentry>
<glossterm>Zarro Boogs Found</glossterm>
<glossdef>
<para>This is the cryptic response sent by Bugzilla when a
query returned no results. It is just a goofy way of
saying "Zero Bugs Found".</para>
</glossdef>
</glossentry>
</glossdiv>
</glossary>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/index.xml
View file @ d819eae3
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-always-quote-attributes:t
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/integration.xml
View file @ d819eae3
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" >
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<!-- Keep these tools listings in alphabetical order please. -MPB -->
......@@ -12,14 +12,13 @@
<section id="cvs">
<title>CVS</title>
<para>We need CVS integration information</para>
<para>CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</para>
</section>
<section id="scm">
<title>Perforce SCM</title>
<para>
Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
You can find the main project page at
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"
......@@ -54,22 +53,25 @@
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/patches.xml
View file @ d819eae3
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="patches">
<appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla">
<title>Useful Patches and Utilities for Bugzilla</title>
<section id="setperl">
<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 easily
change the path to perl on all your Bugzilla files.
This is a C-shell script; if you do not have "csh" or "tcsh" in the search
path on your system, it will not work!
<para> You can use the "setperl.csh" utility to quickly and
easily change the path to perl on all your Bugzilla files. This
is a C-shell script; if you do not have "csh" or "tcsh" in the
search path on your system, it will not work!
</para>
<procedure>
<step>
......@@ -28,18 +27,15 @@
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
</computeroutput>
<computeroutput> <prompt>bash#</prompt> <command>wget -O
setperl.csh
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command> </computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+x setperl.csh</command>
</computeroutput>
<computeroutput> <prompt>bash#</prompt> <command>chmod
u+x setperl.csh</command> </computeroutput>
</para>
</step>
</substeps>
......@@ -59,10 +55,8 @@
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+x duplicates.cgi</command>
</computeroutput>
<computeroutput> <prompt>bash#</prompt> <command>chmod
u+x duplicates.cgi</command> </computeroutput>
</para>
</step>
<step>
......@@ -80,16 +74,14 @@
Run the script:
</para>
<para>
<computeroutput>
<prompt>bash#</prompt>
<computeroutput> <prompt>bash#</prompt>
<command>./setperl.csh /your/path/to/perl</command>
</computeroutput>
<example>
<title>Using Setperl to set your perl path</title>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.csh /usr/bin/perl</command>
<computeroutput> <prompt>bash#</prompt>
<command>./setperl.csh /usr/bin/perl</command>
</computeroutput>
</para>
</example>
......@@ -101,22 +93,23 @@
<section id="cmdline">
<title>Command-line Bugzilla Queries</title>
<para>
Users can query Bugzilla from the command line using
this suite of utilities.
Users can query Bugzilla from the command line using this suite
of utilities.
</para>
<para>
The query.conf file contains the mapping from options to field
names and comparison types. Quoted option names are "grepped" for, so
it should be easy to edit this file. Comments (#) have no effect; you
must make sure these lines do not contain any quoted "option"
names and comparison types. Quoted option names are "grepped"
for, so it should be easy to edit this file. Comments (#) have
no effect; you must make sure these lines do not contain any
quoted "option"
</para>
<para>
buglist is a shell script which submits a Bugzilla query and writes the
resulting HTML page to stdout. It supports both short options,
(such as "-Afoo" or "-Rbar") and long options (such as
"--assignedto=foo" or "--reporter=bar"). If the first character
of an option is not "-", it is treated as if it were prefixed
with "--default=".
buglist is a shell script which submits a Bugzilla query and
writes the resulting HTML page to stdout. It supports both
short options, (such as "-Afoo" or "-Rbar") and long options
(such as "--assignedto=foo" or "--reporter=bar"). If the first
character of an option is not "-", it is treated as if it were
prefixed with "--default=".
</para>
<para>
The columlist is taken from the COLUMNLIST environment variable.
......@@ -128,10 +121,10 @@
<para>
bugs is a simple shell script which calls buglist and extracts
the bug numbers from the output. Adding the prefix
"http://bugzilla.mozilla.org/buglist.cgi?bug_id="
turns the bug list into a working link if any bugs are found.
Counting bugs is easy. Pipe the results through
<command>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</command>
"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug
list into a working link if any bugs are found. Counting bugs is
easy. Pipe the results through <command>sed -e 's/,/ /g' | wc |
awk '{printf $2 "\n"}'</command>
</para>
<para>
Akkana says she has good results piping buglist output through
......@@ -145,26 +138,23 @@
<substeps>
<step>
<para>
<computeroutput>
<prompt>bash$</prompt>
<command>wget -O query.conf 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</command>
</computeroutput>
<computeroutput> <prompt>bash$</prompt> <command>wget -O
query.conf
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</command> </computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash$</prompt>
<command>wget -O buglist 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</command>
</computeroutput>
<computeroutput> <prompt>bash$</prompt> <command>wget -O
buglist
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</command> </computeroutput>
</para>
</step>
<step>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>wget -O bugs 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command>
</computeroutput>
<computeroutput> <prompt>bash#</prompt> <command>wget -O
bugs
'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command> </computeroutput>
</para>
</step>
</substeps>
......@@ -185,53 +175,64 @@
<title>The Quicksearch Utility</title>
<para>
Quicksearch is a new, experimental feature of the 2.12 release.
It consist of two Javascript files, "quicksearch.js" and "localconfig.js",
and two documentation files, "quicksearch.html" and "quicksearchhack.html"
It consist of two Javascript files, "quicksearch.js" and
"localconfig.js", and two documentation files,
"quicksearch.html" and "quicksearchhack.html"
</para>
<para>
The index.html page has been updated to include the QuickSearch text box.
The index.html page has been updated to include the QuickSearch
text box.
</para>
<para>
To take full advantage of the query power, the Bugzilla maintainer must
edit "localconfig.js" according to the value sets used in the local installation.
To take full advantage of the query power, the Bugzilla
maintainer must edit "localconfig.js" according to the value
sets used in the local installation.
</para>
<para>
Currently, keywords must be hard-coded in localconfig.js. If they are not,
keywords are not automatically recognized. This means, if localconfig.js
is left unconfigured, that searching for a bug with the "foo" keyword
will only find bugs with "foo" in the summary, status whiteboard, product or
component name, but not those with the keyword "foo".
Currently, keywords must be hard-coded in localconfig.js. If
they are not, keywords are not automatically recognized. This
means, if localconfig.js is left unconfigured, that searching
for a bug with the "foo" keyword will only find bugs with "foo"
in the summary, status whiteboard, product or component name,
but not those with the keyword "foo".
</para>
<para>
Workarounds for Bugzilla users:
<simplelist>
<member>search for '!foo' (this will find only bugs with the keyword "foo"</member>
<member>search 'foo,!foo' (equivalent to 'foo OR keyword:foo')</member>
<member>search for '!foo' (this will find only bugs with the
keyword "foo"</member>
<member>search 'foo,!foo' (equivalent to 'foo OR
keyword:foo')</member>
</simplelist>
</para>
<para>
When this tool is ported from client-side JavaScript to server-side Perl,
the requirement for hard-coding keywords can be fixed.
<ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=70907">This bug</ulink>
has details.
When this tool is ported from client-side JavaScript to
server-side Perl, the requirement for hard-coding keywords can
be fixed. <ulink
url="http://bugzilla.mozilla.org/show_bug.cgi?id=70907">This bug</ulink> has details.
</para>
</section>
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/requiredsoftware.xml
View file @ d819eae3
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="downloadlinks">
<title>Software Download Links</title>
......@@ -15,7 +15,7 @@
http://www.mozilla.org/projects/bugzilla/</ulink>
</para>
<para>
MySQL: <ulink url="http://www.mysql.org/">http://www.mysql.org/</ulink>
MySQL: <ulink url="http://www.mysql.com/">http://www.mysql.com/</ulink>
</para>
<para>
Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink>
......@@ -63,20 +63,24 @@
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/using.xml
View file @ d819eae3
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<!-- TOC
Chapter: Using Bugzilla
......@@ -38,19 +38,19 @@ Chapter: Using Bugzilla
<section id="whatis">
<title>What is Bugzilla?</title>
<para>
Bugzilla is one example of a class of programs called "Defect Tracking Systems",
or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
groups of developers to keep track of outstanding bugs in their product effectively.
Bugzilla was originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy
bug-tracking database used internally for Netscape Communications. Terry later ported
Bugzilla to
Perl from TCL, and in Perl it remains to this day.
Most commercial defect-tracking software vendors at the
time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla). It
is now the de-facto standard defect-tracking system against which all others are
measured.
Bugzilla is one example of a class of programs called "Defect
Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
Tracking Systems allow individual or groups of developers to keep
track of outstanding bugs in their product effectively. Bugzilla was
originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy bug-tracking database used internally for
Netscape Communications. Terry later ported Bugzilla to Perl from
TCL, and in Perl it remains to this day. Most commercial
defect-tracking software vendors at the time charged enormous
licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser
project, Mozilla). It is now the de-facto standard defect-tracking
system against which all others are measured.
</para>
<para>
Bugzilla has matured immensely, and now boasts many advanced features. These include:
......@@ -87,13 +87,13 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
email, XML, and HTTP APIs
email, XML, console, and HTTP APIs
</para>
</listitem>
<listitem>
<para>
available integration with automated software configuration management systems, including
Perforce and CVS.
Perforce and CVS
</para>
</listitem>
<listitem>
......@@ -137,7 +137,7 @@ Chapter: Using Bugzilla
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
dropped or ignored.
</para>
<para>
These days, many companies are finding that integrated defect-tracking
......@@ -223,12 +223,12 @@ Chapter: Using Bugzilla
<section id="myaccount">
<title>Create a Bugzilla Account</title>
<para>
First thing's first! If you want to use Bugzilla, first you need to create
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:
<ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/">
http://landfill.tequilarista.org/mozilla/bugzilla/</ulink>
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/">
http://landfill.tequilarista.org/bugzilla-tip/</ulink>
</para>
<orderedlist>
<listitem>
......@@ -560,15 +560,15 @@ Chapter: Using Bugzilla
<orderedlist>
<listitem>
<para>
Go back to <ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/">
http://landfill.tequilarista.org/mozilla/bugzilla/</ulink>
Go back to <ulink url="http://landfill.tequilarista.org/bugzilla-tip/">
http://landfill.tequilarista.org/bugzilla-tip/</ulink>
in your browser.
</para>
</listitem>
<listitem>
<para>
Select the
<ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/enter_bug.cgi">
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi">
Enter a new bug report</ulink> link.
</para>
</listitem>
......@@ -716,7 +716,7 @@ Chapter: Using Bugzilla
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
<ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/query.cgi?GoAheadAndLogIn=1">
<ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1">
Landfill</ulink>.
</para>
<section id="accountsettings">
......@@ -861,17 +861,20 @@ Chapter: Using Bugzilla
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:Bugzilla-Guide\.sgml
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/variants.xml
View file @ d819eae3
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">-->
<chapter id="variants">
<title>Bugzilla Variants</title>
......@@ -68,20 +68,24 @@ Regards
</para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-auto-insert-required-elements:t
sgml-balanced-tag-edit:t
sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment