Commit a07f84f3 authored by barnboy%trilobyte.net's avatar barnboy%trilobyte.net

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

be used for 2.14 documentation due to inconsistencies.
parent d87cf85f
<!DOCTYPE BOOK PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!-- Include macros --> <!-- Include macros -->
<!ENTITY about SYSTEM "about.sgml"> <!ENTITY about SYSTEM "about.sgml">
...@@ -17,99 +17,156 @@ ...@@ -17,99 +17,156 @@
<!ENTITY patches SYSTEM "patches.sgml"> <!ENTITY patches SYSTEM "patches.sgml">
<!ENTITY variants SYSTEM "variants.sgml"> <!ENTITY variants SYSTEM "variants.sgml">
<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml"> <!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
<!ENTITY revhistory SYSTEM "revhistory.sgml">
<!ENTITY bz "http://www.mozilla.org/projects/bugzilla">
<!ENTITY bz-ver "2.14">
<!ENTITY bz-cvs-ver "2.15">
<!ENTITY bzg-date "August 10, 2001">
<!ENTITY bzg-ver "2.14.0">
<!ENTITY bzg-cvs-ver "2.15.0">
<!ENTITY bzg-auth "Matthew P. Barnson">
<!ENTITY bzg-auth-email "<email>barnboy@NOSPAM.trilobyte.net</email>">
<!ENTITY mysql "http://www.mysql.com/">
<!ENTITY perl-ver "5.6.1">
]> ]>
<!-- Coding standards for this document
1. Preface new or modified sections with a comment stating who
modified it and when; please also use the "authorinitials" tag.
2. There is no "two".
3. Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc.
4. Use Entities to include files for new chapters in Bugzilla-Guide.sgml.
5. Ensure all documents compile cleanly to HTML after modification.
The errors "DTD Declaration not allowed here" and "DTDDECL catalog types not supported"
are normal errors to be expected when compiling the whole guide.
6. Try to index important terms wherever possible.
7. Follow coding standards at http://www.linuxdoc.org. <!-- Coding standards for this document
8. All tags should be lowercase (needsfix)
9. Code being submitted for review should use the
"review" tag. Documentation on this is available at
http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
under section 4.9.4, "Making notes on the text while it's being written".
10. Please use sensible spacing. The comments at the very end of each Guide * Other than the GFDL, please use the "section" tag instead of "sect1", "sect2", etc.
file define reasonable defaults for PSGML mode in EMACS. * Use Entities to include files for new chapters in Bugzilla-Guide.sgml.
Double-indent tags, use double spacing whenever possible, * Try to use Entities for frequently-used passages of text as well.
try to avoid clutter and feel free to waste space in the code to make it more readable. * Ensure all documents compile cleanly to HTML after modification.
The warning, "DTDDECL catalog types not supported" is normal.
* Try to index important terms wherever possible.
* Use "glossterm" whenever you introduce a new term.
* Follow coding standards at http://www.linuxdoc.org, and
check out the KDE guidelines (they are nice, too)
http://i18n.kde.org/doc/markup.html
* All tags should be lowercase (needsfix)
* Please use sensible spacing. The comments at the very end of each
file define reasonable defaults for PSGML mode in EMACS.
Double-indent tags, use double spacing whenever possible, and
try to avoid clutter and feel free to waste space in the code to make it more readable.
--> -->
<BOOK ID="index"> <book id="index">
<!-- Header --> <!-- Header -->
<BOOKINFO> <bookinfo>
<TITLE>The Bugzilla Guide</TITLE> <title>The Bugzilla Guide</title>
<PUBDATE>2001-04-25</PUBDATE> <pubdate>2001-04-25</pubdate>
<AUTHOR> <revhistory>
<FIRSTNAME>Matthew</FIRSTNAME> <revision>
<OTHERNAME>P.</OTHERNAME> <revnumber>v2.11</revnumber>
<SURNAME>Barnson</SURNAME> <date>20 December 2000</date>
<affiliation> <authorinitials>MPB</authorinitials>
<address><email>barnboy@trilobyte.net</email></address> <revremark>
</affiliation> Converted the README, FAQ, and DATABASE information into
</AUTHOR> SGML docbook format.
</revremark>
<ABSTRACT> </revision>
<PARA>This is the documentation for Bugzilla, the Mozilla bug-tracking system.</PARA>
</ABSTRACT>
<REVHISTORY>
<REVISION>
<REVNUMBER>v2.11</REVNUMBER>
<DATE>20 December 2000</DATE>
<AUTHORINITIALS>MPB</AUTHORINITIALS>
<REVREMARK>Converted the README, FAQ, and DATABASE information into SGML
docbook format.</REVREMARK>
</REVISION>
<revision> <revision>
<revnumber>2.11.1</revnumber> <revnumber>2.11.1</revnumber>
<date>06 March 2001</date> <date>06 March 2001</date>
<authorinitials>MPB</authorinitials> <authorinitials>MPB</authorinitials>
<revremark> <revremark>
Took way too long to revise this for 2.12 release. Took way too long to revise this for 2.12 release. Updated
Updated FAQ to use qandaset tags instead of literallayout, FAQ to use qandaset tags instead of literallayout, cleaned
cleaned up administration section, added User Guide section, up administration section, added User Guide section,
miscellaneous FAQ updates and third-party integration information. miscellaneous FAQ updates and third-party integration
From this point on all new tags are lowercase in preparation for the information. From this point on all new tags are lowercase
2.13 release of the Guide in XML format instead of SGML. in preparation for the 2.13 release of the Guide in XML
format instead of SGML.
</revremark> </revremark>
</revision> </revision>
<revision> <revision>
<revnumber>2.12.0</revnumber> <revnumber>2.12.0</revnumber>
<date>24 April 2001</date> <date>24 April 2001</date>
<authorinitials>MPB</authorinitials> <authorinitials>MPB</authorinitials>
<revremark> <revremark>
Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding Things fixed this release: Elaborated on queryhelp
moving bugs from one keyword to another, clarified possible problems with the Landfill interface, added FAQ regarding moving bugs from one keyword
tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the to another, clarified possible problems with the Landfill
README into the UNIX installation section, and changed the README to indicate the deprecated tutorial, fixed a boatload of typos and unclear sentence
status. Things I know need work: Used "simplelist" a lot, where I should have used structures. Incorporated the README into the UNIX
"procedure" to tag things. Need to lowercase all tags to be XML compliant. installation section, and changed the README to indicate the
deprecated status. Things I know need work: Used
"simplelist" a lot, where I should have used "procedure" to
tag things. Need to lowercase all tags to be XML compliant.
</revremark> </revremark>
</revision> </revision>
</REVHISTORY>
<revision>
<revnumber>2.14.0</revnumber>
<date>07 August 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Attempted to integrate relevant portions of the UNIX and
Windows installation instructions, moved some data from FAQ
to Install, removed references to README from text, added
Mac OS X install instructions, fixed a bunch
of tpyos (Mark Harig), linked text that referenced other
parts of the Guide, and nuked the old MySQL permissions
section.
</revremark>
</revision>
</revhistory>
<authorgroup>
<author>
<firstname>Matthew</firstname>
<othername>P.</othername>
<surname>Barnson</surname>
<affiliation>
<address><email>barnboy@NOSPAM.trilobyte.net</email></address>
</affiliation>
</author>
<collab>
<collabname>Zach Lipton</collabname>
<affiliation>
<address><email>zach@NOSPAM.zachlipton.com</email></address>
</affiliation>
</collab>
<editor>
<firstname>I.</firstname>
<surname>Freely</surname>
<othername>P.</othername>
<affiliation>
<address><email>ipfreely@freely.eye-p.net</email></address>
</affiliation>
</editor>
</authorgroup>
<abstract>
<para>
This is the documentation for Bugzilla, the Mozilla
bug-tracking system.
</para>
<para>
Bugzilla is an enterprise-class set of software utilities
that, when used together, power issue-tracking for hundreds of
organizations around the world, tracking millions of bugs.
While it is easy to use and quite flexible, it is very
difficult for a novice to install and maintain. Although we
have provided step-by-step directions, Bugzilla is not always
easy to get working. Please be sure the person responsible
for installing and maintaining this software is a qualified
professional on operating system upon which you install
Bugzilla.
</para>
</abstract>
<KEYWORDSET> <KEYWORDSET>
<KEYWORD>Bugzilla</KEYWORD> <KEYWORD>Bugzilla</KEYWORD>
...@@ -127,15 +184,15 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html ...@@ -127,15 +184,15 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- About This Guide --> <!-- About This Guide -->
&about; &about;
<!-- Using Bugzilla -->
&using;
<!-- Installing Bugzilla --> <!-- Installing Bugzilla -->
&installation; &installation;
<!-- Administering Bugzilla --> <!-- Administering Bugzilla -->
&administration; &administration;
<!-- Using Bugzilla -->
&using;
<!-- Integrating Bugzilla with Third-Party Tools --> <!-- Integrating Bugzilla with Third-Party Tools -->
&integration; &integration;
...@@ -166,31 +223,26 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html ...@@ -166,31 +223,26 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- Index --> <!-- Index -->
&index; &index;
</BOOK>
</book>
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
Local variables: Local variables:
mode: sgml mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t sgml-always-quote-attributes:t
sgml-indent-step:2 sgml-auto-insert-required-elements:t
sgml-indent-data:t sgml-balanced-tag-edit:t
sgml-parent-document:nil
sgml-exposed-tags:nil sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil sgml-local-catalogs:nil
sgml-local-ecat-files:nil sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End: End:
--> -->
<!-- <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> --> <!-- <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<section id="conventions"> <section id="conventions">
<title>Document Conventions</title> <title>Document Conventions</title>
<indexterm zone="conventions"> <indexterm zone="conventions">
<primary>conventions</primary> <primary>conventions</primary>
</indexterm> </indexterm>
<para>This document uses the following conventions:</para> <para>
This document uses the following conventions
</para>
<informaltable frame="none"> <informaltable frame="none">
<tgroup cols="2"> <tgroup cols="2">
<thead> <thead>
<row> <row>
<entry>Descriptions</entry> <entry>Descriptions</entry>
<entry>Appearance</entry> <entry>Appearance</entry>
</row> </row>
</thead> </thead>
<tbody> <tbody>
<row> <row>
<entry>Caution</entry> <entry>Warnings</entry>
<entry><caution>
<entry> <para>Warnings.</para>
<caution> </caution></entry>
<para>Don't run with scissors!</para>
</caution>
</entry>
</row> </row>
<row> <row>
<entry>Hint or Tip</entry> <entry>Hint</entry>
<entry><tip>
<entry> <para>Hint.</para>
<tip> </tip></entry>
<para>For best results... </para>
</tip>
</entry>
</row> </row>
<row> <row>
<entry>Note</entry> <entry>Notes</entry>
<entry><note>
<entry> <para>Note.</para>
<note> </note></entry>
<para>Dear John...</para>
</note>
</entry>
</row> </row>
<row> <row>
<entry>Warning</entry> <entry>Information requiring special attention</entry>
<entry><warning>
<entry> <para>Warning.</para>
<warning> </warning></entry>
<para>Read this or the cat gets it.</para>
</warning>
</entry>
</row> </row>
<row> <row>
<entry>File or directory name</entry> <entry>File Names</entry>
<entry><filename>file.extension</filename></entry>
<entry>
<filename>filename</filename>
</entry>
</row> </row>
<row> <row>
<entry>Command to be typed</entry> <entry>Directory Names</entry>
<entry><filename class="directory">directory</filename></entry>
<entry>
<command>command</command>
</entry>
</row> </row>
<row> <row>
<entry>Application name</entry> <entry>Commands to be typed</entry>
<entry><command>command</command></entry>
<entry>
<application>application</application>
</entry>
</row> </row>
<row> <row>
<entry> <entry>Applications Names</entry>
Normal user's prompt under bash shell</entry> <entry><application>application</application></entry>
</row>
<row>
<entry><foreignphrase>Prompt</foreignphrase> of users command under bash shell</entry>
<entry>bash$</entry> <entry>bash$</entry>
</row> </row>
<row> <row>
<entry> <entry><foreignphrase>Prompt</foreignphrase> of root users command under bash shell</entry>
Root user's prompt under bash shell</entry>
<entry>bash#</entry> <entry>bash#</entry>
</row> </row>
<row>
<entry><foreignphrase>Prompt</foreignphrase> of user command under tcsh shell</entry>
<entry>tcsh$</entry>
</row>
<row> <row>
<entry> <entry>Environment Variables</entry>
Normal user's prompt under tcsh shell</entry> <entry><envar>VARIABLE</envar></entry>
<entry>tcsh$</entry>
</row> </row>
<row> <row>
<entry>Environment variables</entry> <entry>Emphasized word</entry>
<entry><emphasis>word</emphasis></entry>
<entry>
<envar>VARIABLE</envar>
</entry>
</row> </row>
<row> <row>
<entry>Term found in the glossary</entry> <entry>Code Example</entry>
<entry><programlisting><sgmltag class="starttag">para</sgmltag>Beginning and end of paragraph<sgmltag class="endtag">para</sgmltag></programlisting></entry>
<entry>
<glossterm linkend="gloss-bugzilla">Bugzilla</glossterm>
</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>
</row> </row>
</tbody> </tbody>
</tgroup> </tgroup>
</informaltable> </informaltable>
<para>
This documentation is maintained in DocBook 4.1.2 XML format.
Changes are best submitted as plain text or XML diffs, attached
to a bug filed in the &bzg-bugs; component.
</para>
</section> </section>
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
Local variables: Local variables:
mode: sgml mode: sgml
...@@ -156,9 +109,8 @@ sgml-local-ecat-files:nil ...@@ -156,9 +109,8 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil sgml-minimize-attributes:nil
sgml-namecase-general:t sgml-namecase-general:t
sgml-omittag:t sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter") sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t sgml-shorttag:t
sgml-tag-region-if-active:t sgml-tag-region-if-active:t
End: End:
--> -->
...@@ -13,9 +13,8 @@ sgml-local-ecat-files:nil ...@@ -13,9 +13,8 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil sgml-minimize-attributes:nil
sgml-namecase-general:t sgml-namecase-general:t
sgml-omittag:t sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter") sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t sgml-shorttag:t
sgml-tag-region-if-active:t sgml-tag-region-if-active:t
End: End:
--> -->
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > <!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
<!-- Keep these tools listings in alphabetical order please. -MPB --> <!-- Keep these tools listings in alphabetical order please. -MPB -->
...@@ -12,14 +12,13 @@ ...@@ -12,14 +12,13 @@
<section id="cvs"> <section id="cvs">
<title>CVS</title> <title>CVS</title>
<para>We need CVS integration information</para> <para>CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</para>
</section> </section>
<section id="scm"> <section id="scm">
<title>Perforce SCM</title> <title>Perforce SCM</title>
<para> <para>
Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack. You can find the project page for Bugzilla and Teamtrack Perforce integration at:
You can find the main project page at
<ulink url="http://www.ravenbrook.com/project/p4dti/"> <ulink url="http://www.ravenbrook.com/project/p4dti/">
http://www.ravenbrook.com/project/p4dti</ulink>. "p4dti" is now an officially http://www.ravenbrook.com/project/p4dti</ulink>. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public Depot" supported product from Perforce, and you can find the "Perforce Public Depot"
...@@ -54,22 +53,25 @@ ...@@ -54,22 +53,25 @@
</chapter> </chapter>
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
Local variables: Local variables:
mode: sgml mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t sgml-always-quote-attributes:t
sgml-indent-step:2 sgml-auto-insert-required-elements:t
sgml-indent-data:t sgml-balanced-tag-edit:t
sgml-parent-document:nil
sgml-exposed-tags:nil sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil sgml-local-catalogs:nil
sgml-local-ecat-files:nil sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End: End:
--> -->
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> <!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="patches"> <appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla">
<title>Useful Patches and Utilities for Bugzilla</title> <title>Useful Patches and Utilities for Bugzilla</title>
<section id="setperl"> <section id="setperl" xreflabel="The setperl.csh Utility">
<title>The setperl.csh Utility</title> <title>The setperl.csh Utility</title>
<para> <para> You can use the "setperl.csh" utility to quickly and
You can use the "setperl.csh" utility to quickly and easily easily change the path to perl on all your Bugzilla files. This
change the path to perl on all your Bugzilla files. is a C-shell script; if you do not have "csh" or "tcsh" in the
This is a C-shell script; if you do not have "csh" or "tcsh" in the search search path on your system, it will not work!
path on your system, it will not work!
</para> </para>
<procedure> <procedure>
<step> <step>
...@@ -28,18 +27,15 @@ ...@@ -28,18 +27,15 @@
</step> </step>
<step> <step>
<para> <para>
<computeroutput> <computeroutput> <prompt>bash#</prompt> <command>wget -O
<prompt>bash#</prompt> setperl.csh
<command>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command> 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command> </computeroutput>
</computeroutput>
</para> </para>
</step> </step>
<step> <step>
<para> <para>
<computeroutput> <computeroutput> <prompt>bash#</prompt> <command>chmod
<prompt>bash#</prompt> u+x setperl.csh</command> </computeroutput>
<command>chmod u+x setperl.csh</command>
</computeroutput>
</para> </para>
</step> </step>
</substeps> </substeps>
...@@ -59,10 +55,8 @@ ...@@ -59,10 +55,8 @@
</step> </step>
<step> <step>
<para> <para>
<computeroutput> <computeroutput> <prompt>bash#</prompt> <command>chmod
<prompt>bash#</prompt> u+x duplicates.cgi</command> </computeroutput>
<command>chmod u+x duplicates.cgi</command>
</computeroutput>
</para> </para>
</step> </step>
<step> <step>
...@@ -80,16 +74,14 @@ ...@@ -80,16 +74,14 @@
Run the script: Run the script:
</para> </para>
<para> <para>
<computeroutput> <computeroutput> <prompt>bash#</prompt>
<prompt>bash#</prompt>
<command>./setperl.csh /your/path/to/perl</command> <command>./setperl.csh /your/path/to/perl</command>
</computeroutput> </computeroutput>
<example> <example>
<title>Using Setperl to set your perl path</title> <title>Using Setperl to set your perl path</title>
<para> <para>
<computeroutput> <computeroutput> <prompt>bash#</prompt>
<prompt>bash#</prompt> <command>./setperl.csh /usr/bin/perl</command>
<command>./setperl.csh /usr/bin/perl</command>
</computeroutput> </computeroutput>
</para> </para>
</example> </example>
...@@ -101,22 +93,23 @@ ...@@ -101,22 +93,23 @@
<section id="cmdline"> <section id="cmdline">
<title>Command-line Bugzilla Queries</title> <title>Command-line Bugzilla Queries</title>
<para> <para>
Users can query Bugzilla from the command line using Users can query Bugzilla from the command line using this suite
this suite of utilities. of utilities.
</para> </para>
<para> <para>
The query.conf file contains the mapping from options to field The query.conf file contains the mapping from options to field
names and comparison types. Quoted option names are "grepped" for, so names and comparison types. Quoted option names are "grepped"
it should be easy to edit this file. Comments (#) have no effect; you for, so it should be easy to edit this file. Comments (#) have
must make sure these lines do not contain any quoted "option" no effect; you must make sure these lines do not contain any
quoted "option"
</para> </para>
<para> <para>
buglist is a shell script which submits a Bugzilla query and writes the buglist is a shell script which submits a Bugzilla query and
resulting HTML page to stdout. It supports both short options, writes the resulting HTML page to stdout. It supports both
(such as "-Afoo" or "-Rbar") and long options (such as short options, (such as "-Afoo" or "-Rbar") and long options
"--assignedto=foo" or "--reporter=bar"). If the first character (such as "--assignedto=foo" or "--reporter=bar"). If the first
of an option is not "-", it is treated as if it were prefixed character of an option is not "-", it is treated as if it were
with "--default=". prefixed with "--default=".
</para> </para>
<para> <para>
The columlist is taken from the COLUMNLIST environment variable. The columlist is taken from the COLUMNLIST environment variable.
...@@ -128,10 +121,10 @@ ...@@ -128,10 +121,10 @@
<para> <para>
bugs is a simple shell script which calls buglist and extracts bugs is a simple shell script which calls buglist and extracts
the bug numbers from the output. Adding the prefix the bug numbers from the output. Adding the prefix
"http://bugzilla.mozilla.org/buglist.cgi?bug_id=" "http://bugzilla.mozilla.org/buglist.cgi?bug_id=" turns the bug
turns the bug list into a working link if any bugs are found. list into a working link if any bugs are found. Counting bugs is
Counting bugs is easy. Pipe the results through easy. Pipe the results through <command>sed -e 's/,/ /g' | wc |
<command>sed -e 's/,/ /g' | wc | awk '{printf $2 "\n"}'</command> awk '{printf $2 "\n"}'</command>
</para> </para>
<para> <para>
Akkana says she has good results piping buglist output through Akkana says she has good results piping buglist output through
...@@ -145,26 +138,23 @@ ...@@ -145,26 +138,23 @@
<substeps> <substeps>
<step> <step>
<para> <para>
<computeroutput> <computeroutput> <prompt>bash$</prompt> <command>wget -O
<prompt>bash$</prompt> query.conf
<command>wget -O query.conf 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</command> 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26157'</command> </computeroutput>
</computeroutput>
</para> </para>
</step> </step>
<step> <step>
<para> <para>
<computeroutput> <computeroutput> <prompt>bash$</prompt> <command>wget -O
<prompt>bash$</prompt> buglist
<command>wget -O buglist 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</command> 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26944'</command> </computeroutput>
</computeroutput>
</para> </para>
</step> </step>
<step> <step>
<para> <para>
<computeroutput> <computeroutput> <prompt>bash#</prompt> <command>wget -O
<prompt>bash#</prompt> bugs
<command>wget -O bugs 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command> 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=26215'</command> </computeroutput>
</computeroutput>
</para> </para>
</step> </step>
</substeps> </substeps>
...@@ -185,53 +175,64 @@ ...@@ -185,53 +175,64 @@
<title>The Quicksearch Utility</title> <title>The Quicksearch Utility</title>
<para> <para>
Quicksearch is a new, experimental feature of the 2.12 release. Quicksearch is a new, experimental feature of the 2.12 release.
It consist of two Javascript files, "quicksearch.js" and "localconfig.js", It consist of two Javascript files, "quicksearch.js" and
and two documentation files, "quicksearch.html" and "quicksearchhack.html" "localconfig.js", and two documentation files,
"quicksearch.html" and "quicksearchhack.html"
</para> </para>
<para> <para>
The index.html page has been updated to include the QuickSearch text box. The index.html page has been updated to include the QuickSearch
text box.
</para> </para>
<para> <para>
To take full advantage of the query power, the Bugzilla maintainer must To take full advantage of the query power, the Bugzilla
edit "localconfig.js" according to the value sets used in the local installation. maintainer must edit "localconfig.js" according to the value
sets used in the local installation.
</para> </para>
<para> <para>
Currently, keywords must be hard-coded in localconfig.js. If they are not, Currently, keywords must be hard-coded in localconfig.js. If
keywords are not automatically recognized. This means, if localconfig.js they are not, keywords are not automatically recognized. This
is left unconfigured, that searching for a bug with the "foo" keyword means, if localconfig.js is left unconfigured, that searching
will only find bugs with "foo" in the summary, status whiteboard, product or for a bug with the "foo" keyword will only find bugs with "foo"
component name, but not those with the keyword "foo". in the summary, status whiteboard, product or component name,
but not those with the keyword "foo".
</para> </para>
<para> <para>
Workarounds for Bugzilla users: Workarounds for Bugzilla users:
<simplelist> <simplelist>
<member>search for '!foo' (this will find only bugs with the keyword "foo"</member> <member>search for '!foo' (this will find only bugs with the
<member>search 'foo,!foo' (equivalent to 'foo OR keyword:foo')</member> keyword "foo"</member>
<member>search 'foo,!foo' (equivalent to 'foo OR
keyword:foo')</member>
</simplelist> </simplelist>
</para> </para>
<para> <para>
When this tool is ported from client-side JavaScript to server-side Perl, When this tool is ported from client-side JavaScript to
the requirement for hard-coding keywords can be fixed. server-side Perl, the requirement for hard-coding keywords can
<ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=70907">This bug</ulink> be fixed. <ulink
has details. url="http://bugzilla.mozilla.org/show_bug.cgi?id=70907">This bug</ulink> has details.
</para> </para>
</section> </section>
</appendix> </appendix>
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
Local variables: Local variables:
mode: sgml mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t sgml-always-quote-attributes:t
sgml-indent-step:2 sgml-auto-insert-required-elements:t
sgml-indent-data:t sgml-balanced-tag-edit:t
sgml-parent-document:nil
sgml-exposed-tags:nil sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil sgml-local-catalogs:nil
sgml-local-ecat-files:nil sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End: End:
--> -->
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> --> <!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<appendix id="downloadlinks"> <appendix id="downloadlinks">
<title>Software Download Links</title> <title>Software Download Links</title>
<para>
<para>All of these sites are current as of April, 2001. Hopefully they'll All of these sites are current as of April, 2001. Hopefully
stay current for a while.</para> they'll stay current for a while.
<para>Apache Web Server:
<ulink url="http://www.apache.org/"/>
Optional web server for Bugzilla, but recommended because of broad user
base and support.</para>
<para>Bugzilla:
<ulink url="http://www.bugzilla.org/"/>
</para> </para>
<para>
<para>MySQL: Apache Web Server: <ulink url="http://www.apache.org/">http://www.apache.org</ulink>
<ulink url="http://www.mysql.com/"/> Optional web server for Bugzilla, but recommended because of broad user base and support.
</para> </para>
<para>
<para>Perl: Bugzilla: <ulink url="http://www.mozilla.org/projects/bugzilla/">
<ulink url="http://www.perl.org/"/> http://www.mozilla.org/projects/bugzilla/</ulink>
</para> </para>
<para>
<para>CPAN: MySQL: <ulink url="http://www.mysql.com/">http://www.mysql.com/</ulink>
<ulink url="http://www.cpan.org/"/>
</para> </para>
<para>
<para>DBI Perl module: Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink>
<ulink url="http://www.cpan.org/modules/by-module/DBI/"/>
</para> </para>
<para>
<para>MySQL related Perl modules: CPAN: <ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink>
<ulink url="http://www.cpan.org/modules/by-module/Mysql/"/>
</para> </para>
<para>
<para>TimeDate Perl module collection: DBI Perl module:
<ulink url="http://www.cpan.org/modules/by-module/Date/"/> <ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/</ulink>
</para> </para>
<para>
<para>GD Perl module: Data::Dumper module:
<ulink url="http://www.cpan.org/modules/by-module/GD/"/> <ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/</ulink>
Alternately, you should be able to find the latest version of GD at
<ulink url="http://www.boutell.com/gd/"/>
</para> </para>
<para>
<para>Chart::Base module: MySQL related Perl modules:
<ulink url="http://www.cpan.org/modules/by-module/Chart/"/> <ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/</ulink>
</para> </para>
<para>
<para>(But remember, Bundle::Bugzilla will install all the modules for you.) TimeDate Perl module collection:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/</ulink>
</para>
<para>
GD Perl module:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/">
ftp://ftp.cpan.org/pub/perl/CPAN/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>
<para>
Chart::Base module:
<ulink url="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/">
ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/</ulink>
</para>
<para>
LinuxDoc Software:
<ulink url="http://www.linuxdoc.org/">http://www.linuxdoc.org/</ulink>
(for documentation maintenance)
</para>
</appendix> </appendix>
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
Local variables: Local variables:
mode: sgml mode: sgml
...@@ -69,9 +79,8 @@ sgml-local-ecat-files:nil ...@@ -69,9 +79,8 @@ sgml-local-ecat-files:nil
sgml-minimize-attributes:nil sgml-minimize-attributes:nil
sgml-namecase-general:t sgml-namecase-general:t
sgml-omittag:t sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.xml" "book" "chapter") sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t sgml-shorttag:t
sgml-tag-region-if-active:t sgml-tag-region-if-active:t
End: End:
--> -->
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> <!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<!-- TOC <!-- TOC
Chapter: Using Bugzilla Chapter: Using Bugzilla
...@@ -38,19 +38,19 @@ Chapter: Using Bugzilla ...@@ -38,19 +38,19 @@ Chapter: Using Bugzilla
<section id="whatis"> <section id="whatis">
<title>What is Bugzilla?</title> <title>What is Bugzilla?</title>
<para> <para>
Bugzilla is one example of a class of programs called "Defect Tracking Systems", Bugzilla is one example of a class of programs called "Defect
or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or Tracking Systems", or, more commonly, "Bug-Tracking Systems". Defect
groups of developers to keep track of outstanding bugs in their product effectively. Tracking Systems allow individual or groups of developers to keep
Bugzilla was originally written by Terry Weissman in a programming language called track of outstanding bugs in their product effectively. Bugzilla was
"TCL", to replace a crappy originally written by Terry Weissman in a programming language called
bug-tracking database used internally for Netscape Communications. Terry later ported "TCL", to replace a crappy bug-tracking database used internally for
Bugzilla to Netscape Communications. Terry later ported Bugzilla to Perl from
Perl from TCL, and in Perl it remains to this day. TCL, and in Perl it remains to this day. Most commercial
Most commercial defect-tracking software vendors at the defect-tracking software vendors at the time charged enormous
time charged enormous licensing fees, and Bugzilla quickly became a favorite of the licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla). It open-source crowd (with its genesis in the open-source browser
is now the de-facto standard defect-tracking system against which all others are project, Mozilla). It is now the de-facto standard defect-tracking
measured. system against which all others are measured.
</para> </para>
<para> <para>
Bugzilla has matured immensely, and now boasts many advanced features. These include: Bugzilla has matured immensely, and now boasts many advanced features. These include:
...@@ -87,13 +87,13 @@ Chapter: Using Bugzilla ...@@ -87,13 +87,13 @@ Chapter: Using Bugzilla
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
email, XML, and HTTP APIs email, XML, console, and HTTP APIs
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
available integration with automated software configuration management systems, including available integration with automated software configuration management systems, including
Perforce and CVS. Perforce and CVS
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
...@@ -137,7 +137,7 @@ Chapter: Using Bugzilla ...@@ -137,7 +137,7 @@ Chapter: Using Bugzilla
with bug-tracking software, and instead simply relied on shared lists and with bug-tracking software, and instead simply relied on shared lists and
email to monitor the status of defects. This procedure is error-prone and email to monitor the status of defects. This procedure is error-prone and
tends to cause those bugs judged least significant by developers to be tends to cause those bugs judged least significant by developers to be
dropped or ignored dropped or ignored.
</para> </para>
<para> <para>
These days, many companies are finding that integrated defect-tracking These days, many companies are finding that integrated defect-tracking
...@@ -223,12 +223,12 @@ Chapter: Using Bugzilla ...@@ -223,12 +223,12 @@ Chapter: Using Bugzilla
<section id="myaccount"> <section id="myaccount">
<title>Create a Bugzilla Account</title> <title>Create a Bugzilla Account</title>
<para> <para>
First thing's first! If you want to use Bugzilla, first you need to create First things first! If you want to use Bugzilla, first you need to create
an account. Consult with the administrator responsible for your installation an account. Consult with the administrator responsible for your installation
of Bugzilla for the URL you should use to access it. of Bugzilla for the URL you should use to access it.
If you're test-driving the end-user Bugzilla experience, use this URL: If you're test-driving the end-user Bugzilla experience, use this URL:
<ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/"> <ulink url="http://landfill.tequilarista.org/bugzilla-tip/">
http://landfill.tequilarista.org/mozilla/bugzilla/</ulink> http://landfill.tequilarista.org/bugzilla-tip/</ulink>
</para> </para>
<orderedlist> <orderedlist>
<listitem> <listitem>
...@@ -560,15 +560,15 @@ Chapter: Using Bugzilla ...@@ -560,15 +560,15 @@ Chapter: Using Bugzilla
<orderedlist> <orderedlist>
<listitem> <listitem>
<para> <para>
Go back to <ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/"> Go back to <ulink url="http://landfill.tequilarista.org/bugzilla-tip/">
http://landfill.tequilarista.org/mozilla/bugzilla/</ulink> http://landfill.tequilarista.org/bugzilla-tip/</ulink>
in your browser. in your browser.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Select the Select the
<ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/enter_bug.cgi"> <ulink url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi">
Enter a new bug report</ulink> link. Enter a new bug report</ulink> link.
</para> </para>
</listitem> </listitem>
...@@ -716,7 +716,7 @@ Chapter: Using Bugzilla ...@@ -716,7 +716,7 @@ Chapter: Using Bugzilla
Let's plunge into what you can do! The first step is to click Let's plunge into what you can do! The first step is to click
the "Edit prefs" link at the footer of each page once you the "Edit prefs" link at the footer of each page once you
have logged in to have logged in to
<ulink url="http://landfill.tequilarista.org/mozilla/bugzilla/query.cgi?GoAheadAndLogIn=1"> <ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1">
Landfill</ulink>. Landfill</ulink>.
</para> </para>
<section id="accountsettings"> <section id="accountsettings">
...@@ -861,17 +861,20 @@ Chapter: Using Bugzilla ...@@ -861,17 +861,20 @@ Chapter: Using Bugzilla
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
Local variables: Local variables:
mode: sgml mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t sgml-always-quote-attributes:t
sgml-indent-step:2 sgml-auto-insert-required-elements:t
sgml-indent-data:t sgml-balanced-tag-edit:t
sgml-parent-document:Bugzilla-Guide\.sgml
sgml-exposed-tags:nil sgml-exposed-tags:nil
sgml-general-insert-case:lower
sgml-indent-data:t
sgml-indent-step:2
sgml-local-catalogs:nil sgml-local-catalogs:nil
sgml-local-ecat-files:nil sgml-local-ecat-files:nil
sgml-minimize-attributes:nil
sgml-namecase-general:t
sgml-omittag:t
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
sgml-shorttag:t
sgml-tag-region-if-active:t
End: 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