Skip to content

bugzilla
bugzilla
Commit 74bcd6f1 authored by gerv%gerv.net's avatar gerv%gerv.net
Browse files
Options

More documentation updates.

parent 62f5b900
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 572 additions and 982 deletions
docs/sgml/administration.sgml
View file @ 74bcd6f1
This source diff could not be displayed because it is too large. You can view the blob instead.
docs/sgml/conventions.sgml
View file @ 74bcd6f1
<!-- <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<section id="conventions">
<title>Document Conventions</title>
<indexterm zone="conventions">
<primary>conventions</primary>
</indexterm>
<para>
This document uses the following conventions
</para>
<para>This document uses the following conventions</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Descriptions</entry>
<entry>Appearance</entry>
</row>
</thead>
<tbody>
<row>
<entry>Warnings</entry>
<entry><caution>
<entry>
<caution>
<para>Don't run with scissors!</para>
</caution></entry>
</caution>
</entry>
</row>
<row>
<entry>Hint</entry>
<entry><tip>
<entry>
<tip>
<para>Warm jar lids under the hot tap to loosen them.</para>
</tip></entry>
</tip>
</entry>
</row>
<row>
<entry>Notes</entry>
<entry><note>
<entry>
<note>
<para>Dear John...</para>
</note></entry>
</note>
</entry>
</row>
<row>
<entry>Information requiring special attention</entry>
<entry><warning>
<entry>
<warning>
<para>Read this or the cat gets it.</para>
</warning></entry>
</warning>
</entry>
</row>
<row>
<entry>File Names</entry>
<entry><filename>file.extension</filename></entry>
<entry>
<filename>file.extension</filename>
</entry>
</row>
<row>
<entry>Directory Names</entry>
<entry><filename class="directory">directory</filename></entry>
<entry>
<filename class="directory">directory</filename>
</entry>
</row>
<row>
<entry>Commands to be typed</entry>
<entry><command>command</command></entry>
<entry>
<command>command</command>
</entry>
</row>
<row>
<entry>Applications Names</entry>
<entry><application>application</application></entry>
<entry>
<application>application</application>
</entry>
</row>
<row>
<entry><foreignphrase>Prompt</foreignphrase> of users command under bash shell</entry>
<entry>
<foreignphrase>Prompt</foreignphrase>
of users command under bash shell</entry>
<entry>bash$</entry>
</row>
<row>
<entry><foreignphrase>Prompt</foreignphrase> of root users command under bash shell</entry>
<entry>
<foreignphrase>Prompt</foreignphrase>
of root users command under bash shell</entry>
<entry>bash#</entry>
</row>
<row>
<entry><foreignphrase>Prompt</foreignphrase> of user command under tcsh shell</entry>
<entry>tcsh$</entry>
</row>
<row>
<entry>
<foreignphrase>Prompt</foreignphrase>
of user command under tcsh shell</entry>
<entry>tcsh$</entry>
</row>
<row>
<entry>Environment Variables</entry>
<entry><envar>VARIABLE</envar></entry>
<entry>
<envar>VARIABLE</envar>
</entry>
</row>
<row>
<entry>Emphasized word</entry>
<entry><emphasis>word</emphasis></entry>
<entry>
<emphasis>word</emphasis>
</entry>
</row>
<row>
<entry>Code Example</entry>
<entry><programlisting><sgmltag class="starttag">para</sgmltag>Beginning and end of paragraph<sgmltag class="endtag">para</sgmltag></programlisting></entry>
<entry>
<programlisting>
<sgmltag class="starttag">para</sgmltag>
Beginning and end of paragraph
<sgmltag class="endtag">para</sgmltag>
</programlisting>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</section>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
......@@ -114,3 +171,4 @@ sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/dbschema.mysql
View file @ 74bcd6f1
# 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/index.sgml
View file @ 74bcd6f1
......@@ -18,3 +18,4 @@ sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/integration.sgml
View file @ 74bcd6f1
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<!-- Keep these tools listings in alphabetical order please. -MPB -->
<chapter id="integration">
<title>Integrating Bugzilla with Third-Party Tools</title>
<section id="bonsai" xreflabel="Bonsai, the Mozilla automated CVS management system">
<section id="bonsai"
xreflabel="Bonsai, the Mozilla automated CVS management system">
<title>Bonsai</title>
<para>Bonsai is a web-based tool for managing <xref
linkend="cvs" />
. Using Bonsai, administrators can control open/closed status
of trees, query a fast relational database back-end for change,
branch, and comment information, and view changes made since the
last time the tree was closed. These kinds of changes cause the
engineer responsible to be <quote>on the hook</quote> (include
cool URL link here for Hook policies at mozilla.org). Bonsai
also includes gateways to <xref
linkend="tinderbox" /> and Bugzilla </para>
<para>Bonsai is a web-based tool for managing
<xref linkend="cvs" />
. Using Bonsai, administrators can control open/closed status of trees,
query a fast relational database back-end for change, branch, and comment
information, and view changes made since the last time the tree was
closed. These kinds of changes cause the engineer responsible to be
<quote>on the hook</quote>
(include cool URL link here for Hook policies at mozilla.org). Bonsai
also includes gateways to
<xref linkend="tinderbox" />
and Bugzilla</para>
</section>
<section id="cvs" xreflabel="CVS, the Concurrent Versioning System">
<title>CVS</title>
<para>CVS integration is best accomplished, at this point, using
the Bugzilla Email Gateway. There have been some files
submitted to allow greater CVS integration, but we need to make
certain that Bugzilla is not tied into one particular software
management package.</para>
<para>
Follow the instructions in the FAQ for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to
your Bugzilla e-mail gateway with the subject of <quote>[Bug
XXXX]</quote>, and you can have CVS check-in comments append
to your Bugzilla bug. If you have your check-in script include
an @resolution field, you can even change the Bugzilla bug
state.
</para>
<para>
There is also a project, based upon somewhat dated Bugzilla
code, to integrate CVS and Bugzilla through CVS' ability to
email. Check it out at:
<ulink url="http://homepages.kcbbs.gen.nz/~tonyg/">
http://homepages.kcbbs.gen.nz/~tonyg/</ulink>, under the
<quote>cvszilla</quote> link.
</para>
<para>CVS integration is best accomplished, at this point, using the
Bugzilla Email Gateway. There have been some files submitted to allow
greater CVS integration, but we need to make certain that Bugzilla is not
tied into one particular software management package.</para>
<para>Follow the instructions in the FAQ for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to your
Bugzilla e-mail gateway with the subject of
<quote>[Bug XXXX]</quote>
, and you can have CVS check-in comments append to your Bugzilla bug. If
you have your check-in script include an @resolution field, you can even
change the Bugzilla bug state.</para>
<para>There is also a project, based upon somewhat dated Bugzilla code,
to integrate CVS and Bugzilla through CVS' ability to email. Check it out
at:
<ulink url="http://homepages.kcbbs.gen.nz/~tonyg/">
http://homepages.kcbbs.gen.nz/~tonyg/</ulink>
, under the
<quote>cvszilla</quote>
link.</para>
</section>
<section id="scm" xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS">
<section id="scm"
xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS">
<title>Perforce SCM</title>
<para>
You can find the project page for Bugzilla and Teamtrack
Perforce integration (p4dti) at: <ulink
url="http://www.ravenbrook.com/project/p4dti/"> http://www.ravenbrook.com/project/p4dti</ulink> . <quote>p4dti</quote> is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html"> http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
</para>
<para>
Integration of Perforce with Bugzilla, once patches are applied,
is seamless. Perforce replication information will appear below
the comments of each bug. Be certain you have a matching set of
patches for the Bugzilla version you are installing. p4dti is
designed to support multiple defect trackers, and maintains its
own documentation for it. Please consult the pages linked above
for further information.
</para>
<para>You can find the project page for Bugzilla and Teamtrack Perforce
integration (p4dti) at:
<ulink url="http://www.ravenbrook.com/project/p4dti/">
http://www.ravenbrook.com/project/p4dti</ulink>
.
<quote>p4dti</quote>
is now an officially supported product from Perforce, and you can find
the "Perforce Public Depot" p4dti page at
<ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
http://public.perforce.com/public/perforce/p4dti/index.html</ulink>
.</para>
<para>Integration of Perforce with Bugzilla, once patches are applied, is
seamless. Perforce replication information will appear below the comments
of each bug. Be certain you have a matching set of patches for the
Bugzilla version you are installing. p4dti is designed to support
multiple defect trackers, and maintains its own documentation for it.
Please consult the pages linked above for further information.</para>
</section>
<section id="tinderbox" xreflabel="Tinderbox, the Mozilla automated build management system">
<section id="tinderbox"
xreflabel="Tinderbox, the Mozilla automated build management system">
<title>Tinderbox/Tinderbox2</title>
<para>We need Tinderbox integration information.</para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
......@@ -93,3 +108,4 @@ sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/requiredsoftware.sgml
View file @ 74bcd6f1
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="downloadlinks">
<title>Software Download Links</title>
<para>
All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while.
</para>
<para>
Apache Web Server: <ulink url="http://www.apache.org/">http://www.apache.org</ulink>
Optional web server for Bugzilla, but recommended because of broad user base and support.
</para>
<para>
Bugzilla: <ulink url="http://www.mozilla.org/projects/bugzilla/">
http://www.mozilla.org/projects/bugzilla/</ulink>
</para>
<para>
MySQL: <ulink url="http://www.mysql.com/">http://www.mysql.com/</ulink>
<para>All of these sites are current as of April, 2001. Hopefully they'll
stay current for a while.</para>
<para>Apache Web Server:
<ulink url="http://www.apache.org/">http://www.apache.org</ulink>
Optional web server for Bugzilla, but recommended because of broad user
base and support.</para>
<para>Bugzilla:
<ulink url="http://www.bugzilla.org/">
http://www.bugzilla.org/</ulink>
</para>
<para>
Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink>
<para>MySQL:
<ulink url="http://www.mysql.com/">http://www.mysql.com/</ulink>
</para>
<para>
CPAN: <ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink>
<para>Perl:
<ulink url="http://www.perl.org">http://www.perl.org/</ulink>
</para>
<para>
DBI Perl module:
<ulink url="http://www.cpan.org/modules/by-module/DBI/">
http://www.cpan.org/modules/by-module/DBI/</ulink>
<para>CPAN:
<ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink>
</para>
<para>
Data::Dumper module:
<ulink url="http://www.cpan.org/modules/by-module/Data/">
http://www.cpan.org/modules/by-module/Data/</ulink>
<para>DBI Perl module:
<ulink url="http://www.cpan.org/modules/by-module/DBI/">
http://www.cpan.org/modules/by-module/DBI/</ulink>
</para>
<para>
MySQL related Perl modules:
<ulink url="http://www.cpan.org/modules/by-module/Mysql/">
http://www.cpan.org/modules/by-module/Mysql/</ulink>
<para>Data::Dumper module:
<ulink url="http://www.cpan.org/modules/by-module/Data/">
http://www.cpan.org/modules/by-module/Data/</ulink>
</para>
<para>
TimeDate Perl module collection:
<ulink url="http://www.cpan.org/modules/by-module/Date/">
http://www.cpan.org/modules/by-module/Date/</ulink>
<para>MySQL related Perl modules:
<ulink url="http://www.cpan.org/modules/by-module/Mysql/">
http://www.cpan.org/modules/by-module/Mysql/</ulink>
</para>
<para>
GD Perl module:
<ulink url="http://www.cpan.org/modules/by-module/GD/">
http://www.cpan.org/modules/by-module/GD/</ulink>
Alternately, you should be able to find the latest version of
GD at <ulink url="http://www.boutell.com/gd/">http://www.boutell.com/gd/</ulink>
<para>TimeDate Perl module collection:
<ulink url="http://www.cpan.org/modules/by-module/Date/">
http://www.cpan.org/modules/by-module/Date/</ulink>
</para>
<para>
Chart::Base module:
<ulink url="http://www.cpan.org/modules/by-module/Chart/">
http://www.cpan.org/modules/by-module/Chart/</ulink>
<para>GD Perl module:
<ulink url="http://www.cpan.org/modules/by-module/GD/">
http://www.cpan.org/modules/by-module/GD/</ulink>
Alternately, you should be able to find the latest version of GD at
<ulink url="http://www.boutell.com/gd/">http://www.boutell.com/gd/</ulink>
</para>
<para>
LinuxDoc Software:
<ulink url="http://www.linuxdoc.org/">http://www.linuxdoc.org/</ulink>
(for documentation maintenance)
<para>Chart::Base module:
<ulink url="http://www.cpan.org/modules/by-module/Chart/">
http://www.cpan.org/modules/by-module/Chart/</ulink>
</para>
<para>(But remember, Bundle::Bugzilla will install all the modules for you.)
</para>
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
......@@ -84,3 +85,4 @@ sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/sgml/variants.sgml
View file @ 74bcd6f1
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">-->
<chapter id="variants" xreflabel="Bugzilla Variants and Competitors">
<title>Bugzilla Variants and Competitors</title>
<para>I created this section to answer questions about Bugzilla
competitors and variants, then found a wonderful site which covers
an awful lot of what I wanted to discuss. Rather than quote it in
its entirety, I'll simply refer you here: <ulink
url="http://linas.org/linux/pm.html">http://linas.org/linux/pm.html</ulink></para>
<para>I created this section to answer questions about Bugzilla competitors
and variants, then found a wonderful site which covers an awful lot of what
I wanted to discuss. Rather than quote it in its entirety, I'll simply
refer you here:
<ulink url="http://linas.org/linux/pm.html">
http://linas.org/linux/pm.html</ulink>
</para>
<section id="rhbugzilla" xreflabel="Red Hat Bugzilla">
<title>Red Hat Bugzilla</title>
<para>
Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
the ability to work with Oracle, MySQL, and PostGreSQL databases
serving as the back-end, instead of just MySQL. Dave Lawrence
has worked very hard to keep Red Hat Bugzilla up-to-date, and
many people prefer the snappier-looking page layout of Red Hat
Bugzilla to the default Mozilla-standard formatting.
<para>Red Hat Bugzilla is probably the most popular Bugzilla variant on
the planet. One of the major benefits of Red Hat Bugzilla is the ability
to work with Oracle, MySQL, and PostGreSQL databases serving as the
back-end, instead of just MySQL. Dave Lawrence has worked very hard to
keep Red Hat Bugzilla up-to-date, and many people prefer the
snappier-looking page layout of Red Hat Bugzilla to the default
Mozilla-standard formatting.</para>
<para>URL:
<ulink url="http://bugzilla.redhat.com/bugzilla/">
http://bugzilla.redhat.com/bugzilla/</ulink>
</para>
<para>URL: <ulink
url="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</ulink></para>
</section>
<section id="variant-fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris">
<title>Loki Bugzilla (Fenris)</title>
<para>Fenris can be found at <ulink
url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para>
<para>Fenris can be found at
<ulink url="http://fenris.lokigames.com/">
http://fenris.lokigames.com</ulink>
. It is a fork from Bugzilla.</para>
</section>
<section id="variant-issuezilla" xreflabel="Issuezilla">
<title>Issuezilla</title>
<para>Issuezilla is another fork from Bugzilla, and seems nearly
as popular as the Red Hat Bugzilla fork. Some Issuezilla team
members are regular contributors to the Bugzilla mailing
list/newsgroup. Issuezilla is not the primary focus of
bug-tracking at tigris.org, however. Their Java-based
bug-tracker, <xref linkend="variant-scarab" />, is under heavy development
and looks promising!</para>
<para>URL: <ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">http://issuezilla.tigris.org/servlets/ProjectHome</ulink></para>
<para>Issuezilla is another fork from Bugzilla, and seems nearly as
popular as the Red Hat Bugzilla fork. Some Issuezilla team members are
regular contributors to the Bugzilla mailing list/newsgroup. Issuezilla
is not the primary focus of bug-tracking at tigris.org, however. Their
Java-based bug-tracker,
<xref linkend="variant-scarab" />
, is under heavy development and looks promising!</para>
<para>URL:
<ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">
http://issuezilla.tigris.org/servlets/ProjectHome</ulink>
</para>
</section>
<section id="variant-scarab" xreflabel="Scarab, a newfangled Java-based issue tracker">
<section id="variant-scarab"
xreflabel="Scarab, a newfangled Java-based issue tracker">
<title>Scarab</title>
<para>Scarab is a promising new bug-tracking system built using
Java Serlet technology. As of this writing, no source code has
been released as a package, but you can obtain the code from
CVS.
<para>Scarab is a promising new bug-tracking system built using Java
Serlet technology. As of this writing, no source code has been released
as a package, but you can obtain the code from CVS.</para>
<para>URL:
<ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink>
</para>
<para>URL: <ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink></para>
</section>
<section id="variant-perforce" xreflabel="Using Perforce to track bugs">
<title>Perforce SCM</title>
<para>Although Perforce isn't really a bug tracker, it can be used
as such through the <quote>jobs</quote> functionality.</para>
<para><ulink
url="http://www.perforce.com/perforce/technotes/note052.html"></ulink>http://www.perforce.com/perforce/technotes/note052.html</para>
<para>Although Perforce isn't really a bug tracker, it can be used as
such through the
<quote>jobs</quote>
functionality.</para>
<para>
<ulink url="http://www.perforce.com/perforce/technotes/note052.html">
</ulink>
http://www.perforce.com/perforce/technotes/note052.html</para>
</section>
<section id="variant-sourceforge" xreflabel="SourceForge">
<title>SourceForge</title>
<para>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the
Internet than strictly a bug tracker, but if you're hunting for
bug-tracking for your open project, it may be just what the
software engineer ordered!</para>
<para>URL: <ulink
url="http://www.sourceforge.net">http://www.sourceforge.net</ulink></para>
</section>
<para>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the Internet than
strictly a bug tracker, but if you're hunting for bug-tracking for your
open project, it may be just what the software engineer ordered!</para>
<para>URL:
<ulink url="http://www.sourceforge.net">
http://www.sourceforge.net</ulink>
</para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
......@@ -94,3 +119,4 @@ sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/administration.xml
View file @ 74bcd6f1
This source diff could not be displayed because it is too large. You can view the blob instead.
docs/xml/conventions.xml
View file @ 74bcd6f1
<!-- <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<section id="conventions">
<title>Document Conventions</title>
<indexterm zone="conventions">
<primary>conventions</primary>
</indexterm>
<para>
This document uses the following conventions
</para>
<para>This document uses the following conventions</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Descriptions</entry>
<entry>Appearance</entry>
</row>
</thead>
<tbody>
<row>
<entry>Warnings</entry>
<entry><caution>
<entry>
<caution>
<para>Don't run with scissors!</para>
</caution></entry>
</caution>
</entry>
</row>
<row>
<entry>Hint</entry>
<entry><tip>
<entry>
<tip>
<para>Warm jar lids under the hot tap to loosen them.</para>
</tip></entry>
</tip>
</entry>
</row>
<row>
<entry>Notes</entry>
<entry><note>
<entry>
<note>
<para>Dear John...</para>
</note></entry>
</note>
</entry>
</row>
<row>
<entry>Information requiring special attention</entry>
<entry><warning>
<entry>
<warning>
<para>Read this or the cat gets it.</para>
</warning></entry>
</warning>
</entry>
</row>
<row>
<entry>File Names</entry>
<entry><filename>file.extension</filename></entry>
<entry>
<filename>file.extension</filename>
</entry>
</row>
<row>
<entry>Directory Names</entry>
<entry><filename class="directory">directory</filename></entry>
<entry>
<filename class="directory">directory</filename>
</entry>
</row>
<row>
<entry>Commands to be typed</entry>
<entry><command>command</command></entry>
<entry>
<command>command</command>
</entry>
</row>
<row>
<entry>Applications Names</entry>
<entry><application>application</application></entry>
<entry>
<application>application</application>
</entry>
</row>
<row>
<entry><foreignphrase>Prompt</foreignphrase> of users command under bash shell</entry>
<entry>
<foreignphrase>Prompt</foreignphrase>
of users command under bash shell</entry>
<entry>bash$</entry>
</row>
<row>
<entry><foreignphrase>Prompt</foreignphrase> of root users command under bash shell</entry>
<entry>
<foreignphrase>Prompt</foreignphrase>
of root users command under bash shell</entry>
<entry>bash#</entry>
</row>
<row>
<entry><foreignphrase>Prompt</foreignphrase> of user command under tcsh shell</entry>
<entry>tcsh$</entry>
</row>
<row>
<entry>
<foreignphrase>Prompt</foreignphrase>
of user command under tcsh shell</entry>
<entry>tcsh$</entry>
</row>
<row>
<entry>Environment Variables</entry>
<entry><envar>VARIABLE</envar></entry>
<entry>
<envar>VARIABLE</envar>
</entry>
</row>
<row>
<entry>Emphasized word</entry>
<entry><emphasis>word</emphasis></entry>
<entry>
<emphasis>word</emphasis>
</entry>
</row>
<row>
<entry>Code Example</entry>
<entry><programlisting><sgmltag class="starttag">para</sgmltag>Beginning and end of paragraph<sgmltag class="endtag">para</sgmltag></programlisting></entry>
<entry>
<programlisting>
<sgmltag class="starttag">para</sgmltag>
Beginning and end of paragraph
<sgmltag class="endtag">para</sgmltag>
</programlisting>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</section>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
......@@ -114,3 +171,4 @@ sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/dbschema.mysql
View file @ 74bcd6f1
# 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/index.xml
View file @ 74bcd6f1
......@@ -18,3 +18,4 @@ sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/integration.xml
View file @ 74bcd6f1
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<!-- Keep these tools listings in alphabetical order please. -MPB -->
<chapter id="integration">
<title>Integrating Bugzilla with Third-Party Tools</title>
<section id="bonsai" xreflabel="Bonsai, the Mozilla automated CVS management system">
<section id="bonsai"
xreflabel="Bonsai, the Mozilla automated CVS management system">
<title>Bonsai</title>
<para>Bonsai is a web-based tool for managing <xref
linkend="cvs" />
. Using Bonsai, administrators can control open/closed status
of trees, query a fast relational database back-end for change,
branch, and comment information, and view changes made since the
last time the tree was closed. These kinds of changes cause the
engineer responsible to be <quote>on the hook</quote> (include
cool URL link here for Hook policies at mozilla.org). Bonsai
also includes gateways to <xref
linkend="tinderbox" /> and Bugzilla </para>
<para>Bonsai is a web-based tool for managing
<xref linkend="cvs" />
. Using Bonsai, administrators can control open/closed status of trees,
query a fast relational database back-end for change, branch, and comment
information, and view changes made since the last time the tree was
closed. These kinds of changes cause the engineer responsible to be
<quote>on the hook</quote>
(include cool URL link here for Hook policies at mozilla.org). Bonsai
also includes gateways to
<xref linkend="tinderbox" />
and Bugzilla</para>
</section>
<section id="cvs" xreflabel="CVS, the Concurrent Versioning System">
<title>CVS</title>
<para>CVS integration is best accomplished, at this point, using
the Bugzilla Email Gateway. There have been some files
submitted to allow greater CVS integration, but we need to make
certain that Bugzilla is not tied into one particular software
management package.</para>
<para>
Follow the instructions in the FAQ for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to
your Bugzilla e-mail gateway with the subject of <quote>[Bug
XXXX]</quote>, and you can have CVS check-in comments append
to your Bugzilla bug. If you have your check-in script include
an @resolution field, you can even change the Bugzilla bug
state.
</para>
<para>
There is also a project, based upon somewhat dated Bugzilla
code, to integrate CVS and Bugzilla through CVS' ability to
email. Check it out at:
<ulink url="http://homepages.kcbbs.gen.nz/~tonyg/">
http://homepages.kcbbs.gen.nz/~tonyg/</ulink>, under the
<quote>cvszilla</quote> link.
</para>
<para>CVS integration is best accomplished, at this point, using the
Bugzilla Email Gateway. There have been some files submitted to allow
greater CVS integration, but we need to make certain that Bugzilla is not
tied into one particular software management package.</para>
<para>Follow the instructions in the FAQ for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to your
Bugzilla e-mail gateway with the subject of
<quote>[Bug XXXX]</quote>
, and you can have CVS check-in comments append to your Bugzilla bug. If
you have your check-in script include an @resolution field, you can even
change the Bugzilla bug state.</para>
<para>There is also a project, based upon somewhat dated Bugzilla code,
to integrate CVS and Bugzilla through CVS' ability to email. Check it out
at:
<ulink url="http://homepages.kcbbs.gen.nz/~tonyg/">
http://homepages.kcbbs.gen.nz/~tonyg/</ulink>
, under the
<quote>cvszilla</quote>
link.</para>
</section>
<section id="scm" xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS">
<section id="scm"
xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS">
<title>Perforce SCM</title>
<para>
You can find the project page for Bugzilla and Teamtrack
Perforce integration (p4dti) at: <ulink
url="http://www.ravenbrook.com/project/p4dti/"> http://www.ravenbrook.com/project/p4dti</ulink> . <quote>p4dti</quote> is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html"> http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
</para>
<para>
Integration of Perforce with Bugzilla, once patches are applied,
is seamless. Perforce replication information will appear below
the comments of each bug. Be certain you have a matching set of
patches for the Bugzilla version you are installing. p4dti is
designed to support multiple defect trackers, and maintains its
own documentation for it. Please consult the pages linked above
for further information.
</para>
<para>You can find the project page for Bugzilla and Teamtrack Perforce
integration (p4dti) at:
<ulink url="http://www.ravenbrook.com/project/p4dti/">
http://www.ravenbrook.com/project/p4dti</ulink>
.
<quote>p4dti</quote>
is now an officially supported product from Perforce, and you can find
the "Perforce Public Depot" p4dti page at
<ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
http://public.perforce.com/public/perforce/p4dti/index.html</ulink>
.</para>
<para>Integration of Perforce with Bugzilla, once patches are applied, is
seamless. Perforce replication information will appear below the comments
of each bug. Be certain you have a matching set of patches for the
Bugzilla version you are installing. p4dti is designed to support
multiple defect trackers, and maintains its own documentation for it.
Please consult the pages linked above for further information.</para>
</section>
<section id="tinderbox" xreflabel="Tinderbox, the Mozilla automated build management system">
<section id="tinderbox"
xreflabel="Tinderbox, the Mozilla automated build management system">
<title>Tinderbox/Tinderbox2</title>
<para>We need Tinderbox integration information.</para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
......@@ -93,3 +108,4 @@ sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/requiredsoftware.xml
View file @ 74bcd6f1
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="downloadlinks">
<title>Software Download Links</title>
<para>
All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while.
</para>
<para>
Apache Web Server: <ulink url="http://www.apache.org/">http://www.apache.org</ulink>
Optional web server for Bugzilla, but recommended because of broad user base and support.
</para>
<para>
Bugzilla: <ulink url="http://www.mozilla.org/projects/bugzilla/">
http://www.mozilla.org/projects/bugzilla/</ulink>
</para>
<para>
MySQL: <ulink url="http://www.mysql.com/">http://www.mysql.com/</ulink>
<para>All of these sites are current as of April, 2001. Hopefully they'll
stay current for a while.</para>
<para>Apache Web Server:
<ulink url="http://www.apache.org/">http://www.apache.org</ulink>
Optional web server for Bugzilla, but recommended because of broad user
base and support.</para>
<para>Bugzilla:
<ulink url="http://www.bugzilla.org/">
http://www.bugzilla.org/</ulink>
</para>
<para>
Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink>
<para>MySQL:
<ulink url="http://www.mysql.com/">http://www.mysql.com/</ulink>
</para>
<para>
CPAN: <ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink>
<para>Perl:
<ulink url="http://www.perl.org">http://www.perl.org/</ulink>
</para>
<para>
DBI Perl module:
<ulink url="http://www.cpan.org/modules/by-module/DBI/">
http://www.cpan.org/modules/by-module/DBI/</ulink>
<para>CPAN:
<ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink>
</para>
<para>
Data::Dumper module:
<ulink url="http://www.cpan.org/modules/by-module/Data/">
http://www.cpan.org/modules/by-module/Data/</ulink>
<para>DBI Perl module:
<ulink url="http://www.cpan.org/modules/by-module/DBI/">
http://www.cpan.org/modules/by-module/DBI/</ulink>
</para>
<para>
MySQL related Perl modules:
<ulink url="http://www.cpan.org/modules/by-module/Mysql/">
http://www.cpan.org/modules/by-module/Mysql/</ulink>
<para>Data::Dumper module:
<ulink url="http://www.cpan.org/modules/by-module/Data/">
http://www.cpan.org/modules/by-module/Data/</ulink>
</para>
<para>
TimeDate Perl module collection:
<ulink url="http://www.cpan.org/modules/by-module/Date/">
http://www.cpan.org/modules/by-module/Date/</ulink>
<para>MySQL related Perl modules:
<ulink url="http://www.cpan.org/modules/by-module/Mysql/">
http://www.cpan.org/modules/by-module/Mysql/</ulink>
</para>
<para>
GD Perl module:
<ulink url="http://www.cpan.org/modules/by-module/GD/">
http://www.cpan.org/modules/by-module/GD/</ulink>
Alternately, you should be able to find the latest version of
GD at <ulink url="http://www.boutell.com/gd/">http://www.boutell.com/gd/</ulink>
<para>TimeDate Perl module collection:
<ulink url="http://www.cpan.org/modules/by-module/Date/">
http://www.cpan.org/modules/by-module/Date/</ulink>
</para>
<para>
Chart::Base module:
<ulink url="http://www.cpan.org/modules/by-module/Chart/">
http://www.cpan.org/modules/by-module/Chart/</ulink>
<para>GD Perl module:
<ulink url="http://www.cpan.org/modules/by-module/GD/">
http://www.cpan.org/modules/by-module/GD/</ulink>
Alternately, you should be able to find the latest version of GD at
<ulink url="http://www.boutell.com/gd/">http://www.boutell.com/gd/</ulink>
</para>
<para>
LinuxDoc Software:
<ulink url="http://www.linuxdoc.org/">http://www.linuxdoc.org/</ulink>
(for documentation maintenance)
<para>Chart::Base module:
<ulink url="http://www.cpan.org/modules/by-module/Chart/">
http://www.cpan.org/modules/by-module/Chart/</ulink>
</para>
<para>(But remember, Bundle::Bugzilla will install all the modules for you.)
</para>
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
......@@ -84,3 +85,4 @@ sgml-shorttag:t
sgml-tag-region-if-active:t
End:
-->
docs/xml/variants.xml
View file @ 74bcd6f1
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">-->
<chapter id="variants" xreflabel="Bugzilla Variants and Competitors">
<title>Bugzilla Variants and Competitors</title>
<para>I created this section to answer questions about Bugzilla
competitors and variants, then found a wonderful site which covers
an awful lot of what I wanted to discuss. Rather than quote it in
its entirety, I'll simply refer you here: <ulink
url="http://linas.org/linux/pm.html">http://linas.org/linux/pm.html</ulink></para>
<para>I created this section to answer questions about Bugzilla competitors
and variants, then found a wonderful site which covers an awful lot of what
I wanted to discuss. Rather than quote it in its entirety, I'll simply
refer you here:
<ulink url="http://linas.org/linux/pm.html">
http://linas.org/linux/pm.html</ulink>
</para>
<section id="rhbugzilla" xreflabel="Red Hat Bugzilla">
<title>Red Hat Bugzilla</title>
<para>
Red Hat Bugzilla is probably the most popular Bugzilla variant
on the planet. One of the major benefits of Red Hat Bugzilla is
the ability to work with Oracle, MySQL, and PostGreSQL databases
serving as the back-end, instead of just MySQL. Dave Lawrence
has worked very hard to keep Red Hat Bugzilla up-to-date, and
many people prefer the snappier-looking page layout of Red Hat
Bugzilla to the default Mozilla-standard formatting.
<para>Red Hat Bugzilla is probably the most popular Bugzilla variant on
the planet. One of the major benefits of Red Hat Bugzilla is the ability
to work with Oracle, MySQL, and PostGreSQL databases serving as the
back-end, instead of just MySQL. Dave Lawrence has worked very hard to
keep Red Hat Bugzilla up-to-date, and many people prefer the
snappier-looking page layout of Red Hat Bugzilla to the default
Mozilla-standard formatting.</para>
<para>URL:
<ulink url="http://bugzilla.redhat.com/bugzilla/">
http://bugzilla.redhat.com/bugzilla/</ulink>
</para>
<para>URL: <ulink
url="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</ulink></para>
</section>
<section id="variant-fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris">
<title>Loki Bugzilla (Fenris)</title>
<para>Fenris can be found at <ulink
url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para>
<para>Fenris can be found at
<ulink url="http://fenris.lokigames.com/">
http://fenris.lokigames.com</ulink>
. It is a fork from Bugzilla.</para>
</section>
<section id="variant-issuezilla" xreflabel="Issuezilla">
<title>Issuezilla</title>
<para>Issuezilla is another fork from Bugzilla, and seems nearly
as popular as the Red Hat Bugzilla fork. Some Issuezilla team
members are regular contributors to the Bugzilla mailing
list/newsgroup. Issuezilla is not the primary focus of
bug-tracking at tigris.org, however. Their Java-based
bug-tracker, <xref linkend="variant-scarab" />, is under heavy development
and looks promising!</para>
<para>URL: <ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">http://issuezilla.tigris.org/servlets/ProjectHome</ulink></para>
<para>Issuezilla is another fork from Bugzilla, and seems nearly as
popular as the Red Hat Bugzilla fork. Some Issuezilla team members are
regular contributors to the Bugzilla mailing list/newsgroup. Issuezilla
is not the primary focus of bug-tracking at tigris.org, however. Their
Java-based bug-tracker,
<xref linkend="variant-scarab" />
, is under heavy development and looks promising!</para>
<para>URL:
<ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">
http://issuezilla.tigris.org/servlets/ProjectHome</ulink>
</para>
</section>
<section id="variant-scarab" xreflabel="Scarab, a newfangled Java-based issue tracker">
<section id="variant-scarab"
xreflabel="Scarab, a newfangled Java-based issue tracker">
<title>Scarab</title>
<para>Scarab is a promising new bug-tracking system built using
Java Serlet technology. As of this writing, no source code has
been released as a package, but you can obtain the code from
CVS.
<para>Scarab is a promising new bug-tracking system built using Java
Serlet technology. As of this writing, no source code has been released
as a package, but you can obtain the code from CVS.</para>
<para>URL:
<ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink>
</para>
<para>URL: <ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink></para>
</section>
<section id="variant-perforce" xreflabel="Using Perforce to track bugs">
<title>Perforce SCM</title>
<para>Although Perforce isn't really a bug tracker, it can be used
as such through the <quote>jobs</quote> functionality.</para>
<para><ulink
url="http://www.perforce.com/perforce/technotes/note052.html"></ulink>http://www.perforce.com/perforce/technotes/note052.html</para>
<para>Although Perforce isn't really a bug tracker, it can be used as
such through the
<quote>jobs</quote>
functionality.</para>
<para>
<ulink url="http://www.perforce.com/perforce/technotes/note052.html">
</ulink>
http://www.perforce.com/perforce/technotes/note052.html</para>
</section>
<section id="variant-sourceforge" xreflabel="SourceForge">
<title>SourceForge</title>
<para>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the
Internet than strictly a bug tracker, but if you're hunting for
bug-tracking for your open project, it may be just what the
software engineer ordered!</para>
<para>URL: <ulink
url="http://www.sourceforge.net">http://www.sourceforge.net</ulink></para>
</section>
<para>SourceForge is more of a way of coordinating geographically
distributed free software and open source projects over the Internet than
strictly a bug tracker, but if you're hunting for bug-tracking for your
open project, it may be just what the software engineer ordered!</para>
<para>URL:
<ulink url="http://www.sourceforge.net">
http://www.sourceforge.net</ulink>
</para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
......@@ -94,3 +119,4 @@ 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