Skip to content

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

Initial conversion to XML format from SGML.

Note this is a work-in-progress. It compiles cleanly, but I am not yet submitting compiled HTML and text. There is one notable problem: nsgmls barfs on the <imagedata> tag in database.sgml during validation. openjade handles it fine. Weird.
parent b2bd185e
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 209 additions and 209 deletions
docs/sgml/Bugzilla-Guide.sgml
View file @ b54d65e4
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" [
<!-- Include macros -->
<!ENTITY about SYSTEM "about.sgml">
......@@ -148,16 +148,16 @@ try to avoid clutter and feel free to waste space in the code to make it more re
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
While it is easy to use and quite flexible, it is
difficult for a novice to install and maintain. Although we
have provided step-by-step directions, Bugzilla is not always
easy to get working. Please be sure the person responsible
for installing and maintaining this software is a qualified
professional on operating system upon which you install
professional for the operating system upon which you install
Bugzilla.
</para>
<para>
THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT.
IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
ADDITIONS TO THE GUIDE WRITTEN IN HTML!
......@@ -165,18 +165,18 @@ try to avoid clutter and feel free to waste space in the code to make it more re
</abstract>
<KEYWORDSET>
<KEYWORD>Bugzilla</KEYWORD>
<KEYWORD>Guide</KEYWORD>
<KEYWORD>installation</KEYWORD>
<KEYWORD>FAQ</KEYWORD>
<KEYWORD>administration</KEYWORD>
<KEYWORD>integration</KEYWORD>
<KEYWORD>MySQL</KEYWORD>
<KEYWORD>Mozilla</KEYWORD>
<KEYWORD>webtools</KEYWORD>
</KEYWORDSET>
</BOOKINFO>
<keywordset>
<keyword>Bugzilla</keyword>
<keyword>Guide</keyword>
<keyword>installation</keyword>
<keyword>FAQ</keyword>
<keyword>administration</keyword>
<keyword>integration</keyword>
<keyword>MySQL</keyword>
<keyword>Mozilla</keyword>
<keyword>webtools</keyword>
</keywordset>
</bookinfo>
<!-- About This Guide -->
&about;
......@@ -203,7 +203,7 @@ try to avoid clutter and feel free to waste space in the code to make it more re
&faq;
<!-- Appendix: Required Bugzilla Software Links -->
&requiredsoftware
&requiredsoftware;
<!-- Appendix: The Database Schema -->
&database;
......
docs/sgml/administration.sgml
View file @ b54d65e4
......@@ -8,7 +8,7 @@
</subtitle>
<para>
So you followed <quote><xref linkend="installation"></quote> to the
So you followed <quote><xref linkend="installation" /></quote> to the
letter, and logged into Bugzilla for the very first time with your
super-duper god account. You sit, contentedly staring at the
Bugzilla Query Screen, the worst of the whole mad business of
......@@ -623,7 +623,7 @@
<subtitle>Formerly, and in some spots still, called
"Programs"</subtitle>
<para>
<glossterm linkend="gloss_product" baseform="product">Products</glossterm> are
<glossterm linkend="gloss-product" baseform="product">Products</glossterm> are
the broadest category in Bugzilla, and you should have the
least of these. If your company makes computer games, you
should have one product per game, and possibly a few special
......
docs/sgml/database.sgml
View file @ b54d65e4
......@@ -13,7 +13,7 @@
<para>
<mediaobject>
<imageobject>
<imagedata fileref="../images/dbschema.jpg" format="jpg">
<imagedata fileref="../images/dbschema.jpg" format="JPG" />
</imageobject>
<textobject>
......@@ -359,7 +359,7 @@ http://www.devshed.com/Server_Side/MySQL/
</section>
<section id="granttables">
<title>MySQL Permissions & Grant Tables</title>
<title>MySQL Permissions &amp; Grant Tables</title>
<note>
<para>The following portion of documentation comes from my
......@@ -480,7 +480,7 @@ mysql> GRANT
SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,DROP,RELOAD,SHUTDOWN,PROCESS,
FILE,
ON keystone.*
TO <$sys_dbuser name>@localhost
TO &lt;$sys_dbuser name>@localhost
IDENTIFIED BY '(password)'
WITH GRANT OPTION;
......@@ -488,7 +488,7 @@ OR
mysql> GRANT ALL PRIVELEGES
ON keystone.*
TO <$sys_dbuser name>@localhost
TO &lt;$sys_dbuser name>@localhost
IDENTIFIED BY '(password)'
WITH GRANT OPTION;
......
docs/sgml/faq.sgml
View file @ b54d65e4
......@@ -6,7 +6,7 @@
<qandaset>
<qandadiv id="faq_general">
<qandadiv id="faq-general">
<title>General Questions</title>
<qandaentry>
......@@ -270,7 +270,7 @@
</qandadiv>
<qandadiv id="faq_redhat">
<qandadiv id="faq-redhat">
<title>Red Hat Bugzilla</title>
<para>
<note>
......@@ -496,7 +496,7 @@
</qandadiv>
<qandadiv id="faq_loki">
<qandadiv id="faq-loki">
<title>Loki Bugzilla (AKA Fenris)</title>
<qandaentry>
......@@ -515,7 +515,7 @@
</qandadiv>
<qandadiv id="faq_phb">
<qandadiv id="faq-phb">
<title>Pointy-Haired-Boss Questions</title>
<para>
<note>
......@@ -1011,7 +1011,7 @@ if ($::FORM{sub} eq 'PutFooter') {
your Bugzilla install can run untended for years. If your
Bugzilla strategy is critical to your business workflow, hire somebody
with reasonable UNIX or Perl skills to handle your process management and
bug-tracking maintenance & customization.
bug-tracking maintenance &amp; customization.
</para>
</answer>
</qandaentry>
......@@ -1032,7 +1032,7 @@ if ($::FORM{sub} eq 'PutFooter') {
</qandaentry>
</qandadiv>
<qandadiv id="faq_install">
<qandadiv id="faq-install">
<title>Bugzilla Installation</title>
<qandaentry>
<question>
......@@ -1078,7 +1078,7 @@ if ($::FORM{sub} eq 'PutFooter') {
</qandadiv>
<qandadiv id="faq_security">
<qandadiv id="faq-security">
<title>Bugzilla Security</title>
<qandaentry>
......@@ -1133,7 +1133,7 @@ if ($::FORM{sub} eq 'PutFooter') {
</qandaentry>
</qandadiv>
<qandadiv id="faq_email">
<qandadiv id="faq-email">
<title>Bugzilla Email</title>
<qandaentry>
......@@ -1263,7 +1263,7 @@ if ($::FORM{sub} eq 'PutFooter') {
</qandaentry>
</qandadiv>
<qandadiv id="faq_db">
<qandadiv id="faq-db">
<title>Bugzilla Database</title>
<qandaentry>
......@@ -1451,7 +1451,7 @@ if ($::FORM{sub} eq 'PutFooter') {
</qandadiv>
<qandadiv id="faq_nt">
<qandadiv id="faq-nt">
<title>Bugzilla and Win32</title>
<qandaentry>
......@@ -1662,7 +1662,7 @@ A: Sure! Here ya go!
</qandadiv>
<qandadiv id="faq_use">
<qandadiv id="faq-use">
<title>Bugzilla Usage</title>
<qandaentry>
......@@ -1754,7 +1754,7 @@ A: Sure! Here ya go!
</qandadiv>
<qandadiv id="faq_hacking">
<qandadiv id="faq-hacking">
<title>Bugzilla Hacking</title>
<qandaentry>
......@@ -1862,7 +1862,7 @@ A: Sure! Here ya go!
</qandaset>
</APPENDIX>
</appendix>
<!-- Keep this comment at the end of the file
......
docs/sgml/future.sgml
View file @ b54d65e4
......@@ -357,7 +357,7 @@ Keywords
group is more important than the previous, and therefore appears
closer to the top.
Keyword Grouping & Ordering
Keyword Grouping &amp; Ordering
We could further enhance both the global and bug specific keyword list
by grouping keywords. We should always have a "flat" view of
......
docs/sgml/gfdl.sgml
View file @ b54d65e4
......@@ -18,7 +18,7 @@ Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.</para>
</blockquote>
<sect1 label="0" id="gfdl_0">
<sect1 label="0" id="gfdl-0">
<title>PREAMBLE</title>
<para>The purpose of this License is to make a manual, textbook,
......@@ -45,7 +45,7 @@ of this license document, but changing it is not allowed.</para>
whose purpose is instruction or reference.</para>
</sect1>
<sect1 label="1" id="gfdl_1">
<sect1 label="1" id="gfdl-1">
<title>APPLICABILITY AND DEFINITIONS</title>
<para>This License applies to any manual or other work that
......@@ -113,7 +113,7 @@ of this license document, but changing it is not allowed.</para>
text.</para>
</sect1>
<sect1 label="2" id="gfdl_2">
<sect1 label="2" id="gfdl-2">
<title>VERBATIM COPYING</title>
<para>You may copy and distribute the Document in any medium,
......@@ -131,7 +131,7 @@ of this license document, but changing it is not allowed.</para>
above, and you may publicly display copies.</para>
</sect1>
<sect1 label="3" id="gfdl_3">
<sect1 label="3" id="gfdl-3">
<title>COPYING IN QUANTITY</title>
<para>If you publish printed copies of the Document numbering more
......@@ -173,7 +173,7 @@ of this license document, but changing it is not allowed.</para>
updated version of the Document.</para>
</sect1>
<sect1 label="4" id="gfdl_4">
<sect1 label="4" id="gfdl-4">
<title>MODIFICATIONS</title>
<para>You may copy and distribute a Modified Version of the
......@@ -304,7 +304,7 @@ of this license document, but changing it is not allowed.</para>
or to assert or imply endorsement of any Modified Version.</para>
</sect1>
<sect1 label="5" id="gfdl_5">
<sect1 label="5" id="gfdl-5">
<title>COMBINING DOCUMENTS</title>
<para>You may combine the Document with other documents released
......@@ -331,7 +331,7 @@ of this license document, but changing it is not allowed.</para>
must delete all sections entitled "Endorsements."</para>
</sect1>
<sect1 label="6" id="gfdl_6">
<sect1 label="6" id="gfdl-6">
<title>COLLECTIONS OF DOCUMENTS</title>
<para>You may make a collection consisting of the Document and
......@@ -348,7 +348,7 @@ of this license document, but changing it is not allowed.</para>
copying of that document.</para>
</sect1>
<sect1 label="7" id="gfdl_7">
<sect1 label="7" id="gfdl-7">
<title>AGGREGATION WITH INDEPENDENT WORKS</title>
<para>A compilation of the Document or its derivatives with other
......@@ -369,7 +369,7 @@ of this license document, but changing it is not allowed.</para>
aggregate.</para>
</sect1>
<sect1 label="8" id="gfdl_8">
<sect1 label="8" id="gfdl-8">
<title>TRANSLATION</title>
<para>Translation is considered a kind of modification, so you may
......@@ -385,7 +385,7 @@ of this license document, but changing it is not allowed.</para>
prevail.</para>
</sect1>
<sect1 label="9" id="gfdl_9">
<sect1 label="9" id="gfdl-9">
<title>TERMINATION</title>
<para>You may not copy, modify, sublicense, or distribute the
......@@ -398,7 +398,7 @@ of this license document, but changing it is not allowed.</para>
compliance.</para>
</sect1>
<sect1 label="10" id="gfdl_10">
<sect1 label="10" id="gfdl-10">
<title>FUTURE REVISIONS OF THIS LICENSE</title>
<para>The Free Software Foundation may publish new, revised
......@@ -419,7 +419,7 @@ of this license document, but changing it is not allowed.</para>
Free Software Foundation.</para>
</sect1>
<sect1 label="" id="gfdl_howto">
<sect1 label="" id="gfdl-howto">
<title>How to use this License for your documents</title>
<para>To use this License in a document you have written, include
......
docs/sgml/glossary.sgml
View file @ b54d65e4
......@@ -23,7 +23,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_a">
<glossdiv id="gloss-a">
<title>A</title>
<glossentry>
<glossterm>Apache</glossterm>
......@@ -40,7 +40,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_b">
<glossdiv id="gloss-b">
<title>B</title>
<glossentry>
<glossterm>Bug</glossterm>
......@@ -89,9 +89,9 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_c">
<glossdiv id="gloss-c">
<title></title>
<glossentry id="gloss_component">
<glossentry id="gloss-component">
<glossterm>Component</glossterm>
<glossdef>
<para>
......@@ -103,7 +103,7 @@
</para>
</glossdef>
</glossentry>
<glossentry id="gloss_cpan">
<glossentry id="gloss-cpan">
<glossterm><acronym>CPAN</acronym></glossterm>
<glossdef>
<para><acronym>CPAN</acronym> stands for the
......@@ -117,7 +117,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_d">
<glossdiv id="gloss-d">
<title>D</title>
<glossentry>
<glossterm>daemon</glossterm>
......@@ -132,7 +132,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_g">
<glossdiv id="gloss-g">
<title></title>
<glossentry>
<glossterm>Groups</glossterm>
......@@ -148,9 +148,9 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_i">
<glossdiv id="gloss-i">
<title>I</title>
<glossentry id="gloss_infiniteloop">
<glossentry id="gloss-infiniteloop">
<glossterm>Infinite Loop</glossterm>
<glossdef>
<para>A loop of information that never ends; see recursion.</para>
......@@ -158,7 +158,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_m">
<glossdiv id="gloss-m">
<title>M</title>
<glossentry>
<glossterm>mysqld</glossterm>
......@@ -173,10 +173,10 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_p">
<glossdiv id="gloss-p">
<title>P</title>
<glossentry>
<glossterm id="gloss_product">Product</glossterm>
<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
......@@ -212,7 +212,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_q">
<glossdiv id="gloss-q">
<title>Q</title>
<glossentry>
<glossterm>QA</glossterm>
......@@ -229,9 +229,9 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_r">
<glossdiv id="gloss-r">
<title>R</title>
<glossentry id="gloss_recursion" xreflabel="Recursion">
<glossentry id="gloss-recursion" xreflabel="Recursion">
<glossterm>Recursion</glossterm>
<glossdef>
<para>The property of a function looking back at itself for
......@@ -243,7 +243,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_s">
<glossdiv id="gloss-s">
<title>S</title>
<glossentry>
<glossterm><acronym>SGML</acronym></glossterm>
......@@ -266,9 +266,9 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_t">
<glossdiv id="gloss-t">
<title>T</title>
<glossentry id="gloss_target_milestone" xreflabel="Target Milestone">
<glossentry id="gloss-target-milestone" xreflabel="Target Milestone">
<glossterm>Target Milestone</glossterm>
<glossdef>
<para>
......@@ -285,7 +285,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_z">
<glossdiv id="gloss-z">
<title>Z</title>
<glossentry id="zarro-boogs-found" xreflabel="Zarro Boogs Found">
<glossterm>Zarro Boogs Found</glossterm>
......
docs/sgml/integration.sgml
View file @ b54d65e4
......@@ -8,7 +8,7 @@
<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">
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
......@@ -16,7 +16,7 @@
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>
linkend="tinderbox" /> and Bugzilla </para>
</section>
<section id="cvs" xreflabel="CVS, the Concurrent Versioning System">
......
docs/sgml/using.sgml
View file @ b54d65e4
......@@ -31,7 +31,7 @@ Chapter: Using Bugzilla
<title>Using Bugzilla</title>
<epigraph>
<para>
What, Why, How, & Where?
What, Why, How, &amp; Where?
</para>
</epigraph>
......@@ -612,7 +612,7 @@ system against which all others are measured.
<para>And all this time, I thought we were taking bugs <emphasis>out</emphasis>...</para>
</epigraph>
<section id="bug_writing">
<section id="bug-writing">
<title>Writing a Great Bug Report</title>
<para>
Before we plunge into writing your first bug report, I
......@@ -701,7 +701,7 @@ system against which all others are measured.
</para>
</section>
<section id="bug_manage">
<section id="bug-manage">
<title>Managing your Bug Reports</title>
<para>
OK, you should have a link to the bug you just created near
......@@ -812,7 +812,7 @@ system against which all others are measured.
their flow charts and know when it is time to pull the bug
onto a quality assurance platform for inspection. Other
people set up email gateways to
<xref linkend="bonsai"> or <xref linkend="tinderbox">, and
<xref linkend="bonsai" /> or <xref linkend="tinderbox" />, and
restrict which types of Bugzilla information are fed to
these systems..
</para>
......
docs/sgml/variants.sgml
View file @ b54d65e4
......@@ -23,25 +23,25 @@
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">
<section id="variant-fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris">
<title>Loki Bugzilla (Fenris)</title>
<para>Fenris can be found at <ulink
url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para>
</section>
<section id="variant_issuezilla" xreflabel="Issuezilla">
<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
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
......@@ -51,7 +51,7 @@
<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">
<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>
......@@ -59,7 +59,7 @@
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">
<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
......
docs/xml/Bugzilla-Guide.xml
View file @ b54d65e4
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" [
<!-- Include macros -->
<!ENTITY about SYSTEM "about.sgml">
......@@ -148,16 +148,16 @@ try to avoid clutter and feel free to waste space in the code to make it more re
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
While it is easy to use and quite flexible, it is
difficult for a novice to install and maintain. Although we
have provided step-by-step directions, Bugzilla is not always
easy to get working. Please be sure the person responsible
for installing and maintaining this software is a qualified
professional on operating system upon which you install
professional for the operating system upon which you install
Bugzilla.
</para>
<para>
THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT.
THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1.2 XML FORMAT.
IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN
TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT
ADDITIONS TO THE GUIDE WRITTEN IN HTML!
......@@ -165,18 +165,18 @@ try to avoid clutter and feel free to waste space in the code to make it more re
</abstract>
<KEYWORDSET>
<KEYWORD>Bugzilla</KEYWORD>
<KEYWORD>Guide</KEYWORD>
<KEYWORD>installation</KEYWORD>
<KEYWORD>FAQ</KEYWORD>
<KEYWORD>administration</KEYWORD>
<KEYWORD>integration</KEYWORD>
<KEYWORD>MySQL</KEYWORD>
<KEYWORD>Mozilla</KEYWORD>
<KEYWORD>webtools</KEYWORD>
</KEYWORDSET>
</BOOKINFO>
<keywordset>
<keyword>Bugzilla</keyword>
<keyword>Guide</keyword>
<keyword>installation</keyword>
<keyword>FAQ</keyword>
<keyword>administration</keyword>
<keyword>integration</keyword>
<keyword>MySQL</keyword>
<keyword>Mozilla</keyword>
<keyword>webtools</keyword>
</keywordset>
</bookinfo>
<!-- About This Guide -->
&about;
......@@ -203,7 +203,7 @@ try to avoid clutter and feel free to waste space in the code to make it more re
&faq;
<!-- Appendix: Required Bugzilla Software Links -->
&requiredsoftware
&requiredsoftware;
<!-- Appendix: The Database Schema -->
&database;
......
docs/xml/administration.xml
View file @ b54d65e4
......@@ -8,7 +8,7 @@
</subtitle>
<para>
So you followed <quote><xref linkend="installation"></quote> to the
So you followed <quote><xref linkend="installation" /></quote> to the
letter, and logged into Bugzilla for the very first time with your
super-duper god account. You sit, contentedly staring at the
Bugzilla Query Screen, the worst of the whole mad business of
......@@ -623,7 +623,7 @@
<subtitle>Formerly, and in some spots still, called
"Programs"</subtitle>
<para>
<glossterm linkend="gloss_product" baseform="product">Products</glossterm> are
<glossterm linkend="gloss-product" baseform="product">Products</glossterm> are
the broadest category in Bugzilla, and you should have the
least of these. If your company makes computer games, you
should have one product per game, and possibly a few special
......
docs/xml/database.xml
View file @ b54d65e4
......@@ -13,7 +13,7 @@
<para>
<mediaobject>
<imageobject>
<imagedata fileref="../images/dbschema.jpg" format="jpg">
<imagedata fileref="../images/dbschema.jpg" format="JPG" />
</imageobject>
<textobject>
......@@ -359,7 +359,7 @@ http://www.devshed.com/Server_Side/MySQL/
</section>
<section id="granttables">
<title>MySQL Permissions & Grant Tables</title>
<title>MySQL Permissions &amp; Grant Tables</title>
<note>
<para>The following portion of documentation comes from my
......@@ -480,7 +480,7 @@ mysql> GRANT
SELECT,INSERT,UPDATE,DELETE,INDEX,ALTER,CREATE,DROP,RELOAD,SHUTDOWN,PROCESS,
FILE,
ON keystone.*
TO <$sys_dbuser name>@localhost
TO &lt;$sys_dbuser name>@localhost
IDENTIFIED BY '(password)'
WITH GRANT OPTION;
......@@ -488,7 +488,7 @@ OR
mysql> GRANT ALL PRIVELEGES
ON keystone.*
TO <$sys_dbuser name>@localhost
TO &lt;$sys_dbuser name>@localhost
IDENTIFIED BY '(password)'
WITH GRANT OPTION;
......
docs/xml/faq.xml
View file @ b54d65e4
......@@ -6,7 +6,7 @@
<qandaset>
<qandadiv id="faq_general">
<qandadiv id="faq-general">
<title>General Questions</title>
<qandaentry>
......@@ -270,7 +270,7 @@
</qandadiv>
<qandadiv id="faq_redhat">
<qandadiv id="faq-redhat">
<title>Red Hat Bugzilla</title>
<para>
<note>
......@@ -496,7 +496,7 @@
</qandadiv>
<qandadiv id="faq_loki">
<qandadiv id="faq-loki">
<title>Loki Bugzilla (AKA Fenris)</title>
<qandaentry>
......@@ -515,7 +515,7 @@
</qandadiv>
<qandadiv id="faq_phb">
<qandadiv id="faq-phb">
<title>Pointy-Haired-Boss Questions</title>
<para>
<note>
......@@ -1011,7 +1011,7 @@ if ($::FORM{sub} eq 'PutFooter') {
your Bugzilla install can run untended for years. If your
Bugzilla strategy is critical to your business workflow, hire somebody
with reasonable UNIX or Perl skills to handle your process management and
bug-tracking maintenance & customization.
bug-tracking maintenance &amp; customization.
</para>
</answer>
</qandaentry>
......@@ -1032,7 +1032,7 @@ if ($::FORM{sub} eq 'PutFooter') {
</qandaentry>
</qandadiv>
<qandadiv id="faq_install">
<qandadiv id="faq-install">
<title>Bugzilla Installation</title>
<qandaentry>
<question>
......@@ -1078,7 +1078,7 @@ if ($::FORM{sub} eq 'PutFooter') {
</qandadiv>
<qandadiv id="faq_security">
<qandadiv id="faq-security">
<title>Bugzilla Security</title>
<qandaentry>
......@@ -1133,7 +1133,7 @@ if ($::FORM{sub} eq 'PutFooter') {
</qandaentry>
</qandadiv>
<qandadiv id="faq_email">
<qandadiv id="faq-email">
<title>Bugzilla Email</title>
<qandaentry>
......@@ -1263,7 +1263,7 @@ if ($::FORM{sub} eq 'PutFooter') {
</qandaentry>
</qandadiv>
<qandadiv id="faq_db">
<qandadiv id="faq-db">
<title>Bugzilla Database</title>
<qandaentry>
......@@ -1451,7 +1451,7 @@ if ($::FORM{sub} eq 'PutFooter') {
</qandadiv>
<qandadiv id="faq_nt">
<qandadiv id="faq-nt">
<title>Bugzilla and Win32</title>
<qandaentry>
......@@ -1662,7 +1662,7 @@ A: Sure! Here ya go!
</qandadiv>
<qandadiv id="faq_use">
<qandadiv id="faq-use">
<title>Bugzilla Usage</title>
<qandaentry>
......@@ -1754,7 +1754,7 @@ A: Sure! Here ya go!
</qandadiv>
<qandadiv id="faq_hacking">
<qandadiv id="faq-hacking">
<title>Bugzilla Hacking</title>
<qandaentry>
......@@ -1862,7 +1862,7 @@ A: Sure! Here ya go!
</qandaset>
</APPENDIX>
</appendix>
<!-- Keep this comment at the end of the file
......
docs/xml/gfdl.xml
View file @ b54d65e4
......@@ -18,7 +18,7 @@ Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.</para>
</blockquote>
<sect1 label="0" id="gfdl_0">
<sect1 label="0" id="gfdl-0">
<title>PREAMBLE</title>
<para>The purpose of this License is to make a manual, textbook,
......@@ -45,7 +45,7 @@ of this license document, but changing it is not allowed.</para>
whose purpose is instruction or reference.</para>
</sect1>
<sect1 label="1" id="gfdl_1">
<sect1 label="1" id="gfdl-1">
<title>APPLICABILITY AND DEFINITIONS</title>
<para>This License applies to any manual or other work that
......@@ -113,7 +113,7 @@ of this license document, but changing it is not allowed.</para>
text.</para>
</sect1>
<sect1 label="2" id="gfdl_2">
<sect1 label="2" id="gfdl-2">
<title>VERBATIM COPYING</title>
<para>You may copy and distribute the Document in any medium,
......@@ -131,7 +131,7 @@ of this license document, but changing it is not allowed.</para>
above, and you may publicly display copies.</para>
</sect1>
<sect1 label="3" id="gfdl_3">
<sect1 label="3" id="gfdl-3">
<title>COPYING IN QUANTITY</title>
<para>If you publish printed copies of the Document numbering more
......@@ -173,7 +173,7 @@ of this license document, but changing it is not allowed.</para>
updated version of the Document.</para>
</sect1>
<sect1 label="4" id="gfdl_4">
<sect1 label="4" id="gfdl-4">
<title>MODIFICATIONS</title>
<para>You may copy and distribute a Modified Version of the
......@@ -304,7 +304,7 @@ of this license document, but changing it is not allowed.</para>
or to assert or imply endorsement of any Modified Version.</para>
</sect1>
<sect1 label="5" id="gfdl_5">
<sect1 label="5" id="gfdl-5">
<title>COMBINING DOCUMENTS</title>
<para>You may combine the Document with other documents released
......@@ -331,7 +331,7 @@ of this license document, but changing it is not allowed.</para>
must delete all sections entitled "Endorsements."</para>
</sect1>
<sect1 label="6" id="gfdl_6">
<sect1 label="6" id="gfdl-6">
<title>COLLECTIONS OF DOCUMENTS</title>
<para>You may make a collection consisting of the Document and
......@@ -348,7 +348,7 @@ of this license document, but changing it is not allowed.</para>
copying of that document.</para>
</sect1>
<sect1 label="7" id="gfdl_7">
<sect1 label="7" id="gfdl-7">
<title>AGGREGATION WITH INDEPENDENT WORKS</title>
<para>A compilation of the Document or its derivatives with other
......@@ -369,7 +369,7 @@ of this license document, but changing it is not allowed.</para>
aggregate.</para>
</sect1>
<sect1 label="8" id="gfdl_8">
<sect1 label="8" id="gfdl-8">
<title>TRANSLATION</title>
<para>Translation is considered a kind of modification, so you may
......@@ -385,7 +385,7 @@ of this license document, but changing it is not allowed.</para>
prevail.</para>
</sect1>
<sect1 label="9" id="gfdl_9">
<sect1 label="9" id="gfdl-9">
<title>TERMINATION</title>
<para>You may not copy, modify, sublicense, or distribute the
......@@ -398,7 +398,7 @@ of this license document, but changing it is not allowed.</para>
compliance.</para>
</sect1>
<sect1 label="10" id="gfdl_10">
<sect1 label="10" id="gfdl-10">
<title>FUTURE REVISIONS OF THIS LICENSE</title>
<para>The Free Software Foundation may publish new, revised
......@@ -419,7 +419,7 @@ of this license document, but changing it is not allowed.</para>
Free Software Foundation.</para>
</sect1>
<sect1 label="" id="gfdl_howto">
<sect1 label="" id="gfdl-howto">
<title>How to use this License for your documents</title>
<para>To use this License in a document you have written, include
......
docs/xml/glossary.xml
View file @ b54d65e4
......@@ -23,7 +23,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_a">
<glossdiv id="gloss-a">
<title>A</title>
<glossentry>
<glossterm>Apache</glossterm>
......@@ -40,7 +40,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_b">
<glossdiv id="gloss-b">
<title>B</title>
<glossentry>
<glossterm>Bug</glossterm>
......@@ -89,9 +89,9 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_c">
<glossdiv id="gloss-c">
<title></title>
<glossentry id="gloss_component">
<glossentry id="gloss-component">
<glossterm>Component</glossterm>
<glossdef>
<para>
......@@ -103,7 +103,7 @@
</para>
</glossdef>
</glossentry>
<glossentry id="gloss_cpan">
<glossentry id="gloss-cpan">
<glossterm><acronym>CPAN</acronym></glossterm>
<glossdef>
<para><acronym>CPAN</acronym> stands for the
......@@ -117,7 +117,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_d">
<glossdiv id="gloss-d">
<title>D</title>
<glossentry>
<glossterm>daemon</glossterm>
......@@ -132,7 +132,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_g">
<glossdiv id="gloss-g">
<title></title>
<glossentry>
<glossterm>Groups</glossterm>
......@@ -148,9 +148,9 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_i">
<glossdiv id="gloss-i">
<title>I</title>
<glossentry id="gloss_infiniteloop">
<glossentry id="gloss-infiniteloop">
<glossterm>Infinite Loop</glossterm>
<glossdef>
<para>A loop of information that never ends; see recursion.</para>
......@@ -158,7 +158,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_m">
<glossdiv id="gloss-m">
<title>M</title>
<glossentry>
<glossterm>mysqld</glossterm>
......@@ -173,10 +173,10 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_p">
<glossdiv id="gloss-p">
<title>P</title>
<glossentry>
<glossterm id="gloss_product">Product</glossterm>
<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
......@@ -212,7 +212,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_q">
<glossdiv id="gloss-q">
<title>Q</title>
<glossentry>
<glossterm>QA</glossterm>
......@@ -229,9 +229,9 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_r">
<glossdiv id="gloss-r">
<title>R</title>
<glossentry id="gloss_recursion" xreflabel="Recursion">
<glossentry id="gloss-recursion" xreflabel="Recursion">
<glossterm>Recursion</glossterm>
<glossdef>
<para>The property of a function looking back at itself for
......@@ -243,7 +243,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_s">
<glossdiv id="gloss-s">
<title>S</title>
<glossentry>
<glossterm><acronym>SGML</acronym></glossterm>
......@@ -266,9 +266,9 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_t">
<glossdiv id="gloss-t">
<title>T</title>
<glossentry id="gloss_target_milestone" xreflabel="Target Milestone">
<glossentry id="gloss-target-milestone" xreflabel="Target Milestone">
<glossterm>Target Milestone</glossterm>
<glossdef>
<para>
......@@ -285,7 +285,7 @@
</glossentry>
</glossdiv>
<glossdiv id="gloss_z">
<glossdiv id="gloss-z">
<title>Z</title>
<glossentry id="zarro-boogs-found" xreflabel="Zarro Boogs Found">
<glossterm>Zarro Boogs Found</glossterm>
......
docs/xml/integration.xml
View file @ b54d65e4
......@@ -8,7 +8,7 @@
<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">
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
......@@ -16,7 +16,7 @@
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>
linkend="tinderbox" /> and Bugzilla </para>
</section>
<section id="cvs" xreflabel="CVS, the Concurrent Versioning System">
......
docs/xml/using.xml
View file @ b54d65e4
......@@ -31,7 +31,7 @@ Chapter: Using Bugzilla
<title>Using Bugzilla</title>
<epigraph>
<para>
What, Why, How, & Where?
What, Why, How, &amp; Where?
</para>
</epigraph>
......@@ -612,7 +612,7 @@ system against which all others are measured.
<para>And all this time, I thought we were taking bugs <emphasis>out</emphasis>...</para>
</epigraph>
<section id="bug_writing">
<section id="bug-writing">
<title>Writing a Great Bug Report</title>
<para>
Before we plunge into writing your first bug report, I
......@@ -701,7 +701,7 @@ system against which all others are measured.
</para>
</section>
<section id="bug_manage">
<section id="bug-manage">
<title>Managing your Bug Reports</title>
<para>
OK, you should have a link to the bug you just created near
......@@ -812,7 +812,7 @@ system against which all others are measured.
their flow charts and know when it is time to pull the bug
onto a quality assurance platform for inspection. Other
people set up email gateways to
<xref linkend="bonsai"> or <xref linkend="tinderbox">, and
<xref linkend="bonsai" /> or <xref linkend="tinderbox" />, and
restrict which types of Bugzilla information are fed to
these systems..
</para>
......
docs/xml/variants.xml
View file @ b54d65e4
......@@ -23,25 +23,25 @@
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">
<section id="variant-fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris">
<title>Loki Bugzilla (Fenris)</title>
<para>Fenris can be found at <ulink
url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para>
</section>
<section id="variant_issuezilla" xreflabel="Issuezilla">
<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
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
......@@ -51,7 +51,7 @@
<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">
<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>
......@@ -59,7 +59,7 @@
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">
<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
......
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