Skip to content

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

Updated Bugzilla Guide and README to fix bug 76156, bug 76841, and bug 26242.

The README is now gutted, pointers to Guide. Also some new sections added, old ones fixed, and notes appended to deprecated sections I've not yet had the heart to remove.
parent 064f6ba6
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 2455 additions and 362 deletions
docs/html/about.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>About This Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/aboutthisguide.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Purpose and Scope of this Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/administration.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Administering Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -98,6 +98,30 @@ HREF="useradmin.html#DEFAULTUSER"
HREF="useradmin.html#MANAGEUSERS"
>Managing Other Users</A
></DT
><DD
><DL
><DT
>3.2.2.1. <A
HREF="useradmin.html#LOGIN"
>Logging In</A
></DT
><DT
>3.2.2.2. <A
HREF="useradmin.html#CREATENEWUSERS"
>Creating new users</A
></DT
><DT
>3.2.2.3. <A
HREF="useradmin.html#DISABLEUSERS"
>Disabling Users</A
></DT
><DT
>3.2.2.4. <A
HREF="useradmin.html#MODIFYUSERS"
>Modifying Users</A
></DT
></DL
></DD
></DL
></DD
><DT
......@@ -152,7 +176,7 @@ COLOR="RED"
><P
>So you followed the README isntructions to the letter, and
just logged into bugzilla with your super-duper god account and you are sitting at the query
screen. Yet, you have nothing to query. Your first act of bisuness needs to be to setup the
screen. Yet, you have nothing to query. Your first act of business needs to be to setup the
operating parameters for bugzilla.</P
></DIV
><DIV
......
docs/html/bonsai.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Bonsai</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/bugprobs.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Bug Issues</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/bz30.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Bugzilla 3.0</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/cleanupwork.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Cleaning up after mucking with Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -16,8 +16,8 @@ REL="PREVIOUS"
TITLE="MySQL Permissions & Grant Tables"
HREF="granttables.html"><LINK
REL="NEXT"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD
TITLE="Bugzilla Variants"
HREF="variants.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
......@@ -51,13 +51,13 @@ HREF="granttables.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix B. The Bugzilla Database</TD
>Appendix C. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="patches.html"
HREF="variants.html"
>Next</A
></TD
></TR
......@@ -71,11 +71,11 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="CLEANUPWORK"
>B.4. Cleaning up after mucking with Bugzilla</A
>C.4. Cleaning up after mucking with Bugzilla</A
></H1
><P
CLASS="LITERALLAYOUT"
>Contributed&nbsp;by&nbsp;Eric&nbsp;Hansen:<br>
>Contributed&nbsp;by&nbsp;Eric&nbsp;Hanson:<br>
There&nbsp;are&nbsp;several&nbsp;things,&nbsp;and&nbsp;one&nbsp;trick.&nbsp;&nbsp;There&nbsp;is&nbsp;a&nbsp;small&nbsp;tiny&nbsp;piece&nbsp;of<br>
documentation&nbsp;I&nbsp;saw&nbsp;once&nbsp;that&nbsp;said&nbsp;something&nbsp;very&nbsp;important.<br>
1)&nbsp;&nbsp;After&nbsp;pretty&nbsp;much&nbsp;any&nbsp;manual&nbsp;working&nbsp;of&nbsp;the&nbsp;Mysql&nbsp;db,&nbsp;you&nbsp;must<br>
......@@ -124,7 +124,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="patches.html"
HREF="variants.html"
>Next</A
></TD
></TR
......@@ -146,7 +146,7 @@ HREF="database.html"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Useful Patches and Utilities for Bugzilla</TD
>Bugzilla Variants</TD
></TR
></TABLE
></DIV
......
docs/html/cmdline.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Command-line Bugzilla Queries</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -13,7 +13,7 @@ REL="UP"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"><LINK
REL="PREVIOUS"
TITLE="The setperl.pl Utility"
TITLE="The setperl.csh Utility"
HREF="setperl.html"><LINK
REL="NEXT"
TITLE="The Quicksearch Utility"
......@@ -51,7 +51,7 @@ HREF="setperl.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix C. Useful Patches and Utilities for Bugzilla</TD
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="CMDLINE"
>C.2. Command-line Bugzilla Queries</A
>D.2. Command-line Bugzilla Queries</A
></H1
><P
> Users can query Bugzilla from the command line using
......@@ -240,7 +240,7 @@ HREF="quicksearch.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The setperl.pl Utility</TD
>The setperl.csh Utility</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/contributors.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Contributors</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -74,10 +74,15 @@ NAME="CONTRIBUTORS"
>1.6. Contributors</A
></H1
><P
> Thanks go to these people for significant contributions to this documentation:
> Thanks go to these people for significant contributions
to this documentation (in no particular order):
</P
><P
> Zach Lipton, Andrew Pearson, Spencer Smith, Eric Hansen
> Zach Lipton (significant textual contributions),
Andrew Pearson,
Spencer Smith,
Eric Hanson,
Kevin Brannen,
</P
></DIV
><DIV
......
docs/html/conventions.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Document Conventions</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -79,7 +79,7 @@ NAME="CONVENTIONS"
><DIV
CLASS="INFORMALTABLE"
><A
NAME="AEN111"
NAME="AEN117"
></A
><P
></P
......
docs/html/copyright.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Copyright Information</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -74,7 +74,7 @@ NAME="COPYRIGHT"
>1.2. Copyright Information</A
></H1
><A
NAME="AEN51"
NAME="AEN57"
></A
><TABLE
BORDER="0"
......
docs/html/credits.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Credits</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/cvs.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>CVS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/database.html
View file @ 2d4d7c92
......@@ -4,14 +4,14 @@
>The Bugzilla Database</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Bugzilla FAQ"
HREF="faq.html"><LINK
TITLE="Software Download Links"
HREF="downloadlinks.html"><LINK
REL="NEXT"
TITLE="Database Schema Chart"
HREF="dbschema.html"></HEAD
......@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="faq.html"
HREF="downloadlinks.html"
>Prev</A
></TD
><TD
......@@ -67,7 +67,7 @@ CLASS="APPENDIX"
><H1
><A
NAME="DATABASE"
>Appendix B. The Bugzilla Database</A
>Appendix C. The Bugzilla Database</A
></H1
><DIV
CLASS="TOC"
......@@ -77,22 +77,22 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>B.1. <A
>C.1. <A
HREF="dbschema.html"
>Database Schema Chart</A
></DT
><DT
>B.2. <A
>C.2. <A
HREF="dbdoc.html"
>MySQL Bugzilla Database Introduction</A
></DT
><DT
>B.3. <A
>C.3. <A
HREF="granttables.html"
>MySQL Permissions &#38; Grant Tables</A
></DT
><DT
>B.4. <A
>C.4. <A
HREF="cleanupwork.html"
>Cleaning up after mucking with Bugzilla</A
></DT
......@@ -105,7 +105,7 @@ CLASS="NOTE"
><P
><B
>Note: </B
>This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers? </P
>This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?</P
></BLOCKQUOTE
></DIV
></DIV
......@@ -124,7 +124,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="faq.html"
HREF="downloadlinks.html"
>Prev</A
></TD
><TD
......@@ -149,7 +149,7 @@ HREF="dbschema.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The Bugzilla FAQ</TD
>Software Download Links</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/dbaseintegrity.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Database Integrity</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/dbdoc.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>MySQL Bugzilla Database Introduction</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="dbschema.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix B. The Bugzilla Database</TD
>Appendix C. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="DBDOC"
>B.2. MySQL Bugzilla Database Introduction</A
>C.2. MySQL Bugzilla Database Introduction</A
></H1
><P
CLASS="LITERALLAYOUT"
......
docs/html/dbschema.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Database Schema Chart</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="database.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix B. The Bugzilla Database</TD
>Appendix C. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="DBSCHEMA"
>B.1. Database Schema Chart</A
>C.1. Database Schema Chart</A
></H1
><P
> <DIV
......
docs/html/disclaimer.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Disclaimer</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/downloadlinks.html 0 → 100644
View file @ 2d4d7c92
<HTML
><HEAD
><TITLE
>Software Download Links</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Bugzilla FAQ"
HREF="faq.html"><LINK
REL="NEXT"
TITLE="The Bugzilla Database"
HREF="database.html"></HEAD
><BODY
CLASS="APPENDIX"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="faq.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="database.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="APPENDIX"
><H1
><A
NAME="DOWNLOADLINKS"
>Appendix B. Software Download Links</A
></H1
><P
> All of these sites are current as of April, 2001. Hopefully
they'll stay current for a while.
</P
><P
> Apache Web Server: <A
HREF="http://www.apache.org/"
TARGET="_top"
>http://www.apache.org</A
>
Optional web server for Bugzilla, but recommended because of broad user base and support.
</P
><P
> Bugzilla: <A
HREF="http://www.mozilla.org/projects/bugzilla/"
TARGET="_top"
> http://www.mozilla.org/projects/bugzilla/</A
>
</P
><P
> MySQL: <A
HREF="http://www.mysql.org/"
TARGET="_top"
>http://www.mysql.org/</A
>
</P
><P
> Perl: <A
HREF="http://www.perl.org"
TARGET="_top"
>http://www.perl.org/</A
>
</P
><P
> CPAN: <A
HREF="http://www.cpan.org/"
TARGET="_top"
>http://www.cpan.org/</A
>
</P
><P
> DBI Perl module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/DBI/</A
>
</P
><P
> Data::Dumper module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Data/</A
>
</P
><P
> MySQL related Perl modules:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Mysql/</A
>
</P
><P
> TimeDate Perl module collection:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Date/</A
>
</P
><P
> GD Perl module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/GD/</A
>
Alternately, you should be able to find the latest version of
GD at <A
HREF="http://www.boutell.com/gd/"
TARGET="_top"
>http://www.boutell.com/gd/</A
>
</P
><P
> Chart::Base module:
<A
HREF="ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/"
TARGET="_top"
> ftp://ftp.cpan.org/pub/perl/CPAN/modules/by-module/Chart/</A
>
</P
><P
> LinuxDoc Software:
<A
HREF="http://www.linuxdoc.org/"
TARGET="_top"
>http://www.linuxdoc.org/</A
>
(for documentation maintenance)
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="faq.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="database.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>The Bugzilla FAQ</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Bugzilla Database</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/feedback.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Feedback</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/future.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>The Future of Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -116,7 +116,7 @@ WIDTH="100%"
><TD
><PRE
CLASS="SYNOPSIS"
>This section largely contributed by Matthew Tuck</PRE
>Bugzilla's Future. Much of this is the present, now.</PRE
></TD
></TR
></TABLE
......
docs/html/gfdl.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>GNU Free Documentation License</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -67,7 +67,7 @@ CLASS="APPENDIX"
><H1
><A
NAME="GFDL"
>Appendix D. GNU Free Documentation License</A
>Appendix E. GNU Free Documentation License</A
></H1
><DIV
CLASS="TOC"
......@@ -141,7 +141,7 @@ HREF="gfdl_howto.html"
><P
>Version 1.1, March 2000</P
><A
NAME="AEN1609"
NAME="AEN2019"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......
docs/html/gfdl_0.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>PREAMBLE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_1.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>APPLICABILITY AND DEFINITIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_0.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_10.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>FUTURE REVISIONS OF THIS LICENSE</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_9.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_2.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>VERBATIM COPYING</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_1.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_3.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>COPYING IN QUANTITY</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_2.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_4.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>MODIFICATIONS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_3.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_5.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>COMBINING DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_4.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_6.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>COLLECTIONS OF DOCUMENTS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_5.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_7.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>AGGREGATION WITH INDEPENDENT WORKS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_6.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_8.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>TRANSLATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_7.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_9.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>TERMINATION</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_8.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......
docs/html/gfdl_howto.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>How to use this License for your documents</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="gfdl_10.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix D. GNU Free Documentation License</TD
>Appendix E. GNU Free Documentation License</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -78,7 +78,7 @@ NAME="GFDL_HOWTO"
a copy of the License in the document and put the following
copyright and license notices just after the title page:</P
><A
NAME="AEN1699"
NAME="AEN2109"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......
docs/html/glossary.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Glossary</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -163,7 +163,7 @@ NAME="GLOSS_P"
><DIV
CLASS="EXAMPLE"
><A
NAME="AEN1735"
NAME="AEN2145"
></A
><P
><B
......
docs/html/granttables.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>MySQL Permissions &#38; Grant Tables</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="dbdoc.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix B. The Bugzilla Database</TD
>Appendix C. The Bugzilla Database</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="GRANTTABLES"
>B.3. MySQL Permissions &#38; Grant Tables</A
>C.3. MySQL Permissions &#38; Grant Tables</A
></H1
><DIV
CLASS="NOTE"
......@@ -80,7 +80,13 @@ CLASS="NOTE"
><P
><B
>Note: </B
>The following portion of documentation comes from my answer to an old discussion of Keynote, a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the Keynote support group regarding MySQL grant table permissions, and how to use them effectively. It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables since this time, but it serves as a decent introduction and troubleshooting document for grant table issues. I used Keynote to track my troubles until I discovered Bugzilla, which gave me a whole new set of troubles to work on : )</P
>The following portion of documentation comes from my answer to an old discussion of Keystone,
a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the
Keystone support group regarding MySQL grant table permissions, and how to use them effectively.
It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables
since this time, but it serves as a decent introduction and troubleshooting document for grant
table issues. I used Keynote to track my troubles until I discovered Bugzilla,
which gave me a whole new set of troubles to work on : )</P
></BLOCKQUOTE
></DIV
><P
......
docs/html/how.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>How do I use Bugzilla?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -97,7 +97,7 @@ VALIGN="TOP"
></TR
></TABLE
><P
> Bugzilla is a large and complex system. Describing how to use it
> Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or administering
a Bugzilla installation, please consult the Installing and Administering
Bugzilla portions of this Guide. This section is principally aimed towards
......@@ -112,11 +112,37 @@ HREF="http://landfill.tequilarista.org/"
TARGET="_top"
> landfill.tequilarista.org</A
>.
<DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> Some people have run into difficulties completing this tutorial. If
you run into problems, please check the updated, online documentation available
at <A
HREF="http://www.trilobyte.net/barnsons/"
TARGET="_top"
>http://www.trilobyte.net/barnsons</A
>.
If you're still stumped, please subscribe to the newsgroup and provide details of exactly
what's stumping you! If enough people complain, I'll have to fix it in the next
version of this Guide. You can subscribe to the newsgroup at
<A
HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
TARGET="_top"
> news://news.mozilla.org/netscape.public.mozilla.webtools</A
>
</P
></BLOCKQUOTE
></DIV
>
Although Landfill serves as a great introduction to Bugzilla, it does not offer
all the options you would have as a user on your own installation of Bugzilla,
nor can it do more than serve as a general introduction to Bugzilla.
However, please use it if you want to
follow this tutorial.
nor can it do more than serve as a general introduction to Bugzilla. Additionally,
Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
may work slightly differently than mentioned here.
</P
><DIV
CLASS="SECTION"
......@@ -318,7 +344,7 @@ TYPE="1"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN745"
NAME="AEN1095"
></A
><P
><B
......@@ -327,7 +353,7 @@ NAME="AEN745"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN747"
NAME="AEN1097"
></A
><P
></P
......@@ -379,7 +405,7 @@ NAME="AEN747"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN755"
NAME="AEN1105"
></A
><P
><B
......@@ -388,7 +414,7 @@ NAME="AEN755"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN757"
NAME="AEN1107"
></A
><P
></P
......
docs/html/index.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>The Bugzilla Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="NEXT"
TITLE="About This Guide"
......@@ -63,6 +63,84 @@ CLASS="ADDRESS"
></DIV
></DIV
><DIV
CLASS="REVHISTORY"
><TABLE
WIDTH="100%"
BORDER="0"
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
COLSPAN="3"
><B
>Revision History</B
></TH
></TR
><TR
><TD
ALIGN="LEFT"
>Revision v2.11</TD
><TD
ALIGN="LEFT"
>20 December 2000</TD
><TD
ALIGN="LEFT"
>Revised by: MPB</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Converted the README, FAQ, and DATABASE information into SGML
docbook format.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 2.11.1</TD
><TD
ALIGN="LEFT"
>06 March 2001</TD
><TD
ALIGN="LEFT"
>Revised by: MPB</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Took way too long to revise this for 2.12 release.
Updated FAQ to use qandaset tags instead of literallayout,
cleaned up administration section, added User Guide section,
miscellaneous FAQ updates and third-party integration information.
From this point on all new tags are lowercase in preparation for the
2.13 release of the Guide in XML format instead of SGML.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 2.12.0</TD
><TD
ALIGN="LEFT"
>24 April 2001</TD
><TD
ALIGN="LEFT"
>Revised by: MPB</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
moving bugs from one keyword to another, clarified possible problems with the Landfill
tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
README into the UNIX installation section, and changed the README to indicate the deprecated
status. Things I know need work: Used "simplelist" a lot, where I should have used
"procedure" to tag things. Need to lowercase all tags to be XML compliant.</TD
></TR
></TABLE
></DIV
><DIV
><DIV
CLASS="ABSTRACT"
><A
......@@ -150,11 +228,143 @@ HREF="installation.html"
HREF="readme.unix.html"
>UNIX Installation</A
></DT
><DD
><DL
><DT
>2.1.1. <A
HREF="readme.unix.html#AEN190"
>ERRATA</A
></DT
><DT
>2.1.2. <A
HREF="readme.unix.html#AEN204"
>Step-by-step Install</A
></DT
><DD
><DL
><DT
>2.1.2.1. <A
HREF="readme.unix.html#AEN206"
>Introduction</A
></DT
><DT
>2.1.2.2. <A
HREF="readme.unix.html#AEN211"
>Installing the Prerequisites</A
></DT
><DT
>2.1.2.3. <A
HREF="readme.unix.html#AEN242"
>Installing MySQL Database</A
></DT
><DT
>2.1.2.4. <A
HREF="readme.unix.html#AEN248"
>Perl (5.004 or greater)</A
></DT
><DT
>2.1.2.5. <A
HREF="readme.unix.html#AEN259"
>DBI Perl Module</A
></DT
><DT
>2.1.2.6. <A
HREF="readme.unix.html#AEN296"
>Data::Dumper Perl Module</A
></DT
><DT
>2.1.2.7. <A
HREF="readme.unix.html#AEN300"
>MySQL related Perl Module Collection</A
></DT
><DT
>2.1.2.8. <A
HREF="readme.unix.html#AEN309"
>TimeDate Perl Module Collection</A
></DT
><DT
>2.1.2.9. <A
HREF="readme.unix.html#AEN312"
>GD Perl Module (1.8.3)</A
></DT
><DT
>2.1.2.10. <A
HREF="readme.unix.html#AEN318"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
>2.1.2.11. <A
HREF="readme.unix.html#AEN321"
>DB_File Perl Module</A
></DT
><DT
>2.1.2.12. <A
HREF="readme.unix.html#AEN324"
>HTTP Server</A
></DT
><DT
>2.1.2.13. <A
HREF="readme.unix.html#AEN334"
>Installing the Bugzilla Files</A
></DT
><DT
>2.1.2.14. <A
HREF="readme.unix.html#AEN343"
>Setting Up the MySQL Database</A
></DT
><DT
>2.1.2.15. <A
HREF="readme.unix.html#AEN379"
>Tweaking "localconfig"</A
></DT
><DT
>2.1.2.16. <A
HREF="readme.unix.html#AEN401"
>Setting Up Maintainers Manuall (Optional)</A
></DT
><DT
>2.1.2.17. <A
HREF="readme.unix.html#AEN410"
>The Whining Cron (Optional)</A
></DT
><DT
>2.1.2.18. <A
HREF="readme.unix.html#AEN417"
>Bug Graphs (Optional)</A
></DT
><DT
>2.1.2.19. <A
HREF="readme.unix.html#AEN429"
>Securing MySQL</A
></DT
><DT
>2.1.2.20. <A
HREF="readme.unix.html#AEN495"
>Installation General Notes</A
></DT
></DL
></DD
></DL
></DD
><DT
>2.2. <A
HREF="readme.windows.html"
>Win32 (Win98+/NT/2K) Installation</A
></DT
><DD
><DL
><DT
>2.2.1. <A
HREF="readme.windows.html#NTVERIFIED"
>Win32 Installation: Step-by-step</A
></DT
><DT
>2.2.2. <A
HREF="readme.windows.html#ADDLWINTIPS"
>Additional Windows Tips</A
></DT
></DL
></DD
></DL
></DD
><DT
......@@ -174,11 +384,83 @@ HREF="postinstall-check.html"
HREF="useradmin.html"
>User Administration</A
></DT
><DD
><DL
><DT
>3.2.1. <A
HREF="useradmin.html#DEFAULTUSER"
>Creating the Default User</A
></DT
><DT
>3.2.2. <A
HREF="useradmin.html#MANAGEUSERS"
>Managing Other Users</A
></DT
><DD
><DL
><DT
>3.2.2.1. <A
HREF="useradmin.html#LOGIN"
>Logging In</A
></DT
><DT
>3.2.2.2. <A
HREF="useradmin.html#CREATENEWUSERS"
>Creating new users</A
></DT
><DT
>3.2.2.3. <A
HREF="useradmin.html#DISABLEUSERS"
>Disabling Users</A
></DT
><DT
>3.2.2.4. <A
HREF="useradmin.html#MODIFYUSERS"
>Modifying Users</A
></DT
></DL
></DD
></DL
></DD
><DT
>3.3. <A
HREF="programadmin.html"
>Product, Component, Milestone, and Version Administration</A
></DT
><DD
><DL
><DT
>3.3.1. <A
HREF="programadmin.html#PRODUCTS"
>Products</A
></DT
><DT
>3.3.2. <A
HREF="programadmin.html#COMPONENTS"
>Components</A
></DT
><DT
>3.3.3. <A
HREF="programadmin.html#VERSIONS"
>Versions</A
></DT
><DT
>3.3.4. <A
HREF="programadmin.html#MILESTONES"
>Milestones</A
></DT
><DT
>3.3.5. <A
HREF="programadmin.html#VOTING"
>Voting</A
></DT
><DT
>3.3.6. <A
HREF="programadmin.html#GROUPS"
>Groups and Group Security</A
></DT
></DL
></DD
><DT
>3.4. <A
HREF="security.html"
......@@ -208,11 +490,87 @@ HREF="why.html"
HREF="how.html"
>How do I use Bugzilla?</A
></DT
><DD
><DL
><DT
>4.3.1. <A
HREF="how.html#MYACCOUNT"
>Create a Bugzilla Account</A
></DT
><DT
>4.3.2. <A
HREF="how.html#QUERY"
>The Bugzilla Query Page</A
></DT
><DT
>4.3.3. <A
HREF="how.html#BUGREPORTS"
>Creating and Managing Bug Reports</A
></DT
><DD
><DL
><DT
>4.3.3.1. <A
HREF="how.html#BUG_WRITING"
>Writing a Great Bug Report</A
></DT
><DT
>4.3.3.2. <A
HREF="how.html#BUG_MANAGE"
>Managing your Bug Reports</A
></DT
></DL
></DD
></DL
></DD
><DT
>4.4. <A
HREF="init4me.html"
>What's in it for me?</A
></DT
><DD
><DL
><DT
>4.4.1. <A
HREF="init4me.html#ACCOUNTSETTINGS"
>Account Settings</A
></DT
><DT
>4.4.2. <A
HREF="init4me.html#EMAILSETTINGS"
>Email Settings</A
></DT
><DD
><DL
><DT
>4.4.2.1. <A
HREF="init4me.html#NOTIFICATION"
>Email Notification</A
></DT
><DT
>4.4.2.2. <A
HREF="init4me.html#NEWEMAILTECH"
>New Email Technology</A
></DT
><DT
>4.4.2.3. <A
HREF="init4me.html#WATCHSETTINGS"
>"Watching" Users</A
></DT
></DL
></DD
><DT
>4.4.3. <A
HREF="init4me.html#FOOTERSETTINGS"
>Page Footer</A
></DT
><DT
>4.4.4. <A
HREF="init4me.html#PERMISSIONSETTINGS"
>Permissions</A
></DT
></DL
></DD
><DT
>4.5. <A
HREF="usingbz-conc.html"
......@@ -295,59 +653,78 @@ HREF="faq.html"
></DT
><DT
>B. <A
HREF="downloadlinks.html"
>Software Download Links</A
></DT
><DT
>C. <A
HREF="database.html"
>The Bugzilla Database</A
></DT
><DD
><DL
><DT
>B.1. <A
>C.1. <A
HREF="dbschema.html"
>Database Schema Chart</A
></DT
><DT
>B.2. <A
>C.2. <A
HREF="dbdoc.html"
>MySQL Bugzilla Database Introduction</A
></DT
><DT
>B.3. <A
>C.3. <A
HREF="granttables.html"
>MySQL Permissions &#38; Grant Tables</A
></DT
><DT
>B.4. <A
>C.4. <A
HREF="cleanupwork.html"
>Cleaning up after mucking with Bugzilla</A
></DT
></DL
></DD
><DT
>C. <A
>7. <A
HREF="variants.html"
>Bugzilla Variants</A
></DT
><DD
><DL
><DT
>7.1. <A
HREF="rhbugzilla.html"
>Red Hat Bugzilla</A
></DT
></DL
></DD
><DT
>D. <A
HREF="patches.html"
>Useful Patches and Utilities for Bugzilla</A
></DT
><DD
><DL
><DT
>C.1. <A
>D.1. <A
HREF="setperl.html"
>The setperl.pl Utility</A
>The setperl.csh Utility</A
></DT
><DT
>C.2. <A
>D.2. <A
HREF="cmdline.html"
>Command-line Bugzilla Queries</A
></DT
><DT
>C.3. <A
>D.3. <A
HREF="quicksearch.html"
>The Quicksearch Utility</A
></DT
></DL
></DD
><DT
>D. <A
>E. <A
HREF="gfdl.html"
>GNU Free Documentation License</A
></DT
......@@ -431,53 +808,65 @@ CLASS="LOT"
>List of Examples</B
></DT
><DT
>2-1. <A
HREF="readme.windows.html#AEN646"
>Removing encrypt() for Windows NT installations</A
></DT
><DT
>3-1. <A
HREF="programadmin.html#AEN491"
HREF="programadmin.html#AEN838"
>Creating some Components</A
></DT
><DT
>3-2. <A
HREF="programadmin.html#AEN520"
HREF="programadmin.html#AEN867"
>Common Use of Versions</A
></DT
><DT
>3-3. <A
HREF="programadmin.html#AEN524"
HREF="programadmin.html#AEN871"
>A Different Use of Versions</A
></DT
><DT
>3-4. <A
HREF="programadmin.html#AEN552"
HREF="programadmin.html#AEN899"
>Using SortKey with Target Milestone</A
></DT
><DT
>3-5. <A
HREF="programadmin.html#AEN590"
HREF="programadmin.html#AEN937"
>When to Use Group Security</A
></DT
><DT
>3-6. <A
HREF="programadmin.html#AEN607"
HREF="programadmin.html#AEN954"
>Creating a New Group</A
></DT
><DT
>4-1. <A
HREF="how.html#AEN745"
HREF="how.html#AEN1095"
>Some Famous Software Versions</A
></DT
><DT
>4-2. <A
HREF="how.html#AEN755"
HREF="how.html#AEN1105"
>Mozilla Webtools Components</A
></DT
><DT
>D-1. <A
HREF="setperl.html#AEN1963"
>Using Setperl to set your perl path</A
></DT
><DT
>1. <A
HREF="glossary.html#AEN1735"
HREF="glossary.html#AEN2145"
>A Sample Product</A
></DT
></DL
></DIV
></DIV
>] &#62;
</DIV
><DIV
CLASS="NAVFOOTER"
><HR
......
docs/html/init4me.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>What's in it for me?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -150,6 +150,20 @@ CLASS="SECTION"
NAME="NOTIFICATION"
>4.4.2.1. Email Notification</A
></H3
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> The email notification settings described below have been obsoleted in Bugzilla 2.12, and
this section will be replaced with a comprehensive description of the amazing array of
new options at your disposal. However, in the meantime, throw this chunk out the window
and go crazy with goofing around with different notification options.
</P
></BLOCKQUOTE
></DIV
><P
> Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
In the drop-down "Notify me of changes to", select one of
......
docs/html/installation.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Installing Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -81,6 +81,143 @@ CLASS="TOC"
HREF="readme.unix.html"
>UNIX Installation</A
></DT
><DD
><DL
><DT
>2.1.1. <A
HREF="readme.unix.html#AEN190"
>ERRATA</A
></DT
><DT
>2.1.2. <A
HREF="readme.unix.html#AEN204"
>Step-by-step Install</A
></DT
><DD
><DL
><DT
>2.1.2.1. <A
HREF="readme.unix.html#AEN206"
>Introduction</A
></DT
><DT
>2.1.2.2. <A
HREF="readme.unix.html#AEN211"
>Installing the Prerequisites</A
></DT
><DT
>2.1.2.3. <A
HREF="readme.unix.html#AEN242"
>Installing MySQL Database</A
></DT
><DT
>2.1.2.4. <A
HREF="readme.unix.html#AEN248"
>Perl (5.004 or greater)</A
></DT
><DT
>2.1.2.5. <A
HREF="readme.unix.html#AEN259"
>DBI Perl Module</A
></DT
><DT
>2.1.2.6. <A
HREF="readme.unix.html#AEN296"
>Data::Dumper Perl Module</A
></DT
><DT
>2.1.2.7. <A
HREF="readme.unix.html#AEN300"
>MySQL related Perl Module Collection</A
></DT
><DT
>2.1.2.8. <A
HREF="readme.unix.html#AEN309"
>TimeDate Perl Module Collection</A
></DT
><DT
>2.1.2.9. <A
HREF="readme.unix.html#AEN312"
>GD Perl Module (1.8.3)</A
></DT
><DT
>2.1.2.10. <A
HREF="readme.unix.html#AEN318"
>Chart::Base Perl Module (0.99c)</A
></DT
><DT
>2.1.2.11. <A
HREF="readme.unix.html#AEN321"
>DB_File Perl Module</A
></DT
><DT
>2.1.2.12. <A
HREF="readme.unix.html#AEN324"
>HTTP Server</A
></DT
><DT
>2.1.2.13. <A
HREF="readme.unix.html#AEN334"
>Installing the Bugzilla Files</A
></DT
><DT
>2.1.2.14. <A
HREF="readme.unix.html#AEN343"
>Setting Up the MySQL Database</A
></DT
><DT
>2.1.2.15. <A
HREF="readme.unix.html#AEN379"
>Tweaking "localconfig"</A
></DT
><DT
>2.1.2.16. <A
HREF="readme.unix.html#AEN401"
>Setting Up Maintainers Manuall (Optional)</A
></DT
><DT
>2.1.2.17. <A
HREF="readme.unix.html#AEN410"
>The Whining Cron (Optional)</A
></DT
><DT
>2.1.2.18. <A
HREF="readme.unix.html#AEN417"
>Bug Graphs (Optional)</A
></DT
><DT
>2.1.2.19. <A
HREF="readme.unix.html#AEN429"
>Securing MySQL</A
></DT
><DT
>2.1.2.20. <A
HREF="readme.unix.html#AEN495"
>Installation General Notes</A
></DT
><DD
><DL
><DT
>2.1.2.20.1. <A
HREF="readme.unix.html#AEN497"
>Modifying Your Running System</A
></DT
><DT
>2.1.2.20.2. <A
HREF="readme.unix.html#AEN502"
>Upgrading From Previous Versions</A
></DT
><DT
>2.1.2.20.3. <A
HREF="readme.unix.html#AEN505"
>UNIX Installation Instructions History</A
></DT
></DL
></DD
></DL
></DD
></DL
></DD
><DT
>2.2. <A
HREF="readme.windows.html"
......
docs/html/integration.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Integrating Bugzilla with Third-Party Tools</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/newversions.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>New Versions</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/patches.html
View file @ 2d4d7c92
......@@ -4,16 +4,16 @@
>Useful Patches and Utilities for Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Cleaning up after mucking with Bugzilla"
HREF="cleanupwork.html"><LINK
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"><LINK
REL="NEXT"
TITLE="The setperl.pl Utility"
TITLE="The setperl.csh Utility"
HREF="setperl.html"></HEAD
><BODY
CLASS="APPENDIX"
......@@ -41,7 +41,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="cleanupwork.html"
HREF="rhbugzilla.html"
>Prev</A
></TD
><TD
......@@ -67,7 +67,7 @@ CLASS="APPENDIX"
><H1
><A
NAME="PATCHES"
>Appendix C. Useful Patches and Utilities for Bugzilla</A
>Appendix D. Useful Patches and Utilities for Bugzilla</A
></H1
><DIV
CLASS="TOC"
......@@ -77,17 +77,17 @@ CLASS="TOC"
>Table of Contents</B
></DT
><DT
>C.1. <A
>D.1. <A
HREF="setperl.html"
>The setperl.pl Utility</A
>The setperl.csh Utility</A
></DT
><DT
>C.2. <A
>D.2. <A
HREF="cmdline.html"
>Command-line Bugzilla Queries</A
></DT
><DT
>C.3. <A
>D.3. <A
HREF="quicksearch.html"
>The Quicksearch Utility</A
></DT
......@@ -109,7 +109,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cleanupwork.html"
HREF="rhbugzilla.html"
>Prev</A
></TD
><TD
......@@ -134,7 +134,7 @@ HREF="setperl.html"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Cleaning up after mucking with Bugzilla</TD
>Red Hat Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
......@@ -144,7 +144,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The setperl.pl Utility</TD
>The setperl.csh Utility</TD
></TR
></TABLE
></DIV
......
docs/html/postinstall-check.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Post-Installation Checklist</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -86,6 +86,17 @@ CLASS="PROCEDURE"
TYPE="1"
><LI
><P
> Bring up "editparams.cgi" in your web browser. For instance, to edit parameters
at mozilla.org, the URL would be <A
HREF="http://bugzilla.mozilla.org/editparams.cgi"
TARGET="_top"
> http://bugzilla.mozilla.org/editparams.cgi</A
>, also available under the "edit parameters"
link on your query page.
</P
></LI
><LI
><P
> Set "maintainer" to <EM
>your</EM
> email address.
......@@ -115,7 +126,7 @@ TYPE="1"
></LI
><LI
><P
> Set "usebuggroupsentry" to "1" if you want to be able to restrict access to products.
> Set "usebuggroupsentry" to "1" if you want to restrict access to products.
Once again, if you are simply testing your installation, I suggest against
turning this parameter on; the strict security checking may stop you from
being able to modify your new entries.
......@@ -152,14 +163,16 @@ CLASS="NOTE"
attempting to commit a change to the database.
</P
><P
> If you use the "shadowdb" option, it is only natural that you should turn the "queryagainstshadowdb"
> If you use the "shadowdb" option,
it is only natural that you should turn the "queryagainstshadowdb"
option "On" as well. Otherwise you are replicating data into a shadow database for no reason!
</P
></LI
><LI
><P
> If you have custom logos or HTML you must put in place to fit within your site design guidelines,
place the code in the "headerhtml", "footerhtml", "errorhtml", "bannerhtml", or "blurbhtml" text boxes.
place the code in the "headerhtml", "footerhtml", "errorhtml",
"bannerhtml", or "blurbhtml" text boxes.
<DIV
CLASS="NOTE"
><BLOCKQUOTE
......@@ -167,10 +180,12 @@ CLASS="NOTE"
><P
><B
>Note: </B
> The "headerhtml" text box is the HTML printed out <EM
> The "headerhtml" text box is the HTML printed out
<EM
>before</EM
> any other code on the page.
If you have a special banner, put the code for it in "bannerhtml". You may want to leave these
If you have a special banner, put the code for it in "bannerhtml".
You may want to leave these
settings at the defaults initially.
</P
></BLOCKQUOTE
......@@ -187,27 +202,33 @@ CLASS="NOTE"
></LI
><LI
><P
> Set "newemailtech" to "on". Your users will thank you. This is the default in the post-2.12 world.
> Ensure "newemailtech" is "on".
Your users will thank you. This is the default in the post-2.12 world, and is
only an issue if you are upgrading.
</P
></LI
><LI
><P
> Do you want to use the qa contact ("useqacontact") and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility, particularly when you have an existing
> Do you want to use the qa contact ("useqacontact")
and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility,
particularly when you have an existing
Quality Assurance and/or Release Engineering team,
but they may not be needed for smaller installations.
</P
></LI
><LI
><P
> Set "whinedays" to the amount of days you want to let bugs go in the "New" or "Reopened" state before
> Set "whinedays" to the amount of days you want to let bugs go
in the "New" or "Reopened" state before
notifying people they have untouched new bugs. If you do not plan to use this feature, simply do
not set up the whining cron job described in the README, or set this value to "0".
</P
></LI
><LI
><P
> Set the "commenton" options according to your site policy. It is a wise idea to require comments when users
> Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users
resolve, reassign, or reopen bugs.
<DIV
CLASS="NOTE"
......
docs/html/programadmin.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Product, Component, Milestone, and Version Administration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -194,7 +194,7 @@ NAME="COMPONENTS"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN491"
NAME="AEN838"
></A
><P
><B
......@@ -203,7 +203,7 @@ NAME="AEN491"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN493"
NAME="AEN840"
></A
><P
></P
......@@ -324,7 +324,7 @@ NAME="VERSIONS"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN520"
NAME="AEN867"
></A
><P
><B
......@@ -333,7 +333,7 @@ NAME="AEN520"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN522"
NAME="AEN869"
></A
><P
></P
......@@ -354,7 +354,7 @@ NAME="AEN522"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN524"
NAME="AEN871"
></A
><P
><B
......@@ -363,7 +363,7 @@ NAME="AEN524"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN526"
NAME="AEN873"
></A
><P
></P
......@@ -472,7 +472,7 @@ TYPE="1"
><DIV
CLASS="EXAMPLE"
><A
NAME="AEN552"
NAME="AEN899"
></A
><P
><B
......@@ -481,7 +481,7 @@ NAME="AEN552"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN554"
NAME="AEN901"
></A
><P
></P
......@@ -645,7 +645,7 @@ NAME="GROUPS"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN590"
NAME="AEN937"
></A
><P
><B
......@@ -654,7 +654,7 @@ NAME="AEN590"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN592"
NAME="AEN939"
></A
><P
></P
......@@ -747,7 +747,7 @@ TYPE="1"
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN607"
NAME="AEN954"
></A
><P
><B
......@@ -756,7 +756,7 @@ NAME="AEN607"
><DIV
CLASS="INFORMALEXAMPLE"
><A
NAME="AEN609"
NAME="AEN956"
></A
><P
></P
......
docs/html/quicksearch.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>The Quicksearch Utility</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="cmdline.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix C. Useful Patches and Utilities for Bugzilla</TD
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,7 +71,7 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="QUICKSEARCH"
>C.3. The Quicksearch Utility</A
>D.3. The Quicksearch Utility</A
></H1
><P
> Quicksearch is a new, experimental feature of the 2.12 release.
......
docs/html/readme.windows.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Win32 (Win98+/NT/2K) Installation</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -510,7 +510,7 @@ CLASS="TIP"
>Tip: </B
> From Andrew Pearson:
<A
NAME="AEN304"
NAME="AEN624"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......@@ -548,6 +548,149 @@ CLASS="COMMAND"
</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="TIP"
><BLOCKQUOTE
CLASS="TIP"
><P
><B
>Tip: </B
>"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</P
><A
NAME="AEN634"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
> Hi - I am updating bugzilla to 2.12 so I can tell you what I did (after I
deleted the current dir and copied the files in).
</P
><P
> In checksetup.pl, I did the following...
</P
><DIV
CLASS="PROCEDURE"
><OL
TYPE="1"
><LI
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>my $webservergid = getgrnam($my_webservergroup);
</PRE
></TD
></TR
></TABLE
><P
>to</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>my $webservergid = 'Administrators'
</PRE
></TD
></TR
></TABLE
></LI
><LI
><P
> I then ran checksetup.pl
</P
></LI
><LI
><P
> I removed all the encrypt()
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN646"
></A
><P
><B
>Example 2-1. Removing encrypt() for Windows NT installations</B
></P
><P
> Replace this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " .
SqlQuote(substr($realcryptpwd, 0, 2)) . ")");
my $enteredcryptpwd = FetchOneColumn();
</PRE
></TD
></TR
></TABLE
>
with this:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>my $enteredcryptpwd = $enteredpwd
</PRE
></TD
></TR
></TABLE
>
in cgi.pl.
</P
></DIV
>
</P
></LI
><LI
><P
> I renamed processmail to processmail.pl
</P
></LI
><LI
><P
> I altered the sendmail statements to windmail:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>
open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t &#62; mail.log";
</PRE
></TD
></TR
></TABLE
>
</P
><P
> The quotes around the dir is for the spaces. mail.log is for the output
</P
></LI
></OL
></DIV
></BLOCKQUOTE
></BLOCKQUOTE
></DIV
></DIV
></DIV
><DIV
......
docs/html/rhbugzilla.html 0 → 100644
View file @ 2d4d7c92
<HTML
><HEAD
><TITLE
>Red Hat Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Bugzilla Variants"
HREF="variants.html"><LINK
REL="PREVIOUS"
TITLE="Bugzilla Variants"
HREF="variants.html"><LINK
REL="NEXT"
TITLE="Useful Patches and Utilities for Bugzilla"
HREF="patches.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="variants.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 7. Bugzilla Variants</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="patches.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="RHBUGZILLA"
>7.1. Red Hat Bugzilla</A
></H1
><P
> Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
on the planet.
One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
database, as well as MySQL.
Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
<A
NAME="AEN1913"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><P
CLASS="LITERALLAYOUT"
> &nbsp;&nbsp;Hello.&nbsp;I&nbsp;apologize&nbsp;that&nbsp;I&nbsp;am&nbsp;getting&nbsp;back&nbsp;to&nbsp;you&nbsp;so&nbsp;late.&nbsp;It&nbsp;has&nbsp;been&nbsp;difficult&nbsp;to&nbsp;keep<br>
up&nbsp;with&nbsp;email&nbsp;this&nbsp;past&nbsp;week.&nbsp;I&nbsp;have&nbsp;checked&nbsp;out&nbsp;your&nbsp;updated&nbsp;documentation&nbsp;and&nbsp;I&nbsp;will<br>
have&nbsp;to&nbsp;say&nbsp;very&nbsp;good&nbsp;work.&nbsp;A&nbsp;few&nbsp;notes&nbsp;and&nbsp;additions&nbsp;as&nbsp;follows.<br>
<br>
(ed:&nbsp;from&nbsp;the&nbsp;FAQ)<br>
&#62;For&nbsp;the&nbsp;record,&nbsp;we&nbsp;are&nbsp;not&nbsp;using&nbsp;any&nbsp;template&nbsp;type&nbsp;implementation&nbsp;for&nbsp;the&nbsp;cosmetic&nbsp;changes&nbsp;<br>
&#62;maded&nbsp;to&nbsp;Bugzilla.&nbsp;It&nbsp;is&nbsp;just&nbsp;alot&nbsp;of&nbsp;html&nbsp;changes&nbsp;in&nbsp;the&nbsp;code&nbsp;itself.&nbsp;I&nbsp;admit&nbsp;I&nbsp;may&nbsp;have&nbsp;<br>
&#62;gotten&nbsp;a&nbsp;little&nbsp;carried&nbsp;away&nbsp;with&nbsp;it&nbsp;but&nbsp;the&nbsp;corporate&nbsp;types&nbsp;asked&nbsp;for&nbsp;a&nbsp;more&nbsp;standardized&nbsp;<br>
&#62;interface&nbsp;to&nbsp;match&nbsp;up&nbsp;with&nbsp;other&nbsp;projects&nbsp;relating&nbsp;to&nbsp;Red&nbsp;Hat&nbsp;web&nbsp;sites.&nbsp;A&nbsp;lot&nbsp;of&nbsp;other&nbsp;web&nbsp;<br>
&#62;based&nbsp;internal&nbsp;tools&nbsp;I&nbsp;am&nbsp;working&nbsp;on&nbsp;also&nbsp;look&nbsp;like&nbsp;Bugzilla.&nbsp;<br>
<br>
<br>
This&nbsp;should&nbsp;probably&nbsp;be&nbsp;changed&nbsp;since&nbsp;we&nbsp;are&nbsp;now&nbsp;in&nbsp;fact&nbsp;using&nbsp;Text::Template&nbsp;for&nbsp;most<br>
of&nbsp;the&nbsp;html&nbsp;rendering.&nbsp;You&nbsp;actually&nbsp;state&nbsp;this&nbsp;later&nbsp;in&nbsp;your&nbsp;numbered&nbsp;list.<br>
<br>
Also&nbsp;number&nbsp;6&nbsp;contradicts&nbsp;number&nbsp;8&nbsp;where&nbsp;number&nbsp;6&nbsp;would&nbsp;be&nbsp;the&nbsp;most&nbsp;up&nbsp;to&nbsp;date&nbsp;status<br>
on&nbsp;the&nbsp;Oracle&nbsp;port.<br>
<br>
Additional&nbsp;Information:<br>
-----------------------------<br>
1.&nbsp;Comments&nbsp;are&nbsp;now&nbsp;stored&nbsp;in&nbsp;varchar&nbsp;fields&nbsp;of&nbsp;4k&nbsp;in&nbsp;size&nbsp;each.&nbsp;If&nbsp;the&nbsp;comment&nbsp;is&nbsp;more<br>
than&nbsp;4k&nbsp;it&nbsp;is&nbsp;broken&nbsp;up&nbsp;into&nbsp;chunks&nbsp;and&nbsp;given&nbsp;a&nbsp;sort&nbsp;number&nbsp;so&nbsp;each&nbsp;comment&nbsp;can&nbsp;be&nbsp;re<br>
assembled&nbsp;in&nbsp;the&nbsp;correct&nbsp;order.&nbsp;This&nbsp;was&nbsp;done&nbsp;because&nbsp;originally&nbsp;I&nbsp;was&nbsp;storing&nbsp;the&nbsp;comments<br>
in&nbsp;a&nbsp;long&nbsp;datatype&nbsp;which&nbsp;unfortunately&nbsp;cannot&nbsp;be&nbsp;indexed&nbsp;or&nbsp;joined&nbsp;with&nbsp;another&nbsp;table.&nbsp;This<br>
cause&nbsp;the&nbsp;search&nbsp;of&nbsp;text&nbsp;within&nbsp;the&nbsp;long&nbsp;description&nbsp;to&nbsp;be&nbsp;disabled&nbsp;for&nbsp;a&nbsp;long&nbsp;time.&nbsp;That<br>
is&nbsp;now&nbsp;working&nbsp;and&nbsp;is&nbsp;nto&nbsp;showing&nbsp;any&nbsp;noticeble&nbsp;performance&nbsp;hit&nbsp;that&nbsp;I&nbsp;can&nbsp;tell.&nbsp;<br>
<br>
2.&nbsp;Work&nbsp;is&nbsp;being&nbsp;started&nbsp;on&nbsp;internationalizing&nbsp;the&nbsp;Bugzilla&nbsp;source&nbsp;we&nbsp;have&nbsp;to&nbsp;allow&nbsp;our<br>
Japanese&nbsp;customers&nbsp;to&nbsp;enter&nbsp;bug&nbsp;reports&nbsp;into&nbsp;a&nbsp;single&nbsp;bugzilla&nbsp;system.&nbsp;This&nbsp;will&nbsp;probably<br>
be&nbsp;done&nbsp;by&nbsp;using&nbsp;the&nbsp;nvarchar&nbsp;data&nbsp;types&nbsp;supported&nbsp;by&nbsp;Oracle&nbsp;which&nbsp;allows&nbsp;storage&nbsp;of<br>
double&nbsp;byte&nbsp;characters&nbsp;and&nbsp;also&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;Accept-Language&nbsp;in&nbsp;the&nbsp;http&nbsp;header&nbsp;for&nbsp;<br>
detection&nbsp;by&nbsp;Bugilla&nbsp;of&nbsp;which&nbsp;language&nbsp;to&nbsp;render.<br>
<br>
3.&nbsp;Of&nbsp;course&nbsp;even&nbsp;more&nbsp;cosmetic&nbsp;changes.&nbsp;It&nbsp;is&nbsp;difficult&nbsp;to&nbsp;keep&nbsp;up&nbsp;with&nbsp;the&nbsp;ever&nbsp;<br>
changing&nbsp;faces&nbsp;of&nbsp;www.redhat.com.<br>
<br>
4.&nbsp;Some&nbsp;convenience&nbsp;enhancements&nbsp;in&nbsp;the&nbsp;administration&nbsp;utilities.&nbsp;And&nbsp;more&nbsp;integration<br>
with&nbsp;other&nbsp;internal/external&nbsp;Red&nbsp;Hat&nbsp;web&nbsp;sites.<br>
<br>
I&nbsp;hope&nbsp;this&nbsp;information&nbsp;may&nbsp;prove&nbsp;helpful&nbsp;for&nbsp;your&nbsp;documentation.&nbsp;Please&nbsp;contact<br>
me&nbsp;if&nbsp;you&nbsp;have&nbsp;any&nbsp;more&nbsp;question&nbsp;or&nbsp;I&nbsp;can&nbsp;do&nbsp;anything&nbsp;else.<br>
<br>
Regards<br>
</P
></BLOCKQUOTE
>
</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="variants.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="patches.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Bugzilla Variants</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="variants.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Useful Patches and Utilities for Bugzilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/scm.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Perforce SCM</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -74,14 +74,38 @@ NAME="SCM"
>5.3. Perforce SCM</A
></H1
><P
> Richard Brooksby and his team have an integration tool
in public beta. You can find it at
> Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
You can find the main project page at
<A
HREF="http://www.ravenbrook.com/project/p4dt"
HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top"
> http://www.ravenbrook.com/project/p4dti</A
>. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public Depot"
p4dti page at <A
HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
TARGET="_top"
> http://public.perforce.com/public/perforce/p4dti/index.html</A
>.
</P
><P
> Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
patches for 2.12 will be out shortly. Check the project page regularly for updates, or
take the given patches and patch it manually. p4dti is designed to support multiple defect
trackers, and maintains its own documentation for it. Please consult the pages linked
above for further information.
</P
><P
> Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
have synchronization problems, the easiest way to avoid them is to only put the bug
information, comments, etc. into Bugzilla, and not into the Perforce change records.
They will link anyway; merely reference the bug ID fixed in your change description,
and put a comment into Bugzilla
giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
question.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/searching.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Better Searching</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/security.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Bugzilla Security</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -172,8 +172,10 @@ TARGET="_top"
></LI
><LI
><P
> Ensure you have adequate access controls for $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/localconfig.
The localconfig file stores your "bugs" user password, which would be terrible to have in the hands
> Ensure you have adequate access controls for $BUGZILLA_HOME/data/, $BUGZILLA_HOME/localconfig,
and $BUGZILLA_HOME/shadow directories.
The localconfig file stores your "bugs" user password,
which would be terrible to have in the hands
of a criminal. Also some files under $BUGZILLA_HOME/data store sensitive information.
</P
><P
......@@ -187,7 +189,7 @@ TARGET="_top"
HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=65572"
TARGET="_top"
> Bug 65572</A
> for adequate protection in your data/ and shadow/ directories.
> for adequate protection in your data/ and shadow/ directories.
</P
><P
> Note the instructions which follow are Apache-specific. If you use IIS, Netscape, or other
......@@ -228,11 +230,6 @@ CLASS="LITERALLAYOUT"
>
</P
></LI
><LI
><P
>
</P
></LI
></OL
>
</P
......
docs/html/setperl.html
View file @ 2d4d7c92
<HTML
><HEAD
><TITLE
>The setperl.pl Utility</TITLE
>The setperl.csh Utility</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -51,7 +51,7 @@ HREF="patches.html"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix C. Useful Patches and Utilities for Bugzilla</TD
>Appendix D. Useful Patches and Utilities for Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
......@@ -71,12 +71,14 @@ CLASS="SECTION"
CLASS="SECTION"
><A
NAME="SETPERL"
>C.1. The setperl.pl Utility</A
>D.1. The setperl.csh Utility</A
></H1
><P
>
You can use the "setperl.pl" utility to quickly and easily
You can use the "setperl.csh" utility to quickly and easily
change the path to perl on all your Bugzilla files.
This is a C-shell script; if you do not have "csh" or "tcsh" in the search
path on your system, it will not work!
</P
><DIV
CLASS="PROCEDURE"
......@@ -84,7 +86,7 @@ CLASS="PROCEDURE"
TYPE="1"
><LI
><P
> Download the "setperl.pl" utility to your Bugzilla
> Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
</P
><OL
......@@ -116,7 +118,7 @@ CLASS="PROMPT"
>
<B
CLASS="COMMAND"
>wget -O setperl.pl 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</B
>
</TT
>
......@@ -132,7 +134,7 @@ CLASS="PROMPT"
>
<B
CLASS="COMMAND"
>chmod u+x setperl.pl</B
>chmod u+x setperl.csh</B
>
</TT
>
......@@ -210,10 +212,35 @@ CLASS="PROMPT"
>
<B
CLASS="COMMAND"
>./setperl.pl /your/path/to/perl</B
>./setperl.csh /your/path/to/perl</B
>
</TT
>
<DIV
CLASS="EXAMPLE"
><A
NAME="AEN1963"
></A
><P
><B
>Example D-1. Using Setperl to set your perl path</B
></P
><P
> <TT
CLASS="COMPUTEROUTPUT"
> <TT
CLASS="PROMPT"
>bash#</TT
>
<B
CLASS="COMMAND"
>./setperl.csh /usr/bin/perl</B
>
</TT
>
</P
></DIV
>
</P
></LI
></OL
......
docs/html/spamlite.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Reducing Spam</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -120,7 +120,11 @@ watching.&nbsp;&nbsp;With&nbsp;this,&nbsp;you&nbsp;could&nbsp;choose&nbsp;whethe
dependency&nbsp;and&nbsp;keyword&nbsp;changes,&nbsp;for&nbsp;example.<br>
<br>
Both&nbsp;of&nbsp;these&nbsp;proposals&nbsp;live&nbsp;at<br>
"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".</P
"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".<br>
Note&nbsp;that&nbsp;they&nbsp;also&nbsp;live&nbsp;at<br>
"http://bugzilla.mozilla.org/show_bug.cgi?id=17464",&nbsp;and&nbsp;the&nbsp;change&nbsp;<br>
has&nbsp;been&nbsp;checked&nbsp;in.&nbsp;&nbsp;This&nbsp;is&nbsp;fixed&nbsp;with&nbsp;Bugzilla&nbsp;2.12&nbsp;and&nbsp;is&nbsp;no&nbsp;longer<br>
an&nbsp;issue.&nbsp;&nbsp;Woo-Hoo!</P
></P
></DIV
><DIV
......
docs/html/tinderbox.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Tinderbox</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/trackingbugs.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Description Flags and Tracking Bugs</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/translations.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Translations</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -74,7 +74,8 @@ NAME="TRANSLATIONS"
>1.8. Translations</A
></H1
><P
> The Bugzilla Guide needs translators! Please volunteer your translation into the language of your choice.
> The Bugzilla Guide needs translators!
Please volunteer your translation into the language of your choice.
If you will translate this Guide, please notify the members of the mozilla-webtools mailing list at
<TT
CLASS="EMAIL"
......@@ -82,7 +83,8 @@ CLASS="EMAIL"
HREF="mailto:mozilla-webtools@mozilla.org"
>mozilla-webtools@mozilla.org</A
>&#62;</TT
>
>. Since The Bugzilla Guide is also hosted on the
Linux Documentation Project, you would also do well to notify
</P
></DIV
><DIV
......
docs/html/useradmin.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>User Administration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/using.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Using Bugzilla</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -131,6 +131,20 @@ HREF="how.html#QUERY"
HREF="how.html#BUGREPORTS"
>Creating and Managing Bug Reports</A
></DT
><DD
><DL
><DT
>4.3.3.1. <A
HREF="how.html#BUG_WRITING"
>Writing a Great Bug Report</A
></DT
><DT
>4.3.3.2. <A
HREF="how.html#BUG_MANAGE"
>Managing your Bug Reports</A
></DT
></DL
></DD
></DL
></DD
><DT
......@@ -150,6 +164,25 @@ HREF="init4me.html#ACCOUNTSETTINGS"
HREF="init4me.html#EMAILSETTINGS"
>Email Settings</A
></DT
><DD
><DL
><DT
>4.4.2.1. <A
HREF="init4me.html#NOTIFICATION"
>Email Notification</A
></DT
><DT
>4.4.2.2. <A
HREF="init4me.html#NEWEMAILTECH"
>New Email Technology</A
></DT
><DT
>4.4.2.3. <A
HREF="init4me.html#WATCHSETTINGS"
>"Watching" Users</A
></DT
></DL
></DD
><DT
>4.4.3. <A
HREF="init4me.html#FOOTERSETTINGS"
......
docs/html/usingbz-conc.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Using Bugzilla-Conclusion</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......
docs/html/variants.html 0 → 100644
View file @ 2d4d7c92
<HTML
><HEAD
><TITLE
>Bugzilla Variants</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Cleaning up after mucking with Bugzilla"
HREF="cleanupwork.html"><LINK
REL="NEXT"
TITLE="Red Hat Bugzilla"
HREF="rhbugzilla.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="cleanupwork.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="rhbugzilla.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="VARIANTS"
>Chapter 7. Bugzilla Variants</A
></H1
><DIV
CLASS="NOTE"
><BLOCKQUOTE
CLASS="NOTE"
><P
><B
>Note: </B
> I <EM
>know</EM
> there are more variants than just RedHat Bugzilla out there.
Please help me get information about them, their project status, and benefits there
might be in using them or in using their code in main-tree Bugzilla.
</P
></BLOCKQUOTE
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cleanupwork.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="rhbugzilla.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Cleaning up after mucking with Bugzilla</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Red Hat Bugzilla</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
\ No newline at end of file
docs/html/whatis.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>What is Bugzilla?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -77,11 +77,14 @@ NAME="WHATIS"
> Bugzilla is one example of a class of programs called "Defect Tracking Systems",
or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
groups of developers to keep track of outstanding bugs in their product effectively.
At the time Bugzilla was originally written, as a port from Netscape Communications'
"Bugsplat!" program to Perl from TCL, there were very few competitors in the market
for bug-tracking software. Most commercial defect-tracking software vendors at the
time charged enormous licensing fees. Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla) and
Bugzilla was originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy
bug-tracking database used internally for Netscape Communications. Terry later ported
Bugzilla to
Perl from TCL, and in Perl it remains to this day.
Most commercial defect-tracking software vendors at the
time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla). It
is now the de-facto standard defect-tracking system against which all others are
measured.
</P
......@@ -127,7 +130,8 @@ NAME="WHATIS"
></LI
><LI
><P
> integration with several automated software configuration management systems
> available integration with automated software configuration management systems, including
Perforce and CVS.
</P
></LI
><LI
......@@ -147,6 +151,12 @@ NAME="WHATIS"
no internationalization, and dependence on some nonstandard libraries.
</P
><P
> Some recent headway has been made on the query front, however. If you are using the latest
version of Bugzilla, you should see a "simple search" form on the default front page of
your Bugzilla install. Type in two or three search terms and you should pull up some
relevant information. This is also available as "queryhelp.cgi".
</P
><P
> Despite these small problems, Bugzilla is very hard to beat. It is under <EM
>very</EM
>
......
docs/html/why.html
View file @ 2d4d7c92
......@@ -4,7 +4,7 @@
>Why Should We Use Bugzilla?</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
......@@ -124,7 +124,7 @@ VALIGN="TOP"
> Bugzilla is very adaptable to various situations. Known uses currently
include IT support queues, Systems Administration deployment management,
chip design and development problem tracking (both pre-and-post fabrication),
and software bug tracking for luminaries such as Redhat, Loki software,
and software and hardware bug tracking for luminaries such as Redhat, Loki software,
Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
configuration management and replication problems
......
docs/sgml/Bugzilla-Guide.sgml
View file @ 2d4d7c92
......@@ -16,6 +16,7 @@
<!ENTITY database SYSTEM "database.sgml">
<!ENTITY patches SYSTEM "patches.sgml">
<!ENTITY variants SYSTEM "variants.sgml">
<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
]>
......@@ -58,7 +59,7 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<BOOKINFO>
<TITLE>The Bugzilla Guide</TITLE>
<PUBDATE>v2.11.1, 06 March 2001</PUBDATE>
<PUBDATE>v2.12.0, 24 April 2001</PUBDATE>
<AUTHOR>
<FIRSTNAME>Matthew</FIRSTNAME>
<OTHERNAME>P.</OTHERNAME>
......@@ -84,6 +85,7 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<revision>
<revnumber>2.11.1</revnumber>
<date>06 March 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Took way too long to revise this for 2.12 release.
Updated FAQ to use qandaset tags instead of literallayout,
......@@ -93,6 +95,20 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
2.13 release of the Guide in XML format instead of SGML.
</revremark>
</revision>
<revision>
<revnumber>2.12.0</revnumber>
<date>24 April 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
moving bugs from one keyword to another, clarified possible problems with the Landfill
tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
README into the UNIX installation section, and changed the README to indicate the deprecated
status. Things I know need work: Used "simplelist" a lot, where I should have used
"procedure" to tag things. Need to lowercase all tags to be XML compliant.
</revremark>
</revision>
</REVHISTORY>
<KEYWORDSET>
......@@ -129,6 +145,9 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- Appendix: The Frequently Asked Questions -->
&faq;
<!-- Appendix: Required Bugzilla Software Links -->
&requiredsoftware
<!-- Appendix: The Database Schema -->
&database;
......
docs/sgml/about.sgml
View file @ 2d4d7c92
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.sgml"> ] > -->
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.sgml"> ] >
<CHAPTER ID="about">
<TITLE>About This Guide</TITLE>
......@@ -176,10 +176,15 @@
<SECTION id="contributors">
<TITLE>Contributors</TITLE>
<PARA>
Thanks go to these people for significant contributions to this documentation:
Thanks go to these people for significant contributions
to this documentation (in no particular order):
</PARA>
<PARA>
Zach Lipton, Andrew Pearson, Spencer Smith, Eric Hansen
Zach Lipton (significant textual contributions),
Andrew Pearson,
Spencer Smith,
Eric Hanson,
Kevin Brannen,
</PARA>
</SECTION>
<SECTION ID="feedback">
......@@ -195,9 +200,11 @@
<SECTION ID="translations">
<TITLE>Translations</TITLE>
<PARA>
The Bugzilla Guide needs translators! Please volunteer your translation into the language of your choice.
The Bugzilla Guide needs translators!
Please volunteer your translation into the language of your choice.
If you will translate this Guide, please notify the members of the mozilla-webtools mailing list at
<email>mozilla-webtools@mozilla.org</email>
<email>mozilla-webtools@mozilla.org</email>. Since The Bugzilla Guide is also hosted on the
Linux Documentation Project, you would also do well to notify
</PARA>
</SECTION>
......
docs/sgml/administration.sgml
View file @ 2d4d7c92
......@@ -30,7 +30,7 @@ Chapter: Administration
<PARA>
So you followed the README isntructions to the letter, and
just logged into bugzilla with your super-duper god account and you are sitting at the query
screen. Yet, you have nothing to query. Your first act of bisuness needs to be to setup the
screen. Yet, you have nothing to query. Your first act of business needs to be to setup the
operating parameters for bugzilla.</PARA>
<SECTION id="postinstall-check">
......@@ -48,6 +48,14 @@ operating parameters for bugzilla.</PARA>
<PROCEDURE>
<STEP>
<PARA>
Bring up "editparams.cgi" in your web browser. For instance, to edit parameters
at mozilla.org, the URL would be <ULINK URL="http://bugzilla.mozilla.org/editparams.cgi">
http://bugzilla.mozilla.org/editparams.cgi</ULINK>, also available under the "edit parameters"
link on your query page.
</PARA>
</STEP>
<STEP>
<PARA>
Set "maintainer" to <EMPHASIS>your</EMPHASIS> email address.
This allows Bugzilla's error messages
to display your email
......@@ -71,7 +79,7 @@ operating parameters for bugzilla.</PARA>
</STEP>
<STEP>
<PARA>
Set "usebuggroupsentry" to "1" if you want to be able to restrict access to products.
Set "usebuggroupsentry" to "1" if you want to restrict access to products.
Once again, if you are simply testing your installation, I suggest against
turning this parameter on; the strict security checking may stop you from
being able to modify your new entries.
......@@ -99,18 +107,22 @@ operating parameters for bugzilla.</PARA>
attempting to commit a change to the database.
</PARA>
<PARA>
If you use the "shadowdb" option, it is only natural that you should turn the "queryagainstshadowdb"
If you use the "shadowdb" option,
it is only natural that you should turn the "queryagainstshadowdb"
option "On" as well. Otherwise you are replicating data into a shadow database for no reason!
</PARA>
</STEP>
<STEP>
<PARA>
If you have custom logos or HTML you must put in place to fit within your site design guidelines,
place the code in the "headerhtml", "footerhtml", "errorhtml", "bannerhtml", or "blurbhtml" text boxes.
place the code in the "headerhtml", "footerhtml", "errorhtml",
"bannerhtml", or "blurbhtml" text boxes.
<NOTE>
<PARA>
The "headerhtml" text box is the HTML printed out <EMPHASIS>before</EMPHASIS> any other code on the page.
If you have a special banner, put the code for it in "bannerhtml". You may want to leave these
The "headerhtml" text box is the HTML printed out
<EMPHASIS>before</EMPHASIS> any other code on the page.
If you have a special banner, put the code for it in "bannerhtml".
You may want to leave these
settings at the defaults initially.
</PARA>
</NOTE>
......@@ -125,27 +137,33 @@ operating parameters for bugzilla.</PARA>
</STEP>
<STEP>
<PARA>
Set "newemailtech" to "on". Your users will thank you. This is the default in the post-2.12 world.
Ensure "newemailtech" is "on".
Your users will thank you. This is the default in the post-2.12 world, and is
only an issue if you are upgrading.
</PARA>
</STEP>
<STEP>
<PARA>
Do you want to use the qa contact ("useqacontact") and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility, particularly when you have an existing
Do you want to use the qa contact ("useqacontact")
and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility,
particularly when you have an existing
Quality Assurance and/or Release Engineering team,
but they may not be needed for smaller installations.
</PARA>
</STEP>
<STEP>
<PARA>
Set "whinedays" to the amount of days you want to let bugs go in the "New" or "Reopened" state before
Set "whinedays" to the amount of days you want to let bugs go
in the "New" or "Reopened" state before
notifying people they have untouched new bugs. If you do not plan to use this feature, simply do
not set up the whining cron job described in the README, or set this value to "0".
</PARA>
</STEP>
<STEP>
<PARA>
Set the "commenton" options according to your site policy. It is a wise idea to require comments when users
Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users
resolve, reassign, or reopen bugs.
<NOTE>
<PARA>
......@@ -456,9 +474,6 @@ operating parameters for bugzilla.</PARA>
Dear Lord, we have to get our users to do WHAT?
</PARA>
</EPIGRAPH>
<REMARK>
Many thanks to Zach Lipton for his contributions to this section
</REMARK>
<SECTION id="products">
<TITLE>Products</TITLE>
......@@ -1033,15 +1048,17 @@ operating parameters for bugzilla.</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Ensure you have adequate access controls for $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/localconfig.
The localconfig file stores your "bugs" user password, which would be terrible to have in the hands
Ensure you have adequate access controls for $BUGZILLA_HOME/data/, $BUGZILLA_HOME/localconfig,
and $BUGZILLA_HOME/shadow directories.
The localconfig file stores your "bugs" user password,
which would be terrible to have in the hands
of a criminal. Also some files under $BUGZILLA_HOME/data store sensitive information.
</PARA>
<PARA>
On Apache, you can use .htaccess files to protect access to these directories, as outlined
in <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ULINK> for the
localconfig file, and <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=65572">
Bug 65572</ULINK> for adequate protection in your data/ and shadow/ directories.
Bug 65572</ULINK> for adequate protection in your data/ and shadow/ directories.
</PARA>
<PARA>
Note the instructions which follow are Apache-specific. If you use IIS, Netscape, or other
......@@ -1076,12 +1093,6 @@ operating parameters for bugzilla.</PARA>
</LITERALLAYOUT>
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
</PARA>
</LISTITEM>
</ORDEREDLIST>
</PARA>
</SECTION>
......
docs/sgml/database.sgml
View file @ 2d4d7c92
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<APPENDIX id="database">
<TITLE>The Bugzilla Database</TITLE>
<NOTE>
<PARA>This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers? <REMARK>MPB</REMARK></PARA>
<PARA>This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?</PARA>
</NOTE>
<SECTION id="dbschema">
<TITLE>Database Schema Chart</TITLE>
......@@ -405,7 +405,13 @@ http://www.devshed.com/Server_Side/MySQL/
<TITLE>MySQL Permissions & Grant Tables</TITLE>
<NOTE>
<PARA>The following portion of documentation comes from my answer to an old discussion of Keynote, a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the Keynote support group regarding MySQL grant table permissions, and how to use them effectively. It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables since this time, but it serves as a decent introduction and troubleshooting document for grant table issues. I used Keynote to track my troubles until I discovered Bugzilla, which gave me a whole new set of troubles to work on : )</PARA>
<PARA>The following portion of documentation comes from my answer to an old discussion of Keystone,
a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the
Keystone support group regarding MySQL grant table permissions, and how to use them effectively.
It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables
since this time, but it serves as a decent introduction and troubleshooting document for grant
table issues. I used Keynote to track my troubles until I discovered Bugzilla,
which gave me a whole new set of troubles to work on : )</PARA>
</NOTE>
<LITERALLAYOUT>
......@@ -589,7 +595,7 @@ NEW CONTACT INFORMATION:
<SECTION id="cleanupwork">
<TITLE>Cleaning up after mucking with Bugzilla</TITLE>
<LITERALLAYOUT>
Contributed by Eric Hansen:
Contributed by Eric Hanson:
There are several things, and one trick. There is a small tiny piece of
documentation I saw once that said something very important.
1) After pretty much any manual working of the Mysql db, you must
......
docs/sgml/faq.sgml
View file @ 2d4d7c92
......@@ -272,7 +272,14 @@
<qandadiv id="faq_redhat">
<title>Red Hat Bugzilla</title>
<para>
<note>
<para>
<emphasis>This section is no longer up-to-date.</emphasis>
Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
</para>
</note>
</para>
<qandaentry>
<question>
<para>
......@@ -430,7 +437,8 @@
<note>
<para>
This information is somewhat dated; I last updated it
7 June 2000.
7 June 2000. Please see the "Variants" section of "The Bugzilla Guide"
for more up-to-date information regarding Red Hat Bugzilla.
</para>
</note>
<emphasis>Dave Lawrence</emphasis>:
......@@ -465,7 +473,7 @@
thing going to help others that may need it.
</para>
<para>
As Matt has mentioned it is still using out-dated code and with a
As Matt has mentioned it is still using out-dated code and with a
little help I would like to bring everything up to date for
eventual incorporation with the main cvs tree. Due to other
duties I have with the company any help with this wiould be
......@@ -490,16 +498,21 @@
<qandadiv id="faq_loki">
<title>Loki Bugzilla (AKA Fenris)</title>
<note>
<para>
Loki's "Fenris" Bugzilla is no longer actively maintained.
It works well enough for Loki. Additionally, the major
differences in Fenris have now been integrated into
the main source tree of Bugzilla, so there's not much
reason to go grab the source. I left this section of the
FAQ principally for historical interest.
</para>
</note>
<para>
<note>
<para>
Loki's "Fenris" Bugzilla is based upon the (now ancient) Bugzilla 2.8
tree, and is no longer actively maintained.
It works well enough for Loki. Additionally, the major
differences in Fenris have now been integrated into
the main source tree of Bugzilla, so there's not much
reason to go grab the source. I leave this section of the
FAQ principally for historical interest, but unless Loki has further
input into Bugzilla's future, it will be deprecated in future versions
of the Guide.
</para>
</note>
</para>
<qandaentry>
<question>
......@@ -558,12 +571,14 @@
<qandadiv id="faq_phb">
<title>Pointy-Haired-Boss Questions</title>
<note>
<para>
The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :)
</para>
</note>
<para>
<note>
<para>
The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :)
</para>
</note>
</para>
<qandaentry>
<question>
......@@ -1228,7 +1243,7 @@
is unavailable.
</para>
<para>
This is now a configurable parameter called "sendmailparm", available
This is now a configurable parameter called "sendmailnow", available
from editparams.cgi.
</para>
</answer>
......@@ -1767,6 +1782,26 @@ A: Sure! Here ya go!
<qandaentry>
<question>
<para>
How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</para>
</question>
<answer>
<para>
This is well-documented here: <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=49862">
http://bugzilla.mozilla.org/show_bug.cgi?id=49862</ulink>. Ultimately, it's as easy
as adding the "---" priority field to your localconfig file in the appropriate area,
re-running checksetup.pl, and then changing the default priority in your browser using
"editparams.cgi". Hmm, now that I think about it, that is kind of a klunky way to handle
it, but for now it's what we have! Although the bug has been closed "resolved wontfix",
there may be a better way to handle this...
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
What's the best way to submit patches? What guidelines should I follow?
</para>
</question>
......
docs/sgml/future.sgml
View file @ 2d4d7c92
......@@ -2,7 +2,7 @@
<chapter id="future">
<title>The Future of Bugzilla</title>
<synopsis>This section largely contributed by Matthew Tuck</synopsis>
<synopsis>Bugzilla's Future. Much of this is the present, now.</synopsis>
<section id="spamlite">
<title>Reducing Spam</title>
<para><literallayout>
......@@ -51,6 +51,10 @@ dependency and keyword changes, for example.
Both of these proposals live at
"http://bugzilla.mozilla.org/show_bug.cgi?id=14137".
Note that they also live at
"http://bugzilla.mozilla.org/show_bug.cgi?id=17464", and the change
has been checked in. This is fixed with Bugzilla 2.12 and is no longer
an issue. Woo-Hoo!
</literallayout></para>
</section>
......
docs/sgml/integration.sgml
View file @ 2d4d7c92
<!-- <!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 -->
......@@ -18,10 +18,31 @@
<section id="scm">
<title>Perforce SCM</title>
<para>
Richard Brooksby and his team have an integration tool
in public beta. You can find it at
<ulink url="http://www.ravenbrook.com/project/p4dt">
http://www.ravenbrook.com/project/p4dti</ulink>.
Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
You can find the main project page at
<ulink url="http://www.ravenbrook.com/project/p4dti/">
http://www.ravenbrook.com/project/p4dti</ulink>. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public Depot"
p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
</para>
<para>
Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
patches for 2.12 will be out shortly. Check the project page regularly for updates, or
take the given patches and patch it manually. p4dti is designed to support multiple defect
trackers, and maintains its own documentation for it. Please consult the pages linked
above for further information.
</para>
<para>
Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
have synchronization problems, the easiest way to avoid them is to only put the bug
information, comments, etc. into Bugzilla, and not into the Perforce change records.
They will link anyway; merely reference the bug ID fixed in your change description,
and put a comment into Bugzilla
giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
question.
</para>
</section>
......
docs/sgml/patches.sgml
View file @ 2d4d7c92
......@@ -4,15 +4,17 @@
<title>Useful Patches and Utilities for Bugzilla</title>
<section id="setperl">
<title>The setperl.pl Utility</title>
<title>The setperl.csh Utility</title>
<para>
You can use the "setperl.pl" utility to quickly and easily
You can use the "setperl.csh" utility to quickly and easily
change the path to perl on all your Bugzilla files.
This is a C-shell script; if you do not have "csh" or "tcsh" in the search
path on your system, it will not work!
</para>
<procedure>
<step>
<para>
Download the "setperl.pl" utility to your Bugzilla
Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
</para>
<substeps>
......@@ -28,7 +30,7 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>wget -O setperl.pl 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
<command>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
</computeroutput>
</para>
</step>
......@@ -36,7 +38,7 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+x setperl.pl</command>
<command>chmod u+x setperl.csh</command>
</computeroutput>
</para>
</step>
......@@ -80,8 +82,17 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.pl /your/path/to/perl</command>
<command>./setperl.csh /your/path/to/perl</command>
</computeroutput>
<example>
<title>Using Setperl to set your perl path</title>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.csh /usr/bin/perl</command>
</computeroutput>
</para>
</example>
</para>
</step>
</procedure>
......@@ -206,4 +217,21 @@
</para>
</section>
</appendix>
\ No newline at end of file
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
docs/sgml/requiredsoftware.sgml 0 → 100644
View file @ 2d4d7c92
<!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.org/">http://www.mysql.org/</ulink>
</para>
<para>
Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink>
</para>
<para>
CPAN: <ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink>
</para>
<para>
DBI Perl module:
<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>
Data::Dumper module:
<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>
</para>
<para>
MySQL related Perl modules:
<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>
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>
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>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
docs/sgml/using.sgml
View file @ 2d4d7c92
......@@ -41,11 +41,14 @@ Chapter: Using Bugzilla
Bugzilla is one example of a class of programs called "Defect Tracking Systems",
or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
groups of developers to keep track of outstanding bugs in their product effectively.
At the time Bugzilla was originally written, as a port from Netscape Communications'
"Bugsplat!" program to Perl from TCL, there were very few competitors in the market
for bug-tracking software. Most commercial defect-tracking software vendors at the
time charged enormous licensing fees. Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla) and
Bugzilla was originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy
bug-tracking database used internally for Netscape Communications. Terry later ported
Bugzilla to
Perl from TCL, and in Perl it remains to this day.
Most commercial defect-tracking software vendors at the
time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla). It
is now the de-facto standard defect-tracking system against which all others are
measured.
</para>
......@@ -89,7 +92,8 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
integration with several automated software configuration management systems
available integration with automated software configuration management systems, including
Perforce and CVS.
</para>
</listitem>
<listitem>
......@@ -108,6 +112,12 @@ Chapter: Using Bugzilla
no internationalization, and dependence on some nonstandard libraries.
</para>
<para>
Some recent headway has been made on the query front, however. If you are using the latest
version of Bugzilla, you should see a "simple search" form on the default front page of
your Bugzilla install. Type in two or three search terms and you should pull up some
relevant information. This is also available as "queryhelp.cgi".
</para>
<para>
Despite these small problems, Bugzilla is very hard to beat. It is under <emphasis>very</emphasis>
active development to address the current issues, and a long-awaited overhaul in the form
of Bugzilla 3.0 is expected sometime later this year.
......@@ -147,7 +157,7 @@ Chapter: Using Bugzilla
Bugzilla is very adaptable to various situations. Known uses currently
include IT support queues, Systems Administration deployment management,
chip design and development problem tracking (both pre-and-post fabrication),
and software bug tracking for luminaries such as Redhat, Loki software,
and software and hardware bug tracking for luminaries such as Redhat, Loki software,
Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
configuration management and replication problems
......@@ -178,7 +188,7 @@ Chapter: Using Bugzilla
</epigraph>
<para>
Bugzilla is a large and complex system. Describing how to use it
Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or administering
a Bugzilla installation, please consult the Installing and Administering
Bugzilla portions of this Guide. This section is principally aimed towards
......@@ -190,11 +200,24 @@ Chapter: Using Bugzilla
options available at the Bugzilla test installation,
<ulink url="http://landfill.tequilarista.org/">
landfill.tequilarista.org</ulink>.
<note>
<para>
Some people have run into difficulties completing this tutorial. If
you run into problems, please check the updated, online documentation available
at <ulink url="http://www.trilobyte.net/barnsons/">http://www.trilobyte.net/barnsons</ulink>.
If you're still stumped, please subscribe to the newsgroup and provide details of exactly
what's stumping you! If enough people complain, I'll have to fix it in the next
version of this Guide. You can subscribe to the newsgroup at
<ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">
news://news.mozilla.org/netscape.public.mozilla.webtools</ulink>
</para>
</note>
Although Landfill serves as a great introduction to Bugzilla, it does not offer
all the options you would have as a user on your own installation of Bugzilla,
nor can it do more than serve as a general introduction to Bugzilla.
However, please use it if you want to
follow this tutorial.
nor can it do more than serve as a general introduction to Bugzilla. Additionally,
Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
may work slightly differently than mentioned here.
</para>
<section id="myaccount">
......@@ -714,6 +737,14 @@ Chapter: Using Bugzilla
<title>Email Settings</title>
<section id="notification">
<title>Email Notification</title>
<note>
<para>
The email notification settings described below have been obsoleted in Bugzilla 2.12, and
this section will be replaced with a comprehensive description of the amazing array of
new options at your disposal. However, in the meantime, throw this chunk out the window
and go crazy with goofing around with different notification options.
</para>
</note>
<para>
Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
In the drop-down "Notify me of changes to", select one of
......
docs/sgml/variants.sgml
View file @ 2d4d7c92
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<chapter id="variants">
<title>Bugzilla Variants</title>
<note>
<para>
I <emphasis>know</emphasis> there are more variants than just RedHat Bugzilla out there.
Please help me get information about them, their project status, and benefits there
might be in using them or in using their code in main-tree Bugzilla.
</para>
</note>
<section id="rhbugzilla">
<title>Red Hat Bugzilla</title>
<para>
Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
on the planet.
One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
database, as well as MySQL.
Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
<blockquote>
<literallayout>
Hello. I apologize that I am getting back to you so late. It has been difficult to keep
up with email this past week. I have checked out your updated documentation and I will
have to say very good work. A few notes and additions as follows.
(ed: from the FAQ)
>For the record, we are not using any template type implementation for the cosmetic changes
>maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have
>gotten a little carried away with it but the corporate types asked for a more standardized
>interface to match up with other projects relating to Red Hat web sites. A lot of other web
>based internal tools I am working on also look like Bugzilla.
This should probably be changed since we are now in fact using Text::Template for most
of the html rendering. You actually state this later in your numbered list.
Also number 6 contradicts number 8 where number 6 would be the most up to date status
on the Oracle port.
Additional Information:
-----------------------------
1. Comments are now stored in varchar fields of 4k in size each. If the comment is more
than 4k it is broken up into chunks and given a sort number so each comment can be re
assembled in the correct order. This was done because originally I was storing the comments
in a long datatype which unfortunately cannot be indexed or joined with another table. This
cause the search of text within the long description to be disabled for a long time. That
is now working and is nto showing any noticeble performance hit that I can tell.
2. Work is being started on internationalizing the Bugzilla source we have to allow our
Japanese customers to enter bug reports into a single bugzilla system. This will probably
be done by using the nvarchar data types supported by Oracle which allows storage of
double byte characters and also the use of the Accept-Language in the http header for
detection by Bugilla of which language to render.
3. Of course even more cosmetic changes. It is difficult to keep up with the ever
changing faces of www.redhat.com.
4. Some convenience enhancements in the administration utilities. And more integration
with other internal/external Red Hat web sites.
I hope this information may prove helpful for your documentation. Please contact
me if you have any more question or I can do anything else.
Regards
</literallayout>
</blockquote>
</para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
docs/xml/Bugzilla-Guide.xml
View file @ 2d4d7c92
......@@ -16,6 +16,7 @@
<!ENTITY database SYSTEM "database.sgml">
<!ENTITY patches SYSTEM "patches.sgml">
<!ENTITY variants SYSTEM "variants.sgml">
<!ENTITY requiredsoftware SYSTEM "requiredsoftware.sgml">
]>
......@@ -58,7 +59,7 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<BOOKINFO>
<TITLE>The Bugzilla Guide</TITLE>
<PUBDATE>v2.11.1, 06 March 2001</PUBDATE>
<PUBDATE>v2.12.0, 24 April 2001</PUBDATE>
<AUTHOR>
<FIRSTNAME>Matthew</FIRSTNAME>
<OTHERNAME>P.</OTHERNAME>
......@@ -84,6 +85,7 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<revision>
<revnumber>2.11.1</revnumber>
<date>06 March 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Took way too long to revise this for 2.12 release.
Updated FAQ to use qandaset tags instead of literallayout,
......@@ -93,6 +95,20 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
2.13 release of the Guide in XML format instead of SGML.
</revremark>
</revision>
<revision>
<revnumber>2.12.0</revnumber>
<date>24 April 2001</date>
<authorinitials>MPB</authorinitials>
<revremark>
Things fixed this release: Elaborated on queryhelp interface, added FAQ regarding
moving bugs from one keyword to another, clarified possible problems with the Landfill
tutorial, fixed a boatload of typos and unclear sentence structures. Incorporated the
README into the UNIX installation section, and changed the README to indicate the deprecated
status. Things I know need work: Used "simplelist" a lot, where I should have used
"procedure" to tag things. Need to lowercase all tags to be XML compliant.
</revremark>
</revision>
</REVHISTORY>
<KEYWORDSET>
......@@ -129,6 +145,9 @@ http://www.linuxdoc.org/LDP/LDP-Author-Guide/tools-hints.html
<!-- Appendix: The Frequently Asked Questions -->
&faq;
<!-- Appendix: Required Bugzilla Software Links -->
&requiredsoftware
<!-- Appendix: The Database Schema -->
&database;
......
docs/xml/about.xml
View file @ 2d4d7c92
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.sgml"> ] > -->
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.sgml"> ] >
<CHAPTER ID="about">
<TITLE>About This Guide</TITLE>
......@@ -176,10 +176,15 @@
<SECTION id="contributors">
<TITLE>Contributors</TITLE>
<PARA>
Thanks go to these people for significant contributions to this documentation:
Thanks go to these people for significant contributions
to this documentation (in no particular order):
</PARA>
<PARA>
Zach Lipton, Andrew Pearson, Spencer Smith, Eric Hansen
Zach Lipton (significant textual contributions),
Andrew Pearson,
Spencer Smith,
Eric Hanson,
Kevin Brannen,
</PARA>
</SECTION>
<SECTION ID="feedback">
......@@ -195,9 +200,11 @@
<SECTION ID="translations">
<TITLE>Translations</TITLE>
<PARA>
The Bugzilla Guide needs translators! Please volunteer your translation into the language of your choice.
The Bugzilla Guide needs translators!
Please volunteer your translation into the language of your choice.
If you will translate this Guide, please notify the members of the mozilla-webtools mailing list at
<email>mozilla-webtools@mozilla.org</email>
<email>mozilla-webtools@mozilla.org</email>. Since The Bugzilla Guide is also hosted on the
Linux Documentation Project, you would also do well to notify
</PARA>
</SECTION>
......
docs/xml/administration.xml
View file @ 2d4d7c92
......@@ -30,7 +30,7 @@ Chapter: Administration
<PARA>
So you followed the README isntructions to the letter, and
just logged into bugzilla with your super-duper god account and you are sitting at the query
screen. Yet, you have nothing to query. Your first act of bisuness needs to be to setup the
screen. Yet, you have nothing to query. Your first act of business needs to be to setup the
operating parameters for bugzilla.</PARA>
<SECTION id="postinstall-check">
......@@ -48,6 +48,14 @@ operating parameters for bugzilla.</PARA>
<PROCEDURE>
<STEP>
<PARA>
Bring up "editparams.cgi" in your web browser. For instance, to edit parameters
at mozilla.org, the URL would be <ULINK URL="http://bugzilla.mozilla.org/editparams.cgi">
http://bugzilla.mozilla.org/editparams.cgi</ULINK>, also available under the "edit parameters"
link on your query page.
</PARA>
</STEP>
<STEP>
<PARA>
Set "maintainer" to <EMPHASIS>your</EMPHASIS> email address.
This allows Bugzilla's error messages
to display your email
......@@ -71,7 +79,7 @@ operating parameters for bugzilla.</PARA>
</STEP>
<STEP>
<PARA>
Set "usebuggroupsentry" to "1" if you want to be able to restrict access to products.
Set "usebuggroupsentry" to "1" if you want to restrict access to products.
Once again, if you are simply testing your installation, I suggest against
turning this parameter on; the strict security checking may stop you from
being able to modify your new entries.
......@@ -99,18 +107,22 @@ operating parameters for bugzilla.</PARA>
attempting to commit a change to the database.
</PARA>
<PARA>
If you use the "shadowdb" option, it is only natural that you should turn the "queryagainstshadowdb"
If you use the "shadowdb" option,
it is only natural that you should turn the "queryagainstshadowdb"
option "On" as well. Otherwise you are replicating data into a shadow database for no reason!
</PARA>
</STEP>
<STEP>
<PARA>
If you have custom logos or HTML you must put in place to fit within your site design guidelines,
place the code in the "headerhtml", "footerhtml", "errorhtml", "bannerhtml", or "blurbhtml" text boxes.
place the code in the "headerhtml", "footerhtml", "errorhtml",
"bannerhtml", or "blurbhtml" text boxes.
<NOTE>
<PARA>
The "headerhtml" text box is the HTML printed out <EMPHASIS>before</EMPHASIS> any other code on the page.
If you have a special banner, put the code for it in "bannerhtml". You may want to leave these
The "headerhtml" text box is the HTML printed out
<EMPHASIS>before</EMPHASIS> any other code on the page.
If you have a special banner, put the code for it in "bannerhtml".
You may want to leave these
settings at the defaults initially.
</PARA>
</NOTE>
......@@ -125,27 +137,33 @@ operating parameters for bugzilla.</PARA>
</STEP>
<STEP>
<PARA>
Set "newemailtech" to "on". Your users will thank you. This is the default in the post-2.12 world.
Ensure "newemailtech" is "on".
Your users will thank you. This is the default in the post-2.12 world, and is
only an issue if you are upgrading.
</PARA>
</STEP>
<STEP>
<PARA>
Do you want to use the qa contact ("useqacontact") and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility, particularly when you have an existing
Do you want to use the qa contact ("useqacontact")
and status whiteboard ("usestatuswhiteboard") fields?
These fields are useful because they allow for more flexibility,
particularly when you have an existing
Quality Assurance and/or Release Engineering team,
but they may not be needed for smaller installations.
</PARA>
</STEP>
<STEP>
<PARA>
Set "whinedays" to the amount of days you want to let bugs go in the "New" or "Reopened" state before
Set "whinedays" to the amount of days you want to let bugs go
in the "New" or "Reopened" state before
notifying people they have untouched new bugs. If you do not plan to use this feature, simply do
not set up the whining cron job described in the README, or set this value to "0".
</PARA>
</STEP>
<STEP>
<PARA>
Set the "commenton" options according to your site policy. It is a wise idea to require comments when users
Set the "commenton" options according to your site policy.
It is a wise idea to require comments when users
resolve, reassign, or reopen bugs.
<NOTE>
<PARA>
......@@ -456,9 +474,6 @@ operating parameters for bugzilla.</PARA>
Dear Lord, we have to get our users to do WHAT?
</PARA>
</EPIGRAPH>
<REMARK>
Many thanks to Zach Lipton for his contributions to this section
</REMARK>
<SECTION id="products">
<TITLE>Products</TITLE>
......@@ -1033,15 +1048,17 @@ operating parameters for bugzilla.</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
Ensure you have adequate access controls for $BUGZILLA_HOME/data/ and $BUGZILLA_HOME/localconfig.
The localconfig file stores your "bugs" user password, which would be terrible to have in the hands
Ensure you have adequate access controls for $BUGZILLA_HOME/data/, $BUGZILLA_HOME/localconfig,
and $BUGZILLA_HOME/shadow directories.
The localconfig file stores your "bugs" user password,
which would be terrible to have in the hands
of a criminal. Also some files under $BUGZILLA_HOME/data store sensitive information.
</PARA>
<PARA>
On Apache, you can use .htaccess files to protect access to these directories, as outlined
in <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=57161">Bug 57161</ULINK> for the
localconfig file, and <ULINK URL="http://bugzilla.mozilla.org/show_bug.cgi?id=65572">
Bug 65572</ULINK> for adequate protection in your data/ and shadow/ directories.
Bug 65572</ULINK> for adequate protection in your data/ and shadow/ directories.
</PARA>
<PARA>
Note the instructions which follow are Apache-specific. If you use IIS, Netscape, or other
......@@ -1076,12 +1093,6 @@ operating parameters for bugzilla.</PARA>
</LITERALLAYOUT>
</PARA>
</LISTITEM>
<LISTITEM>
<PARA>
</PARA>
</LISTITEM>
</ORDEREDLIST>
</PARA>
</SECTION>
......
docs/xml/database.xml
View file @ 2d4d7c92
<!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> -->
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<APPENDIX id="database">
<TITLE>The Bugzilla Database</TITLE>
<NOTE>
<PARA>This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers? <REMARK>MPB</REMARK></PARA>
<PARA>This document really needs to be updated with more fleshed out information about primary keys, interrelationships, and maybe some nifty tables to document dependencies. Any takers?</PARA>
</NOTE>
<SECTION id="dbschema">
<TITLE>Database Schema Chart</TITLE>
......@@ -405,7 +405,13 @@ http://www.devshed.com/Server_Side/MySQL/
<TITLE>MySQL Permissions & Grant Tables</TITLE>
<NOTE>
<PARA>The following portion of documentation comes from my answer to an old discussion of Keynote, a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the Keynote support group regarding MySQL grant table permissions, and how to use them effectively. It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables since this time, but it serves as a decent introduction and troubleshooting document for grant table issues. I used Keynote to track my troubles until I discovered Bugzilla, which gave me a whole new set of troubles to work on : )</PARA>
<PARA>The following portion of documentation comes from my answer to an old discussion of Keystone,
a cool product that does trouble-ticket tracking for IT departments. I wrote this post to the
Keystone support group regarding MySQL grant table permissions, and how to use them effectively.
It is badly in need of updating, as I believe MySQL has added a field or two to the grant tables
since this time, but it serves as a decent introduction and troubleshooting document for grant
table issues. I used Keynote to track my troubles until I discovered Bugzilla,
which gave me a whole new set of troubles to work on : )</PARA>
</NOTE>
<LITERALLAYOUT>
......@@ -589,7 +595,7 @@ NEW CONTACT INFORMATION:
<SECTION id="cleanupwork">
<TITLE>Cleaning up after mucking with Bugzilla</TITLE>
<LITERALLAYOUT>
Contributed by Eric Hansen:
Contributed by Eric Hanson:
There are several things, and one trick. There is a small tiny piece of
documentation I saw once that said something very important.
1) After pretty much any manual working of the Mysql db, you must
......
docs/xml/faq.xml
View file @ 2d4d7c92
......@@ -272,7 +272,14 @@
<qandadiv id="faq_redhat">
<title>Red Hat Bugzilla</title>
<para>
<note>
<para>
<emphasis>This section is no longer up-to-date.</emphasis>
Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide.
</para>
</note>
</para>
<qandaentry>
<question>
<para>
......@@ -430,7 +437,8 @@
<note>
<para>
This information is somewhat dated; I last updated it
7 June 2000.
7 June 2000. Please see the "Variants" section of "The Bugzilla Guide"
for more up-to-date information regarding Red Hat Bugzilla.
</para>
</note>
<emphasis>Dave Lawrence</emphasis>:
......@@ -465,7 +473,7 @@
thing going to help others that may need it.
</para>
<para>
As Matt has mentioned it is still using out-dated code and with a
As Matt has mentioned it is still using out-dated code and with a
little help I would like to bring everything up to date for
eventual incorporation with the main cvs tree. Due to other
duties I have with the company any help with this wiould be
......@@ -490,16 +498,21 @@
<qandadiv id="faq_loki">
<title>Loki Bugzilla (AKA Fenris)</title>
<note>
<para>
Loki's "Fenris" Bugzilla is no longer actively maintained.
It works well enough for Loki. Additionally, the major
differences in Fenris have now been integrated into
the main source tree of Bugzilla, so there's not much
reason to go grab the source. I left this section of the
FAQ principally for historical interest.
</para>
</note>
<para>
<note>
<para>
Loki's "Fenris" Bugzilla is based upon the (now ancient) Bugzilla 2.8
tree, and is no longer actively maintained.
It works well enough for Loki. Additionally, the major
differences in Fenris have now been integrated into
the main source tree of Bugzilla, so there's not much
reason to go grab the source. I leave this section of the
FAQ principally for historical interest, but unless Loki has further
input into Bugzilla's future, it will be deprecated in future versions
of the Guide.
</para>
</note>
</para>
<qandaentry>
<question>
......@@ -558,12 +571,14 @@
<qandadiv id="faq_phb">
<title>Pointy-Haired-Boss Questions</title>
<note>
<para>
The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :)
</para>
</note>
<para>
<note>
<para>
The title of this section doesn't mean you're a PHB -- it just means
you probably HAVE a PHB who wants to know this :)
</para>
</note>
</para>
<qandaentry>
<question>
......@@ -1228,7 +1243,7 @@
is unavailable.
</para>
<para>
This is now a configurable parameter called "sendmailparm", available
This is now a configurable parameter called "sendmailnow", available
from editparams.cgi.
</para>
</answer>
......@@ -1767,6 +1782,26 @@ A: Sure! Here ya go!
<qandaentry>
<question>
<para>
How can I change the default priority to a null value? For instance, have the default
priority be "---" instead of "P2"?
</para>
</question>
<answer>
<para>
This is well-documented here: <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=49862">
http://bugzilla.mozilla.org/show_bug.cgi?id=49862</ulink>. Ultimately, it's as easy
as adding the "---" priority field to your localconfig file in the appropriate area,
re-running checksetup.pl, and then changing the default priority in your browser using
"editparams.cgi". Hmm, now that I think about it, that is kind of a klunky way to handle
it, but for now it's what we have! Although the bug has been closed "resolved wontfix",
there may be a better way to handle this...
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>
What's the best way to submit patches? What guidelines should I follow?
</para>
</question>
......
docs/xml/integration.xml
View file @ 2d4d7c92
<!-- <!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 -->
......@@ -18,10 +18,31 @@
<section id="scm">
<title>Perforce SCM</title>
<para>
Richard Brooksby and his team have an integration tool
in public beta. You can find it at
<ulink url="http://www.ravenbrook.com/project/p4dt">
http://www.ravenbrook.com/project/p4dti</ulink>.
Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
You can find the main project page at
<ulink url="http://www.ravenbrook.com/project/p4dti/">
http://www.ravenbrook.com/project/p4dti</ulink>. "p4dti" is now an officially
supported product from Perforce, and you can find the "Perforce Public Depot"
p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
</para>
<para>
Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However,
p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate
patches for 2.12 will be out shortly. Check the project page regularly for updates, or
take the given patches and patch it manually. p4dti is designed to support multiple defect
trackers, and maintains its own documentation for it. Please consult the pages linked
above for further information.
</para>
<para>
Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or
to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you
have synchronization problems, the easiest way to avoid them is to only put the bug
information, comments, etc. into Bugzilla, and not into the Perforce change records.
They will link anyway; merely reference the bug ID fixed in your change description,
and put a comment into Bugzilla
giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology
question.
</para>
</section>
......
docs/xml/patches.xml
View file @ 2d4d7c92
......@@ -4,15 +4,17 @@
<title>Useful Patches and Utilities for Bugzilla</title>
<section id="setperl">
<title>The setperl.pl Utility</title>
<title>The setperl.csh Utility</title>
<para>
You can use the "setperl.pl" utility to quickly and easily
You can use the "setperl.csh" utility to quickly and easily
change the path to perl on all your Bugzilla files.
This is a C-shell script; if you do not have "csh" or "tcsh" in the search
path on your system, it will not work!
</para>
<procedure>
<step>
<para>
Download the "setperl.pl" utility to your Bugzilla
Download the "setperl.csh" utility to your Bugzilla
directory and make it executable.
</para>
<substeps>
......@@ -28,7 +30,7 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>wget -O setperl.pl 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
<command>wget -O setperl.csh 'http://bugzilla.mozilla.org/showattachment.cgi?attach_id=10795'</command>
</computeroutput>
</para>
</step>
......@@ -36,7 +38,7 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>chmod u+x setperl.pl</command>
<command>chmod u+x setperl.csh</command>
</computeroutput>
</para>
</step>
......@@ -80,8 +82,17 @@
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.pl /your/path/to/perl</command>
<command>./setperl.csh /your/path/to/perl</command>
</computeroutput>
<example>
<title>Using Setperl to set your perl path</title>
<para>
<computeroutput>
<prompt>bash#</prompt>
<command>./setperl.csh /usr/bin/perl</command>
</computeroutput>
</para>
</example>
</para>
</step>
</procedure>
......@@ -206,4 +217,21 @@
</para>
</section>
</appendix>
\ No newline at end of file
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
docs/xml/requiredsoftware.xml 0 → 100644
View file @ 2d4d7c92
<!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.org/">http://www.mysql.org/</ulink>
</para>
<para>
Perl: <ulink url="http://www.perl.org">http://www.perl.org/</ulink>
</para>
<para>
CPAN: <ulink url="http://www.cpan.org/">http://www.cpan.org/</ulink>
</para>
<para>
DBI Perl module:
<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>
Data::Dumper module:
<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>
</para>
<para>
MySQL related Perl modules:
<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>
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>
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>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
-->
docs/xml/using.xml
View file @ 2d4d7c92
......@@ -41,11 +41,14 @@ Chapter: Using Bugzilla
Bugzilla is one example of a class of programs called "Defect Tracking Systems",
or, more commonly, "Bug-Tracking Systems". Defect Tracking Systems allow individual or
groups of developers to keep track of outstanding bugs in their product effectively.
At the time Bugzilla was originally written, as a port from Netscape Communications'
"Bugsplat!" program to Perl from TCL, there were very few competitors in the market
for bug-tracking software. Most commercial defect-tracking software vendors at the
time charged enormous licensing fees. Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla) and
Bugzilla was originally written by Terry Weissman in a programming language called
"TCL", to replace a crappy
bug-tracking database used internally for Netscape Communications. Terry later ported
Bugzilla to
Perl from TCL, and in Perl it remains to this day.
Most commercial defect-tracking software vendors at the
time charged enormous licensing fees, and Bugzilla quickly became a favorite of the
open-source crowd (with its genesis in the open-source browser project, Mozilla). It
is now the de-facto standard defect-tracking system against which all others are
measured.
</para>
......@@ -89,7 +92,8 @@ Chapter: Using Bugzilla
</listitem>
<listitem>
<para>
integration with several automated software configuration management systems
available integration with automated software configuration management systems, including
Perforce and CVS.
</para>
</listitem>
<listitem>
......@@ -108,6 +112,12 @@ Chapter: Using Bugzilla
no internationalization, and dependence on some nonstandard libraries.
</para>
<para>
Some recent headway has been made on the query front, however. If you are using the latest
version of Bugzilla, you should see a "simple search" form on the default front page of
your Bugzilla install. Type in two or three search terms and you should pull up some
relevant information. This is also available as "queryhelp.cgi".
</para>
<para>
Despite these small problems, Bugzilla is very hard to beat. It is under <emphasis>very</emphasis>
active development to address the current issues, and a long-awaited overhaul in the form
of Bugzilla 3.0 is expected sometime later this year.
......@@ -147,7 +157,7 @@ Chapter: Using Bugzilla
Bugzilla is very adaptable to various situations. Known uses currently
include IT support queues, Systems Administration deployment management,
chip design and development problem tracking (both pre-and-post fabrication),
and software bug tracking for luminaries such as Redhat, Loki software,
and software and hardware bug tracking for luminaries such as Redhat, Loki software,
Linux-Mandrake, and VA Systems. Combined with systems such as CVS, Bonsai,
or Perforce SCM, Bugzilla provides a powerful, easy-to-use solution to
configuration management and replication problems
......@@ -178,7 +188,7 @@ Chapter: Using Bugzilla
</epigraph>
<para>
Bugzilla is a large and complex system. Describing how to use it
Bugzilla is a large, complex system. Describing how to use it
requires some time. If you are only interested in installing or administering
a Bugzilla installation, please consult the Installing and Administering
Bugzilla portions of this Guide. This section is principally aimed towards
......@@ -190,11 +200,24 @@ Chapter: Using Bugzilla
options available at the Bugzilla test installation,
<ulink url="http://landfill.tequilarista.org/">
landfill.tequilarista.org</ulink>.
<note>
<para>
Some people have run into difficulties completing this tutorial. If
you run into problems, please check the updated, online documentation available
at <ulink url="http://www.trilobyte.net/barnsons/">http://www.trilobyte.net/barnsons</ulink>.
If you're still stumped, please subscribe to the newsgroup and provide details of exactly
what's stumping you! If enough people complain, I'll have to fix it in the next
version of this Guide. You can subscribe to the newsgroup at
<ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">
news://news.mozilla.org/netscape.public.mozilla.webtools</ulink>
</para>
</note>
Although Landfill serves as a great introduction to Bugzilla, it does not offer
all the options you would have as a user on your own installation of Bugzilla,
nor can it do more than serve as a general introduction to Bugzilla.
However, please use it if you want to
follow this tutorial.
nor can it do more than serve as a general introduction to Bugzilla. Additionally,
Landfill often runs cutting-edge versions of Bugzilla for testing, so some things
may work slightly differently than mentioned here.
</para>
<section id="myaccount">
......@@ -714,6 +737,14 @@ Chapter: Using Bugzilla
<title>Email Settings</title>
<section id="notification">
<title>Email Notification</title>
<note>
<para>
The email notification settings described below have been obsoleted in Bugzilla 2.12, and
this section will be replaced with a comprehensive description of the amazing array of
new options at your disposal. However, in the meantime, throw this chunk out the window
and go crazy with goofing around with different notification options.
</para>
</note>
<para>
Ahh, here you can reduce or increase the amount of email sent you from Bugzilla!
In the drop-down "Notify me of changes to", select one of
......
docs/xml/variants.xml
View file @ 2d4d7c92
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
<chapter id="variants">
<title>Bugzilla Variants</title>
<note>
<para>
I <emphasis>know</emphasis> there are more variants than just RedHat Bugzilla out there.
Please help me get information about them, their project status, and benefits there
might be in using them or in using their code in main-tree Bugzilla.
</para>
</note>
<section id="rhbugzilla">
<title>Red Hat Bugzilla</title>
<para>
Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla,
on the planet.
One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a
database, as well as MySQL.
Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla,
<blockquote>
<literallayout>
Hello. I apologize that I am getting back to you so late. It has been difficult to keep
up with email this past week. I have checked out your updated documentation and I will
have to say very good work. A few notes and additions as follows.
(ed: from the FAQ)
>For the record, we are not using any template type implementation for the cosmetic changes
>maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have
>gotten a little carried away with it but the corporate types asked for a more standardized
>interface to match up with other projects relating to Red Hat web sites. A lot of other web
>based internal tools I am working on also look like Bugzilla.
This should probably be changed since we are now in fact using Text::Template for most
of the html rendering. You actually state this later in your numbered list.
Also number 6 contradicts number 8 where number 6 would be the most up to date status
on the Oracle port.
Additional Information:
-----------------------------
1. Comments are now stored in varchar fields of 4k in size each. If the comment is more
than 4k it is broken up into chunks and given a sort number so each comment can be re
assembled in the correct order. This was done because originally I was storing the comments
in a long datatype which unfortunately cannot be indexed or joined with another table. This
cause the search of text within the long description to be disabled for a long time. That
is now working and is nto showing any noticeble performance hit that I can tell.
2. Work is being started on internationalizing the Bugzilla source we have to allow our
Japanese customers to enter bug reports into a single bugzilla system. This will probably
be done by using the nvarchar data types supported by Oracle which allows storage of
double byte characters and also the use of the Accept-Language in the http header for
detection by Bugilla of which language to render.
3. Of course even more cosmetic changes. It is difficult to keep up with the ever
changing faces of www.redhat.com.
4. Some convenience enhancements in the administration utilities. And more integration
with other internal/external Red Hat web sites.
I hope this information may prove helpful for your documentation. Please contact
me if you have any more question or I can do anything else.
Regards
</literallayout>
</blockquote>
</para>
</section>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-namecase-general:t
sgml-general-insert-case:lower
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:2
sgml-indent-data:t
sgml-parent-document:nil
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
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