diff options
67 files changed, 12577 insertions, 9166 deletions
diff --git a/docs/README.docs b/docs/README.docs index 6b5d6ed61..4ccd7044d 100644 --- a/docs/README.docs +++ b/docs/README.docs @@ -38,12 +38,74 @@ point, but for now they are convenient and don't hurt anything. documentation. Please address comments and questions to the newsgroup: news://news.mozilla.org/netscape/public/mozilla/webtools . +========== +HOW TO SET UP YOUR OWN SGML EDITING ENVIRONMENT: +========== + +Trying to set up an SGML/XML Docbook editing environment the +first time can be a daunting task. +I use Linux-Mandrake, in part, because it has a fully-functional +SGML/XML Docbook editing environment included as part of the +distribution CD's. If you have easier instructions for how to +do this for a particular Linux distribution or platform, please +let the team know at the mailing list: mozilla-webtools@mozilla.org. + +The following text is taken nearly verbatim from +http://bugzilla.mozilla.org/show_bug.cgi?id=95970, where I gave +these instructions to someone who wanted the greater manageability +maintaining a document in Docbook brings: + +This is just off the top of my head, but here goes. Note some of these may +NOT be necessary, but I don't think they hurt anything by being installed. + +rpms: + +openjade +jadetex +docbook-dtd41-sgml +docbook-style-dsssl +docbook-dtd31-sgml +docbook-style-dsssl-doc +xemacs +psgml +sgml-tools +sgml-common + +Set up environment: + +in your .bashrc add this line (after installing above RPMS): +export SGML_CATALOG_FILES=/etc/sgml/catalog + +Download "ldp.dsl" from the Resources page on linuxdoc.org. This is the +stylesheet I use to get the HTML and text output. It works well, and has a +nice, consistent look with the rest of the linuxdoc documents. You'll have to +adjust the paths in ldp.dsl at the top of the file to reflect the actual +locations of your docbook catalog files. I created a directory, +/usr/share/sgml/docbook/ldp, and put the ldp.dsl file there. I then edited +ldp.dsl and changed two lines near the top: +<!ENTITY docbook.dsl SYSTEM "../dsssl-stylesheets-1.62/html/docbook.dsl" CDATA +dsssl> +...and... +<!ENTITY docbook.dsl SYSTEM "../dsssl-stylesheets-1.62/print/docbook.dsl" CDATA +dsssl> + +Note the difference is the top one points to the HTML docbook stylesheet, +and the next one points to the PRINT docbook stylesheet. + + You know, this sure looks awful involved. Anyway, once you have this in +place, add to your .bashrc: +export LDP_HOME=/usr/share/sgml/docbook/ldp + + I suggest xemacs for editing your SGML/XML Docbook documents. The darn +thing just works, and generally includes PSGML mode by default. You can +download psgml at http://www.sourceforge.net/projects/psgml. + +========== NOTES: +========== Here are the commands I use to maintain this documentation. - You MUST have DocBook 4.1 set up correctly in order for this to work, - but there's only a single REMARK tag that's incompatible with 3.1. - Maybe I'll downgrade to DocBook 3.1 to make your life easier... + You MUST have DocBook 4.1 set up correctly in order for this to work. Substitute your own path to "ldp.dsl" for "$LDP_HOME". diff --git a/docs/html/Bugzilla-Guide.html b/docs/html/Bugzilla-Guide.html index 5a6f96b55..fc7f40771 100644 --- a/docs/html/Bugzilla-Guide.html +++ b/docs/html/Bugzilla-Guide.html @@ -74,12 +74,6 @@ CLASS="ADDRESS" ></DIV ></DIV ><BR></SPAN -><H4 -CLASS="EDITEDBY" ->Edited by</H4 -><H3 -CLASS="EDITOR" ->I. P. Freely</H3 ><DIV CLASS="REVHISTORY" ><TABLE @@ -189,7 +183,7 @@ COLSPAN="3" ><DIV CLASS="ABSTRACT" ><A -NAME="AEN46" +NAME="AEN39" ></A ><P ></P @@ -210,6 +204,12 @@ NAME="AEN46" Bugzilla. </P ><P +> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT. + IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN + TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT + ADDITIONS TO THE GUIDE WRITTEN IN HTML! + </P +><P ></P ></DIV ></DIV @@ -333,7 +333,7 @@ HREF="#BUG_MANAGE" ><DT >2.4. <A HREF="#INIT4ME" ->What's in it for me?</A +>Where can I find my user preferences?</A ></DT ><DD ><DL @@ -406,12 +406,12 @@ HREF="#STEPBYSTEP" ><DL ><DT >3.2.1. <A -HREF="#AEN478" +HREF="#AEN486" >Introduction</A ></DT ><DT >3.2.2. <A -HREF="#AEN484" +HREF="#AEN492" >Installing the Prerequisites</A ></DT ><DT @@ -426,77 +426,80 @@ HREF="#INSTALL-PERL" ></DT ><DT >3.2.5. <A -HREF="#AEN537" +HREF="#AEN579" >DBI Perl Module</A ></DT ><DT >3.2.6. <A -HREF="#AEN574" +HREF="#AEN617" >Data::Dumper Perl Module</A ></DT ><DT >3.2.7. <A -HREF="#AEN578" +HREF="#AEN622" >MySQL related Perl Module Collection</A ></DT ><DT >3.2.8. <A -HREF="#AEN587" +HREF="#AEN631" >TimeDate Perl Module Collection</A ></DT ><DT >3.2.9. <A -HREF="#AEN590" +HREF="#AEN635" >GD Perl Module (1.8.3)</A ></DT ><DT >3.2.10. <A -HREF="#AEN596" +HREF="#AEN644" >Chart::Base Perl Module (0.99c)</A ></DT ><DT >3.2.11. <A -HREF="#AEN599" +HREF="#AEN648" >DB_File Perl Module</A ></DT ><DT >3.2.12. <A -HREF="#AEN602" +HREF="#AEN651" >HTTP Server</A ></DT ><DT >3.2.13. <A -HREF="#AEN616" +HREF="#AEN669" >Installing the Bugzilla Files</A ></DT ><DT >3.2.14. <A -HREF="#AEN636" +HREF="#AEN696" >Setting Up the MySQL Database</A ></DT ><DT >3.2.15. <A -HREF="#AEN675" ->Tweaking "localconfig"</A +HREF="#AEN743" +>Tweaking <TT +CLASS="FILENAME" +>localconfig</TT +></A ></DT ><DT >3.2.16. <A -HREF="#AEN704" +HREF="#AEN781" >Setting Up Maintainers Manually (Optional)</A ></DT ><DT >3.2.17. <A -HREF="#AEN713" +HREF="#AEN792" >The Whining Cron (Optional)</A ></DT ><DT >3.2.18. <A -HREF="#AEN723" +HREF="#AEN802" >Bug Graphs (Optional)</A ></DT ><DT >3.2.19. <A -HREF="#AEN735" +HREF="#AEN814" >Securing MySQL</A ></DT ></DL @@ -520,12 +523,12 @@ HREF="#GENINSTALL" ><DL ><DT >3.5.1. <A -HREF="#AEN837" +HREF="#AEN916" >Modifying Your Running System</A ></DT ><DT >3.5.2. <A -HREF="#AEN844" +HREF="#AEN923" >Upgrading From Previous Versions</A ></DT ><DT @@ -538,7 +541,20 @@ CLASS="FILENAME" ></DT ><DT >3.5.4. <A -HREF="#AEN865" +HREF="#MOD_THROTTLE" +><TT +CLASS="FILENAME" +>mod_throttle</TT +> and Security</A +></DT +><DT +>3.5.5. <A +HREF="#CONTENT_TYPE" +>Preventing untrusted Bugzilla content from executing malicious Javascript code</A +></DT +><DT +>3.5.6. <A +HREF="#AEN964" >UNIX Installation Instructions History</A ></DT ></DL @@ -691,7 +707,7 @@ HREF="#SCM" ><DT >5.4. <A HREF="#TINDERBOX" ->Tinderbox</A +>Tinderbox/Tinderbox2</A ></DT ></DL ></DD @@ -731,14 +747,14 @@ HREF="#DBDOC" ><DL ><DT >C.2.1. <A -HREF="#AEN2089" +HREF="#AEN2217" >Bugzilla Database Basics</A ></DT ><DD ><DL ><DT >C.2.1.1. <A -HREF="#AEN2118" +HREF="#AEN2246" >Bugzilla Database Tables</A ></DT ></DL @@ -755,7 +771,7 @@ HREF="#GRANTTABLES" ><DT >7. <A HREF="#VARIANTS" ->Bugzilla Variants</A +>Bugzilla Variants and Competitors</A ></DT ><DD ><DL @@ -764,6 +780,31 @@ HREF="#VARIANTS" HREF="#RHBUGZILLA" >Red Hat Bugzilla</A ></DT +><DT +>7.2. <A +HREF="#VARIANT_FENRIS" +>Loki Bugzilla (Fenris)</A +></DT +><DT +>7.3. <A +HREF="#VARIANT_ISSUEZILLA" +>Issuezilla</A +></DT +><DT +>7.4. <A +HREF="#VARIANT_SCARAB" +>Scarab</A +></DT +><DT +>7.5. <A +HREF="#VARIANT_PERFORCE" +>Perforce SCM</A +></DT +><DT +>7.6. <A +HREF="#VARIANT_SOURCEFORGE" +>SourceForge</A +></DT ></DL ></DD ><DT @@ -775,16 +816,24 @@ HREF="#PATCHES" ><DL ><DT >D.1. <A +HREF="#REWRITE" +>Apache <TT +CLASS="FILENAME" +>mod_rewrite</TT +> magic</A +></DT +><DT +>D.2. <A HREF="#SETPERL" >The setperl.csh Utility</A ></DT ><DT ->D.2. <A +>D.3. <A HREF="#CMDLINE" >Command-line Bugzilla Queries</A ></DT ><DT ->D.3. <A +>D.4. <A HREF="#QUICKSEARCH" >The Quicksearch Utility</A ></DT @@ -876,72 +925,73 @@ CLASS="LOT" ></DT ><DT >2-1. <A -HREF="#AEN297" +HREF="#AEN307" >Some Famous Software Versions</A ></DT ><DT >2-2. <A -HREF="#AEN307" +HREF="#AEN317" >Mozilla Webtools Components</A ></DT ><DT >3-1. <A -HREF="#AEN625" +HREF="#AEN685" >Setting up bonsaitools symlink</A ></DT ><DT >3-2. <A -HREF="#AEN697" +HREF="#AEN774" >Running checksetup.pl as the web user</A ></DT ><DT >3-3. <A -HREF="#AEN910" +HREF="#AEN1012" >Installing ActivePerl ppd Modules on Microsoft Windows</A ></DT ><DT >3-4. <A -HREF="#AEN1084" ->Removing encrypt() for Windows NT installations</A +HREF="#AEN1180" +>Removing encrypt() for Windows NT Bugzilla version + 2.12 or earlier</A ></DT ><DT >4-1. <A -HREF="#AEN1279" +HREF="#AEN1413" >Creating some Components</A ></DT ><DT >4-2. <A -HREF="#AEN1308" +HREF="#AEN1442" >Common Use of Versions</A ></DT ><DT >4-3. <A -HREF="#AEN1312" +HREF="#AEN1446" >A Different Use of Versions</A ></DT ><DT >4-4. <A -HREF="#AEN1340" +HREF="#AEN1474" >Using SortKey with Target Milestone</A ></DT ><DT >4-5. <A -HREF="#AEN1376" +HREF="#AEN1510" >When to Use Group Security</A ></DT ><DT >4-6. <A -HREF="#AEN1393" +HREF="#AEN1527" >Creating a New Group</A ></DT ><DT >D-1. <A -HREF="#AEN2193" +HREF="#AEN2360" >Using Setperl to set your perl path</A ></DT ><DT >1. <A -HREF="#AEN2389" +HREF="#AEN2602" >A Sample Product</A ></DT ></DL @@ -969,16 +1019,15 @@ NAME="ABOUTTHISGUIDE" document you see today. </P ><P -> Despite the lack of updates, Bugzilla is simply the best piece - of bug-tracking software the world has ever seen. This document - is intended to be the comprehensive guide to the installation, - administration, maintenance, and use of the Bugzilla - bug-tracking system. +> Bugzilla is simply the best piece of bug-tracking software the + world has ever seen. This document is intended to be the + comprehensive guide to the installation, administration, + maintenance, and use of the Bugzilla bug-tracking system. </P ><P > This release of the Bugzilla Guide is the <EM ->2.14.0</EM +>2.14</EM > release. It is so named that it may match the current version of Bugzilla. The numbering tradition stems from that used for many free software projects, @@ -1008,7 +1057,7 @@ TARGET="_top" of Bugzilla, as of this writing (August 10, 2001) is 2.14; if something were seriously wrong with that edition of the Guide, subsequent releases would receive an additional dotted-decimal - digit to indicate the update (2.14.0.1, 2.14.0.2, etc.). + digit to indicate the update (2.14.1, 2.14.2, etc.). Got it? Good. </P ><P @@ -1035,7 +1084,7 @@ NAME="COPYRIGHT" >1.2. Copyright Information</A ></H1 ><A -NAME="AEN76" +NAME="AEN70" ></A ><TABLE BORDER="0" @@ -1148,7 +1197,7 @@ NAME="NEWVERSIONS" >1.4. New Versions</A ></H1 ><P -> This is the 2.14.0 version of The Bugzilla Guide. If you are +> This is the 2.14 version of The Bugzilla Guide. If you are reading this from any source other than those below, please check one of these mirrors to make sure you are reading an up-to-date version of the Guide. @@ -1340,7 +1389,7 @@ NAME="CONVENTIONS" ><DIV CLASS="INFORMALTABLE" ><A -NAME="AEN135" +NAME="AEN129" ></A ><P ></P @@ -1682,7 +1731,7 @@ VALIGN="TOP" ><I ><P ><I ->What, Why, How, & What's in it for me?</I +>What, Why, How, & Where?</I ></P ></I ></TD @@ -1753,8 +1802,10 @@ system against which all others are measured. ></LI ><LI ><P -> available integration with automated software configuration management systems, including - Perforce and CVS +> available integration with automated software + configuration management systems, including Perforce and + CVS (through the Bugzilla email interface and + checkin/checkout scripts) </P ></LI ><LI @@ -1766,25 +1817,33 @@ system against which all others are measured. > </P ><P -> Despite its current robustness and popularity, however, Bugzilla - faces some near-term challenges, such as reliance on a single database, a lack of - abstraction of the user interface and program logic, verbose email bug - notifications, a powerful but daunting query interface, little reporting configurability, - problems with extremely large queries, some unsupportable bug resolution options, - no internationalization, and dependence on some nonstandard libraries. +> Despite its current robustness and popularity, Bugzilla faces + some near-term challenges, such as reliance on a single + database, a lack of abstraction of the user interface and + program logic, verbose email bug notifications, a powerful but + daunting query interface, little reporting configurability, + problems with extremely large queries, some unsupportable bug + resolution options, little internationalization (although non-US + character sets are accepted for comments), 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". +> Some recent headway has been made on the query front, however. + If you are using the latest version of Bugzilla, you should see + a <SPAN +CLASS="QUOTE" +>"simple search"</SPAN +> 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 +> Despite these small problems, Bugzilla is very hard to beat. It + is under <EM >very</EM -> - 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. +> active development to address + the current issues, and continually gains new features. </P ></DIV ><DIV @@ -1819,23 +1878,25 @@ VALIGN="TOP" ></TR ></TABLE ><P -> For many years, defect-tracking software has remained principally the domain - of large software development houses. Even then, most shops never bothered - with bug-tracking software, and instead simply relied on shared lists and - email to monitor the status of defects. This procedure is error-prone and - tends to cause those bugs judged least significant by developers to be +> For many years, defect-tracking software has remained + principally the domain of large software development houses. + Even then, most shops never bothered with bug-tracking software, + and instead simply relied on shared lists and email to monitor + the status of defects. This procedure is error-prone and tends + to cause those bugs judged least significant by developers to be dropped or ignored. </P ><P -> These days, many companies are finding that integrated defect-tracking - systems reduce downtime, increase productivity, and raise customer - satisfaction with their systems. Along with full disclosure, an open - bug-tracker allows manufacturers to keep in touch with their clients - and resellers, to communicate about problems effectively throughout - the data management chain. Many corporations have also discovered that - defect-tracking helps reduce costs by providing IT support accountability, - telephone support knowledge bases, and a common, well-understood system - for accounting for unusual system or software issues. +> These days, many companies are finding that integrated + defect-tracking systems reduce downtime, increase productivity, + and raise customer satisfaction with their systems. Along with + full disclosure, an open bug-tracker allows manufacturers to + keep in touch with their clients and resellers, to communicate + about problems effectively throughout the data management chain. + Many corporations have also discovered that defect-tracking + helps reduce costs by providing IT support accountability, + telephone support knowledge bases, and a common, well-understood + system for accounting for unusual system or software issues. </P ><P > But why should <EM @@ -1843,28 +1904,35 @@ VALIGN="TOP" > use Bugzilla? </P ><P -> 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 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 +> 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 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 </P ><P -> Bugzilla can dramatically increase the productivity and accountability - of individual employees by providing a documented workflow and positive - feedback for good performance. How many times do you wake up in the - morning, remembering that you were supposed to do *something* today, - but you just can't quite remember? Put it in Bugzilla, and you have a record - of it from which you can extrapolate milestones, predict product versions - for integration, and by using Bugzilla's e-mail integration features - be able to follow the discussion trail that led to critical decisions. +> Bugzilla can dramatically increase the productivity and + accountability of individual employees by providing a documented + workflow and positive feedback for good performance. How many + times do you wake up in the morning, remembering that you were + supposed to do <EM +>something</EM +> today, but you + just can't quite remember? Put it in Bugzilla, and you have a + record of it from which you can extrapolate milestones, predict + product versions for integration, and by using Bugzilla's e-mail + integration features be able to follow the discussion trail that + led to critical decisions. </P ><P -> Ultimately, Bugzilla puts the power in your hands to improve your value - to your employer or business while providing a usable framework for your natural - attention to detail and knowledge store to flourish. +> Ultimately, Bugzilla puts the power in your hands to improve + your value to your employer or business while providing a usable + framework for your natural attention to detail and knowledge + store to flourish. </P ></DIV ><DIV @@ -1900,19 +1968,21 @@ VALIGN="TOP" ></TABLE ><P > 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 - developing end-user mastery of Bugzilla, so you may fully enjoy the benefits - afforded by using this reliable open-source bug-tracking software. + 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 developing end-user + mastery of Bugzilla, so you may fully enjoy the benefits + afforded by using this reliable open-source bug-tracking + software. </P ><P -> Throughout this portion of the Guide, we will refer to user account - options available at the Bugzilla test installation, +> Throughout this portion of the Guide, we will refer to user + account options available at the Bugzilla test installation, <A HREF="http://landfill.tequilarista.org/" TARGET="_top" -> landfill.tequilarista.org</A +> landfill.tequilarista.org</A >. <DIV CLASS="NOTE" @@ -1935,32 +2005,29 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> Some people have run into difficulties completing this tutorial. If - you run into problems, please check the updated, online documentation available - at <A +> 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 +>. 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 +> news://news.mozilla.org/netscape.public.mozilla.webtools</A > </P ></TD ></TR ></TABLE ></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. Additionally, - Landfill often runs cutting-edge versions of Bugzilla for testing, so some things - may work slightly differently than mentioned here. +> 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. 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" @@ -1971,14 +2038,14 @@ NAME="MYACCOUNT" >2.3.1. Create a Bugzilla Account</A ></H2 ><P -> First things first! If you want to use Bugzilla, first you need to create - an account. Consult with the administrator responsible for your installation - of Bugzilla for the URL you should use to access it. - If you're test-driving the end-user Bugzilla experience, use this URL: - <A +> First things first! If you want to use Bugzilla, first you + need to create an account. Consult with the administrator + responsible for your installation of Bugzilla for the URL you + should use to access it. If you're test-driving the end-user + Bugzilla experience, use this URL: <A HREF="http://landfill.tequilarista.org/bugzilla-tip/" TARGET="_top" -> http://landfill.tequilarista.org/bugzilla-tip/</A +> http://landfill.tequilarista.org/bugzilla-tip/</A > </P ><P @@ -1992,23 +2059,40 @@ TYPE="1" ></LI ><LI ><P -> Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself) - in the spaces provided, then select the "Create Account" button. +> Enter your "E-mail address" and "Real Name" (or whatever + name you want to call yourself) in the spaces provided, + then select the "Create Account" button. </P ></LI ><LI ><P -> Within 5-10 minutes, you should receive an email to the address you provided above, - which contains your login name (generally the same as the email address), and - a password you can use to access your account. This password is randomly generated, - and should be changed at your nearest opportunity (we'll go into how to do it later). +> Within moments, you should receive an email to the address + you provided above, which contains your login name + (generally the same as the email address), and a password + you can use to access your account. This password is + randomly generated, and should be changed at your nearest + opportunity (we'll go into how to do it later). </P ></LI ><LI ><P -> Click the "Log In" link in the yellow area at the bottom of the page in your browser, - then enter your "E-mail address" and "Password" you just received into the spaces provided, - and select "Login". +> Click the <SPAN +CLASS="QUOTE" +>"Log In"</SPAN +> link in the yellow area at + the bottom of the page in your browser, then enter your + <SPAN +CLASS="QUOTE" +>"E-mail address"</SPAN +> and <SPAN +CLASS="QUOTE" +>"Password"</SPAN +> + you just received into the spaces provided, and select + <SPAN +CLASS="QUOTE" +>"Login"</SPAN +>. <DIV CLASS="NOTE" ><P @@ -2030,9 +2114,17 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> If you ever forget your password, you can come back to this page, enter your - "E-mail address", then select the "E-mail me a password" button to have your password - mailed to you again so that you can login. +> If you ever forget your password, you can come back to + this page, enter your <SPAN +CLASS="QUOTE" +>"E-mail address"</SPAN +>, + then select the <SPAN +CLASS="QUOTE" +>"E-mail me a password"</SPAN +> + button to have your password mailed to you again so + that you can login. </P ></TD ></TR @@ -2060,11 +2152,21 @@ ALT="Caution"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> Many modern browsers include an "Auto-Complete" or "Form Fill" feature to - remember the user names and passwords you type in at many sites. Unfortunately, - sometimes they attempt to "guess" what you will put in as your password, and guess - wrong. If you notice a text box is already filled out, please overwrite the contents - of the text box so you can be sure to input the correct information. +> Many modern browsers include an + <SPAN +CLASS="QUOTE" +>"Auto-Complete"</SPAN +> or <SPAN +CLASS="QUOTE" +>"Form + Fill"</SPAN +> feature to remember the user names and + passwords you type in at many sites. Unfortunately, + sometimes they attempt to guess what you will put in + as your password, and guess wrong. If you notice a + text box is already filled out, please overwrite the + contents of the text box so you can be sure to input + the correct information. </P ></TD ></TR @@ -2075,11 +2177,15 @@ VALIGN="TOP" ></LI ></OL ><P -> Congratulations! If you followed these directions, you now are the - proud owner of a user account on landfill.tequilarista.org (Landfill) or - your local Bugzilla install. You should now see in your browser a - page called the "Bugzilla Query Page". It may look daunting, but - with this Guide to walk you through it, you will master it in no time. +> Congratulations! If you followed these directions, you now + are the proud owner of a user account on + landfill.tequilarista.org (Landfill) or your local Bugzilla + install. You should now see in your browser a page called the + <SPAN +CLASS="QUOTE" +>"Bugzilla Query Page"</SPAN +>. It may look daunting, but with this + Guide to walk you through it, you will master it in no time. </P ></DIV ><DIV @@ -2091,16 +2197,27 @@ NAME="QUERY" >2.3.2. The Bugzilla Query Page</A ></H2 ><P -> The Bugzilla Query Page is the heart and soul of Bugzilla. It is the master - interface where you can find any bug report, comment, or patch currently in the Bugzilla - system. We'll go into how to create your own bug report later on. +> The Bugzilla Query Page is the heart and soul of the Bugzilla + user experience. It is the master interface where you can + find any bug report, comment, or patch currently in the + Bugzilla system. We'll go into how to create your own bug + report later on. </P ><P -> There are efforts underway to simplify query usage. If you have a local installation - of Bugzilla 2.12 or higher, you should have "quicksearch.html" available - to use and simplify your searches. There is also, or shortly will be, a helper - for the query interface, called "queryhelp.cgi". Landfill tends to run the latest code, - so these two utilities should be available there for your perusal. +> There are efforts underway to simplify query usage. If you + have a local installation of Bugzilla 2.12 or higher, you + should have <TT +CLASS="FILENAME" +>quicksearch.html</TT +> available to + use and simplify your searches. There is also a helper for + the query interface, called + <TT +CLASS="FILENAME" +>queryhelp.cgi</TT +>. Landfill tends to run the + latest code, so these two utilities should be available there + for your perusal. </P ><P > At this point, please visit the main Bugzilla site, @@ -2111,23 +2228,32 @@ TARGET="_top" >, to see a more fleshed-out query page. </P ><P -> The first thing you need to notice about the Bugzilla Query Page is that - nearly every box you see on your screen has a hyperlink nearby, explaining what - it is or what it does. Near the upper-left-hand corner of your browser window - you should see the word "Status" underlined. Select it. +> The first thing you need to notice about the Bugzilla Query + Page is that nearly every box you see on your screen has a + hyperlink nearby, explaining what it is or what it does. Near + the upper-left-hand corner of your browser window you should + see the word <SPAN +CLASS="QUOTE" +>"Status"</SPAN +> underlined. Select it. </P ><P -> Notice the page that popped up? Every underlined word you see on your screen - is a hyperlink that will take you to context-sensitive help. - Click around for a while, and learn what everything here does. To return - to the query interface after pulling up a help page, use the "Back" button in - your browser. +> Notice the page that popped up? Every underlined word you see + on your screen is a hyperlink that will take you to + context-sensitive help. Click around for a while, and learn + what everything here does. To return to the query interface + after pulling up a help page, use the <SPAN +CLASS="QUOTE" +>"Back"</SPAN +> + button in your browser. </P ><P -> I'm sure that after checking out the online help, you are now an Expert - on the Bugzilla Query Page. If, however, you feel you haven't mastered it yet, - let me walk you through making a few successful queries to find out what there - are in the Bugzilla bug-tracking system itself. +> I'm sure that after checking out the online help, you are now + an expert on the Bugzilla Query Page. If, however, you feel + you haven't mastered it yet, let me walk you through making a + few successful queries to find out what there are in the + Bugzilla bug-tracking system itself. </P ><P ></P @@ -2135,27 +2261,37 @@ TARGET="_top" TYPE="1" ><LI ><P -> Ensure you are back on the "Bugzilla Query Page" - Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys", - "Priority", or "Severity". The default query for "Status" is to find all bugs that - are NEW, ASSIGNED, or REOPENED, which is what we want. If you don't select anything - in the other 5 scrollboxes there, then you are saying that "any of these are OK"; - we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95" - OpSys (Operating System). You're smart, I think you have it figured out. +> Ensure you are back on the <SPAN +CLASS="QUOTE" +>"Bugzilla Query + Page"</SPAN +>. Do nothing in the boxes marked "Status", + "Resolution", "Platform", "OpSys", "Priority", or + "Severity". The default query for "Status" is to find all + bugs that are NEW, ASSIGNED, or REOPENED, which is what we + want. If you don't select anything in the other 5 + scrollboxes there, then you are saying that "any of these + are OK"; we're not locking ourselves into only finding + bugs on the "DEC" Platform, or "Windows 95" OpSys + (Operating System). You're smart, I think you have it + figured out. </P ><P > Basically, selecting <EM >anything</EM -> on the query page narrows your search - down. Leaving stuff unselected, or text boxes unfilled, broadens your search! +> on the + query page narrows your search down. Leaving stuff + unselected, or text boxes unfilled, broadens your search. </P ></LI ><LI ><P -> You see the box immediately below the top six boxes that contains an "Email" text box, - with the words "matching as", a drop-down selection box, then some checkboxes with - "Assigned To" checked by default? This allows you to filter your search down based upon - email address. Let's put my email address in there, and see what happens. +> You see the box immediately below the top six boxes that + contains an "Email" text box, with the words "matching + as", a drop-down selection box, then some checkboxes with + "Assigned To" checked by default? This allows you to + filter your search down based upon email address. Let's + put my email address in there, and see what happens. </P ><P > Type "barnboy@trilobyte.net" in the top Email text box. @@ -2163,24 +2299,29 @@ TYPE="1" ></LI ><LI ><P -> Let's narrow the search some more. Scroll down until you find the box with the word - "Program" over the top of it. This is where we can narrow our search down to only - specific products (software programs or product lines) in our Bugzilla database. - Please notice the box is a <EM +> Let's narrow the search some more. Scroll down until you + find the box with the word "Program" over the top of it. + This is where we can narrow our search down to only + specific products (software programs or product lines) in + our Bugzilla database. Please notice the box is a + <EM >scrollbox</EM ->. Using the down arrow on the - scrollbox, scroll down until you can see an entry called "Webtools". Select this entry. +>. Using the down arrow on + the scrollbox, scroll down until you can see an entry + called "Webtools". Select this entry. </P ></LI ><LI ><P -> Did you notice that some of the boxes to the right changed when you selected "Webtools"? - Every Program (or Product) has different Versions, Components, and Target Milestones associated - with it. A "Version" is the number of a software program. +> Did you notice that some of the boxes to the right changed + when you selected "Webtools"? Every Program (or Product) + has different Versions, Components, and Target Milestones + associated with it. A "Version" is the number of a + software program. <DIV CLASS="EXAMPLE" ><A -NAME="AEN297" +NAME="AEN307" ></A ><P ><B @@ -2189,42 +2330,45 @@ NAME="AEN297" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN299" +NAME="AEN309" ></A ><P ></P ><P -> Do you remember the hype in 1995 when Microsoft Windows 95(r) was released? - It may have been several years - ago, but Microsoft(tm) spent over $300 Million advertising this new Version of their - software. Three years later, they released Microsoft Windows 98(r), - another new version, to great fanfare, and then in 2000 quietly - released Microsoft Windows ME(Millenium Edition)(r). +> Do you remember the hype in 1995 when Microsoft + Windows 95(r) was released? It may have been several + years ago, but Microsoft(tm) spent over $300 Million + advertising this new Version of their software. + Three years later, they released Microsoft Windows + 98(r), another new version, to great fanfare, and + then in 2000 quietly released Microsoft Windows + ME(Millenium Edition)(r). </P ><P -> Software "Versions" help a manufacturer differentiate - their current product from their - previous products. Most do not identify their products - by the year they were released. - Instead, the "original" version of their software will - often be numbered "1.0", with - small bug-fix releases on subsequent tenths of a digit. In most cases, it's not - a decimal number; for instance, often 1.9 is an <EM +> Software "Versions" help a manufacturer + differentiate their current product from their + previous products. Most do not identify their + products by the year they were released. Instead, + the "original" version of their software will often + be numbered "1.0", with small bug-fix releases on + subsequent tenths of a digit. In most cases, it's + not a decimal number; for instance, often 1.9 is an + <EM >older</EM -> version - of the software than 1.11, - but is a <EM +> version of the software + than 1.11, but is a <EM >newer</EM -> version than 1.1.1. +> + version than 1.1.1. </P ><P -> In general, a "Version" in Bugzilla should refer to +> In general, a "Version" in Bugzilla should refer to <EM >released</EM -> - products, not products that have not yet been released - to the public. Forthcoming products - are what the Target Milestone field is for. +> products, not products + that have not yet been released to the public. + Forthcoming products are what the Target Milestone + field is for. </P ><P ></P @@ -2241,7 +2385,7 @@ NAME="AEN299" <DIV CLASS="EXAMPLE" ><A -NAME="AEN307" +NAME="AEN317" ></A ><P ><B @@ -2250,7 +2394,7 @@ NAME="AEN307" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN309" +NAME="AEN319" ></A ><P ></P @@ -2337,26 +2481,25 @@ BORDER="0" > </P ><P -> A "Milestone", or "Target Milestone" is a often a planned future "Version" of a - product. In many cases, though, Milestones simply represent significant dates for - a developer. Having certain features in your Product is frequently - tied to revenue (money) - the developer will receive if the features work by the time she - reaches the Target Milestone. - Target Milestones are a great tool to organize your time. - If someone will pay you $100,000 for - incorporating certain features by a certain date, - those features by that Milestone date become - a very high priority. Milestones tend to be highly malleable creatures, - though, that appear - to be in reach but are out of reach by the time the important day arrives. +> A "Milestone", or "Target Milestone" is a often a planned + future "Version" of a product. In many cases, though, + Milestones simply represent significant dates for a + developer. Having certain features in your Product is + frequently tied to revenue (money) the developer will + receive if the features work by the time she reaches the + Target Milestone. Target Milestones are a great tool to + organize your time. If someone will pay you $100,000 for + incorporating certain features by a certain date, those + features by that Milestone date become a very high + priority. Milestones tend to be highly malleable + creatures, though, that appear to be in reach but are out + of reach by the time the important day arrives. </P ><P -> The Bugzilla Project has set up Milestones for future - Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, - a Target Milestone can just as easily be a specific date, - code name, or weird alphanumeric - combination, like "M19". +> The Bugzilla Project has set up Milestones for future + Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a + Target Milestone can just as easily be a specific date, + code name, or weird alphanumeric combination, like "M19". </P ></LI ><LI @@ -2373,25 +2516,25 @@ BORDER="0" ></LI ><LI ><P -> Congratulations! You've completed your first Query, and have before you the Bug List - of the author of this Guide, Matthew P. Barnson (barnboy@trilobyte.net). If I'm - doing well, - you'll have a cryptic "Zarro Boogs Found" message on your screen. It is just - a happy hacker's way of saying "Zero Bugs Found". However, I am fairly certain I will +> Congratulations! You've completed your first Query, and + have before you the Bug List of the author of this Guide, + Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing + well, you'll have a cryptic "Zarro Boogs Found" message on + your screen. It is just a happy hacker's way of saying + "Zero Bugs Found". However, I am fairly certain I will always have some bugs assigned to me that aren't done yet, so you won't often see that message! </P ></LI ></OL ><P -> I encourage you to click the bug numbers in the left-hand column and examine - my bugs. Also notice that if you click the underlined - links near the top of this page, they do - not take you to context-sensitive help here, - but instead sort the columns of bugs on the screen! - When you need to sort your bugs by priority, severity, - or the people they are assigned to, this - is a tremendous timesaver. +> I encourage you to click the bug numbers in the left-hand + column and examine my bugs. Also notice that if you click the + underlined links near the top of this page, they do not take + you to context-sensitive help here, but instead sort the + columns of bugs on the screen! When you need to sort your bugs + by priority, severity, or the people they are assigned to, + this is a tremendous timesaver. </P ><P > A couple more interesting things about the Bug List page: @@ -2404,37 +2547,37 @@ BORDER="0" ><TD ><EM >Change Columns</EM ->: - by selecting this link, you can show all kinds - of information in the Bug List</TD +>: by selecting + this link, you can show all kinds of information in the + Bug List</TD ></TR ><TR ><TD ><EM >Change several bugs at once</EM ->: - If you have sufficient rights to change all - the bugs shown in the Bug List, you can mass-modify them. - This is a big time-saver.</TD +>: If + you have sufficient rights to change all the bugs shown in + the Bug List, you can mass-modify them. This is a big + time-saver.</TD ></TR ><TR ><TD ><EM >Send mail to bug owners</EM ->: - If you have many related bugs, you can request - an update from every person who owns the bugs in - the Bug List asking them the status.</TD +>: If you + have many related bugs, you can request an update from + every person who owns the bugs in the Bug List asking them + the status.</TD ></TR ><TR ><TD ><EM >Edit this query</EM ->: - If you didn't get exactly the results you were looking for, - you can return to the Query page through this link and make - small revisions to the query you just made so - you get more accurate results.</TD +>: If you didn't + get exactly the results you were looking for, you can + return to the Query page through this link and make small + revisions to the query you just made so you get more + accurate results.</TD ></TR ></TBODY ></TABLE @@ -2463,17 +2606,14 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> There are many more options to the Bugzilla Query Page - and the Bug List than I have shown you. - But this should be enough for you to learn to get around. - I encourage you to check out the - <A +> There are many more options to the Bugzilla Query Page and + the Bug List than I have shown you. But this should be + enough for you to learn to get around. I encourage you to + check out the <A HREF="http://www.mozilla.org/bugs/" TARGET="_top" >Bugzilla Home Page</A -> - to learn about the Anatomy - and Life Cycle of a Bug before continuing. +> to learn about the Anatomy and Life Cycle of a Bug before continuing. </P ></TD ></TR @@ -2522,30 +2662,33 @@ NAME="BUG_WRITING" >2.3.3.1. Writing a Great Bug Report</A ></H3 ><P -> Before we plunge into writing your first bug report, I encourage you to read - <A +> Before we plunge into writing your first bug report, I + encourage you to read some bug-writing guidelines. If you + are reading this document as part of a Bugzilla CVS checkout + or un-tarred Bugzilla distribution, you should be able to + read them by clicking <A +HREF="../../bugwritinghelp.html" +TARGET="_top" +>here</A +>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <A HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html" TARGET="_top" ->Mozilla.org's Bug - Writing Guidelines</A ->. While some of the advice is Mozilla-specific, the basic - principles of reporting Reproducible, Specific bugs, isolating the Product you are - using, the Version of the Product, the Component which failed, the Hardware Platform, and - Operating System you were using at the time of the failure go a long way toward ensuring accurate, - responsible fixes for the bug that bit you. +>http://www.mozilla.org/quality/bug-writing-guidelines.html</A +>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you. </P ><P -> While you are at it, why not learn how to find previously reported bugs? Mozilla.org - has published a great tutorial on finding duplicate bugs, available at - <A +> While you are at it, why not learn how to find previously + reported bugs? Mozilla.org has published a great tutorial + on finding duplicate bugs, available at <A HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html" TARGET="_top" -> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A +> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A >. </P ><P -> I realize this was a lot to read. However, understanding the mentality of writing - great bug reports will help us on the next part! +> I realize this was a lot to read. However, understanding + the mentality of writing great bug reports will help us on + the next part! </P ><P ></P @@ -2556,18 +2699,16 @@ TYPE="1" > Go back to <A HREF="http://landfill.tequilarista.org/bugzilla-tip/" TARGET="_top" -> http://landfill.tequilarista.org/bugzilla-tip/</A -> - in your browser. +> http://landfill.tequilarista.org/bugzilla-tip/</A +> in your browser. </P ></LI ><LI ><P -> Select the - <A +> Select the <A HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi" TARGET="_top" -> Enter a new bug report</A +> Enter a new bug report</A > link. </P ></LI @@ -2578,11 +2719,11 @@ TARGET="_top" ></LI ><LI ><P -> Now you should be at the "Enter Bug" form. - The "reporter" should have been automatically filled out - for you (or else Bugzilla prompted you to Log In again - -- you did keep the email with your username - and password, didn't you?). +> Now you should be at the "Enter Bug" form. The + "reporter" should have been automatically filled out for + you (or else Bugzilla prompted you to Log In again -- + you did keep the email with your username and password, + didn't you?). </P ></LI ><LI @@ -2592,36 +2733,37 @@ TARGET="_top" ></LI ><LI ><P -> Bugzilla should have made reasonable guesses, based upon your browser, - for the "Platform" and "OS" drop-down - boxes. If those are wrong, change them -- if you're on an SGI box - running IRIX, we want to know! +> Bugzilla should have made reasonable guesses, based upon + your browser, for the "Platform" and "OS" drop-down + boxes. If those are wrong, change them -- if you're on + an SGI box running IRIX, we want to know! </P ></LI ><LI ><P -> Fill in the "Assigned To" box with the email address you provided earlier. - This way you don't end up sending copies of your bug to lots of other people, - since it's just a test bug. +> Fill in the "Assigned To" box with the email address you + provided earlier. This way you don't end up sending + copies of your bug to lots of other people, since it's + just a test bug. </P ></LI ><LI ><P -> Leave the "CC" text box blank. - Fill in the "URL" box with "http://www.mozilla.org". +> Leave the "CC" text box blank. Fill in the "URL" box + with "http://www.mozilla.org". </P ></LI ><LI ><P -> Enter "The Bugzilla Guide" in the Summary text box, - and place any comments you have on this - tutorial, or the Guide in general, into the Description box. +> Enter "The Bugzilla Guide" in the Summary text box, and + place any comments you have on this tutorial, or the + Guide in general, into the Description box. </P ></LI ></OL ><P -> Voila! Select "Commit" and send in your bug report! - Next we'll look at resolving bugs. +> Voila! Select "Commit" and send in your bug report! Next + we'll look at resolving bugs. </P ></DIV ><DIV @@ -2633,10 +2775,10 @@ NAME="BUG_MANAGE" >2.3.3.2. Managing your Bug Reports</A ></H3 ><P -> OK, you should have a link to the bug you just created near the top of your page. - It should say - "Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX". - Select this link. +> OK, you should have a link to the bug you just created near + the top of your page. It should say "Bug XXXX posted", with + a link to the right saying "Back to BUG# XXXX". Select this + link. </P ><P ></P @@ -2644,35 +2786,32 @@ NAME="BUG_MANAGE" TYPE="1" ><LI ><P -> Scroll down a bit on the subsequent page, - until you see the "Resolve bug, changing resolution to (dropdown box). - Normally, you would - "Accept bug (change status to ASSIGNED)", fix it, and then resolve. - But in this case, we're - going to short-circuit the process because this wasn't a real bug. - Change the dropdown next to - "Resolve Bug" to "INVALID", make sure the radio button is - marked next to "Resolve Bug", then - click "Commit". +> Scroll down a bit on the subsequent page, until you see + the "Resolve bug, changing resolution to (dropdown box). + Normally, you would "Accept bug (change status to + ASSIGNED)", fix it, and then resolve. But in this case, + we're going to short-circuit the process because this + wasn't a real bug. Change the dropdown next to "Resolve + Bug" to "INVALID", make sure the radio button is marked + next to "Resolve Bug", then click "Commit". </P ></LI ><LI ><P -> Hey! It said it couldn't take the change in a big red box! - That's right, you must specify - a Comment in order to make this change. Select the "Back" - button in your browser, add a - Comment, then try Resolving the bug with INVALID status again. - This time it should work. +> Hey! It said it couldn't take the change in a big red + box! That's right, you must specify a Comment in order + to make this change. Select the "Back" button in your + browser, add a Comment, then try Resolving the bug with + INVALID status again. This time it should work. </P ></LI ></OL ><P > You have now learned the basics of Bugzilla navigation, - entering a bug, and bug maintenance. - I encourage you to explore these features, and see what you can do with them! - We'll spend no more time on individual Bugs or Queries from this point on, so you are - on your own there. + entering a bug, and bug maintenance. I encourage you to + explore these features, and see what you can do with them! + We'll spend no more time on individual Bugs or Queries from + this point on, so you are on your own there. </P ><P > But I'll give a few last hints! @@ -2682,41 +2821,29 @@ TYPE="1" HREF="http://bugzilla.mozilla.org/help.html" TARGET="_top" >CLUE</A -> - on the Query page - that will teach you more how to use the form. +> on the Query page that will teach you more how to use the form. </P ><P -> If you click the hyperlink on the - <A +> If you click the hyperlink on the <A HREF="http://bugzilla.mozilla.org/describecomponents.cgi" TARGET="_top" >Component</A -> - box of the Query page, you will be presented a form that will describe what all - the components are. +> box of the Query page, you will be presented a form that will describe what all the components are. </P ><P -> Possibly the most powerful feature of the Query page is the +> Possibly the most powerful feature of the Query page is the <A HREF="http://bugzilla.mozilla.org/booleanchart.html" TARGET="_top" >Boolean Chart</A -> section. - It's a bit confusing to use the first time, but can provide unparalleled - flexibility in your queries, - allowing you to build extremely powerful requests. +> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests. </P ><P -> Finally, you can build some nifty - <A +> Finally, you can build some nifty <A HREF="http://bugzilla.mozilla.org/reports.cgi" TARGET="_top" >Reports</A -> - using the "Bug Reports" link near the bottom of the query page, and also - available via the "Reports" link - at the footer of each page. +> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page. </P ></DIV ></DIV @@ -2727,7 +2854,7 @@ CLASS="SECTION" CLASS="SECTION" ><A NAME="INIT4ME" ->2.4. What's in it for me?</A +>2.4. Where can I find my user preferences?</A ></H1 ><TABLE BORDER="0" @@ -2757,15 +2884,13 @@ VALIGN="TOP" ></TR ></TABLE ><P -> Customized User Preferences offer tremendous versatility to - your individual Bugzilla experience. - Let's plunge into what you can do! The first step is to click - the "Edit prefs" link at the footer of each page once you - have logged in to - <A +> Customized User Preferences offer tremendous versatility to your + individual Bugzilla experience. Let's plunge into what you can + do! The first step is to click the "Edit prefs" link at the + footer of each page once you have logged in to <A HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1" TARGET="_top" -> Landfill</A +> Landfill</A >. </P ><DIV @@ -2778,16 +2903,29 @@ NAME="ACCOUNTSETTINGS" ></H2 ><P > On this page, you can change your basic Account Settings, - including your password and full name. - For security reasons, in order to change anything on this page you - must type your <EM + including your password and full name. For security reasons, + in order to change anything on this page you must type your + <EM >current</EM -> - password into the "Old Password" field. - If you wish to change your password, type the new password you - want into the "New Password" field and again into the "Re-enter - new password" field to ensure - you typed your new password correctly. Select the "Submit" button and you're done! +> password into the <SPAN +CLASS="QUOTE" +>"Old + Password"</SPAN +> field. If you wish to change your + password, type the new password you want into the <SPAN +CLASS="QUOTE" +>"New + Password"</SPAN +> field and again into the <SPAN +CLASS="QUOTE" +>"Re-enter + new password"</SPAN +> field to ensure you typed your new + password correctly. Select the <SPAN +CLASS="QUOTE" +>"Submit"</SPAN +> button + and you are done. </P ></DIV ><DIV @@ -2806,78 +2944,30 @@ CLASS="SECTION" NAME="NOTIFICATION" >2.4.2.1. Email Notification</A ></H3 -><DIV -CLASS="NOTE" -><P -></P -><TABLE -CLASS="NOTE" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" ><P -> 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 -></TD -></TR -></TABLE -></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 - <P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD -><EM ->All qualifying bugs</EM ->: sends you every change to every bug - where your name is somewhere on it, regardless of who changed it.</TD -></TR -><TR -><TD -><EM ->Only those bugs which I am listed in the CC line</EM ->: prevents - you from receiving mail for which you are the reporter,' - owner, or QA contact. If you are on the CC - list, presumably someone had a <EM ->good</EM -> - reason for you to get the email.</TD -></TR -><TR -><TD -><EM ->All qulifying bugs except those which I change</EM ->: - This is the default, and - a sensible setting. If someone else changes your bugs, you will get emailed, - but if you change bugs - yourself you will receive no notification of the change.</TD -></TR -></TBODY -></TABLE -><P -></P -> +> Here you can reduce or increase the amount of email sent you + from Bugzilla. Although this is referred to as + <SPAN +CLASS="QUOTE" +>"Advanced Email Filtering Options"</SPAN +>, they are, + in fact, the standard email filter set. All of them are + self-explanatory, but you can use the filters in interesting + ways. For instance, some people (notably Quality Assurance + personnel) often only care to receive updates regarding a + bug when the bug changes state, so they can track bugs on + their flow charts and know when it is time to pull the bug + onto a quality assurance platform for inspection. Other + people set up email gateways to + <A +HREF="#BONSAI" +>Bonsai, the Mozilla automated CVS management system</A +> or <A +HREF="#TINDERBOX" +>Tinderbox, the Mozilla automated build management system</A +>, and + restrict which types of Bugzilla information are fed to + these systems.. </P ></DIV ><DIV @@ -2909,27 +2999,30 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> This option may not be available in all Bugzilla installations, depending upon - the preferences of the systems administrator responsible for the setup of your Bugzilla. - However, if you really want this functionality, ask her to "enable newemailtech - in Params" - and "make it the default for all new users", referring her to the Administration section - of this Guide. +> This option may not be available in all Bugzilla + installations, depending upon the preferences of the + systems administrator responsible for the setup of your + Bugzilla. However, if you really want this functionality, + ask her to "enable newemailtech in Params" and "make it + the default for all new users", referring her to the + Administration section of this Guide. </P ></TD ></TR ></TABLE ></DIV ><P -> Disregard the warnings about "experimental and bleeding edge"; the code to handle email - in a cleaner manner than that historically used for Bugzilla is - quite robust and well-tested now. +> Disregard the warnings about "experimental and bleeding + edge"; the code to handle email in a cleaner manner than + that historically used for Bugzilla is quite robust and + well-tested now. </P ><P -> I recommend you enable the option, "Click here to sign up (and risk any bugs)". - Your email-box - will thank you for it. The fundamental shift in "newemailtech" is away from standard UNIX - "diff" output, which is quite ugly, to a prettier, better laid-out email. +> I recommend you enable the option, "Click here to sign up + (and risk any bugs)". Your email-box will thank you for it. + The fundamental shift in "newemailtech" is away from + standard UNIX "diff" output, which is quite ugly, to a + prettier, better laid-out email. </P ></DIV ><DIV @@ -2961,20 +3054,25 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> This option may not be available in all Bugzilla installations, depending upon - the preferences of the systems administrator responsible for the setup of your Bugzilla. - However, if you really want this functionality, ask her to "enable watchers in Params". +> This option may not be available in all Bugzilla + installations, depending upon the preferences of the + systems administrator responsible for the setup of your + Bugzilla. However, if you really want this functionality, + ask her to "enable watchers in Params". </P ></TD ></TR ></TABLE ></DIV ><P -> By entering user email names into the "Users to watch" text entry box, delineated by commas, - you can watch bugs of other users. This powerful functionality enables seamless transitions - as developers change projects, managers wish to get in touch with the issues faced by their - direct reports, or users go on vacation. If any of these three situations apply - to you, you will undoubtedly find this feature quite convenient. +> By entering user email names into the "Users to watch" text + entry box, delineated by commas, you can watch bugs of other + users. This powerful functionality enables seamless + transitions as developers change projects, managers wish to + get in touch with the issues faced by their direct reports, + or users go on vacation. If any of these three situations + apply to you, you will undoubtedly find this feature quite + convenient. </P ></DIV ></DIV @@ -3007,20 +3105,24 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> By default, this page is quite barren. However, go explore the Query Page some more; you will - find that you can store numerous queries on the server, so if you regularly run a particular query - it is just a drop-down menu away. On this page of Preferences, if you have many stored - queries you can elect to have them always one-click away! +> By default, this page is quite barren. However, go explore + the Query Page some more; you will find that you can store + numerous queries on the server, so if you regularly run a + particular query it is just a drop-down menu away. On this + page of Preferences, if you have many stored queries you can + elect to have them always one-click away! </P ></TD ></TR ></TABLE ></DIV ><P -> If you have many stored queries on the server, here you will find individual drop-downs for each - stored query. Each drop-down gives you the option of that query appearing on the footer of every - page in Bugzilla! This gives you powerful one-click access to any complex searches you may set up, - and is an excellent way to impress your boss... +> If you have many stored queries on the server, here you will + find individual drop-downs for each stored query. Each + drop-down gives you the option of that query appearing on the + footer of every page in Bugzilla! This gives you powerful + one-click access to any complex searches you may set up, and + is an excellent way to impress your boss... </P ><DIV CLASS="TIP" @@ -3043,13 +3145,18 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->By default, the "My Bugs" link appears at the bottom of each page. However, this query - gives you both the bugs you have reported, as well as those you are assigned. One of the most - common uses for this page is to remove the "My Bugs" link, replacing it with two other queries, - commonly called "My Bug Reports" and "My Bugs" (but only referencing bugs assigned to you). This - allows you to distinguish those bugs you have reported from those you are assigned. I commonly - set up complex Boolean queries in the Query page and link them to my footer in this page. When - they are significantly complex, a one-click reference can save hours of work.</P +>By default, the "My Bugs" link appears at the bottom of + each page. However, this query gives you both the bugs you + have reported, as well as those you are assigned. One of + the most common uses for this page is to remove the "My + Bugs" link, replacing it with two other queries, commonly + called "My Bug Reports" and "My Bugs" (but only referencing + bugs assigned to you). This allows you to distinguish those + bugs you have reported from those you are assigned. I + commonly set up complex Boolean queries in the Query page + and link them to my footer in this page. When they are + significantly complex, a one-click reference can save hours + of work.</P ></TD ></TR ></TABLE @@ -3064,11 +3171,12 @@ NAME="PERMISSIONSETTINGS" >2.4.4. Permissions</A ></H2 ><P -> This is a purely informative page which outlines your current permissions on - this installation of Bugzilla. If you have permissions to grant certain permissions to - other users, the "other users" link appears on this page as well as the footer. - For more information regarding user administration, please consult the Administration - section of this Guide. +> This is a purely informative page which outlines your current + permissions on this installation of Bugzilla. If you have + permissions to grant certain permissions to other users, the + "other users" link appears on this page as well as the footer. + For more information regarding user administration, please + consult the Administration section of this Guide. </P ></DIV ></DIV @@ -3081,16 +3189,14 @@ NAME="USINGBZ-CONC" >2.5. Using Bugzilla-Conclusion</A ></H1 ><P -> Thank you for reading through this portion of the Bugzilla Guide. I anticipate - it may not yet meet the needs of all readers. If you have additional comments or - corrections to make, please submit your contributions to the - <A +> Thank you for reading through this portion of the Bugzilla + Guide. I anticipate it may not yet meet the needs of all + readers. If you have additional comments or corrections to + make, please submit your contributions to the <A HREF="mailto://mozilla-webtools@mozilla.org" TARGET="_top" >mozilla-webtools</A -> - mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools - newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org +> mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org </P ></DIV ></DIV @@ -3267,7 +3373,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN478" +NAME="AEN486" >3.2.1. Introduction</A ></H2 ><P @@ -3298,7 +3404,7 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN484" +NAME="AEN492" >3.2.2. Installing the Prerequisites</A ></H2 ><DIV @@ -3437,6 +3543,111 @@ VALIGN="TOP" ></TABLE ></DIV > + <DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>Linux-Mandrake 8.0, the author's test system, includes + every required and optional library for Bugzilla. The + easiest way to install them is by using the + <TT +CLASS="FILENAME" +>urpmi</TT +> utility. If you follow these + commands, you should have everything you need for + Bugzilla, and <TT +CLASS="FILENAME" +>checksetup.pl</TT +> should + not complain about any missing libraries. You may already + have some of these installed.</P +><P +></P +><TABLE +BORDER="0" +><TBODY +><TR +><TD +><TT +CLASS="PROMPT" +>bash#</TT +><B +CLASS="COMMAND" +> urpmi + perl-mysql</B +></TD +></TR +><TR +><TD +><TT +CLASS="PROMPT" +>bash#</TT +><B +CLASS="COMMAND" +> urpmi + perl-chart</B +></TD +></TR +><TR +><TD +><TT +CLASS="PROMPT" +>bash#</TT +><B +CLASS="COMMAND" +> urpmi + perl-gd</B +></TD +></TR +><TR +><TD +><TT +CLASS="PROMPT" +>bash#</TT +><B +CLASS="COMMAND" +> urpmi + perl-MailTools</B +> (for Bugzilla email + integration)</TD +></TR +><TR +><TD +><TT +CLASS="PROMPT" +>bash#</TT +><B +CLASS="COMMAND" +> urpmi + apache-modules</B +></TD +></TR +></TBODY +></TABLE +><P +></P +></TD +></TR +></TABLE +></DIV +> </P ></DIV @@ -3449,26 +3660,79 @@ NAME="INSTALL-MYSQL" >3.2.3. Installing MySQL Database</A ></H2 ><P -> Visit MySQL homepage at http://www.mysql.com/ and grab the - latest stable release of the server. Both binaries and source - are available and which you get shouldn't matter. Be aware - that many of the binary versions of MySQL store their data - files in /var which on many installations (particularly common - with linux installations) is part of a smaller root partition. - If you decide to build from sources you can easily set the - dataDir as an option to configure. +> Visit MySQL homepage at <A +HREF="http://www.mysql.com" +TARGET="_top" +>www.mysql.com</A +> and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <TT +CLASS="FILENAME" +>/var</TT +> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <TT +CLASS="FILENAME" +>configure</TT +>. </P ><P -> If you've installed from source or non-package (RPM, deb, - etc.) binaries you'll want to make sure to add mysqld to your +> If you install from source or non-package (RPM, deb, etc.) + binaries you need to add + <I +CLASS="FIRSTTERM" +>mysqld</I +> to your init scripts so the server daemon will come back up whenever - your machine reboots. You also may want to edit those init - scripts, to make sure that mysqld will accept large packets. - By default, mysqld is set up to only accept packets up to 64K - long. This limits the size of attachments you may put on - bugs. If you add something like "-O max_allowed_packet=1M" to - the command that starts mysqld (or safe_mysqld), then you will - be able to have attachments up to about 1 megabyte. + your machine reboots. Further discussion of UNIX init + sequences are beyond the scope of this guide. + <DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>You should have your init script start + <I +CLASS="GLOSSTERM" +>mysqld</I +> with the ability to accept + large packets. By default, <TT +CLASS="FILENAME" +>mysqld</TT +> + only accepts packets up to 64K long. This limits the size + of attachments you may put on bugs. If you add <TT +CLASS="OPTION" +>-O + max_allowed_packet=1M</TT +> to the command that starts + <TT +CLASS="FILENAME" +>mysqld</TT +> (or + <TT +CLASS="FILENAME" +>safe_mysqld</TT +>), then you will be able + to have attachments up to about 1 megabyte.</P +></TD +></TR +></TABLE +></DIV +> + </P ><DIV CLASS="NOTE" @@ -3492,9 +3756,12 @@ ALIGN="LEFT" VALIGN="TOP" ><P > If you plan on running Bugzilla and MySQL on the same - machine, consider using the "--skip-networking" option in - the init script. This enhances security by preventing - network access to MySQL. + machine, consider using the <TT +CLASS="OPTION" +>--skip-networking</TT +> + option in the init script. This enhances security by + preventing network access to MySQL. </P ></TD ></TR @@ -3595,9 +3862,19 @@ ALIGN="LEFT" VALIGN="TOP" ><P > You can skip the following Perl module installation steps by - installing "Bundle::Bugzilla" from CPAN, which includes - them. All Perl module installation steps require you have an - active Internet connection. If you wish to use + installing <SPAN +CLASS="PRODUCTNAME" +>Bundle::Bugzilla</SPAN +> from + <A +HREF="#GLOSS_CPAN" +><I +CLASS="GLOSSTERM" +>CPAN</I +></A +>, which + includes them. All Perl module installation steps require + you have an active Internet connection. If you wish to use Bundle::Bugzilla, however, you must be using the latest version of Perl (at this writing, version 5.6.1) </P @@ -3631,7 +3908,7 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN537" +NAME="AEN579" >3.2.5. DBI Perl Module</A ></H2 ><P @@ -3645,7 +3922,10 @@ NAME="AEN537" > Like almost all Perl modules DBI can be found on the Comprehensive Perl Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a real tendency to bog down, so please use mirrors. The current location - at the time of this writing (02/17/99) can be found in Appendix A. + at the time of this writing can be found in <A +HREF="#DOWNLOADLINKS" +>Appendix B</A +>. </P ><P > Quality, general Perl module installation instructions can be found on @@ -3657,7 +3937,7 @@ NAME="AEN537" <DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN543" +NAME="AEN586" ></A ><P ></P @@ -3711,7 +3991,7 @@ VALIGN="TOP" <DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN550" +NAME="AEN593" ></A ><P ></P @@ -3804,7 +4084,7 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN574" +NAME="AEN617" >3.2.6. Data::Dumper Perl Module</A ></H2 ><P @@ -3814,9 +4094,14 @@ NAME="AEN574" hurt anything. </P ><P -> Data::Dumper is used by the MySQL-related Perl modules. It can be - found on CPAN (link in Appendix A) and can be installed by following - the same four step make sequence used for the DBI module. +> Data::Dumper is used by the MySQL-related Perl modules. It + can be found on CPAN (see <A +HREF="#DOWNLOADLINKS" +>Appendix B</A +>) and + can be + installed by following the same four step make sequence used + for the DBI module. </P ></DIV ><DIV @@ -3824,7 +4109,7 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN578" +NAME="AEN622" >3.2.7. MySQL related Perl Module Collection</A ></H2 ><P @@ -3870,18 +4155,21 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN587" +NAME="AEN631" >3.2.8. TimeDate Perl Module Collection</A ></H2 ><P -> Many of the more common date/time/calendar related Perl modules have - been grouped into a bundle similar to the MySQL modules bundle. This - bundle is stored on the CPAN under the name TimeDate. A link - link may be found in Appendix B, Software Download Links. - The component module we're - most interested in is the Date::Format module, but installing all of them - is probably a good idea anyway. The standard Perl module installation - instructions should work perfectly for this simple package. +> Many of the more common date/time/calendar related Perl + modules have been grouped into a bundle similar to the MySQL + modules bundle. This bundle is stored on the CPAN under the + name TimeDate (see link: <A +HREF="#DOWNLOADLINKS" +>Appendix B</A +>). The + component module we're most interested in is the Date::Format + module, but installing all of them is probably a good idea + anyway. The standard Perl module installation instructions + should work perfectly for this simple package. </P ></DIV ><DIV @@ -3889,21 +4177,26 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN590" +NAME="AEN635" >3.2.9. GD Perl Module (1.8.3)</A ></H2 ><P -> The GD library was written by Thomas Boutell a long while ago to - programatically generate images in C. Since then it's become almost a - defacto standard for programatic image construction. The Perl bindings - to it found in the GD library are used on a million web pages to generate - graphs on the fly. That's what bugzilla will be using it for so you'd - better install it if you want any of the graphing to work. +> The GD library was written by Thomas Boutell a long while + ago to programatically generate images in C. Since then it's + become the defacto standard for programatic image + construction. The Perl bindings to it found in the GD library + are used on millions of web pages to generate graphs on the + fly. That's what bugzilla will be using it for so you must + install it if you want any of the graphing to work. </P ><P -> Actually bugzilla uses the Graph module which relies on GD itself, - but isn't that always the way with OOP. At any rate, you can find the - GD library on CPAN (link in Appendix B, Software Download Links). +> Actually bugzilla uses the Graph module which relies on GD + itself. Isn't that always the way with object-oriented + programming? At any rate, you can find the GD library on CPAN + in <A +HREF="#DOWNLOADLINKS" +>Appendix B</A +>. </P ><DIV CLASS="NOTE" @@ -3926,10 +4219,19 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> The Perl GD library requires some other libraries that may or may not be - installed on your system, including "libpng" and "libgd". The full requirements - are listed in the Perl GD library README. Just realize that if compiling GD fails, - it's probably because you're missing a required library. +> The Perl GD library requires some other libraries that may + or may not be installed on your system, including + <TT +CLASS="CLASSNAME" +>libpng</TT +> and + <TT +CLASS="CLASSNAME" +>libgd</TT +>. The full requirements are + listed in the Perl GD library README. Just realize that if + compiling GD fails, it's probably because you're missing a + required library. </P ></TD ></TR @@ -3941,19 +4243,20 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN596" +NAME="AEN644" >3.2.10. Chart::Base Perl Module (0.99c)</A ></H2 ><P > The Chart module provides bugzilla with on-the-fly charting - abilities. It can be installed in the usual fashion after it has been - fetched from CPAN where it is found as the Chart-x.x... tarball in a - directory to be listed in Appendix B, "Software Download Links". - Note that as with the GD perl - module, only the version listed above, or newer, will work. - Earlier - versions used GIF's, which are no longer supported by the latest - versions of GD. + abilities. It can be installed in the usual fashion after it + has been fetched from CPAN where it is found as the + Chart-x.x... tarball, linked in <A +HREF="#DOWNLOADLINKS" +>Appendix B</A +>. Note that + as with the GD perl module, only the version listed above, or + newer, will work. Earlier versions used GIF's, which are no + longer supported by the latest versions of GD. </P ></DIV ><DIV @@ -3961,13 +4264,15 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN599" +NAME="AEN648" >3.2.11. DB_File Perl Module</A ></H2 ><P -> DB_File is a module which allows Perl programs to make use of the facilities provided by - Berkeley DB version 1.x. This module is required by collectstats.pl which is used for - bug charting. If you plan to make use of bug charting, you must install this module. +> DB_File is a module which allows Perl programs to make use + of the facilities provided by Berkeley DB version 1.x. This + module is required by collectstats.pl which is used for bug + charting. If you plan to make use of bug charting, you must + install this module. </P ></DIV ><DIV @@ -3975,40 +4280,124 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN602" +NAME="AEN651" >3.2.12. HTTP Server</A ></H2 ><P -> You have a freedom of choice here - Apache, Netscape or any other - server on UNIX would do. You can easily run the web server on a different - machine than MySQL, but need to adjust the MySQL "bugs" user permissions - accordingly. +> You have a freedom of choice here - Apache, Netscape or any + other server on UNIX would do. You can easily run the web + server on a different machine than MySQL, but need to adjust + the MySQL <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> user permissions accordingly. + <DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>I strongly recommend Apache as the web server to use. + The Bugzilla Guide installation instructions, in general, + assume you are using Apache. As more users use different + webservers and send me information on the peculiarities of + installing using their favorite webserver, I will provide + notes for them.</P +></TD +></TR +></TABLE +></DIV +> </P ><P -> You'll want to make sure that your web server will run any file - with the .cgi extension as a cgi and not just display it. If you're using - apache that means uncommenting the following line in the srm.conf file: - <TT -CLASS="COMPUTEROUTPUT" ->AddHandler cgi-script .cgi</TT +> You'll want to make sure that your web server will run any + file with the .cgi extension as a cgi and not just display it. + If you're using apache that means uncommenting the following + line in the srm.conf file: + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>AddHandler cgi-script .cgi + </PRE +></FONT +></TD +></TR +></TABLE > </P ><P -> With apache you'll also want to make sure that within the access.conf - file the line: - <TT -CLASS="COMPUTEROUTPUT" -> Options ExecCGI - </TT +> With apache you'll also want to make sure that within the + access.conf file the line: + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>Options ExecCGI</PRE +></FONT +></TD +></TR +></TABLE > - is in the stanza that covers the directories you intend to put the bugzilla - .html and .cgi files into. + is in the stanza that covers the directories into which + you intend to put the bugzilla .html and .cgi files. </P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" ><P -> If you are using a newer version of Apache, both of the above lines will be - (or will need to be) in the httpd.conf file, rather than srm.conf or - access.conf. +> Users of newer versions of Apache will generally find both + of the above lines will be in the httpd.conf file, rather + than srm.conf or access.conf. </P +></TD +></TR +></TABLE +></DIV ><DIV CLASS="WARNING" ><P @@ -4030,24 +4419,27 @@ ALT="Warning"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> There are two critical directories and a file that should not be a served by - the HTTP server. These are the <SPAN +> There are important files and directories that should not + be a served by the HTTP server. These are most files in the + <SPAN CLASS="QUOTE" >"data"</SPAN > and <SPAN CLASS="QUOTE" >"shadow"</SPAN -> - directories and the - <SPAN +> directories + and the <SPAN CLASS="QUOTE" >"localconfig"</SPAN -> file. You should configure your HTTP server to not serve - content from these files. Failure to do so will expose critical passwords - and other data. Please see <A +> file. You should + configure your HTTP server to not serve content from these + files. Failure to do so will expose critical passwords and + other data. Please see <A HREF="#HTACCESS" >.htaccess files and security</A -> for details. +> for details + on how to do this for Apache. I appreciate notes on how to + get this same functionality using other webservers. </P ></TD ></TR @@ -4059,22 +4451,25 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN616" +NAME="AEN669" >3.2.13. Installing the Bugzilla Files</A ></H2 ><P -> You should untar the Bugzilla files into a directory that you're - willing to make writable by the default web server user (probably - <SPAN +> You should untar the Bugzilla files into a directory that + you're willing to make writable by the default web server user + (probably <SPAN CLASS="QUOTE" >"nobody"</SPAN ->). You may decide to put the files off of the main web space - for your web server or perhaps off of /usr/local with a symbolic link - in the web space that points to the bugzilla directory. At any rate, - just dump all the files in the same place (optionally omitting the CVS - directories if they were accidentally tarred up with the rest of Bugzilla) - and make sure you can access the files in that directory through your - web server. +>). You may decide to put the + files off of the main web space for your web server or perhaps + off of <TT +CLASS="FILENAME" +>/usr/local</TT +> with a symbolic link in + the web space that points to the Bugzilla directory. At any + rate, just dump all the files in the same place, and make sure + you can access the files in that directory through your web + server. </P ><DIV CLASS="TIP" @@ -4098,55 +4493,79 @@ ALIGN="LEFT" VALIGN="TOP" ><P > If you symlink the bugzilla directory into your Apache's - HTML heirarchy, you may receive "Forbidden" errors unless you - add the "FollowSymLinks" directive to the <Directory> entry - for the HTML root. + HTML heirarchy, you may receive + <SPAN +CLASS="ERRORNAME" +>Forbidden</SPAN +> errors unless you add the + <SPAN +CLASS="QUOTE" +>"FollowSymLinks"</SPAN +> directive to the + <Directory> entry for the HTML root. </P ></TD ></TR ></TABLE ></DIV ><P -> Once all the files are in a web accessible directory, make that - directory writable by your webserver's user (which may require just - making it world writable). This is a temporary step until you run - the post-install <SPAN -CLASS="QUOTE" ->"checksetup.pl"</SPAN +> Once all the files are in a web accessible directory, make + that directory writable by your webserver's user. This is a + temporary step until you run the post-install + <TT +CLASS="FILENAME" +>checksetup.pl</TT > script, which locks down your - installation. - </P + installation. + </P ><P -> Lastly, you'll need to set up a symbolic link to /usr/bonsaitools/bin/perl - for the correct location of your perl executable (probably /usr/bin/perl). - Otherwise you must hack all the .cgi files to change where they look - for perl. To make future upgrades easier, you should use the symlink - approach. - <DIV +> Lastly, you'll need to set up a symbolic link to + <TT +CLASS="FILENAME" +>/usr/bonsaitools/bin/perl</TT +> for the correct + location of your perl executable (probably + <TT +CLASS="FILENAME" +>/usr/bin/perl</TT +>). Otherwise you must hack + all the .cgi files to change where they look for perl, or use + <A +HREF="#SETPERL" +>The setperl.csh Utility</A +>, found in + <A +HREF="#PATCHES" +>Useful Patches and Utilities for Bugzilla</A +>. I suggest using the symlink + approach for future release compatability. + <DIV CLASS="EXAMPLE" ><A -NAME="AEN625" +NAME="AEN685" ></A ><P ><B >Example 3-1. Setting up bonsaitools symlink</B ></P ><P -> Here's how you set up the Perl symlink on Linux to make Bugzilla work. - Your mileage may vary; if you are running on Solaris, you probably need to subsitute - <SPAN +> Here's how you set up the Perl symlink on Linux to make + Bugzilla work. Your mileage may vary. For some UNIX + operating systems, you probably need to subsitute + <SPAN CLASS="QUOTE" >"/usr/local/bin/perl"</SPAN -> for <SPAN +> for + <SPAN CLASS="QUOTE" >"/usr/bin/perl"</SPAN -> - below; if on certain other UNIX systems, - Perl may live in weird places like <SPAN +> below; if on certain other + UNIX systems, Perl may live in weird places like + <SPAN CLASS="QUOTE" >"/opt/perl"</SPAN >. As root, run these commands: - <TABLE + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -4156,19 +4575,19 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" ->bash# mkdir /usr/bonsaitools -bash# mkdir /usr/bonsaitools/bin +>bash# mkdir /usr/bonsaitools +bash# mkdir /usr/bonsaitools/bin bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl - </PRE + </PRE ></FONT ></TD ></TR ></TABLE > - </P + </P ></DIV > - <DIV + <DIV CLASS="TIP" ><P ></P @@ -4189,7 +4608,7 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> If you don't have root access to set this symlink up, +> If you don't have root access to set this symlink up, check out the <A HREF="#SETPERL" @@ -4197,9 +4616,8 @@ HREF="#SETPERL" >, listed in <A HREF="#PATCHES" >Useful Patches and Utilities for Bugzilla</A ->. - It will change the path to perl in all your Bugzilla files for you. - </P +>. It will change the path to perl in all your Bugzilla files for you. + </P ></TD ></TR ></TABLE @@ -4212,7 +4630,7 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN636" +NAME="AEN696" >3.2.14. Setting Up the MySQL Database</A ></H2 ><P @@ -4221,10 +4639,14 @@ NAME="AEN636" quality bug tracker. </P ><P -> First, you'll want to fix MySQL permissions to allow access from - Bugzilla. For the purpose of this Installation section, the Bugzilla username - will be "bugs", and will have minimal permissions. - +> First, you'll want to fix MySQL permissions to allow access + from Bugzilla. For the purpose of this Installation section, + the Bugzilla username will be <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +>, and will + have minimal permissions. + <DIV CLASS="WARNING" ><P @@ -4261,242 +4683,281 @@ CLASS="COMMAND" ></TABLE ></DIV > - </P + </P ><P -> Give the MySQL root user a password. MySQL passwords are - limited to 16 characters. - <P +> Give the MySQL root user a password. MySQL passwords are + limited to 16 characters. + <P ></P ><TABLE BORDER="0" ><TBODY ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" >bash#</TT -> - <B +> <B CLASS="COMMAND" ->mysql -u root mysql</B -> - </TT +>mysql + -u root mysql</B +> </TT > - </TD + </TD ></TR ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" >mysql></TT -> - <B +> <B CLASS="COMMAND" -> UPDATE user SET Password=PASSWORD ('new_password') - WHERE user='root'; - </B -> - </TT +> UPDATE user SET Password=PASSWORD ('new_password') + WHERE user='root'; </B +> </TT > - </TD + </TD ></TR ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" >mysql></TT -> - <B +> <B CLASS="COMMAND" ->FLUSH PRIVILEGES;</B -> - </TT +>FLUSH + PRIVILEGES;</B +> </TT > - </TD + </TD ></TR ></TBODY ></TABLE ><P ></P -> - From this point on, if you need to access MySQL as the - MySQL root user, you will need to use "mysql -u root -p" and - enter your new_password. Remember that MySQL user names have - nothing to do with Unix user names (login names). - </P +> From this point on, if you need to access + MySQL as the MySQL root user, you will need to use + <B +CLASS="COMMAND" +>mysql -u root -p</B +> and enter your + new_password. Remember that MySQL user names have nothing to + do with Unix user names (login names). + </P ><P -> Next, we create the "bugs" user, and grant sufficient - permissions for checksetup.pl, which we'll use later, to work - its magic. This also restricts the "bugs" user to operations - within a database called "bugs", and only allows the account - to connect from "localhost". Modify it to reflect your setup - if you will be connecting from another machine or as a different - user. - </P +> Next, we create the <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> user, and grant + sufficient permissions for checksetup.pl, which we'll use + later, to work its magic. This also restricts the + <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> user to operations within a database + called <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +>, and only allows the account to + connect from <SPAN +CLASS="QUOTE" +>"localhost"</SPAN +>. Modify it to reflect + your setup if you will be connecting from another machine or + as a different user. + </P ><P -> Remember to set bugs_password to some unique password. - <P +> Remember to set bugs_password to some unique password. + <P ></P ><TABLE BORDER="0" ><TBODY ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" >mysql></TT > - <B + <B CLASS="COMMAND" >GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, - ALTER,CREATE,DROP,REFERENCES - ON bugs.* TO bugs@localhost - IDENTIFIED BY 'bugs_password';</B + ALTER,CREATE,DROP,REFERENCES + ON bugs.* TO bugs@localhost + IDENTIFIED BY 'bugs_password';</B > - </TT + </TT > - </TD + </TD ></TR ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" -> mysql> - </TT +> mysql> + </TT > - <B + <B CLASS="COMMAND" -> FLUSH PRIVILEGES; - </B +> FLUSH PRIVILEGES; + </B > - </TT + </TT > - </TD + </TD ></TR ></TBODY ></TABLE ><P ></P > - </P + </P ><P -> Next, run the magic checksetup.pl script. (Many thanks to Holger - Schurig <holgerschurig@nikocity.de> for writing this script!) - It will make sure Bugzilla files and directories have reasonable - permissions, set up the "data" directory, and create all the MySQL - tables. - <P +> Next, run the magic checksetup.pl script. (Many thanks to + Holger Schurig <holgerschurig@nikocity.de> for writing + this script!) It will make sure Bugzilla files and directories + have reasonable permissions, set up the + <TT +CLASS="FILENAME" +>data</TT +> directory, and create all the MySQL + tables. + <P ></P ><TABLE BORDER="0" ><TBODY ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" >bash#</TT > - <B + <B CLASS="COMMAND" >./checksetup.pl</B +> </TT > - </TT -> - </TD + </TD ></TR ></TBODY ></TABLE ><P ></P -> - The first time you run it, it will create a file called "localconfig". - </P +> The first time you run it, it will create a + file called <TT +CLASS="FILENAME" +>localconfig</TT +>. + </P ></DIV ><DIV CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN675" ->3.2.15. Tweaking "localconfig"</A +NAME="AEN743" +>3.2.15. Tweaking <TT +CLASS="FILENAME" +>localconfig</TT +></A ></H2 ><P -> This file contains a variety of settings you may need to tweak including - how Bugzilla should connect to the MySQL database. - </P +> This file contains a variety of settings you may need to tweak including + how Bugzilla should connect to the MySQL database. + </P ><P -> The connection settings include: - <P +> The connection settings include: + <P ></P ><OL TYPE="1" ><LI ><P -> server's host: just use "localhost" if the MySQL server is - local - </P +> server's host: just use <SPAN +CLASS="QUOTE" +>"localhost"</SPAN +> if the + MySQL server is local + </P ></LI ><LI ><P -> database name: "bugs" if you're following these directions - </P +> database name: <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> if you're following + these directions + </P ></LI ><LI ><P -> MySQL username: "bugs" if you're following these directions - </P +> MySQL username: <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> if you're following + these directions + </P ></LI ><LI ><P -> Password for the "bugs" MySQL account above - </P +> Password for the <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> MySQL account above + </P ></LI ></OL > - </P + </P ><P -> You may also install .htaccess files that the Apache webserver will use - to restrict access to Bugzilla data files. See <A +> You should also install .htaccess files that the Apache + webserver will use to restrict access to Bugzilla data files. + See <A HREF="#HTACCESS" >.htaccess files and security</A >. - </P -><P -> Once you are happy with the settings, re-run checksetup.pl. On this - second run, it will create the database and an administrator account - for which you will be prompted to provide information. - </P + </P ><P -> When logged into an administrator account once Bugzilla is running, - if you go to the query page (off of the bugzilla main menu), you'll - find an 'edit parameters' option that is filled with editable treats. - </P +> Once you are happy with the settings, re-run + <TT +CLASS="FILENAME" +>checksetup.pl</TT +>. On this second run, it will + create the database and an administrator account for which + you will be prompted to provide information. + </P ><P -> Should everything work, you should have a nearly empty copy of the bug - tracking setup. - </P +> When logged into an administrator account once Bugzilla is + running, if you go to the query page (off of the Bugzilla main + menu), you'll find an <SPAN +CLASS="QUOTE" +>"edit parameters"</SPAN +> option + that is filled with editable treats. + </P ><P -> The second time around, checksetup.pl will stall if it is on a - filesystem that does not fully support file locking via flock(), such as - NFS mounts. This support is required for Bugzilla to operate safely with - multiple instances. If flock() is not fully supported, it will stall at: - <SPAN -CLASS="ERRORCODE" ->Now regenerating the shadow database for all bugs.</SPAN +> Should everything work, you will have a nearly empty Bugzilla + database and a newly-created <TT +CLASS="FILENAME" +>localconfig</TT > - <DIV + file in your Bugzilla root directory. + </P +><P +> <DIV CLASS="NOTE" ><P ></P @@ -4517,34 +4978,37 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> The second time you run checksetup.pl, you should become the - user your web server runs as, and that you ensure that you set the - "webservergroup" parameter in localconfig to match the web - server's group - name, if any. I believe, for the next release of Bugzilla, - this will - be fixed so that Bugzilla supports a "webserveruser" parameter - in localconfig - as well. - <DIV +> The second time you run checksetup.pl, you should become + the user your web server runs as, and that you ensure that + you set the <SPAN +CLASS="QUOTE" +>"webservergroup"</SPAN +> parameter in localconfig to + match the web server's group name, if any. I believe, + for the next release of Bugzilla, this will be fixed so + that Bugzilla supports a <SPAN +CLASS="QUOTE" +>"webserveruser"</SPAN +> parameter in + localconfig as well. + <DIV CLASS="EXAMPLE" ><A -NAME="AEN697" +NAME="AEN774" ></A ><P ><B >Example 3-2. Running checksetup.pl as the web user</B ></P ><P -> Assuming your web server runs as user "apache", - and Bugzilla is installed in - "/usr/local/bugzilla", here's one way to run checksetup.pl - as the web server user. - As root, for the <EM +> Assuming your web server runs as user "apache", and + Bugzilla is installed in "/usr/local/bugzilla", here's + one way to run checksetup.pl as the web server user. + As root, for the <EM >second run</EM -> - of checksetup.pl, do this: - <TABLE +> of + checksetup.pl, do this: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -4554,26 +5018,27 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" ->bash# chown -R apache:apache /usr/local/bugzilla -bash# su - apache -bash# cd /usr/local/bugzilla -bash# ./checksetup.pl - </PRE +> +bash# chown -R apache:apache /usr/local/bugzilla +bash# su - apache +bash# cd /usr/local/bugzilla +bash# ./checksetup.pl + </PRE ></FONT ></TD ></TR ></TABLE > - </P + </P ></DIV > - </P + </P ></TD ></TR ></TABLE ></DIV > - </P + </P ><DIV CLASS="NOTE" ><P @@ -4595,10 +5060,10 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> The checksetup.pl script is designed so that you can run +> The checksetup.pl script is designed so that you can run it at any time without causing harm. You should run it after any upgrade to Bugzilla. - </P + </P ></TD ></TR ></TABLE @@ -4609,16 +5074,16 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN704" +NAME="AEN781" >3.2.16. Setting Up Maintainers Manually (Optional)</A ></H2 ><P -> If you want to add someone else to every group by hand, you +> If you want to add someone else to every group by hand, you can do it by typing the appropriate MySQL commands. Run - '<TT -CLASS="COMPUTEROUTPUT" -> mysql -u root -p bugs</TT ->' You + <B +CLASS="COMMAND" +> mysql -u root -p bugs</B +> You may need different parameters, depending on your security settings. Then: <P @@ -4639,7 +5104,12 @@ CLASS="COMMAND" profiles set groupset=0x7fffffffffffffff where login_name = 'XXX';</B > </TT -> +> (yes, that's <EM +>fifteen</EM +><SPAN +CLASS="QUOTE" +>"f"</SPAN +>'s. </TD ></TR ></TBODY @@ -4654,7 +5124,7 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN713" +NAME="AEN792" >3.2.17. The Whining Cron (Optional)</A ></H2 ><P @@ -4740,7 +5210,7 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN723" +NAME="AEN802" >3.2.18. Bug Graphs (Optional)</A ></H2 ><P @@ -4797,7 +5267,7 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN735" +NAME="AEN814" >3.2.19. Securing MySQL</A ></H2 ><P @@ -5270,7 +5740,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN837" +NAME="AEN916" >3.5.1. Modifying Your Running System</A ></H2 ><P @@ -5303,7 +5773,7 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN844" +NAME="AEN923" >3.5.2. Upgrading From Previous Versions</A ></H2 ><P @@ -5420,33 +5890,132 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN865" ->3.5.4. UNIX Installation Instructions History</A +NAME="MOD_THROTTLE" +>3.5.4. <TT +CLASS="FILENAME" +>mod_throttle</TT +> and Security</A +></H2 +><P +> It is possible for a user, by mistake or on purpose, to access + the database many times in a row which can result in very slow + access speeds for other users. If your Bugzilla installation + is experiencing this problem , you may install the Apache + module <TT +CLASS="FILENAME" +>mod_throttle</TT +> which can limit + connections by ip-address. You may download this module at + <A +HREF="http://www.snert.com/Software/Throttle/" +TARGET="_top" +>http://www.snert.com/Software/Throttle/</A +>. Follow the instructions to install into your Apache install. <EM +>This module only functions with the Apache web server!</EM +>. You may use the <B +CLASS="COMMAND" +>ThrottleClientIP</B +> command provided by this module to accomplish this goal. See the <A +HREF="http://www.snert.com/Software/Throttle/" +TARGET="_top" +>Module Instructions</A +> for more information. </P +></DIV +><DIV +CLASS="SECTION" +><HR><H2 +CLASS="SECTION" +><A +NAME="CONTENT_TYPE" +>3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</A +></H2 +><P +>It is possible for a Bugzilla to execute malicious + Javascript code. Due to internationalization concerns, we are + unable to incorporate the code changes necessary to fulfill + the CERT advisory requirements mentioned in <A +HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3" +TARGET="_top" +>http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A +>. Executing the following code snippet from a UNIX command shell will rectify the problem if your Bugzilla installation is intended for an English-speaking audience. As always, be sure your Bugzilla installation has a good backup before making changes, and I recommend you understand what the script is doing before executing it. </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ + do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' >$i.tmp; \ + mv $i.tmp $i; done + </PRE +></FONT +></TD +></TR +></TABLE +></P +><P +> All this one-liner command does is search for all instances of + <SPAN +CLASS="QUOTE" +>"Content-type: text/html"</SPAN +> and replaces it with + <SPAN +CLASS="QUOTE" +>"Content-Type: text/html; charset=ISO-8859-1"</SPAN +>. + This specification prevents possible Javascript attacks on the + browser, and is suggested for all English-speaking sites. For + non-english-speaking Bugzilla sites, I suggest changing + <SPAN +CLASS="QUOTE" +>"ISO-8859-1"</SPAN +>, above, to <SPAN +CLASS="QUOTE" +>"UTF-8"</SPAN +>. + </P +></DIV +><DIV +CLASS="SECTION" +><HR><H2 +CLASS="SECTION" +><A +NAME="AEN964" +>3.5.6. UNIX Installation Instructions History</A ></H2 ><P -> This document was originally adapted from the Bonsai installation - instructions by Terry Weissman <terry@mozilla.org>. +> This document was originally adapted from the Bonsai + installation instructions by Terry Weissman + <terry@mozilla.org>. </P ><P -> The February 25, 1999 re-write of this page was done by Ry4an Brase - <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt, - Martin Pool, & Dan Mosedale (But don't send bug reports to them; - report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi , - project Webtools, component Bugzilla). +> The February 25, 1999 re-write of this page was done by Ry4an + Brase <ry4an@ry4an.org>, with some edits by Terry + Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But + don't send bug reports to them; report them using bugzilla, at + http://bugzilla.mozilla.org/enter_bug.cgi , project Webtools, + component Bugzilla). </P ><P -> This document was heavily modified again Wednesday, March 07 2001 to - reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The - securing MySQL section should be changed to become standard procedure - for Bugzilla installations. +> This document was heavily modified again Wednesday, March 07 + 2001 to reflect changes for Bugzilla 2.12 release by Matthew + P. Barnson. The securing MySQL section should be changed to + become standard procedure for Bugzilla installations. </P ><P -> Finally, the README in its entirety was marked up in SGML and included into - the Guide on April 24, 2001 by Matt Barnson. Since that time, it's undergone - extensive modification as Bugzilla grew. +> Finally, the README in its entirety was marked up in SGML and + included into the Guide on April 24, 2001 by Matt Barnson. + Since that time, it's undergone extensive modification as + Bugzilla grew. </P ><P -> Comments from people using this Guide for the first time are particularly welcome. +> Comments from people using this Guide for the first time are + particularly welcome. </P ></DIV ></DIV @@ -5511,7 +6080,7 @@ VALIGN="TOP" of the <A HREF="#INSTALLATION" ->Chapter 3</A +>Bugzilla Installation</A > section while performing your Win32 installation. </P @@ -5522,13 +6091,14 @@ HREF="#INSTALLATION" be a <EM >very</EM > skilled Windows Systems - Administrator with both strong troubleshooting abilities and - a high tolerance for pain. Bugzilla on NT requires hacking - source code and implementing some advanced utilities. What - follows is the recommended installation procedure for Win32; - additional suggestions are provided in <A + Administrator with strong troubleshooting abilities, a high + tolerance for pain, and moderate perl skills. Bugzilla on NT + requires hacking source code and implementing some advanced + utilities. What follows is the recommended installation + procedure for Win32; additional suggestions are provided in + <A HREF="#FAQ" ->The Bugzilla FAQ</A +>Appendix A</A >. </P ></TD @@ -5544,9 +6114,23 @@ TYPE="1" > Install <A HREF="http://www.apache.org/" TARGET="_top" ->Apache Web Server</A +>Apache Web + Server</A +> for Windows, and copy the Bugzilla files + somewhere Apache can serve them. Please follow all the + instructions referenced in <A +HREF="#INSTALLATION" +>Bugzilla Installation</A +> + regarding your Apache configuration, particularly + instructions regarding the <SPAN +CLASS="QUOTE" +>"AddHandler"</SPAN > - for Windows. + parameter and <SPAN +CLASS="QUOTE" +>"ExecCGI"</SPAN +>. </P ><DIV CLASS="NOTE" @@ -5569,13 +6153,13 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> You may also use Internet Information Server or Personal Web - Server for this purpose. However, setup is slightly more - difficult. If ActivePerl doesn't seem to handle your file - associations correctly (for .cgi and .pl files), please - consult <A +> You may also use Internet Information Server or Personal + Web Server for this purpose. However, setup is quite + different. If ActivePerl doesn't seem to handle your + file associations correctly (for .cgi and .pl files), + please consult <A HREF="#FAQ" ->The Bugzilla FAQ</A +>Appendix A</A >. </P ><P @@ -5671,7 +6255,7 @@ CLASS="COMMAND" ><DIV CLASS="EXAMPLE" ><A -NAME="AEN910" +NAME="AEN1012" ></A ><P ><B @@ -5911,13 +6495,63 @@ CLASS="FILENAME" this line: </P ><P -> "my $webservergid = getgrnam($my_webservergroup); " +> <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>my $webservergid = getgrnam($my_webservergroup); + </PRE +></FONT +></TD +></TR +></TABLE +> </P ><P > to </P ><P -> "my $webservergid = $my_webservergroup; " +> <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>my $webservergid = $my_webservergroup; + </PRE +></FONT +></TD +></TR +></TABLE +> +or the name of the group you wish to own the files explicitly: + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>my $webservergid = 'Administrators' + </PRE +></FONT +></TD +></TR +></TABLE +> </P ></LI ><LI @@ -6226,7 +6860,31 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->The code above needs testing as well to make sure it is correct.</P +> Some have found success using the commercial product, + <SPAN +CLASS="PRODUCTNAME" +>Windmail</SPAN +>. + You could try replacing your sendmail calls with: + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log"; + </PRE +></FONT +></TD +></TR +></TABLE +> + or something to that effect. + </P ></TD ></TR ></TABLE @@ -6387,9 +7045,9 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> This step is completely optional if you are using IIS or - another web server which only decides on an interpreter - based upon the file extension (.pl), rather than the +> This step is optional if you are using IIS or another + web server which only decides on an interpreter based + upon the file extension (.pl), rather than the <SPAN CLASS="QUOTE" >"shebang"</SPAN @@ -6487,10 +7145,11 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> If you are using IIS 5.0 or higher, you must add cgi +> If you are using IIS or Personal Web Server, you must add cgi relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), - such as: <TABLE + such as: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -6549,18 +7208,17 @@ VALIGN="TOP" ><P > From Andrew Pearson: <A -NAME="AEN1062" +NAME="AEN1169" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> "You can make Bugzilla work with Personal Web Server for - Windows 98 and higher, as well as for IIS 4.0. Microsoft has - information available at - <A -HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP" +> You can make Bugzilla work with Personal Web Server for + Windows 98 and higher, as well as for IIS 4.0. + Microsoft has information available at <A +HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP" TARGET="_top" -> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A +> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A > </P ><P @@ -6610,79 +7268,25 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</P -><A -NAME="AEN1072" -></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 -><FONT -COLOR="#000000" -><PRE -CLASS="PROGRAMLISTING" ->my $webservergid = getgrnam($my_webservergroup); - </PRE -></FONT -></TD -></TR -></TABLE -><P ->to</P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="PROGRAMLISTING" ->my $webservergid = 'Administrators' - </PRE -></FONT -></TD -></TR -></TABLE -></LI -><LI -><P -> I then ran checksetup.pl - </P -></LI -><LI -><P -> I removed all the encrypt() - <DIV +> If attempting to run Bugzilla 2.12 or older, you will need + to remove encrypt() calls from the Perl source. This is + <EM +>not necessary</EM +> for Bugzilla 2.13 and + later. + <DIV CLASS="EXAMPLE" ><A -NAME="AEN1084" +NAME="AEN1180" ></A ><P ><B ->Example 3-4. Removing encrypt() for Windows NT installations</B +>Example 3-4. Removing encrypt() for Windows NT Bugzilla version + 2.12 or earlier</B ></P ><P -> Replace this: - <TABLE +> Replace this: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -6692,17 +7296,17 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" ->SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . - SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); -my $enteredcryptpwd = FetchOneColumn(); - </PRE +> +SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); +my $enteredcryptpwd = FetchOneColumn(); + </PRE ></FONT ></TD ></TR ></TABLE > - with this: - <TABLE + with this: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -6712,125 +7316,18 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" ->my $enteredcryptpwd = $enteredpwd - </PRE +> +my $enteredcryptpwd = $enteredpwd + </PRE ></FONT ></TD ></TR ></TABLE > - in cgi.pl. - </P + 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 -><FONT -COLOR="#000000" -><PRE -CLASS="PROGRAMLISTING" -> -open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log"; - </PRE -></FONT -></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 -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="TIP" -><P -></P -><TABLE -CLASS="TIP" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/tip.gif" -HSPACE="5" -ALT="Tip"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P -> This was some late breaking information from Jan Evert. Sorry for the lack of formatting. - </P -><P -CLASS="LITERALLAYOUT" ->I'm busy installing bugzilla on a WinNT machine and I thought I'd notify you<br> -at this moment of the commments I have to section 2.2.1 of the bugzilla<br> -guide (at http://www.trilobyte.net/barnsons/html/).<br> -<br> -Step 1:<br> -I've used apache, installation is really straightforward.<br> -After reading the Unix installation instructions, I found that it is<br> -necessary to add the ExecCGI option to the bugzilla directory. Also the<br> -'AddHandler' line for .cgi is by default commented out.<br> -<br> -Step 3: although just a detail, 'ppm install <module%gt;' will also work<br> -(without .ppd). And, it can also download these automatically from<br> -ActiveState.<br> -<br> -Step 4: although I have cygwin installed, it seems that it is not necessary.<br> -On my machine cygwin is not in the PATH and everything seems to work as<br> -expected.<br> -However, I've not used everything yet.<br> -<br> -Step 6: the 'bugs_password' given in SQL command d needs to be edited into<br> -localconfig later on (Step 7) if the password is not empty. I've also edited<br> -it into globals.pl, but I'm not sure that is needed. In both places, the<br> -variable is named db_pass.<br> -<br> -Step 8: all the sendmail replacements mentioned are not as simple as<br> -described there. Since I am not familiar (yet) with perl, I don't have any<br> -mail working yet.<br> -<br> -Step 9: in globals.pl the encrypt() call can be replaced by just the<br> -unencrypted password. In CGI.pl, the complete SQL command can be removed.<br> -<br> -Step 11: I've only changed the #! lines in *.cgi. I haven't noticed problems<br> -with the system() call yet.<br> -There seem to be only four system() called programs: processmail.pl (handled<br> -by step 10), syncshadowdb (which should probably get the same treatment as<br> -processmail.pl), diff and mysqldump. The last one is only needed with the<br> -shadowdb feature (which I don't use).<br> -<br> -There seems to be one step missing: copying the bugzilla files somehwere<br> -that apache can serve them.<br> -<br> -Just noticed the updated guide... Brian's comment is new. His first comment<br> -will work, but opens up a huge security hole.<br> </P ></TD ></TR @@ -6852,11 +7349,20 @@ COLOR="RED" do with it? </FONT ><P -> So you followed the installation instructions 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 business needs to be to setup the - operating parameters for bugzilla. +> So you followed <SPAN +CLASS="QUOTE" +>"<A +HREF="#INSTALLATION" +>Bugzilla Installation</A +>"</SPAN +> to the + letter, and logged into Bugzilla for the very first time with your + super-duper god account. You sit, contentedly staring at the + Bugzilla Query Screen, the worst of the whole mad business of + installing this terrific program behind you. It seems, though, you + have nothing yet to query! Your first act of business should be to + setup the operating parameters for Bugzilla so you can get busy + getting data into your bug tracker. </P ><DIV CLASS="SECTION" @@ -6867,8 +7373,8 @@ NAME="POSTINSTALL-CHECK" >4.1. Post-Installation Checklist</A ></H1 ><P -> After installation, follow the checklist below to ensure that - you have a successful installation. If you do not see a +> After installation, follow the checklist below to help ensure + that you have a successful installation. If you do not see a recommended setting for a parameter, consider leaving it at the default while you perform your initial tests on your Bugzilla setup. @@ -6879,20 +7385,34 @@ 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. +> Bring up <TT +CLASS="FILENAME" +>editparams.cgi</TT +> in your web + browser. This should be available as the <SPAN +CLASS="QUOTE" +>"edit + parameters"</SPAN +> link from any Bugzilla screen once you + have logged in. </P ></LI ><LI ><P -> Set "maintainer" to <EM +>The <SPAN +CLASS="QUOTE" +>"maintainer"</SPAN +> is the email address of + the person responsible for maintaining this Bugzilla + installation. The maintainer need not be a valid Bugzilla + user. Error pages, error emails, and administrative mail + will be sent with the maintainer as the return email + address.</P +><P +> Set <SPAN +CLASS="QUOTE" +>"maintainer"</SPAN +> to <EM >your</EM > email address. This allows Bugzilla's error messages to display your email @@ -6901,28 +7421,59 @@ TARGET="_top" ></LI ><LI ><P -> Set "urlbase" to the URL reference for your Bugzilla - installation. If your bugzilla query page is at - http://www.foo.com/bugzilla/query.cgi, your url base is - http://www.foo.com/bugzilla/ +>The <SPAN +CLASS="QUOTE" +>"urlbase"</SPAN +> parameter defines the fully + qualified domain name and web server path to your Bugzilla + installation.</P +><P +> For example, if your bugzilla query page is + http://www.foo.com/bugzilla/query.cgi, set your + <SPAN +CLASS="QUOTE" +>"urlbase"</SPAN +> is http://www.foo.com/bugzilla/. </P ></LI ><LI ><P +><SPAN +CLASS="QUOTE" +>"usebuggroups"</SPAN +> dictates whether or not to + implement group-based security for Bugzilla. If set, + Bugzilla bugs can have an associated groupmask defining + which groups of users are allowed to see and edit the + bug.</P +><P > Set "usebuggroups" to "on" <EM >only</EM > if you - need to restrict access to products. I suggest leaving this - parameter <EM + may wish to restrict access to products. I suggest leaving + this parameter <EM >off</EM -> while initially testing - your Bugzilla. +> while initially + testing your Bugzilla. </P ></LI ><LI ><P -> Set "usebuggroupsentry" to "on" if you want to restrict - access to products. Once again, if you are simply testing +> <SPAN +CLASS="QUOTE" +>"usebuggroupsentry"</SPAN +>, when set to + <SPAN +CLASS="QUOTE" +>"on"</SPAN +>, requires that all bugs have an associated + groupmask when submitted. This parameter is made for those + installations where product isolation is a necessity. + </P +><P +> Set "usebuggroupsentry" to "on" if you absolutely need to + restrict access to bugs from the moment they are submitted + through resolution. 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. @@ -6930,6 +7481,24 @@ TARGET="_top" ></LI ><LI ><P +> You run into an interesting problem when Bugzilla reaches a + high level of continuous activity. MySQL supports only + table-level write locking. What this means is that if + someone needs to make a change to a bug, they will lock the + entire table until the operation is complete. Locking for + write also blocks reads until the write is complete. The + <SPAN +CLASS="QUOTE" +>"shadowdb"</SPAN +> parameter was designed to get around + this limitation. While only a single user is allowed to + write to a table at a time, reads can continue unimpeded on + a read-only shadow copy of the database. Although your + database size will double, a shadow database can cause an + enormous performance improvement when implemented on + extremely high-traffic Bugzilla databases. + </P +><P > Set "shadowdb" to "bug_shadowdb" if you will be running a *very* large installation of Bugzilla. The shadow database enables many simultaneous users to read and write to the @@ -6956,9 +7525,13 @@ ALIGN="LEFT" VALIGN="TOP" ><P > Enabling "shadowdb" can adversely affect the stability - of your installation of Bugzilla. You may frequently - need to manually synchronize your databases, or schedule - nightly syncs via "cron" + of your installation of Bugzilla. You should regularly + check that your database is in sync. It is often + advisable to force a shadow database sync nightly via + <SPAN +CLASS="QUOTE" +>"cron"</SPAN +>. </P ></TD ></TR @@ -6970,7 +7543,13 @@ VALIGN="TOP" > to use it, and have repeatedly run into the problem it was designed to solve -- very long wait times while attempting to commit - a change to the database. + a change to the database. Mozilla.org began needing + <SPAN +CLASS="QUOTE" +>"shadowdb"</SPAN +> when they reached around 40,000 + Bugzilla users with several hundred Bugzilla bug changes and + comments per day. </P ><P > If you use the "shadowdb" option, it is only natural that @@ -6981,6 +7560,40 @@ VALIGN="TOP" ></LI ><LI ><P +><SPAN +CLASS="QUOTE" +>"headerhtml"</SPAN +>, <SPAN +CLASS="QUOTE" +>"footerhtml"</SPAN +>, + <SPAN +CLASS="QUOTE" +>"errorhtml"</SPAN +>, <SPAN +CLASS="QUOTE" +>"bannerhtml"</SPAN +>, and + <SPAN +CLASS="QUOTE" +>"blurbhtml"</SPAN +> are all templates which control + display of headers, footers, errors, banners, and additional + data. We could go into some detail regarding the usage of + these, but it is really best just to monkey around with them + a bit to see what they do. I strongly recommend you copy + your <TT +CLASS="FILENAME" +>data/params</TT +> file somewhere safe + before playing with these values, though. If they are + changed dramatically, it may make it impossible for you to + display Bugzilla pages to fix the problem until you have + restored your <TT +CLASS="FILENAME" +>data/params</TT +> file.</P +><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", @@ -7009,10 +7622,11 @@ VALIGN="TOP" > 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 settings at - the defaults initially. +> any other code on the page, + except the CONTENT-TYPE header sent by the Bugzilla + engine. 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 ></TD ></TR @@ -7023,6 +7637,14 @@ VALIGN="TOP" ></LI ><LI ><P +><SPAN +CLASS="QUOTE" +>"passwordmail"</SPAN +> is rather simple. Every + time a user creates an account, the text of this parameter + is read as the text to send to the new user along with their + password message.</P +><P > Add any text you wish to the "passwordmail" parameter box. For instance, many people choose to use this box to give a quick training blurb about how to use Bugzilla at your site. @@ -7030,19 +7652,48 @@ VALIGN="TOP" ></LI ><LI ><P -> 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 +><SPAN +CLASS="QUOTE" +>"useqacontact"</SPAN +> allows you to define an + email address for each component, in addition to that of the + default owner, who will be sent carbon copies of incoming + bugs. The critical difference between a QA Contact and an + Owner is that the QA Contact follows the component. If you + reassign a bug from component A to component B, the QA + Contact for that bug will change with the reassignment, + regardless of owner.</P +><P +><SPAN +CLASS="QUOTE" +>"usestatuswhiteboard"</SPAN +> defines whether you + wish to have a free-form, overwritable field associated with + each bug. The advantage of the Status Whiteboard is that it + can be deleted or modified with ease, and provides an + easily-searchable field for indexing some bugs that have + some trait in common. Many people will put <SPAN +CLASS="QUOTE" +>"help + wanted"</SPAN +>, <SPAN +CLASS="QUOTE" +>"stalled"</SPAN +>, or <SPAN +CLASS="QUOTE" +>"waiting + on reply from somebody"</SPAN +> messages into the Status + Whiteboard field so those who peruse the bugs are aware of + their status even more than that which can be indicated by + the Resolution fields.</P ><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 Quality Assurance and/or Release Engineering team, but they may not be needed - for smaller installations. + for many smaller installations. </P ></LI ><LI @@ -7052,14 +7703,26 @@ VALIGN="TOP" 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 installation instructions, or set this - value to "0". + value to "0" (never whine). </P ></LI ><LI ><P +><SPAN +CLASS="QUOTE" +>"commenton"</SPAN +> fields allow you to dictate + what changes can pass without comment, and which must have a + comment from the person who changed them. Often, + administrators will allow users to add themselves to the CC + list, accept bugs, or change the Status Whiteboard without + adding a comment as to their reasons for the change, yet + require that most other changes come with an + explanation.</P +><P > Set the "commenton" options according to your site policy. It is a wise idea to require comments when users resolve, - reassign, or reopen bugs. + reassign, or reopen bugs at the very least. <DIV CLASS="NOTE" ><P @@ -7096,11 +7759,38 @@ VALIGN="TOP" ></LI ><LI ><P -> Set "supportwatchers" to "On". This feature is helpful for - team leads to monitor progress in their respective areas, - and can offer many other benefits, such as allowing a - developer to pick up a former engineer's bugs without - requiring her to change all the information in the bug. +>The <SPAN +CLASS="QUOTE" +>"supportwatchers"</SPAN +> option can be an + exceptionally powerful tool in the hands of a power Bugzilla + user. By enabling this option, you allow users to receive + email updates whenever other users receive email updates. + This is, of course, subject to the groupset restrictions on + the bug; if the <SPAN +CLASS="QUOTE" +>"watcher"</SPAN +> would not normally be + allowed to view a bug, the watcher cannot get around the + system by setting herself up to watch the bugs of someone + with bugs outside her priveleges. She would still only + receive email updates for those bugs she could normally + view.</P +><P +>For Bugzilla sites which require strong inter-Product + security to prevent snooping, watchers are not a good + idea.</P +><P +> However, for most sites you should set + <SPAN +CLASS="QUOTE" +>"supportwatchers"</SPAN +> to "On". This feature is + helpful for team leads to monitor progress in their + respective areas, and can offer many other benefits, such as + allowing a developer to pick up a former engineer's bugs + without requiring her to change all the information in the + bug. </P ></LI ></OL @@ -7177,6 +7867,15 @@ CLASS="PROMPT" login name)"; </B > </P +><P +>Yes, that is <EM +>fourteen</EM +> + <SPAN +CLASS="QUOTE" +>"f"</SPAN +>'s. A whole lot of f-ing going on if you + want to create a new administator.</P ></TD ></TR ></TABLE @@ -7285,13 +7984,16 @@ VALIGN="TOP" right-hand side of the text entry box. You can match what you type as a case-insensitive substring (the default) of all users on your system, a case-sensitive - regular expression (please see the "man regexp" manual - page for details on regular expression syntax), or a - <EM + regular expression (please see the <B +CLASS="COMMAND" +>man + regexp</B +> manual page for details on regular + expression syntax), or a <EM >reverse</EM -> regular expression match, - where every user name which does NOT match the regular - expression is selected. +> + regular expression match, where every user name which + does NOT match the regular expression is selected. </P ></TD ></TR @@ -7334,10 +8036,17 @@ VALIGN="TOP" >not</EM > send an email informing them of their username and - password. In general, it is preferable to log out and - use the "New Account" button to create users, as it - will pre-populate all the required fields and also - notify the user of her account name and password. + password. While useful for creating dummy accounts + (watchers which shuttle mail to another system, for + instance, or email addresses which are a mailing + list), in general it is preferable to log out and use + the <SPAN +CLASS="QUOTE" +>"New Account"</SPAN +> button to create users, + as it will pre-populate all the required fields and + also notify the user of her account name and + password. </P ></TD ></TR @@ -7386,6 +8095,15 @@ VALIGN="TOP" > Don't disable your own administrative account, or you will hate life! </P +><P +>At this time, <SPAN +CLASS="QUOTE" +>"Disabled Text"</SPAN +> does not + prevent a user from using the email interface. If you + have the email interface enabled, they can still + continue to submit bugs and comments that way. We need + a patch to fix this.</P ></TD ></TR ></TABLE @@ -7459,9 +8177,8 @@ VALIGN="TOP" ><P > <EM >Password</EM ->: You will only see - asterisks in versions of Bugzilla newer than 2.10 or - early 2.11. You can change the user password here. +>: You can change the user + password here. It is normal to only see asterisks. </P ></LI ><LI @@ -7897,7 +8614,7 @@ NAME="COMPONENTS" <DIV CLASS="EXAMPLE" ><A -NAME="AEN1279" +NAME="AEN1413" ></A ><P ><B @@ -7906,7 +8623,7 @@ NAME="AEN1279" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1281" +NAME="AEN1415" ></A ><P ></P @@ -8052,7 +8769,7 @@ NAME="VERSIONS" <DIV CLASS="EXAMPLE" ><A -NAME="AEN1308" +NAME="AEN1442" ></A ><P ><B @@ -8061,7 +8778,7 @@ NAME="AEN1308" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1310" +NAME="AEN1444" ></A ><P ></P @@ -8083,7 +8800,7 @@ NAME="AEN1310" <DIV CLASS="EXAMPLE" ><A -NAME="AEN1312" +NAME="AEN1446" ></A ><P ><B @@ -8092,7 +8809,7 @@ NAME="AEN1312" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1314" +NAME="AEN1448" ></A ><P ></P @@ -8229,7 +8946,7 @@ TYPE="1" ><DIV CLASS="EXAMPLE" ><A -NAME="AEN1340" +NAME="AEN1474" ></A ><P ><B @@ -8238,7 +8955,7 @@ NAME="AEN1340" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1342" +NAME="AEN1476" ></A ><P ></P @@ -8452,7 +9169,7 @@ NAME="GROUPS" <DIV CLASS="EXAMPLE" ><A -NAME="AEN1376" +NAME="AEN1510" ></A ><P ><B @@ -8461,7 +9178,7 @@ NAME="AEN1376" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1378" +NAME="AEN1512" ></A ><P ></P @@ -8578,7 +9295,7 @@ TYPE="1" <DIV CLASS="EXAMPLE" ><A -NAME="AEN1393" +NAME="AEN1527" ></A ><P ><B @@ -8587,7 +9304,7 @@ NAME="AEN1393" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1395" +NAME="AEN1529" ></A ><P ></P @@ -9031,7 +9748,23 @@ NAME="BONSAI" >5.1. Bonsai</A ></H1 ><P ->We need Bonsai integration information.</P +>Bonsai is a web-based tool for managing <A +HREF="#CVS" +>CVS, the Concurrent Versioning System</A +> + . Using Bonsai, administrators can control open/closed status + of trees, query a fast relational database back-end for change, + branch, and comment information, and view changes made since the + last time the tree was closed. These kinds of changes cause the + engineer responsible to be <SPAN +CLASS="QUOTE" +>"on the hook"</SPAN +> (include + cool URL link here for Hook policies at mozilla.org). Bonsai + also includes gateways to <A +HREF="#TINDERBOX" +>Tinderbox, the Mozilla automated build management system</A +> and Bugzilla </P ></DIV ><DIV CLASS="SECTION" @@ -9042,7 +9775,23 @@ NAME="CVS" >5.2. CVS</A ></H1 ><P ->CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</P +>CVS integration is best accomplished, at this point, using + the Bugzilla Email Gateway. There have been some files + submitted to allow greater CVS integration, but we need to make + certain that Bugzilla is not tied into one particular software + management package.</P +><P +> Follow the instructions in the FAQ for enabling Bugzilla e-mail + integration. Ensure that your check-in script sends an email to + your Bugzilla e-mail gateway with the subject of <SPAN +CLASS="QUOTE" +>"[Bug + XXXX]"</SPAN +>, and you can have CVS check-in comments append + to your Bugzilla bug. If you have your check-in script include + an @resolution field, you can even change the Bugzilla bug + state. + </P ></DIV ><DIV CLASS="SECTION" @@ -9053,36 +9802,28 @@ NAME="SCM" >5.3. Perforce SCM</A ></H1 ><P -> You can find the project page for Bugzilla and Teamtrack Perforce integration at: - <A +> You can find the project page for Bugzilla and Teamtrack + Perforce integration (p4dti) at: <A 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 +> http://www.ravenbrook.com/project/p4dti</A +> . <SPAN +CLASS="QUOTE" +>"p4dti"</SPAN +> 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 +> 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. +> Integration of Perforce with Bugzilla, once patches are applied, + is seamless. Perforce replication information will appear below + the comments of each bug. Be certain you have a matching set of + patches for the Bugzilla version you are installing. p4dti is + designed to support multiple defect trackers, and maintains its + own documentation for it. Please consult the pages linked above + for further information. </P ></DIV ><DIV @@ -9091,10 +9832,10 @@ CLASS="SECTION" CLASS="SECTION" ><A NAME="TINDERBOX" ->5.4. Tinderbox</A +>5.4. Tinderbox/Tinderbox2</A ></H1 ><P ->We need Tinderbox integration information</P +>We need Tinderbox integration information.</P ></DIV ></DIV ><DIV @@ -9120,11 +9861,12 @@ CLASS="SYNOPSIS" ></TR ></TABLE ><P ->The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do +> The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do not have more information about it right now, and most of what went into the "future" section is now present. That stuff was blue-sky a year ago; MattyT should have me a new document - sometime...</P + sometime... + </P ></DIV ><DIV CLASS="APPENDIX" @@ -9145,66 +9887,65 @@ HREF="#FAQ_GENERAL" ><DL ><DT >A.1.1. <A -HREF="#AEN1481" +HREF="#AEN1620" > Where can I find information about Bugzilla?</A ></DT ><DT >A.1.2. <A -HREF="#AEN1487" +HREF="#AEN1626" > What license is Bugzilla distributed under? </A ></DT ><DT >A.1.3. <A -HREF="#AEN1493" +HREF="#AEN1632" > How do I get commercial support for Bugzilla? </A ></DT ><DT >A.1.4. <A -HREF="#AEN1500" -> What major companies or projects are currently using - Bugzilla for bug-tracking? +HREF="#AEN1639" +> What major companies or projects are currently using Bugzilla + for bug-tracking? </A ></DT ><DT >A.1.5. <A -HREF="#AEN1525" +HREF="#AEN1664" > Who maintains Bugzilla? </A ></DT ><DT >A.1.6. <A -HREF="#AEN1530" -> How does Bugzilla stack up against other bug-tracking - databases? +HREF="#AEN1670" +> How does Bugzilla stack up against other bug-tracking databases? </A ></DT ><DT >A.1.7. <A -HREF="#AEN1537" +HREF="#AEN1677" > How do I change my user name in Bugzilla? </A ></DT ><DT >A.1.8. <A -HREF="#AEN1542" -> Why doesn't Bugzilla offer this or that feature or - compatability with this other tracking software? +HREF="#AEN1682" +> Why doesn't Bugzilla offer this or that feature or compatability + with this other tracking software? </A ></DT ><DT >A.1.9. <A -HREF="#AEN1549" +HREF="#AEN1689" > Why MySQL? I'm interested in seeing Bugzilla run on Oracle/Sybase/Msql/PostgreSQL/MSSQL? </A ></DT ><DT >A.1.10. <A -HREF="#AEN1567" -> Why do the scripts say "/usr/bonsaitools/bin/perl" instead - of "/usr/bin/perl" or something else? +HREF="#AEN1707" +> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of + "/usr/bin/perl" or something else? </A ></DT ></DL @@ -9218,19 +9959,19 @@ HREF="#FAQ_REDHAT" ><DL ><DT >A.2.1. <A -HREF="#AEN1584" +HREF="#AEN1724" > What about Red Hat Bugzilla? </A ></DT ><DT >A.2.2. <A -HREF="#AEN1592" +HREF="#AEN1732" > What are the primary benefits of Red Hat Bugzilla? </A ></DT ><DT >A.2.3. <A -HREF="#AEN1620" +HREF="#AEN1760" > What's the current status of Red Hat Bugzilla? </A ></DT @@ -9245,20 +9986,8 @@ HREF="#FAQ_LOKI" ><DL ><DT >A.3.1. <A -HREF="#AEN1636" -> What about Loki Bugzilla? - </A -></DT -><DT ->A.3.2. <A -HREF="#AEN1643" -> Who maintains Fenris (Loki Bugzilla) now? - </A -></DT -><DT ->A.3.3. <A -HREF="#AEN1648" -> +HREF="#AEN1773" +> What is Loki Bugzilla (Fenris)? </A ></DT ></DL @@ -9272,204 +10001,192 @@ HREF="#FAQ_PHB" ><DL ><DT >A.4.1. <A -HREF="#AEN1656" -> Is Bugzilla web-based or do you have to have specific - software or specific operating system on your machine? +HREF="#AEN1784" +> Is Bugzilla web-based or do you have to have specific software or + specific operating system on your machine? </A ></DT ><DT >A.4.2. <A -HREF="#AEN1661" -> Has anyone you know of already done any Bugzilla - integration with Perforce (SCM software)? +HREF="#AEN1789" +> Has anyone you know of already done any Bugzilla integration with + Perforce (SCM software)? </A ></DT ><DT >A.4.3. <A -HREF="#AEN1666" +HREF="#AEN1794" > Does Bugzilla allow the user to track multiple projects? </A ></DT ><DT >A.4.4. <A -HREF="#AEN1671" -> If I am on many projects, and search for all bugs assigned - to me, will Bugzilla list them for me and allow me to sort - by project, severity etc? +HREF="#AEN1799" +> If I am on many projects, and search for all bugs assigned to me, will + Bugzilla list them for me and allow me to sort by project, severity etc? </A ></DT ><DT >A.4.5. <A -HREF="#AEN1676" -> Does Bugzilla allow attachments (text, screenshots, urls - etc)? If yes, are there any that are NOT allowed? +HREF="#AEN1804" +> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes, + are there any that are NOT allowed? </A ></DT ><DT >A.4.6. <A -HREF="#AEN1681" -> Does Bugzilla allow us to define our own priorities and - levels? Do we have complete freedom to change the labels - of fields and format of them, and the choice of acceptable - values? +HREF="#AEN1809" +> Does Bugzilla allow us to define our own priorities and levels? Do we + have complete freedom to change the labels of fields and format of them, and + the choice of acceptable values? </A ></DT ><DT >A.4.7. <A -HREF="#AEN1686" -> The index.html page doesn't show the footer. It's really - annoying to have to go to the querypage just to check my - "my bugs" link. How do I get a footer on static HTML - pages? +HREF="#AEN1814" +> The index.html page doesn't show the footer. It's really annoying to have + to go to the querypage just to check my "my bugs" link. How do I get a footer + on static HTML pages? </A ></DT ><DT >A.4.8. <A -HREF="#AEN1692" -> Does Bugzilla provide any reporting features, metrics, - graphs, etc? You know, the type of stuff that management - likes to see. :) +HREF="#AEN1820" +> Does Bugzilla provide any reporting features, metrics, graphs, etc? You + know, the type of stuff that management likes to see. :) </A ></DT ><DT >A.4.9. <A -HREF="#AEN1700" -> Is there email notification and if so, what do you see - when you get an email? Do you see bug number and title or - is it only the number? +HREF="#AEN1828" +> Is there email notification and if so, what do you see when you get an + email? Do you see bug number and title or is it only the number? </A ></DT ><DT >A.4.10. <A -HREF="#AEN1705" +HREF="#AEN1833" > Can email notification be set up to send to multiple people, some on the To List, CC List, BCC List etc? </A ></DT ><DT >A.4.11. <A -HREF="#AEN1710" -> If there is email notification, do users have to have any - particular type of email application? +HREF="#AEN1838" +> If there is email notification, do users have to have any particular + type of email application? </A ></DT ><DT >A.4.12. <A -HREF="#AEN1717" -> If I just wanted to track certain bugs, as they go - through life, can I set it up to alert me via email - whenever that bug changes, whether it be owner, status or - description etc.? +HREF="#AEN1845" +> If I just wanted to track certain bugs, as they go through life, can I + set it up to alert me via email whenever that bug changes, whether it be + owner, status or description etc.? </A ></DT ><DT >A.4.13. <A -HREF="#AEN1722" -> Does Bugzilla allow data to be imported and exported? If I - had outsiders write up a bug report using a MS Word bug - template, could that template be imported into "matching" - fields? If I wanted to take the results of a query and - export that data to MS Excel, could I do that? +HREF="#AEN1850" +> Does Bugzilla allow data to be imported and exported? If I had outsiders + write up a bug report using a MS Word bug template, could that template be + imported into "matching" fields? If I wanted to take the results of a query + and export that data to MS Excel, could I do that? </A ></DT ><DT >A.4.14. <A -HREF="#AEN1730" -> Does Bugzilla allow fields to be added, changed or - deleted? If I want to customize the bug submission form to - meet our needs, can I do that using our terminology? +HREF="#AEN1858" +> Does Bugzilla allow fields to be added, changed or deleted? If I want to + customize the bug submission form to meet our needs, can I do that using our + terminology? </A ></DT ><DT >A.4.15. <A -HREF="#AEN1735" -> Has anyone converted Bugzilla to another language to be - used in other countries? Is it localizable? +HREF="#AEN1863" +> Has anyone converted Bugzilla to another language to be used in other + countries? Is it localizable? </A ></DT ><DT >A.4.16. <A -HREF="#AEN1740" -> Can a user create and save reports? Can they do this in - Word format? Excel format? +HREF="#AEN1868" +> Can a user create and save reports? Can they do this in Word format? + Excel format? </A ></DT ><DT >A.4.17. <A -HREF="#AEN1745" +HREF="#AEN1873" > Can a user re-run a report with a new project, same query? </A ></DT ><DT >A.4.18. <A -HREF="#AEN1750" -> Can a user modify an existing report and then save it into - another name? +HREF="#AEN1878" +> Can a user modify an existing report and then save it into another name? </A ></DT ><DT >A.4.19. <A -HREF="#AEN1755" -> Does Bugzilla have the ability to search by word, phrase, - compound search? +HREF="#AEN1883" +> Does Bugzilla have the ability to search by word, phrase, compound + search? </A ></DT ><DT >A.4.20. <A -HREF="#AEN1760" -> Can the admin person establish separate group and - individual user privileges? +HREF="#AEN1888" +> Can the admin person establish separate group and individual user + privileges? </A ></DT ><DT >A.4.21. <A -HREF="#AEN1765" -> Does Bugzilla provide record locking when there is - simultaneous access to the same bug? Does the second - person get a notice that the bug is in use or how are they - notified? +HREF="#AEN1893" +> Does Bugzilla provide record locking when there is simultaneous access + to the same bug? Does the second person get a notice that the bug is in use + or how are they notified? </A ></DT ><DT >A.4.22. <A -HREF="#AEN1770" +HREF="#AEN1898" > Are there any backup features provided? </A ></DT ><DT >A.4.23. <A -HREF="#AEN1776" +HREF="#AEN1904" > Can users be on the system while a backup is in progress? </A ></DT ><DT >A.4.24. <A -HREF="#AEN1781" -> What type of human resources are needed to be on staff to - install and maintain Bugzilla? Specifically, what type of - skills does the person need to have? I need to find out if - we were to go with Bugzilla, what types of individuals - would we need to hire and how much would that cost vs - buying an "Out-of-the-Box" solution. +HREF="#AEN1909" +> What type of human resources are needed to be on staff to install and + maintain Bugzilla? Specifically, what type of skills does the person need to + have? I need to find out if we were to go with Bugzilla, what types of + individuals would we need to hire and how much would that cost vs buying an + "Out-of-the-Box" solution. </A ></DT ><DT >A.4.25. <A -HREF="#AEN1788" -> What time frame are we looking at if we decide to hire - people to install and maintain the Bugzilla? Is this - something that takes hours or weeks to install and a - couple of hours per week to maintain and customize or is - this a multi-week install process, plus a full time job - for 1 person, 2 people, etc? +HREF="#AEN1916" +> What time frame are we looking at if we decide to hire people to install + and maintain the Bugzilla? Is this something that takes hours or weeks to + install and a couple of hours per week to maintain and customize or is this + a multi-week install process, plus a full time job for 1 person, 2 people, + etc? </A ></DT ><DT >A.4.26. <A -HREF="#AEN1793" -> Is there any licensing fee or other fees for using - Bugzilla? Any out-of-pocket cost other than the bodies - needed as identified above? +HREF="#AEN1921" +> Is there any licensing fee or other fees for using Bugzilla? Any + out-of-pocket cost other than the bodies needed as identified above? </A ></DT ></DL @@ -9483,19 +10200,19 @@ HREF="#FAQ_INSTALL" ><DL ><DT >A.5.1. <A -HREF="#AEN1800" +HREF="#AEN1928" > How do I download and install Bugzilla? </A ></DT ><DT >A.5.2. <A -HREF="#AEN1806" +HREF="#AEN1934" > How do I install Bugzilla on Windows NT? </A ></DT ><DT >A.5.3. <A -HREF="#AEN1811" +HREF="#AEN1939" > Is there an easy way to change the Bugzilla cookie name? </A ></DT @@ -9510,25 +10227,23 @@ HREF="#FAQ_SECURITY" ><DL ><DT >A.6.1. <A -HREF="#AEN1818" -> How do I completely disable MySQL security if it's giving - me problems (I've followed the instructions in the - installation section of this guide!)? +HREF="#AEN1946" +> How do I completely disable MySQL security if it's giving me problems + (I've followed the instructions in the installation section of this guide!)? </A ></DT ><DT >A.6.2. <A -HREF="#AEN1824" +HREF="#AEN1952" > Are there any security problems with Bugzilla? </A ></DT ><DT >A.6.3. <A -HREF="#AEN1829" -> I've implemented the security fixes mentioned in Chris - Yeh's security advisory of 5/10/2000 advising not to run - MySQL as root, and am running into problems with MySQL no - longer working correctly. +HREF="#AEN1957" +> I've implemented the security fixes mentioned in Chris Yeh's security + advisory of 5/10/2000 advising not to run MySQL as root, and am running into + problems with MySQL no longer working correctly. </A ></DT ></DL @@ -9542,49 +10257,48 @@ HREF="#FAQ_EMAIL" ><DL ><DT >A.7.1. <A -HREF="#AEN1836" -> I have a user who doesn't want to receive any more email - from Bugzilla. How do I stop it entirely for this user? +HREF="#AEN1964" +> I have a user who doesn't want to receive any more email from Bugzilla. + How do I stop it entirely for this user? </A ></DT ><DT >A.7.2. <A -HREF="#AEN1841" -> I'm evaluating/testing Bugzilla, and don't want it to send - email to anyone but me. How do I do it? +HREF="#AEN1969" +> I'm evaluating/testing Bugzilla, and don't want it to send email to + anyone but me. How do I do it? </A ></DT ><DT >A.7.3. <A -HREF="#AEN1846" -> I want whineatnews.pl to whine at something more, or other - than, only new bugs. How do I do it? +HREF="#AEN1974" +> I want whineatnews.pl to whine at something more, or other than, only new + bugs. How do I do it? </A ></DT ><DT >A.7.4. <A -HREF="#AEN1852" -> I don't like/want to use Procmail to hand mail off to - bug_email.pl. What alternatives do I have? +HREF="#AEN1980" +> I don't like/want to use Procmail to hand mail off to bug_email.pl. + What alternatives do I have? </A ></DT ><DT >A.7.5. <A -HREF="#AEN1859" -> How do I set up the email interface to submit/change bugs - via email? +HREF="#AEN1987" +> How do I set up the email interface to submit/change bugs via email? </A ></DT ><DT >A.7.6. <A -HREF="#AEN1864" -> Email takes FOREVER to reach me from bugzilla -- it's - extremely slow. What gives? +HREF="#AEN1992" +> Email takes FOREVER to reach me from bugzilla -- it's extremely slow. + What gives? </A ></DT ><DT >A.7.7. <A -HREF="#AEN1871" +HREF="#AEN1999" > How come email never reaches me from bugzilla changes? </A ></DT @@ -9599,64 +10313,61 @@ HREF="#FAQ_DB" ><DL ><DT >A.8.1. <A -HREF="#AEN1879" +HREF="#AEN2007" > I've heard Bugzilla can be used with Oracle? </A ></DT ><DT >A.8.2. <A -HREF="#AEN1884" -> Bugs are missing from queries, but exist in the database - (and I can pull them up by specifying the bug ID). What's - wrong? +HREF="#AEN2012" +> Bugs are missing from queries, but exist in the database (and I can pull + them up by specifying the bug ID). What's wrong? </A ></DT ><DT >A.8.3. <A -HREF="#AEN1889" -> I think my database might be corrupted, or contain invalid - entries. What do I do? +HREF="#AEN2017" +> I think my database might be corrupted, or contain invalid entries. What + do I do? </A ></DT ><DT >A.8.4. <A -HREF="#AEN1894" +HREF="#AEN2022" > I want to manually edit some entries in my database. How? </A ></DT ><DT >A.8.5. <A -HREF="#AEN1899" -> I try to add myself as a user, but Bugzilla always tells - me my password is wrong. +HREF="#AEN2027" +> I try to add myself as a user, but Bugzilla always tells me my password is wrong. </A ></DT ><DT >A.8.6. <A -HREF="#AEN1904" -> I think I've set up MySQL permissions correctly, but - bugzilla still can't connect. +HREF="#AEN2032" +> I think I've set up MySQL permissions correctly, but bugzilla still can't + connect. </A ></DT ><DT >A.8.7. <A -HREF="#AEN1909" -> How do I synchronize bug information among multiple - different Bugzilla databases? +HREF="#AEN2037" +> How do I synchronize bug information among multiple different Bugzilla + databases? </A ></DT ><DT >A.8.8. <A -HREF="#AEN1916" -> Why do I get bizarre errors when trying to submit data, - particularly problems with "groupset"? +HREF="#AEN2044" +> Why do I get bizarre errors when trying to submit data, particularly problems + with "groupset"? </A ></DT ><DT >A.8.9. <A -HREF="#AEN1921" -> How come even after I delete bugs, the long descriptions - show up? +HREF="#AEN2049" +> How come even after I delete bugs, the long descriptions show up? </A ></DT ></DL @@ -9670,36 +10381,34 @@ HREF="#FAQ_NT" ><DL ><DT >A.9.1. <A -HREF="#AEN1928" -> What is the easiest way to run Bugzilla on Win32 - (Win98+/NT/2K)? +HREF="#AEN2056" +> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)? </A ></DT ><DT >A.9.2. <A -HREF="#AEN1933" +HREF="#AEN2061" > Is there a "Bundle::Bugzilla" equivalent for Win32? </A ></DT ><DT >A.9.3. <A -HREF="#AEN1938" -> CGI's are failing with a "something.cgi is not a valid - Windows NT application" error. Why? +HREF="#AEN2066" +> CGI's are failing with a "something.cgi is not a valid Windows NT + application" error. Why? </A ></DT ><DT >A.9.4. <A -HREF="#AEN1946" -> Can I have some general instructions on how to make - Bugzilla on Win32 work? +HREF="#AEN2074" +> Can I have some general instructions on how to make Bugzilla on Win32 work? </A ></DT ><DT >A.9.5. <A -HREF="#AEN1952" -> I'm having trouble with the perl modules for NT not being - able to talk to to the database. +HREF="#AEN2080" +> I'm having trouble with the perl modules for NT not being able to talk to + to the database. </A ></DT ></DL @@ -9713,38 +10422,35 @@ HREF="#FAQ_USE" ><DL ><DT >A.10.1. <A -HREF="#AEN1973" -> The query page is very confusing. Isn't there a simpler - way to query? +HREF="#AEN2101" +> The query page is very confusing. Isn't there a simpler way to query? </A ></DT ><DT >A.10.2. <A -HREF="#AEN1979" -> I'm confused by the behavior of the "accept" button in the - Show Bug form. Why doesn't it assign the bug to me when I - accept it? +HREF="#AEN2107" +> I'm confused by the behavior of the "accept" button in the Show Bug form. + Why doesn't it assign the bug to me when I accept it? </A ></DT ><DT >A.10.3. <A -HREF="#AEN1989" -> I can't upload anything into the database via the "Create - Attachment" link. What am I doing wrong? +HREF="#AEN2117" +> I can't upload anything into the database via the "Create Attachment" + link. What am I doing wrong? </A ></DT ><DT >A.10.4. <A -HREF="#AEN1994" -> Email submissions to Bugzilla that have attachments end up - asking me to save it as a "cgi" file. +HREF="#AEN2122" +> Email submissions to Bugzilla that have attachments end up asking me to + save it as a "cgi" file. </A ></DT ><DT >A.10.5. <A -HREF="#AEN1999" -> How do I change a keyword in Bugzilla, once some bugs are - using it? +HREF="#AEN2127" +> How do I change a keyword in Bugzilla, once some bugs are using it? </A ></DT ></DL @@ -9758,23 +10464,21 @@ HREF="#FAQ_HACKING" ><DL ><DT >A.11.1. <A -HREF="#AEN2006" +HREF="#AEN2134" > What bugs are in Bugzilla right now? </A ></DT ><DT >A.11.2. <A -HREF="#AEN2015" -> How can I change the default priority to a null value? - For instance, have the default priority be "---" instead - of "P2"? +HREF="#AEN2143" +> How can I change the default priority to a null value? For instance, have the default + priority be "---" instead of "P2"? </A ></DT ><DT >A.11.3. <A -HREF="#AEN2021" -> What's the best way to submit patches? What guidelines - should I follow? +HREF="#AEN2149" +> What's the best way to submit patches? What guidelines should I follow? </A ></DT ></DL @@ -9793,7 +10497,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1481" +NAME="AEN1620" ></A ><B >A.1.1. </B @@ -9808,7 +10512,7 @@ CLASS="ANSWER" information at <A HREF="http://www.mozilla.org/projects/bugzilla/" TARGET="_top" -> http://www.mozilla.org/projects/bugzilla/</A +> http://www.mozilla.org/projects/bugzilla/</A > </P ></DIV @@ -9819,7 +10523,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1487" +NAME="AEN1626" ></A ><B >A.1.2. </B @@ -9831,11 +10535,11 @@ CLASS="ANSWER" ><P ><B > </B -> Bugzilla is covered by the Mozilla Public License. See - details at <A +> Bugzilla is covered by the Mozilla Public License. + See details at <A HREF="http://www.mozilla.org/MPL/" TARGET="_top" -> http://www.mozilla.org/MPL/</A +> http://www.mozilla.org/MPL/</A > </P ></DIV @@ -9846,7 +10550,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1493" +NAME="AEN1632" ></A ><B >A.1.3. </B @@ -9862,17 +10566,16 @@ CLASS="ANSWER" HREF="http://www.collab.net/" TARGET="_top" >www.collab.net</A -> - offers Bugzilla as part of their standard offering to - large projects. They do have some minimum fees that are - pretty hefty, and generally aren't interested in small - projects. +> offers + Bugzilla as part of their standard offering to large projects. + They do have some minimum fees that are pretty hefty, and generally + aren't interested in small projects. </P ><P -> There are several experienced Bugzilla hackers on the - mailing list/newsgroup who are willing to whore themselves - out for generous compensation. Try sending a message to - the mailing list asking for a volunteer. +> There are several experienced + Bugzilla hackers on the mailing list/newsgroup who are willing + to whore themselves out for generous compensation. + Try sending a message to the mailing list asking for a volunteer. </P ></DIV ></DIV @@ -9882,12 +10585,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1500" +NAME="AEN1639" ></A ><B >A.1.4. </B -> What major companies or projects are currently using - Bugzilla for bug-tracking? +> What major companies or projects are currently using Bugzilla + for bug-tracking? </P ></DIV ><DIV @@ -9897,9 +10600,8 @@ CLASS="ANSWER" > </B > There are <EM >dozens</EM -> of major comapanies - with public Bugzilla sites to track bugs in their - products. A few include: +> of major comapanies with public + Bugzilla sites to track bugs in their products. A few include: <P ></P ><TABLE @@ -9980,9 +10682,8 @@ BORDER="0" > </P ><P -> Suffice to say, there are more than enough huge projects - using Bugzilla that we can safely say it's extremely - popular. +> Suffice to say, there are more than enough huge projects using Bugzilla + that we can safely say it's extremely popular. </P ></DIV ></DIV @@ -9992,7 +10693,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1525" +NAME="AEN1664" ></A ><B >A.1.5. </B @@ -10004,16 +10705,12 @@ CLASS="ANSWER" ><P ><B > </B -> There are many, many contributors from around the world - maintaining Bugzilla. The designated "Maintainer" is Tara - Hernandez, with QA support by Matthew Tuck. Dan Mosedale - and Dawn Endico are employees of Mozilla.org responsible - for the installation of Bugzilla there, and are very - frequent code contributors. Terry Weissman originally - ported Bugzilla, but "these days, Terry just hangs around - and heckles." The rest of us are mostly transient - developers; Bugzilla suits our needs, and we contribute - code as we have needs for updates. +> Bugzilla maintenance has been in a state of flux recently. + Please check <A +HREF="http://www.mozilla.org/projects/bugzilla/" +TARGET="_top" +>the Bugzilla Project Page for the latest details. </A +> </P ></DIV ></DIV @@ -10023,12 +10720,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1530" +NAME="AEN1670" ></A ><B >A.1.6. </B -> How does Bugzilla stack up against other bug-tracking - databases? +> How does Bugzilla stack up against other bug-tracking databases? </P ></DIV ><DIV @@ -10049,7 +10745,7 @@ CLASS="ANSWER" flexibility, and superior ease-of-use. </P ><P -> If you happen to be a commercial Bugzilla vendor, please +> If you happen to be a commercial bug-tracker vendor, please step forward with a rebuttal so I can include it in the FAQ. We're not in pursuit of Bugzilla ueber alles; we simply love having a powerful, open-source tool to get our @@ -10063,7 +10759,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1537" +NAME="AEN1677" ></A ><B >A.1.7. </B @@ -10075,9 +10771,8 @@ CLASS="ANSWER" ><P ><B > </B -> You can't. However, the administrative account can, by - simply opening your user account in editusers.cgi and - changing the login name. +> You can't. However, the administrative account can, by simply opening + your user account in editusers.cgi and changing the login name. </P ></DIV ></DIV @@ -10087,12 +10782,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1542" +NAME="AEN1682" ></A ><B >A.1.8. </B -> Why doesn't Bugzilla offer this or that feature or - compatability with this other tracking software? +> Why doesn't Bugzilla offer this or that feature or compatability + with this other tracking software? </P ></DIV ><DIV @@ -10100,19 +10795,18 @@ CLASS="ANSWER" ><P ><B > </B -> It may be that the support has not been built yet, or that - you have not yet found it. Bugzilla is making tremendous - strides in usability, customizability, scalability, and - user interface. It is widely considered the most complete - and popular open-source bug-tracking software in - existence. - </P -><P -> That doesn't mean it can't use improvement! You can help - the project along by either hacking a patch yourself that - supports the functionality you require, or else submitting - a "Request for Enhancement" (RFE) using the bug submission - interface at <A +> It may be that the support has not been built yet, or that you + have not yet found it. Bugzilla is making tremendous strides in + usability, customizability, scalability, and user interface. It + is widely considered the most complete and popular open-source + bug-tracking software in existence. + </P +><P +> That doesn't mean it can't use improvement! + You can help the project along by either hacking a patch yourself + that supports the functionality you require, or else submitting a + "Request for Enhancement" (RFE) using the bug submission interface + at <A HREF="http://bugzilla.mozilla.org/" TARGET="_top" >bugzilla.mozilla.org</A @@ -10126,7 +10820,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1549" +NAME="AEN1689" ></A ><B >A.1.9. </B @@ -10141,34 +10835,32 @@ CLASS="ANSWER" > </B >Terry Weissman answers, <A -NAME="AEN1553" +NAME="AEN1693" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P > You're not the only one. But <EM >I</EM -> am - not very interested. I'm not a real SQL or database - person. I just wanted to make a useful tool, and build - it on top of free software. So, I picked MySQL, and - learned SQL by staring at the MySQL manual and some - code lying around here, and wrote Bugzilla. I didn't - know that Enum's were non-standard SQL. I'm not sure - if I would have cared, but I didn't even know. So, to - me, things are "portable" because it uses MySQL, and - MySQL is portable enough. I fully understand (now) - that people want to be portable to other databases, - but that's never been a real concern of mine. +> am not very interested. I'm not + a real SQL or database person. I just wanted to make a useful tool, + and build it on top of free software. So, I picked MySQL, and + learned SQL by staring at the MySQL manual and some code lying + around here, and + wrote Bugzilla. I didn't know that Enum's were non-standard SQL. + I'm not sure if I would have cared, but I didn't even know. So, to + me, things are "portable" because it uses MySQL, and MySQL is + portable enough. I fully understand (now) that people want to be + portable to other databases, but that's never been a real concern + of mine. </P ></BLOCKQUOTE > </P ><P -> Things aren't quite that grim these days, however. Terry - pretty much sums up much of the thinking many of us have - for Bugzilla, but there is light on the horizon for - database-independence! Here are some options: +> Things aren't quite that grim these days, however. Terry pretty much + sums up much of the thinking many of us have for Bugzilla, but there + is light on the horizon for database-independence! Here are some options: </P ><P ></P @@ -10181,11 +10873,10 @@ BORDER="0" ><A HREF="http://bugzilla.redhat.com/" TARGET="_top" ->Red - Hat Bugzilla</A +>Red Hat Bugzilla</A ></EM ->: Runs a modified - Bugzilla 2.8 atop an Oracle database. +>: + Runs a modified Bugzilla 2.8 atop an Oracle database. </TD ></TR ><TR @@ -10196,15 +10887,16 @@ HREF="http://sourceforge.net/projects/interzilla" TARGET="_top" >Interzilla</A ></EM ->: A project to run Bugzilla on Interbase. No code released yet, however. +>: + A project to run Bugzilla on Interbase. No code released yet, however. </TD ></TR ><TR ><TD > <EM >Bugzilla 3.0</EM ->: One of the primary - stated goals is multiple database support. +>: One of the primary stated goals + is multiple database support. </TD ></TR ></TBODY @@ -10219,12 +10911,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1567" +NAME="AEN1707" ></A ><B >A.1.10. </B -> Why do the scripts say "/usr/bonsaitools/bin/perl" instead - of "/usr/bin/perl" or something else? +> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of + "/usr/bin/perl" or something else? </P ></DIV ><DIV @@ -10232,25 +10924,22 @@ CLASS="ANSWER" ><P ><B > </B -> Mozilla.org uses /usr/bonsaitools/bin/perl. The prime - rule in making submissions is "don't break - bugzilla.mozilla.org". If it breaks it, your patch will be - reverted faster than you can do a diff. +> Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making + submissions is "don't break bugzilla.mozilla.org". If it breaks it, your + patch will be reverted faster than you can do a diff. </P ><P -> Here's Terry Weissman's comment, for some historical - context: +> Here's Terry Weissman's comment, for some historical context: <A -NAME="AEN1572" +NAME="AEN1712" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> [This was] purely my own convention. I wanted a place - to put a version of Perl and other tools that was - strictly under my control for the various webtools, - and not subject to anyone else. Edit it to point to - whatever you like. +> [This was] purely my own convention. I wanted a place to put a version of + Perl and other tools that was strictly under my control for the + various webtools, and not subject to anyone else. Edit it to point + to whatever you like. </P ><DIV CLASS="NOTE" @@ -10273,16 +10962,15 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> We always recommend that, if possible, you keep the - path as /usr/bonsaitools/bin/perl, and simply add a - /usr/bonsaitools and /usr/bonsaitools/bin directory, - then symlink your version of perl to - /usr/bonsaitools/bin/perl. This will make upgrading +> We always recommend that, if possible, you keep the path + as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools + and /usr/bonsaitools/bin directory, then symlink your version + of perl to /usr/bonsaitools/bin/perl. This will make upgrading your Bugzilla much easier in the future. </P ><P -> Obviously, if you do not have root access to your - Bugzilla box, our suggestion is irrelevant. +> Obviously, if you do not have root access to your Bugzilla + box, our suggestion is irrelevant. </P ></TD ></TR @@ -10326,8 +11014,7 @@ VALIGN="TOP" > <EM >This section is no longer up-to-date.</EM > - Please see the section on "Red Hat Bugzilla" under - "Variants" in The Bugzilla Guide. + Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide. </P ></TD ></TR @@ -10341,7 +11028,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1584" +NAME="AEN1724" ></A ><B >A.2.1. </B @@ -10353,34 +11040,32 @@ CLASS="ANSWER" ><P ><B > </B -> Red Hat Bugzilla is arguably more user-friendly, - customizable, and scalable than stock Bugzilla. Check it - out at http://bugzilla.redhat.com and the sources at - ftp://people.redhat.com/dkl/. They've set their Bugzilla - up to work with Oracle out of the box. Note that Redhat - Bugzilla is based upon the 2.8 Bugzilla tree; Bugzilla has - made some tremendous advances since the 2.8 release. Why - not download both Bugzillas to check out the differences - for yourself? - </P -><P -> Dave Lawrence, the original Red Hat Bugzilla maintainer, - mentions: +> Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable + than stock Bugzilla. Check it out at + http://bugzilla.redhat.com and the sources at ftp://people.redhat.com/dkl/. + They've set their Bugzilla up to work with Oracle out of the box. + Note that Redhat Bugzilla is based upon the 2.8 Bugzilla tree; + Bugzilla has made some tremendous advances since the 2.8 release. + Why not download both Bugzillas to check out the differences for + yourself? + </P +><P +> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions: <A -NAME="AEN1589" +NAME="AEN1729" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> Somebody needs to take the ball and run with it. I'm - the only maintainer and am very pressed for time. +> Somebody needs to take the ball and run with it. I'm the only + maintainer and am very pressed for time. </P ></BLOCKQUOTE -> If you, or someone you know, has the time - and expertise to do the integration work so main-tree - Bugzilla 2.12 and higher integrates the Red Hat Bugzilla - Oracle modifications, please donate your time to - supporting the Bugzilla project. +> + If you, or someone you know, has the time and expertise to do the integration + work so main-tree Bugzilla 2.12 and higher integrates the Red + Hat Bugzilla Oracle modifications, please donate your + time to supporting the Bugzilla project. </P ></DIV ></DIV @@ -10390,7 +11075,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1592" +NAME="AEN1732" ></A ><B >A.2.2. </B @@ -10406,36 +11091,30 @@ CLASS="ANSWER" >Dave Lawrence</EM >: <A -NAME="AEN1597" +NAME="AEN1737" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> 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. +> 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. </P ><P -> I do want to land the changes that I have made to - Bugzilla but I may have to back out a good deal and - make a different version of Red Hat's Bugzilla for - checking in to CVS. Especially the cosmetic changes - because it seems they may not fit the general public. - I will do that as soon as I can. I also still do my - regular QA responsibilities along with Bugzilla so - time is difficult sometimes to come by. +> I do want to land the changes that I have made to Bugzilla but I may + have to back out a good deal and make a different version of Red Hat's + Bugzilla for checking in to CVS. Especially the cosmetic changes because it + seems they may not fit the general public. I will do that as soon as I can. + I also still do my regular QA responsibilities along with Bugzilla so time + is difficult sometimes to come by. </P ><P -> There are also a good deal of other changes that were - requested by management for things like support - contracts and different permission groups for making - bugs private. Here is a short list of the major +> There are also a good deal of other changes that were requested by + management for things like support contracts and different permission + groups for making bugs private. Here is a short list of the major changes that have been made: </P ><P @@ -10444,93 +11123,78 @@ CLASS="BLOCKQUOTE" TYPE="1" ><LI ><P -> No enum types. All old enum types are now separate - smaller tables. +> No enum types. All old enum types are now separate smaller tables. </P ></LI ><LI ><P -> No bit wise operations. Not all databases support - this so they were changed to a more generic way of - doing this task +> No bit wise operations. Not all databases support this so they were + changed to a more generic way of doing this task </P ></LI ><LI ><P -> Bug reports can only be altered by the reporter, - assignee, or a privileged bugzilla user. The rest - of the world can see the bug but in a - non-changeable format (unless the bug has been - marked private). They can however add comments, - add and remove themselves from the CC list +> Bug reports can only be altered by the reporter, assignee, or a + privileged bugzilla user. The rest of the world can see the bug but in + a non-changeable format (unless the bug has been marked private). They + can however add comments, add and remove themselves from the CC list </P ></LI ><LI ><P -> Different group scheme. Each group has an id - number related to it. There is a user_group table - which contains userid to groupid mappings to - determine which groups each user belongs to. - Additionally there is a bug_group table that has - bugid to groupid mappings to show which groups can - see a particular bug. If there are no entries for - a bug in this table then the bug is public. +> Different group scheme. Each group has an id number related to it. + There is a user_group table which contains userid to groupid mappings + to determine which groups each user belongs to. Additionally there is + a bug_group table that has bugid to groupid mappings to show which + groups can see a particular bug. If there are no entries for a bug in + this table then the bug is public. </P ></LI ><LI ><P -> Product groups. product_table created to only - allow certain products to be visible for certain - groups in both bug entry and query. This was +> Product groups. product_table created to only allow certain products to + be visible for certain groups in both bug entry and query. This was particulary helpful for support contracts. </P ></LI ><LI ><P -> Of course many (too many) changes to Bugzilla code - itself to allow use with Oracle and still allow - operation with Mysql if so desired. Currently if - you use Mysql it is set to use Mysql's old - permission scheme to keep breakage to a minimum. - Hopefully one day this will standardize on one - style which may of course be something completely +> Of course many (too many) changes to Bugzilla code itself to allow use + with Oracle and still allow operation with Mysql if so desired. + Currently if you use Mysql it is set to use Mysql's old permission + scheme to keep breakage to a minimum. Hopefully one day this will + standardize on one style which may of course be something completely different. </P ></LI ><LI ><P -> Uses Text::Template perl module for rendering of - the dynamic HTML pages such as enter_bug.cgi, - query.cgi, bug_form.pl, and for the header and - footer parts of the page. This allows the html to - be separate from the perl code for customizing the - look and feel of the page to one's preference. +> Uses Text::Template perl module for rendering of the dynamic HTML pages + such as enter_bug.cgi, query.cgi, bug_form.pl, and for the header and + footer parts of the page. This allows the html to be separate from the + perl code for customizing the look and feel of the page to one's + preference. </P ></LI ><LI ><P -> There are many other smaller changes. There is - also a port to Oracle that I have been working on - as time permits but is not completely finished but - somewhat usable. I will merge it into our standard - code base when it becomes production quality. - Unfortunately there will have to be some - conditionals in the code to make it work with - other than Oracle due to some differences between - Oracle and Mysql. +> There are many other smaller changes. There is also a port to Oracle + that I have been working on as time permits but is not completely + finished but somewhat usable. I will merge it into our standard code + base when it becomes production quality. Unfortunately there will have + to be some conditionals in the code to make it work with other than + Oracle due to some differences between Oracle and Mysql. </P ></LI ></OL ><P -> Both the Mysql and Oracle versions of our current code - base are available from ftp://people.redhat.com/dkl. - If Terry/Tara wants I can submit patch files for all - of the changes I have made and he can determine what - is suitable for addition to the main bugzilla cade - base. But for me to commit changes to the actual CVS I - will need to back out alot of things that are not - suitable for the rest of the Bugzilla community. I am - open to suggestions. +> Both the Mysql and Oracle versions of our current code base are + available from ftp://people.redhat.com/dkl. If Terry/Tara wants I can submit + patch files for all of the changes I have made and he can determine what is + suitable for addition to the main bugzilla cade base. But for me to commit + changes to the actual CVS I will need to back out alot of things that are + not suitable for the rest of the Bugzilla community. I am open to + suggestions. </P ></BLOCKQUOTE > @@ -10543,7 +11207,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1620" +NAME="AEN1760" ></A ><B >A.2.3. </B @@ -10577,76 +11241,67 @@ ALIGN="LEFT" VALIGN="TOP" ><P > This information is somewhat dated; I last updated it - 7 June 2000. Please see the "Variants" section of - "The Bugzilla Guide" for more up-to-date information - regarding Red Hat Bugzilla. + 7 June 2000. Please see the "Variants" section of "The Bugzilla Guide" + for more up-to-date information regarding Red Hat Bugzilla. </P ></TD ></TR ></TABLE ></DIV -> <EM +> + <EM >Dave Lawrence</EM >: <A -NAME="AEN1627" +NAME="AEN1767" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> I suppose the current thread warrants an update - on the status of Oracle and bugzilla ;) We have now - been running Bugzilla 2.8 on Oracle for the last two - days in our production environment. I tried to do as - much testing as possible with it before going live - which is some of the reason for the long delay. I did - not get enough feedback as I would have liked from - internal developers to help weed out any bugs still - left so I said "Fine, i will take it live and then I - will get the feedback I want :)" So it is now starting - to stabilize and it running quite well after working - feverishly the last two days fixing problems as soon - as they came in from the outside world. The current - branch in cvs is up2date if anyone would like to grab - it and try it out. The oracle _setup.pl is broken - right now due to some last minute changes but I will - update that soon. Therefore you would probably need to - create the database tables the old fashioned way using - the supplied sql creation scripts located in the - ./oracle directory. We have heavy optimizations in the - database it self thanks to the in-house DBA here at - Red Hat so it is running quite fast. The database - itself is located on a dual PII450 with 1GB ram and 14 - high voltage differential raided scsi drives. The - tables and indexes are partitioned in 4 chuncks across - the raided drive which is nice because when ever you - need to do a full table scan, it is actually starting - in 4 different locations on 4 different drives - simultaneously. And the indexes of course are on - separate drives from the data so that speeds things up - tremendously. When I can find the time I will - document all that we have done to get this thing going - to help others that may need it. +> I suppose the current thread warrants an update on the status of + Oracle and bugzilla ;) We have now been running Bugzilla 2.8 on + Oracle for the last two days in our production environment. I + tried to do as much testing as possible with it before going live + which is some of the reason for the long delay. I did not get + enough feedback as I would have liked from internal developers to + help weed out any bugs still left so I said "Fine, i will take it + live and then I will get the feedback I want :)" So it is now + starting to stabilize and it running quite well after working + feverishly the last two days fixing problems as soon as they came + in from the outside world. The current branch in cvs is up2date if + anyone would like to grab it and try it out. The oracle _setup.pl + is broken right now due to some last minute changes but I will + update that soon. Therefore you would probably need to create the + database tables the old fashioned way using the supplied sql + creation scripts located in the ./oracle directory. We have heavy + optimizations in the database it self thanks to the in-house DBA + here at Red Hat so it is running quite fast. The database itself + is located on a dual PII450 with 1GB ram and 14 high voltage + differential raided scsi drives. The tables and indexes are + partitioned in 4 chuncks across the raided drive which is nice + because when ever you need to do a full table scan, it is actually + starting in 4 different locations on 4 different drives + simultaneously. And the indexes of course are on separate drives + from the data so that speeds things up tremendously. When I can + find the time I will document all that we have done to get this + thing going to help others that may need it. </P ><P -> 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 appreciated. What - we are using now is what I call a best first effort. - It definitely can be improved on and may even need - complete rewrites in a lot of areas. A lot of changes - may have to be made in the way Bugzilla does things - currently to make this transition to a more generic - database interface. Fortunately when making the - Oracle changes I made sure I didn't do anything that - I would consider Oracle specific and could not be - easily done with other databases. Alot of the sql - statements need to be broken up into smaller utilities - that themselves would need to make decisions on what - database they are using but the majority of the code - can be made database neutral. +> 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 + appreciated. What we are using now is what I call a best first + effort. It definitely can be improved on and may even need + complete rewrites in a lot of areas. A lot of changes may have to + be made in the way Bugzilla does things currently to make this + transition to a more generic database interface. Fortunately when + making the Oracle changes I made sure I didn't do anything that I + would consider Oracle specific and could not be easily done with + other databases. Alot of the sql statements need to be broken up + into smaller utilities that themselves would need to make + decisions on what database they are using but the majority of the + code can be made database neutral. </P ></BLOCKQUOTE > @@ -10661,55 +11316,17 @@ CLASS="QANDADIV" NAME="FAQ_LOKI" ></A >3. Loki Bugzilla (AKA Fenris)</H3 -><P -> <DIV -CLASS="NOTE" -><P -></P -><TABLE -CLASS="NOTE" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P -> 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. - </P -></TD -></TR -></TABLE -></DIV -> - </P ><DIV CLASS="QANDAENTRY" ><DIV CLASS="QUESTION" ><P ><A -NAME="AEN1636" +NAME="AEN1773" ></A ><B >A.3.1. </B -> What about Loki Bugzilla? +> What is Loki Bugzilla (Fenris)? </P ></DIV ><DIV @@ -10717,71 +11334,12 @@ CLASS="ANSWER" ><P ><B > </B -> Loki Games has a customized version of Bugzilla available - at http://fenris.lokigames.com. From that page, +> Loki Games has a customized version of Bugzilla available at <A -NAME="AEN1640" -></A -><BLOCKQUOTE -CLASS="BLOCKQUOTE" -><P -> You may have noticed that Fenris is a fork from - Bugzilla-- our patches weren't suitable for - integration --and a few people have expressed interest - in the code. Fenris has one major improvement over - Bugzilla, and that is individual comments are not - appended onto a string blob, they are stored as a - record in a separate table. This allows you to, for - instance, separate comments out according to privilege - levels in case your bug database could contain - sensitive information not for public eyes. We also - provide things like email hiding to protect user's - privacy, additional fields such as 'user_affected' in - case someone enters someone else's bug, comment - editing and deletion, and more conditional system - variables than Bugzilla does (turn off attachments, - qacontact, etc.). - </P -></BLOCKQUOTE -> - </P -></DIV -></DIV -><DIV -CLASS="QANDAENTRY" -><DIV -CLASS="QUESTION" -><P -><A -NAME="AEN1643" -></A -><B ->A.3.2. </B -> Who maintains Fenris (Loki Bugzilla) now? - </P -></DIV -><DIV -CLASS="ANSWER" -><P -><B -> </B -> Raphael Barrerro <raistlin@lokigames.com>. Michael - Vance created the initial fork, but no longer maintains - the project. - </P -></DIV -></DIV -><DIV -CLASS="QANDAENTRY" -><DIV -CLASS="QUESTION" -><P -><A -NAME="AEN1648" -></A -><B ->A.3.3. </B -> +HREF="http://fenris.lokigames.com/" +TARGET="_top" +>http://fenris.lokigames.com</A +>. There are some advantages to using Fenris, chief being separation of comments based upon user privacy level, data hiding, forced login for any data retrieval, and some additional fields. Loki has mainted their code, originally a fork from the Bugzilla 2.8 code base, and it is quite a bit different than stock Bugzilla at this point. I recommend you stick with official Bugzilla version 2.14 rather than using a fork, but it's up to you. </P ></DIV ></DIV @@ -10815,9 +11373,8 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> 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 - :) +> 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 :) </P ></TD ></TR @@ -10831,12 +11388,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1656" +NAME="AEN1784" ></A ><B >A.4.1. </B -> Is Bugzilla web-based or do you have to have specific - software or specific operating system on your machine? +> Is Bugzilla web-based or do you have to have specific software or + specific operating system on your machine? </P ></DIV ><DIV @@ -10844,9 +11401,8 @@ CLASS="ANSWER" ><P ><B > </B -> It is web and e-mail based. You can edit bugs by sending - specially formatted email to a properly configured - Bugzilla, or control via the web. +> It is web and e-mail based. You can edit bugs by sending specially + formatted email to a properly configured Bugzilla, or control via the web. </P ></DIV ></DIV @@ -10856,12 +11412,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1661" +NAME="AEN1789" ></A ><B >A.4.2. </B -> Has anyone you know of already done any Bugzilla - integration with Perforce (SCM software)? +> Has anyone you know of already done any Bugzilla integration with + Perforce (SCM software)? </P ></DIV ><DIV @@ -10869,12 +11425,8 @@ CLASS="ANSWER" ><P ><B > </B -> Yes! You can find more information elsewhere in "The - Bugzilla Guide" in the "Integration with Third-Party - Products" section. The section on Perforce isn't very - large, but as the maintainer of the Guide is charged with - Perforce/Bugzilla integration by his company, you can - expect this section to grow. +> Yes! You can find more information elsewhere in "The Bugzilla + Guide" in the "Integration with Third-Party Products" section. </P ></DIV ></DIV @@ -10884,7 +11436,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1666" +NAME="AEN1794" ></A ><B >A.4.3. </B @@ -10899,8 +11451,8 @@ CLASS="ANSWER" > Absolutely! You can track up to a "soft-limit" of around 64 individual "Products", that can each be composed of as many "Components" as you want. Check the Administration - section of the Bugzilla Guide for more information - regarding setting up Products and Components. + section of the Bugzilla Guide for more information regarding + setting up Products and Components. </P ></DIV ></DIV @@ -10910,13 +11462,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1671" +NAME="AEN1799" ></A ><B >A.4.4. </B -> If I am on many projects, and search for all bugs assigned - to me, will Bugzilla list them for me and allow me to sort - by project, severity etc? +> If I am on many projects, and search for all bugs assigned to me, will + Bugzilla list them for me and allow me to sort by project, severity etc? </P ></DIV ><DIV @@ -10934,12 +11485,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1676" +NAME="AEN1804" ></A ><B >A.4.5. </B -> Does Bugzilla allow attachments (text, screenshots, urls - etc)? If yes, are there any that are NOT allowed? +> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes, + are there any that are NOT allowed? </P ></DIV ><DIV @@ -10947,14 +11498,12 @@ CLASS="ANSWER" ><P ><B > </B -> Yes. There are many specific MIME-types that are - pre-defined by Bugzilla, but you may specify any arbitrary - MIME-type you need when you upload the file. Since all - attachments are stored in the database, however, I - recommend storing large binary attachments elsewhere in - the web server's file system and providing a hyperlink as - a comment, or in the provided "URL" field in the bug - report. +> Yes. There are many specific MIME-types that are pre-defined by Bugzilla, + but you may specify any arbitrary MIME-type you need when you + upload the file. Since all attachments are stored in the database, + however, I recommend storing large binary attachments elsewhere + in the web server's file system and providing a hyperlink + as a comment, or in the provided "URL" field in the bug report. </P ></DIV ></DIV @@ -10964,14 +11513,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1681" +NAME="AEN1809" ></A ><B >A.4.6. </B -> Does Bugzilla allow us to define our own priorities and - levels? Do we have complete freedom to change the labels - of fields and format of them, and the choice of acceptable - values? +> Does Bugzilla allow us to define our own priorities and levels? Do we + have complete freedom to change the labels of fields and format of them, and + the choice of acceptable values? </P ></DIV ><DIV @@ -10979,9 +11527,9 @@ CLASS="ANSWER" ><P ><B > </B -> Yes. However, modifying some fields, notably those - related to bug progression states, also require adjusting - the program logic to compensate for the change. +> Yes. However, modifying some fields, notably those related to bug + progression states, also require adjusting the program logic to + compensate for the change. </P ></DIV ></DIV @@ -10991,14 +11539,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1686" +NAME="AEN1814" ></A ><B >A.4.7. </B -> The index.html page doesn't show the footer. It's really - annoying to have to go to the querypage just to check my - "my bugs" link. How do I get a footer on static HTML - pages? +> The index.html page doesn't show the footer. It's really annoying to have + to go to the querypage just to check my "my bugs" link. How do I get a footer + on static HTML pages? </P ></DIV ><DIV @@ -11006,32 +11553,40 @@ CLASS="ANSWER" ><P ><B > </B -> This was a late-breaking question for the Guide, so I just - have to quote the relevant newsgroup thread on it. +> This was a late-breaking question for the Guide, so I just have to + quote the relevant newsgroup thread on it. </P ><P CLASS="LITERALLAYOUT" ->> AFAIK, most sites (even if they have SSI enabled) won't have #exec<br> - cmd > enabled. Perhaps what would be better is a #include<br> - virtual and a > footer.cgi the basically has the "require<br> - 'CGI.pl' and PutFooter command. > > Please note that under<br> - most configurations, this also requires naming > the file<br> - from index.html to index.shtml (and making sure that it<br> - will > still be reconized as an index). Personally, I<br> - think this is better on > a per-installation basis<br> - (perhaps add something to the FAQ that says how > to do<br> - this). Good point. Yeah, easy enough to do, that it<br> - shouldn't be a big deal for someone to take it on if they<br> - want it. FAQ is a good place for it. > Dave Miller wrote:<br> - > >> I did a little experimenting with getting the command<br> - menu and footer on >> the end of the index page while<br> - leaving it as an HTML file... >> >> I was successful. :)<br> - >> >> I added this line: >> >> >> >> Just before the<br> - </BODY> </HTML> at the end of the file. And<br> - it worked. >> >> Thought I'd toss that out there. Should<br> - I check this in? For those that >> have SSI disabled,<br> - it'll act like a comment, so I wouldn't think it would >><br> - break anything.<br> +>> AFAIK, most sites (even if they have SSI enabled) won't have #exec cmd<br> +> enabled. Perhaps what would be better is a #include virtual and a<br> +> footer.cgi the basically has the "require 'CGI.pl' and PutFooter command.<br> +><br> +> Please note that under most configurations, this also requires naming<br> +> the file from index.html to index.shtml (and making sure that it will<br> +> still be reconized as an index). Personally, I think this is better on<br> +> a per-installation basis (perhaps add something to the FAQ that says how<br> +> to do this).<br> +<br> +Good point. Yeah, easy enough to do, that it shouldn't be a big deal for<br> +someone to take it on if they want it. FAQ is a good place for it.<br> +<br> +> Dave Miller wrote:<br> +><br> +>> I did a little experimenting with getting the command menu and footer on<br> +>> the end of the index page while leaving it as an HTML file...<br> +>><br> +>> I was successful. :)<br> +>><br> +>> I added this line:<br> +>><br> +>> <br> +>><br> +>> Just before the </BODY> </HTML> at the end of the file. And it worked.<br> +>><br> +>> Thought I'd toss that out there. Should I check this in? For those that<br> +>> have SSI disabled, it'll act like a comment, so I wouldn't think it would<br> +>> break anything.<br> </P ></DIV ></DIV @@ -11041,13 +11596,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1692" +NAME="AEN1820" ></A ><B >A.4.8. </B -> Does Bugzilla provide any reporting features, metrics, - graphs, etc? You know, the type of stuff that management - likes to see. :) +> Does Bugzilla provide any reporting features, metrics, graphs, etc? You + know, the type of stuff that management likes to see. :) </P ></DIV ><DIV @@ -11058,17 +11612,17 @@ CLASS="ANSWER" > Yes. Look at <A HREF="http://bugzilla.mozilla.org/reports.cgi" TARGET="_top" -> http://bugzilla.mozilla.org/reports.cgi</A -> for basic reporting facilities. +> http://bugzilla.mozilla.org/reports.cgi</A +> for basic reporting + facilities. </P ><P -> For more advanced reporting, I recommend hooking up a - professional reporting package, such as Crystal Reports, - and use ODBC to access the MySQL database. You can do a - lot through the Query page of Bugzilla as well, but right - now Advanced Reporting is much better accomplished through - third-party utilities that can interface with the database - directly. +> For more advanced reporting, I recommend hooking up a professional + reporting package, such as Crystal Reports, and use ODBC to access + the MySQL database. You can do a lot through the Query page of + Bugzilla as well, but right now Advanced Reporting is much + better accomplished through third-party utilities that can + interface with the database directly. </P ><P > Advanced Reporting is a Bugzilla 3.X proposed feature. @@ -11081,13 +11635,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1700" +NAME="AEN1828" ></A ><B >A.4.9. </B -> Is there email notification and if so, what do you see - when you get an email? Do you see bug number and title or - is it only the number? +> Is there email notification and if so, what do you see when you get an + email? Do you see bug number and title or is it only the number? </P ></DIV ><DIV @@ -11095,9 +11648,9 @@ CLASS="ANSWER" ><P ><B > </B -> Email notification is user-configurable. The bug id and - Topic of the bug report accompany each email notification, - along with a list of the changes made. +> Email notification is user-configurable. The bug id and Topic + of the bug report accompany each email notification, along with + a list of the changes made. </P ></DIV ></DIV @@ -11107,7 +11660,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1705" +NAME="AEN1833" ></A ><B >A.4.10. </B @@ -11130,12 +11683,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1710" +NAME="AEN1838" ></A ><B >A.4.11. </B -> If there is email notification, do users have to have any - particular type of email application? +> If there is email notification, do users have to have any particular + type of email application? </P ></DIV ><DIV @@ -11143,8 +11696,8 @@ CLASS="ANSWER" ><P ><B > </B -> Bugzilla email is sent in plain text, the most compatible - mail format on the planet. +> Bugzilla email is sent in plain text, the most compatible mail format + on the planet. <DIV CLASS="NOTE" ><P @@ -11166,14 +11719,12 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> If you decide to use the bugzilla_email integration - features to allow Bugzilla to record responses to mail - with the associated bug, you may need to caution your - users to set their mailer to "respond to messages in - the format in which they were sent". For security - reasons Bugzilla ignores HTML tags in comments, and if - a user sends HTML-based email into Bugzilla the - resulting comment looks downright awful. +> If you decide to use the bugzilla_email integration features + to allow Bugzilla to record responses to mail with the associated bug, + you may need to caution your users to set their mailer to "respond + to messages in the format in which they were sent". For security reasons + Bugzilla ignores HTML tags in comments, and if a user sends HTML-based + email into Bugzilla the resulting comment looks downright awful. </P ></TD ></TR @@ -11189,14 +11740,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1717" +NAME="AEN1845" ></A ><B >A.4.12. </B -> If I just wanted to track certain bugs, as they go - through life, can I set it up to alert me via email - whenever that bug changes, whether it be owner, status or - description etc.? +> If I just wanted to track certain bugs, as they go through life, can I + set it up to alert me via email whenever that bug changes, whether it be + owner, status or description etc.? </P ></DIV ><DIV @@ -11204,11 +11754,10 @@ CLASS="ANSWER" ><P ><B > </B -> Yes. Place yourself in the "cc" field of the bug you wish - to monitor. Then change your "Notify me of changes to" - field in the Email Settings tab of the User Preferences - screen in Bugzilla to the "Only those bugs which I am - listed on the CC line" option. +> Yes. Place yourself in the "cc" field of the bug you wish to monitor. + Then change your "Notify me of changes to" field in the Email Settings + tab of the User Preferences screen in Bugzilla to the "Only those + bugs which I am listed on the CC line" option. </P ></DIV ></DIV @@ -11218,15 +11767,14 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1722" +NAME="AEN1850" ></A ><B >A.4.13. </B -> Does Bugzilla allow data to be imported and exported? If I - had outsiders write up a bug report using a MS Word bug - template, could that template be imported into "matching" - fields? If I wanted to take the results of a query and - export that data to MS Excel, could I do that? +> Does Bugzilla allow data to be imported and exported? If I had outsiders + write up a bug report using a MS Word bug template, could that template be + imported into "matching" fields? If I wanted to take the results of a query + and export that data to MS Excel, could I do that? </P ></DIV ><DIV @@ -11234,27 +11782,26 @@ CLASS="ANSWER" ><P ><B > </B -> Mozilla allows data export through a custom DTD in XML - format. It does not, however, export to specific formats - other than the XML Mozilla DTD. Importing the data into - Excel or any other application is left as an exercise for - the reader. +> Mozilla allows data export through a custom DTD in XML format. + It does not, however, export to specific formats other than the + XML Mozilla DTD. Importing the data into Excel or any other application + is left as an exercise for the reader. </P ><P -> If you create import filters to other applications from - Mozilla's XML, please submit your modifications for - inclusion in future Bugzilla distributions. +> If you create import filters to other applications from Mozilla's XML, + please submit your modifications for inclusion in future Bugzilla + distributions. </P ><P -> As for data import, any application can send data to - Bugzilla through the HTTP protocol, or through Mozilla's - XML API. However, it seems kind of silly to put another - front-end in front of Bugzilla; it makes more sense to - create a simplified bug submission form in HTML. You can - find an excellent example at <A +> As for data import, any application can send data to Bugzilla through + the HTTP protocol, or through Mozilla's XML API. However, it seems + kind of silly to put another front-end in front of Bugzilla; + it makes more sense to create a simplified bug submission form in + HTML. You can find an excellent example at + <A HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html" TARGET="_top" -> http://www.mozilla.org/quality/help/bugzilla-helper.html</A +> http://www.mozilla.org/quality/help/bugzilla-helper.html</A > </P ></DIV @@ -11265,13 +11812,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1730" +NAME="AEN1858" ></A ><B >A.4.14. </B -> Does Bugzilla allow fields to be added, changed or - deleted? If I want to customize the bug submission form to - meet our needs, can I do that using our terminology? +> Does Bugzilla allow fields to be added, changed or deleted? If I want to + customize the bug submission form to meet our needs, can I do that using our + terminology? </P ></DIV ><DIV @@ -11289,12 +11836,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1735" +NAME="AEN1863" ></A ><B >A.4.15. </B -> Has anyone converted Bugzilla to another language to be - used in other countries? Is it localizable? +> Has anyone converted Bugzilla to another language to be used in other + countries? Is it localizable? </P ></DIV ><DIV @@ -11302,10 +11849,10 @@ CLASS="ANSWER" ><P ><B > </B -> Currently, no. Internationalization support for Perl did - not exist in a robust fashion until the recent release of - version 5.6.0; Bugzilla is, and likely will remain (until - 3.X) completely non-localized. +> Currently, no. Internationalization support for Perl did not + exist in a robust fashion until the recent release of version 5.6.0; + Bugzilla is, and likely will remain (until 3.X) completely + non-localized. </P ></DIV ></DIV @@ -11315,12 +11862,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1740" +NAME="AEN1868" ></A ><B >A.4.16. </B -> Can a user create and save reports? Can they do this in - Word format? Excel format? +> Can a user create and save reports? Can they do this in Word format? + Excel format? </P ></DIV ><DIV @@ -11338,7 +11885,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1745" +NAME="AEN1873" ></A ><B >A.4.17. </B @@ -11360,12 +11907,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1750" +NAME="AEN1878" ></A ><B >A.4.18. </B -> Can a user modify an existing report and then save it into - another name? +> Can a user modify an existing report and then save it into another name? </P ></DIV ><DIV @@ -11373,9 +11919,8 @@ CLASS="ANSWER" ><P ><B > </B -> You can save an unlimited number of queries in Bugzilla. - You are free to modify them and rename them to your - heart's desire. +> You can save an unlimited number of queries in Bugzilla. You are free + to modify them and rename them to your heart's desire. </P ></DIV ></DIV @@ -11385,12 +11930,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1755" +NAME="AEN1883" ></A ><B >A.4.19. </B -> Does Bugzilla have the ability to search by word, phrase, - compound search? +> Does Bugzilla have the ability to search by word, phrase, compound + search? </P ></DIV ><DIV @@ -11398,9 +11943,8 @@ CLASS="ANSWER" ><P ><B > </B -> You have no idea. Bugzilla's query interface, - particularly with the advanced Boolean operators, is - incredibly versatile. +> You have no idea. Bugzilla's query interface, particularly with the + advanced Boolean operators, is incredibly versatile. </P ></DIV ></DIV @@ -11410,12 +11954,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1760" +NAME="AEN1888" ></A ><B >A.4.20. </B -> Can the admin person establish separate group and - individual user privileges? +> Can the admin person establish separate group and individual user + privileges? </P ></DIV ><DIV @@ -11433,14 +11977,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1765" +NAME="AEN1893" ></A ><B >A.4.21. </B -> Does Bugzilla provide record locking when there is - simultaneous access to the same bug? Does the second - person get a notice that the bug is in use or how are they - notified? +> Does Bugzilla provide record locking when there is simultaneous access + to the same bug? Does the second person get a notice that the bug is in use + or how are they notified? </P ></DIV ><DIV @@ -11448,9 +11991,8 @@ CLASS="ANSWER" ><P ><B > </B -> Bugzilla does not lock records. It provides mid-air - collision detection, and offers the offending user a - choice of options to deal with the conflict. +> Bugzilla does not lock records. It provides mid-air collision detection, + and offers the offending user a choice of options to deal with the conflict. </P ></DIV ></DIV @@ -11460,7 +12002,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1770" +NAME="AEN1898" ></A ><B >A.4.22. </B @@ -11472,12 +12014,12 @@ CLASS="ANSWER" ><P ><B > </B -> MySQL, the database back-end for Bugzilla, allows - hot-backup of data. You can find strategies for dealing - with backup considerations at <A +> MySQL, the database back-end for Bugzilla, allows hot-backup of data. + You can find strategies for dealing with backup considerations + at <A HREF="http://www.mysql.com/doc/B/a/Backup.html" TARGET="_top" -> http://www.mysql.com/doc/B/a/Backup.html</A +> http://www.mysql.com/doc/B/a/Backup.html</A > </P ></DIV @@ -11488,7 +12030,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1776" +NAME="AEN1904" ></A ><B >A.4.23. </B @@ -11500,8 +12042,8 @@ CLASS="ANSWER" ><P ><B > </B -> Yes. However, commits to the database must wait until the - tables are unlocked. Bugzilla databases are typically +> Yes. However, commits to the database must wait + until the tables are unlocked. Bugzilla databases are typically very small, and backups routinely take less than a minute. </P ></DIV @@ -11512,16 +12054,15 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1781" +NAME="AEN1909" ></A ><B >A.4.24. </B -> What type of human resources are needed to be on staff to - install and maintain Bugzilla? Specifically, what type of - skills does the person need to have? I need to find out if - we were to go with Bugzilla, what types of individuals - would we need to hire and how much would that cost vs - buying an "Out-of-the-Box" solution. +> What type of human resources are needed to be on staff to install and + maintain Bugzilla? Specifically, what type of skills does the person need to + have? I need to find out if we were to go with Bugzilla, what types of + individuals would we need to hire and how much would that cost vs buying an + "Out-of-the-Box" solution. </P ></DIV ><DIV @@ -11529,23 +12070,20 @@ CLASS="ANSWER" ><P ><B > </B -> If Bugzilla is set up correctly from the start, continuing - maintenance needs are minimal and can be completed by - unskilled labor. Things like rotate backup tapes and - check log files for the word "error". +> If Bugzilla is set up correctly from the start, continuing maintenance needs + are minimal and can be completed by unskilled labor. Things like rotate + backup tapes and check log files for the word "error". </P ><P -> Commercial Bug-tracking software typically costs somewhere - upwards of $20,000 or more for 5-10 floating licenses. - Bugzilla consultation is available from skilled members of - the newsgroup. +> Commercial Bug-tracking software typically costs somewhere upwards + of $20,000 or more for 5-10 floating licenses. Bugzilla consultation + is available from skilled members of the newsgroup. </P ><P -> As an example, as of this writing I typically charge $115 - for the first hour, and $89 each hour thereafter for - consulting work. It takes me three to five hours to make - Bugzilla happy on a Development installation of - Linux-Mandrake. +> As an example, as of this writing I typically charge + $115 for the first hour, and $89 each hour thereafter + for consulting work. It takes me three to five hours to make Bugzilla + happy on a Development installation of Linux-Mandrake. </P ></DIV ></DIV @@ -11555,16 +12093,15 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1788" +NAME="AEN1916" ></A ><B >A.4.25. </B -> What time frame are we looking at if we decide to hire - people to install and maintain the Bugzilla? Is this - something that takes hours or weeks to install and a - couple of hours per week to maintain and customize or is - this a multi-week install process, plus a full time job - for 1 person, 2 people, etc? +> What time frame are we looking at if we decide to hire people to install + and maintain the Bugzilla? Is this something that takes hours or weeks to + install and a couple of hours per week to maintain and customize or is this + a multi-week install process, plus a full time job for 1 person, 2 people, + etc? </P ></DIV ><DIV @@ -11572,12 +12109,11 @@ CLASS="ANSWER" ><P ><B > </B -> It all depends on your level of commitment. Someone with - much Bugzilla experience can get you up and running in - less than a day, and your Bugzilla install can run - untended for years. If your Bugzilla strategy is critical - to your business workflow, hire somebody with reasonable - UNIX or Perl skills to handle your process management and +> It all depends on your level of commitment. Someone with much Bugzilla + experience can get you up and running in less than a day, and + your Bugzilla install can run untended for years. If your + Bugzilla strategy is critical to your business workflow, hire somebody + with reasonable UNIX or Perl skills to handle your process management and bug-tracking maintenance & customization. </P ></DIV @@ -11588,13 +12124,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1793" +NAME="AEN1921" ></A ><B >A.4.26. </B -> Is there any licensing fee or other fees for using - Bugzilla? Any out-of-pocket cost other than the bodies - needed as identified above? +> Is there any licensing fee or other fees for using Bugzilla? Any + out-of-pocket cost other than the bodies needed as identified above? </P ></DIV ><DIV @@ -11602,9 +12137,8 @@ CLASS="ANSWER" ><P ><B > </B -> No. MySQL asks, if you find their product valuable, that - you purchase a support contract from them that suits your - needs. +> No. MySQL asks, if you find their product valuable, that you purchase + a support contract from them that suits your needs. </P ></DIV ></DIV @@ -11622,7 +12156,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1800" +NAME="AEN1928" ></A ><B >A.5.1. </B @@ -11637,8 +12171,9 @@ CLASS="ANSWER" > Check <A HREF="http://www.mozilla.org/projects/bugzilla/" TARGET="_top" -> http://www.mozilla.org/projects/bugzilla/</A -> for details. Once you download it, untar it, read the Bugzilla Guide. +> http://www.mozilla.org/projects/bugzilla/</A +> for details. + Once you download it, untar it, read the Bugzilla Guide. </P ></DIV ></DIV @@ -11648,7 +12183,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1806" +NAME="AEN1934" ></A ><B >A.5.2. </B @@ -11660,8 +12195,8 @@ CLASS="ANSWER" ><P ><B > </B -> Installation on Windows NT has its own section in "The - Bugzilla Guide". +> Installation on Windows NT has its own section in + "The Bugzilla Guide". </P ></DIV ></DIV @@ -11671,7 +12206,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1811" +NAME="AEN1939" ></A ><B >A.5.3. </B @@ -11701,13 +12236,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1818" +NAME="AEN1946" ></A ><B >A.6.1. </B -> How do I completely disable MySQL security if it's giving - me problems (I've followed the instructions in the - installation section of this guide!)? +> How do I completely disable MySQL security if it's giving me problems + (I've followed the instructions in the installation section of this guide!)? </P ></DIV ><DIV @@ -11715,14 +12249,12 @@ CLASS="ANSWER" ><P ><B > </B -> Run mysql like this: "mysqld --skip-grant-tables". Please - remember <EM ->this makes mysql as secure as taping a - $100 to the floor of a football stadium bathroom for - safekeeping.</EM -> Please read the Security - section of the Administration chapter of "The Bugzilla - Guide" before proceeding. +> Run mysql like this: "mysqld --skip-grant-tables". Please remember <EM +>this + makes mysql as secure as taping a $100 to the floor of a football stadium + bathroom for safekeeping.</EM +> Please read the Security section of the + Administration chapter of "The Bugzilla Guide" before proceeding. </P ></DIV ></DIV @@ -11732,7 +12264,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1824" +NAME="AEN1952" ></A ><B >A.6.2. </B @@ -11744,11 +12276,10 @@ CLASS="ANSWER" ><P ><B > </B -> The Bugzilla code has not undergone a complete security - audit. It is recommended that you closely examine - permissions on your Bugzilla installation, and follow the - recommended security guidelines found in The Bugzilla - Guide. +> The Bugzilla code has not undergone a complete security audit. + It is recommended that you closely examine permissions on your Bugzilla + installation, and follow the recommended security guidelines found + in The Bugzilla Guide. </P ></DIV ></DIV @@ -11758,14 +12289,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1829" +NAME="AEN1957" ></A ><B >A.6.3. </B -> I've implemented the security fixes mentioned in Chris - Yeh's security advisory of 5/10/2000 advising not to run - MySQL as root, and am running into problems with MySQL no - longer working correctly. +> I've implemented the security fixes mentioned in Chris Yeh's security + advisory of 5/10/2000 advising not to run MySQL as root, and am running into + problems with MySQL no longer working correctly. </P ></DIV ><DIV @@ -11773,9 +12303,9 @@ CLASS="ANSWER" ><P ><B > </B -> This is a common problem, related to running out of file - descriptors. Simply add "ulimit -n unlimited" to the - script which starts mysqld. +> This is a common problem, related to running out of file descriptors. + Simply add "ulimit -n unlimited" to the script which starts + mysqld. </P ></DIV ></DIV @@ -11793,12 +12323,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1836" +NAME="AEN1964" ></A ><B >A.7.1. </B -> I have a user who doesn't want to receive any more email - from Bugzilla. How do I stop it entirely for this user? +> I have a user who doesn't want to receive any more email from Bugzilla. + How do I stop it entirely for this user? </P ></DIV ><DIV @@ -11806,8 +12336,8 @@ CLASS="ANSWER" ><P ><B > </B -> With the email changes to 2.12, the user should be able to - set this in user email preferences. +> With the email changes to 2.12, the user should be able to set + this in user email preferences. </P ></DIV ></DIV @@ -11817,12 +12347,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1841" +NAME="AEN1969" ></A ><B >A.7.2. </B -> I'm evaluating/testing Bugzilla, and don't want it to send - email to anyone but me. How do I do it? +> I'm evaluating/testing Bugzilla, and don't want it to send email to + anyone but me. How do I do it? </P ></DIV ><DIV @@ -11830,9 +12360,8 @@ CLASS="ANSWER" ><P ><B > </B -> Edit the param for the mail text. Replace "To:" with - "X-Real-To:", replace "Cc:" with "X-Real-CC:", and add a - "To: (myemailaddress)". +> Edit the param for the mail text. Replace "To:" with "X-Real-To:", + replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)". </P ></DIV ></DIV @@ -11842,12 +12371,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1846" +NAME="AEN1974" ></A ><B >A.7.3. </B -> I want whineatnews.pl to whine at something more, or other - than, only new bugs. How do I do it? +> I want whineatnews.pl to whine at something more, or other than, only new + bugs. How do I do it? </P ></DIV ><DIV @@ -11855,12 +12384,14 @@ CLASS="ANSWER" ><P ><B > </B -> Try Klaas Freitag's excellent patch for "whineatassigned" - functionality. You can find it at<A -HREF=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679" +> Try Klaas Freitag's excellent patch for "whineatassigned" functionality. + You can find it at<A +HREF=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679" TARGET="_top" -> http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A ->. This patch is against an older version of Bugzilla, so you must apply the diffs manually. +> http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A +>. This + patch is against an older version of Bugzilla, so you must apply + the diffs manually. </P ></DIV ></DIV @@ -11870,12 +12401,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1852" +NAME="AEN1980" ></A ><B >A.7.4. </B -> I don't like/want to use Procmail to hand mail off to - bug_email.pl. What alternatives do I have? +> I don't like/want to use Procmail to hand mail off to bug_email.pl. + What alternatives do I have? </P ></DIV ><DIV @@ -11883,22 +12414,21 @@ CLASS="ANSWER" ><P ><B > </B -> You can call bug_email.pl directly from your aliases file, - with an entry like this: +> You can call bug_email.pl directly from your aliases file, with + an entry like this: <A -NAME="AEN1856" +NAME="AEN1984" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> bugzilla-daemon: - "|/usr/local/bin/bugzilla/contrib/bug_email.pl" +> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" </P ></BLOCKQUOTE -> However, this is fairly nasty and subject to - problems; you also need to set up your smrsh (sendmail - restricted shell) to allow it. In a pinch, though, it can - work. +> + However, this is fairly nasty and subject to problems; you also + need to set up your smrsh (sendmail restricted shell) to allow + it. In a pinch, though, it can work. </P ></DIV ></DIV @@ -11908,12 +12438,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1859" +NAME="AEN1987" ></A ><B >A.7.5. </B -> How do I set up the email interface to submit/change bugs - via email? +> How do I set up the email interface to submit/change bugs via email? </P ></DIV ><DIV @@ -11921,9 +12450,8 @@ CLASS="ANSWER" ><P ><B > </B -> You can find an updated README.mailif file in the contrib/ - directory of your Bugzilla distribution that walks you - through the setup. +> You can find an updated README.mailif file in the contrib/ directory + of your Bugzilla distribution that walks you through the setup. </P ></DIV ></DIV @@ -11933,12 +12461,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1864" +NAME="AEN1992" ></A ><B >A.7.6. </B -> Email takes FOREVER to reach me from bugzilla -- it's - extremely slow. What gives? +> Email takes FOREVER to reach me from bugzilla -- it's extremely slow. + What gives? </P ></DIV ><DIV @@ -11946,23 +12474,22 @@ CLASS="ANSWER" ><P ><B > </B -> If you are using an alternate Mail Transport Agent (MTA - other than sendmail), make sure the options given in the - "processmail" script for all instances of "sendmail" are - correct for your MTA. If you are using Sendmail, you may - wish to delete the "-ODeliveryMode=deferred" option in the - "processmail" script for every invocation of "sendmail". - (Be sure and leave the "-t" option, though!) +> If you are using an alternate Mail Transport Agent (MTA other than + sendmail), make sure the options given in the "processmail" script for all + instances of "sendmail" are correct for your MTA. If you are using Sendmail, + you may wish to delete the "-ODeliveryMode=deferred" option in the + "processmail" script for every invocation of "sendmail". (Be sure and leave + the "-t" option, though!) </P ><P > A better alternative is to change the "-O" option to - "-ODeliveryMode=background". This prevents Sendmail from - hanging your Bugzilla Perl processes if the domain to - which it must send mail is unavailable. + "-ODeliveryMode=background". This prevents Sendmail from hanging your + Bugzilla Perl processes if the domain to which it must send mail + is unavailable. </P ><P -> This is now a configurable parameter called "sendmailnow", - available from editparams.cgi. +> This is now a configurable parameter called "sendmailnow", available + from editparams.cgi. </P ></DIV ></DIV @@ -11972,7 +12499,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1871" +NAME="AEN1999" ></A ><B >A.7.7. </B @@ -11984,16 +12511,15 @@ CLASS="ANSWER" ><P ><B > </B -> Double-check that you have not turned off email in your - user preferences. Confirm that Bugzilla is able to send - email by visiting the "Log In" link of your Bugzilla - installation and clicking the "Email me a password" button - after entering your email address. +> Double-check that you have not turned off email in your user preferences. + Confirm that Bugzilla is able to send email by visiting the "Log In" + link of your Bugzilla installation and clicking the "Email me a password" + button after entering your email address. </P ><P -> If you never receive mail from Bugzilla, chances you do - not have sendmail in "/usr/lib/sendmail". Ensure sendmail - lives in, or is symlinked to, "/usr/lib/sendmail". +> If you never receive mail from Bugzilla, chances you do not have + sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked + to, "/usr/lib/sendmail". </P ></DIV ></DIV @@ -12011,7 +12537,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1879" +NAME="AEN2007" ></A ><B >A.8.1. </B @@ -12023,11 +12549,10 @@ CLASS="ANSWER" ><P ><B > </B -> Red Hat Bugzilla, mentioned above, works with Oracle. The - current version from Mozilla.org does not have this - capability. Unfortunately, though you will sacrifice a - lot of the really great features available in Bugzilla - 2.10 and 2.12 if you go with the 2.8-based Redhat version. +> Red Hat Bugzilla, mentioned above, works with Oracle. The current version + from Mozilla.org does not have this capability. Unfortunately, though + you will sacrifice a lot of the really great features available in + Bugzilla 2.10 and 2.12 if you go with the 2.8-based Redhat version. </P ></DIV ></DIV @@ -12037,13 +12562,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1884" +NAME="AEN2012" ></A ><B >A.8.2. </B -> Bugs are missing from queries, but exist in the database - (and I can pull them up by specifying the bug ID). What's - wrong? +> Bugs are missing from queries, but exist in the database (and I can pull + them up by specifying the bug ID). What's wrong? </P ></DIV ><DIV @@ -12051,23 +12575,19 @@ CLASS="ANSWER" ><P ><B > </B -> You've almost certainly enabled the "shadow database", - but for some reason it hasn't been updated for all your - bugs. This is the database against which queries are run, - so that really complex or slow queries won't lock up - portions of the database for other users. You can turn off - the shadow database in editparams.cgi. If you wish to - continue using the shadow database, then as your "bugs" - user run "./syncshadowdb -syncall" from the command line - in the bugzilla installation directory to recreate your - shadow database. After it finishes, be sure to check the - params and make sure that "queryagainstshadowdb" is still - turned on. The syncshadowdb program turns it off if it was - on, and is supposed to turn it back on when completed; - that way, if it crashes in the middle of recreating the - database, it will stay off forever until someone turns it - back on by hand. Apparently, it doesn't always do that - yet. +> You've almost certainly enabled the "shadow database", but for some + reason it hasn't been updated for all your bugs. This is the database + against which queries are run, so that really complex or slow queries won't + lock up portions of the database for other users. You can turn off the + shadow database in editparams.cgi. If you wish to continue using the shadow + database, then as your "bugs" user run "./syncshadowdb -syncall" from the + command line in the bugzilla installation directory to recreate your shadow + database. After it finishes, be sure to check the params and make sure that + "queryagainstshadowdb" is still turned on. The syncshadowdb program turns it + off if it was on, and is supposed to turn it back on when completed; that + way, if it crashes in the middle of recreating the database, it will stay + off forever until someone turns it back on by hand. Apparently, it doesn't + always do that yet. </P ></DIV ></DIV @@ -12077,12 +12597,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1889" +NAME="AEN2017" ></A ><B >A.8.3. </B -> I think my database might be corrupted, or contain invalid - entries. What do I do? +> I think my database might be corrupted, or contain invalid entries. What + do I do? </P ></DIV ><DIV @@ -12090,14 +12610,12 @@ CLASS="ANSWER" ><P ><B > </B -> Run the "sanity check" utility (./sanitycheck.cgi in the - bugzilla_home directory) to see! If it all comes back, - you're OK. If it doesn't come back OK (i.e. any red - letters), there are certain things Bugzilla can recover - from and certain things it can't. If it can't - auto-recover, I hope you're familiar with mysqladmin - commands or have installed another way to manage your - database... +> Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home + directory) to see! If it all comes back, you're OK. If it doesn't come back + OK (i.e. any red letters), there are certain things Bugzilla can recover + from and certain things it can't. If it can't auto-recover, I hope you're + familiar with mysqladmin commands or have installed another way to manage + your database... </P ></DIV ></DIV @@ -12107,7 +12625,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1894" +NAME="AEN2022" ></A ><B >A.8.4. </B @@ -12119,14 +12637,12 @@ CLASS="ANSWER" ><P ><B > </B -> There is no facility in Bugzilla itself to do this. It's - also generally not a smart thing to do if you don't know - exactly what you're doing. However, if you understand SQL - you can use the mysqladmin utility to manually insert, - delete, and modify table information. Personally, I use - "phpMyAdmin". You have to compile a PHP module with MySQL - support to make it work, but it's very clean and easy to - use. +> There is no facility in Bugzilla itself to do this. It's also generally + not a smart thing to do if you don't know exactly what you're doing. + However, if you understand SQL you can use the mysqladmin utility to + manually insert, delete, and modify table information. Personally, I + use "phpMyAdmin". You have to compile a PHP module with MySQL + support to make it work, but it's very clean and easy to use. </P ></DIV ></DIV @@ -12136,12 +12652,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1899" +NAME="AEN2027" ></A ><B >A.8.5. </B -> I try to add myself as a user, but Bugzilla always tells - me my password is wrong. +> I try to add myself as a user, but Bugzilla always tells me my password is wrong. </P ></DIV ><DIV @@ -12149,11 +12664,9 @@ CLASS="ANSWER" ><P ><B > </B -> Certain version of MySQL (notably, 3.23.29 and 3.23.30) - accidentally disabled the "crypt()" function. This - prevented MySQL from storing encrypted passwords. Upgrade - to the "3.23 stable" version of MySQL and you should be - good to go. +> Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled + the "crypt()" function. This prevented MySQL from storing encrypted passwords. + Upgrade to the "3.23 stable" version of MySQL and you should be good to go. </P ></DIV ></DIV @@ -12163,12 +12676,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1904" +NAME="AEN2032" ></A ><B >A.8.6. </B -> I think I've set up MySQL permissions correctly, but - bugzilla still can't connect. +> I think I've set up MySQL permissions correctly, but bugzilla still can't + connect. </P ></DIV ><DIV @@ -12176,12 +12689,11 @@ CLASS="ANSWER" ><P ><B > </B -> Try running MySQL from its binary: "mysqld - --skip-grant-tables". This will allow you to completely - rule out grant tables as the cause of your frustration. - However, I do not recommend you run it this way on a - regular basis, unless you really want your web site - defaced and your machine cracked. +> Try running MySQL from its binary: "mysqld --skip-grant-tables". This + will allow you to completely rule out grant tables as the cause of your + frustration. However, I do not recommend you run it this way on a regular + basis, unless you really want your web site defaced and your machine + cracked. </P ></DIV ></DIV @@ -12191,12 +12703,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1909" +NAME="AEN2037" ></A ><B >A.8.7. </B -> How do I synchronize bug information among multiple - different Bugzilla databases? +> How do I synchronize bug information among multiple different Bugzilla + databases? </P ></DIV ><DIV @@ -12204,22 +12716,20 @@ CLASS="ANSWER" ><P ><B > </B -> Well, you can synchronize or you can move bugs. - Synchronization will only work one way -- you can create a - read-only copy of the database at one site, and have it - regularly updated at intervals from the main database. +> Well, you can synchronize or you can move bugs. Synchronization will + only work one way -- you can create a read-only copy of the database + at one site, and have it regularly updated at intervals from the main + database. </P ><P -> MySQL has some synchronization features builtin to the - latest releases. It would be great if someone looked into - the possibilities there and provided a report to the - newsgroup on how to effectively synchronize two Bugzilla - installations. +> MySQL has some synchronization features builtin to the latest releases. + It would be great if someone looked into the possibilities there + and provided a report to the newsgroup on how to effectively + synchronize two Bugzilla installations. </P ><P -> If you simply need to transfer bugs from one Bugzilla to - another, checkout the "move.pl" script in the Bugzilla - distribution. +> If you simply need to transfer bugs from one Bugzilla to another, + checkout the "move.pl" script in the Bugzilla distribution. </P ></DIV ></DIV @@ -12229,12 +12739,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1916" +NAME="AEN2044" ></A ><B >A.8.8. </B -> Why do I get bizarre errors when trying to submit data, - particularly problems with "groupset"? +> Why do I get bizarre errors when trying to submit data, particularly problems + with "groupset"? </P ></DIV ><DIV @@ -12242,10 +12752,9 @@ CLASS="ANSWER" ><P ><B > </B -> If you're sure your MySQL parameters are correct, you - might want turn "strictvaluechecks" OFF in editparams.cgi. - If you have "usebugsentry" set "On", you also cannot - submit a bug as readable by more than one group with +> If you're sure your MySQL parameters are correct, you might want turn + "strictvaluechecks" OFF in editparams.cgi. If you have "usebugsentry" set + "On", you also cannot submit a bug as readable by more than one group with "strictvaluechecks" ON. </P ></DIV @@ -12256,12 +12765,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1921" +NAME="AEN2049" ></A ><B >A.8.9. </B -> How come even after I delete bugs, the long descriptions - show up? +> How come even after I delete bugs, the long descriptions show up? </P ></DIV ><DIV @@ -12269,11 +12777,10 @@ CLASS="ANSWER" ><P ><B > </B -> Delete everything from $BUZILLA_HOME/shadow. Bugzilla - creates shadow files there, with each filename - corresponding to a bug number. Also be sure to run - syncshadowdb to make sure, if you are using a shadow - database, that the shadow database is current. +> Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow + files there, with each filename corresponding to a + bug number. Also be sure to run syncshadowdb to make sure, if you are using + a shadow database, that the shadow database is current. </P ></DIV ></DIV @@ -12291,12 +12798,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1928" +NAME="AEN2056" ></A ><B >A.9.1. </B -> What is the easiest way to run Bugzilla on Win32 - (Win98+/NT/2K)? +> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)? </P ></DIV ><DIV @@ -12304,8 +12810,8 @@ CLASS="ANSWER" ><P ><B > </B -> Remove Windows. Install Linux. Install Bugzilla. The boss - will never know the difference. +> Remove Windows. Install Linux. Install Bugzilla. + The boss will never know the difference. </P ></DIV ></DIV @@ -12315,7 +12821,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1933" +NAME="AEN2061" ></A ><B >A.9.2. </B @@ -12327,10 +12833,9 @@ CLASS="ANSWER" ><P ><B > </B -> Not currently. Bundle::Bugzilla enormously simplifies - Bugzilla installation on UNIX systems. If someone can - volunteer to create a suitable PPM bundle for Win32, it - would be appreciated. +> Not currently. Bundle::Bugzilla enormously simplifies Bugzilla + installation on UNIX systems. If someone can volunteer to + create a suitable PPM bundle for Win32, it would be appreciated. </P ></DIV ></DIV @@ -12340,12 +12845,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1938" +NAME="AEN2066" ></A ><B >A.9.3. </B -> CGI's are failing with a "something.cgi is not a valid - Windows NT application" error. Why? +> CGI's are failing with a "something.cgi is not a valid Windows NT + application" error. Why? </P ></DIV ><DIV @@ -12353,32 +12858,27 @@ CLASS="ANSWER" ><P ><B > </B -> Depending on what Web server you are using, you will have - to configure the Web server to treat *.cgi files as CGI - scripts. In IIS, you do this by adding *.cgi to the App - Mappings with the <path>\perl.exe %s %s as the +> Depending on what Web server you are using, you will have to configure + the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by + adding *.cgi to the App Mappings with the <path>\perl.exe %s %s as the executable. </P ><P > Microsoft has some advice on this matter, as well: <A -NAME="AEN1943" +NAME="AEN2071" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> "Set application mappings. In the ISM, map the - extension for the script file(s) to the executable for - the script interpreter. For example, you might map the - extension .py to Python.exe, the executable for the - Python script interpreter. Note For the ActiveState - Perl script interpreter, the extension .pl is - associated with PerlIS.dll by default. If you want to - change the association of .pl to perl.exe, you need to - change the application mapping. In the mapping, you - must add two percent (%) characters to the end of the - pathname for perl.exe, as shown in this example: - c:\perl\bin\perl.exe %s %s" +> "Set application mappings. In the ISM, map the extension for the script + file(s) to the executable for the script interpreter. For example, you might + map the extension .py to Python.exe, the executable for the Python script + interpreter. Note For the ActiveState Perl script interpreter, the extension + .pl is associated with PerlIS.dll by default. If you want to change the + association of .pl to perl.exe, you need to change the application mapping. + In the mapping, you must add two percent (%) characters to the end of the + pathname for perl.exe, as shown in this example: c:\perl\bin\perl.exe %s %s" </P ></BLOCKQUOTE > @@ -12391,12 +12891,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1946" +NAME="AEN2074" ></A ><B >A.9.4. </B -> Can I have some general instructions on how to make - Bugzilla on Win32 work? +> Can I have some general instructions on how to make Bugzilla on Win32 work? </P ></DIV ><DIV @@ -12404,56 +12903,95 @@ CLASS="ANSWER" ><P ><B > </B -> The following couple entries are deprecated in favor of - the Windows installation instructions available in the - "Administration" portion of "The Bugzilla Guide". However, - they are provided here for historical interest and - insight. <P +> The following couple entries are deprecated in favor of the Windows installation + instructions available in the "Administration" portion of "The Bugzilla Guide". + However, they are provided here for historical interest and insight. + <P CLASS="LITERALLAYOUT" -> 1. #!C:/perl/bin/perl had to be<br> - added to every perl file. 2. Converted to Net::SMTP to<br> - handle mail messages instead of /usr/bin/sendmail. 3.<br> - The crypt function isn't available on Windows NT (at<br> - least none that I am aware), so I made encrypted<br> - passwords = plaintext passwords. 4. The system call to<br> - diff had to be changed to the Cygwin diff. 5. This was<br> - just to get a demo running under NT, it seems to be<br> - working good, and I have inserted almost 100 bugs from<br> - another bug tracking system. Since this work was done<br> - just to get an in-house demo, I am NOT planning on<br> - making a patch for submission to Bugzilla. If you would<br> - like a zip file, let me know. Q: Hmm, couldn't figure it<br> - out from the general instructions above. How about<br> - step-by-step? A: Sure! Here ya go! 1. Install IIS 4.0<br> - from the NT Option Pack #4. 2. Download and install<br> - Active Perl. 3. Install the Windows GNU tools from<br> - Cygwin. Make sure to add the bin directory to your<br> - system path. (Everyone should have these, whether they<br> - decide to use Bugzilla or not. :-) ) 4. Download<br> - relevant packages from ActiveState at<br> - http://www.activestate.com/packages/zips/. +<br> - DBD-Mysql.zip 5. Extract each zip file with WinZip, and<br> - install each ppd file using the notation: ppm install<br> - <module>.ppd 6. Install Mysql. *Note: If you move<br> - the default install from c:\mysql, you must add the<br> - appropriate startup parameters to the NT service. (ex.<br> - -b e:\\programs\\mysql) 7. Download any Mysql client.<br> - http://www.mysql.com/download_win.html 8. Setup MySql.<br> - (These are the commands that I used.) I. Cleanup default<br> - database settings. C:\mysql\bin\mysql -u root mysql<br> - mysql> DELETE FROM user WHERE Host='localhost' AND<br> - User=''; mysql> quit C:\mysql\bin\mysqladmin reload II.<br> - Set password for root. C:\mysql\bin\mysql -u root mysql<br> - mysql> UPDATE user SET Password=PASSWORD('new_password')<br> - WHERE user='root'; mysql> FLUSH PRIVILEGES; mysql> quit<br> - C:\mysql\bin\mysqladmin -u root reload III. Create bugs<br> - user. C:\mysql\bin\mysql -u root -p mysql> insert into<br> - user (host,user,password) values('localhost','bugs','');<br> - mysql> quit C:\mysql\bin\mysqladmin -u root reload IV.<br> - Create the bugs database. C:\mysql\bin\mysql -u root -p<br> - mysql> create database bugs; V. Give the bugs user<br> - access to the bugs database. mysql> insert into db<br> - (host,db,user,select_priv,insert_priv,update_priv,delete_priv,create_priv,drop_priv) values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N') mysql> quit C:\mysql\bin\mysqladmin -u root reload 9. Run the table scripts to setup the bugs database. 10. Change CGI.pm to use the following regular expression because of differing backslashes in NT versus UNIX. o $0 =~ m:[^\\]*$:; 11. Had to make the crypt password = plain text password in the database. (Thanks to Andrew Lahser" <andrew_lahser@merck.com>" on this one.) The files that I changed were: o globals.pl o CGI.pl o alternately, you can try commenting all references to 'crypt' string and replace them with similar lines but without encrypt() or crypr() functions insida all files. 12. Replaced sendmail with Windmail. Basically, you have to come up with a sendmail substitute for NT. Someone said that they used a Perl module (Net::SMTP), but I was trying to save time and do as little Perl coding as possible. 13. Added "perl" to the beginning of all Perl system calls that use a perl script as an argument and renamed processmail to processmail.pl. 14. In processmail.pl, I added binmode(HANDLE) before all read() calls. I'm not sure about this one, but the read() under NT wasn't counting the EOLs without the binary read." </P +> 1. #!C:/perl/bin/perl had to be added to every perl file.<br> + 2. Converted to Net::SMTP to handle mail messages instead of<br> + /usr/bin/sendmail.<br> + 3. The crypt function isn't available on Windows NT (at least none that I<br> + am aware), so I made encrypted passwords = plaintext passwords.<br> + 4. The system call to diff had to be changed to the Cygwin diff.<br> + 5. This was just to get a demo running under NT, it seems to be working<br> + good, and I have inserted almost 100 bugs from another bug tracking<br> + system. Since this work was done just to get an in-house demo, I am NOT<br> + planning on making a patch for submission to Bugzilla. If you would<br> + like a zip file, let me know.<br> +<br> +Q: Hmm, couldn't figure it out from the general instructions above. How<br> +about step-by-step?<br> +A: Sure! Here ya go!<br> +<br> + 1. Install IIS 4.0 from the NT Option Pack #4.<br> + 2. Download and install Active Perl.<br> + 3. Install the Windows GNU tools from Cygwin. Make sure to add the bin<br> + directory to your system path. (Everyone should have these, whether<br> + they decide to use Bugzilla or not. :-) )<br> + 4. Download relevant packages from ActiveState at<br> + http://www.activestate.com/packages/zips/. + DBD-Mysql.zip<br> + 5. Extract each zip file with WinZip, and install each ppd file using the<br> + notation: ppm install <module>.ppd<br> + 6. Install Mysql. *Note: If you move the default install from c:\mysql,<br> + you must add the appropriate startup parameters to the NT service. (ex.<br> + -b e:\\programs\\mysql)<br> + 7. Download any Mysql client. http://www.mysql.com/download_win.html<br> + 8. Setup MySql. (These are the commands that I used.)<br> +<br> + I. Cleanup default database settings.<br> + C:\mysql\bin\mysql -u root mysql<br> + mysql> DELETE FROM user WHERE Host='localhost' AND User='';<br> + mysql> quit<br> + C:\mysql\bin\mysqladmin reload<br> +<br> + II. Set password for root.<br> + C:\mysql\bin\mysql -u root mysql<br> + mysql> UPDATE user SET Password=PASSWORD('new_password')<br> + WHERE user='root';<br> + mysql> FLUSH PRIVILEGES;<br> + mysql> quit<br> + C:\mysql\bin\mysqladmin -u root reload<br> +<br> + III. Create bugs user.<br> + C:\mysql\bin\mysql -u root -p<br> + mysql> insert into user (host,user,password)<br> + values('localhost','bugs','');<br> + mysql> quit<br> + C:\mysql\bin\mysqladmin -u root reload<br> +<br> + IV. Create the bugs database.<br> + C:\mysql\bin\mysql -u root -p<br> + mysql> create database bugs;<br> +<br> + V. Give the bugs user access to the bugs database.<br> + mysql> insert into db<br> + (host,db,user,select_priv,insert_priv,update_priv,delete_priv,create_priv,drop_priv)<br> + values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N')<br> + mysql> quit<br> + C:\mysql\bin\mysqladmin -u root reload<br> + 9. Run the table scripts to setup the bugs database.<br> + 10. Change CGI.pm to use the following regular expression because of<br> + differing backslashes in NT versus UNIX.<br> + o $0 =~ m:[^\\]*$:;<br> + 11. Had to make the crypt password = plain text password in the database.<br> + (Thanks to Andrew Lahser" <andrew_lahser@merck.com>" on this one.) The<br> + files that I changed were:<br> + o globals.pl<br> + o CGI.pl<br> + o alternately, you can try commenting all references to 'crypt'<br> + string and replace them with similar lines but without encrypt()<br> + or crypr() functions insida all files.<br> + 12. Replaced sendmail with Windmail. Basically, you have to come up with a<br> + sendmail substitute for NT. Someone said that they used a Perl module<br> + (Net::SMTP), but I was trying to save time and do as little Perl coding<br> + as possible.<br> + 13. Added "perl" to the beginning of all Perl system calls that use a perl<br> + script as an argument and renamed processmail to processmail.pl.<br> + 14. In processmail.pl, I added binmode(HANDLE) before all read() calls. I'm<br> + not sure about this one, but the read() under NT wasn't counting the<br> + EOLs without the binary read."<br> + </P > </P ></DIV @@ -12464,12 +13002,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1952" +NAME="AEN2080" ></A ><B >A.9.5. </B -> I'm having trouble with the perl modules for NT not being - able to talk to to the database. +> I'm having trouble with the perl modules for NT not being able to talk to + to the database. </P ></DIV ><DIV @@ -12509,18 +13047,18 @@ CLASS="PROMPT" >PPM></TT > <B CLASS="COMMAND" ->install DBI DBD-mysql - GD</B +>install DBI DBD-mysql GD</B > </P ></LI ></OL -> I reckon TimeDate and Data::Dumper come - with the activeperl. You can check the ActiveState site - for packages for installation through PPM. <A -HREF=" http://www.activestate.com/Packages/" +> + I reckon TimeDate and Data::Dumper come with the activeperl. You can check + the ActiveState site for packages for installation through PPM. + <A +HREF=" http://www.activestate.com/Packages/" TARGET="_top" -> http://www.activestate.com/Packages/</A +> http://www.activestate.com/Packages/</A > </P ></DIV @@ -12539,12 +13077,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1973" +NAME="AEN2101" ></A ><B >A.10.1. </B -> The query page is very confusing. Isn't there a simpler - way to query? +> The query page is very confusing. Isn't there a simpler way to query? </P ></DIV ><DIV @@ -12552,12 +13089,13 @@ CLASS="ANSWER" ><P ><B > </B -> We are developing in that direction. You can follow - progress on this at <A +> We are developing in that direction. You can follow progress on this + at <A HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=16775" TARGET="_top" -> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A ->. Some functionality is available in Bugzilla 2.12, and is available as "quicksearch.html" +> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A +>. Some functionality + is available in Bugzilla 2.12, and is available as "quicksearch.html" </P ></DIV ></DIV @@ -12567,13 +13105,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1979" +NAME="AEN2107" ></A ><B >A.10.2. </B -> I'm confused by the behavior of the "accept" button in the - Show Bug form. Why doesn't it assign the bug to me when I - accept it? +> I'm confused by the behavior of the "accept" button in the Show Bug form. + Why doesn't it assign the bug to me when I accept it? </P ></DIV ><DIV @@ -12581,9 +13118,9 @@ CLASS="ANSWER" ><P ><B > </B -> The current behavior is acceptable to bugzilla.mozilla.org - and most users. I personally don't like it. You have - your choice of patches to change this behavior, however. +> The current behavior is acceptable to bugzilla.mozilla.org and most + users. I personally don't like it. You have your choice of patches + to change this behavior, however. <P ></P ><TABLE @@ -12594,7 +13131,7 @@ BORDER="0" ><A HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029" TARGET="_top" -> Add a "and accept bug" radio button</A +> Add a "and accept bug" radio button</A ></TD ></TR ><TR @@ -12602,16 +13139,16 @@ TARGET="_top" ><A HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153" TARGET="_top" -> "Accept" button automatically assigns to you</A +> "Accept" button automatically assigns to you</A ></TD ></TR ></TBODY ></TABLE ><P ></P -> Note that these patches are somewhat dated. - You will need to do the find and replace manually to apply - them. They are very small, though. It is easy. +> + Note that these patches are somewhat dated. You will need to do the find + and replace manually to apply them. They are very small, though. It is easy. </P ></DIV ></DIV @@ -12621,12 +13158,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1989" +NAME="AEN2117" ></A ><B >A.10.3. </B -> I can't upload anything into the database via the "Create - Attachment" link. What am I doing wrong? +> I can't upload anything into the database via the "Create Attachment" + link. What am I doing wrong? </P ></DIV ><DIV @@ -12634,10 +13171,9 @@ CLASS="ANSWER" ><P ><B > </B -> The most likely cause is a very old browser or a browser - that is incompatible with file upload via POST. Download - the latest Netscape, Microsoft, or Mozilla browser to - handle uploads correctly. +> The most likely cause is a very old browser or a browser that is + incompatible with file upload via POST. Download the latest Netscape, + Microsoft, or Mozilla browser to handle uploads correctly. </P ></DIV ></DIV @@ -12647,12 +13183,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1994" +NAME="AEN2122" ></A ><B >A.10.4. </B -> Email submissions to Bugzilla that have attachments end up - asking me to save it as a "cgi" file. +> Email submissions to Bugzilla that have attachments end up asking me to + save it as a "cgi" file. </P ></DIV ><DIV @@ -12660,10 +13196,9 @@ CLASS="ANSWER" ><P ><B > </B -> Yup. Just rename it once you download it, or save it - under a different filename. This will not be fixed - anytime too soon, because it would cripple some other - functionality. +> Yup. Just rename it once you download it, or save it under a different + filename. This will not be fixed anytime too soon, because it would + cripple some other functionality. </P ></DIV ></DIV @@ -12673,12 +13208,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1999" +NAME="AEN2127" ></A ><B >A.10.5. </B -> How do I change a keyword in Bugzilla, once some bugs are - using it? +> How do I change a keyword in Bugzilla, once some bugs are using it? </P ></DIV ><DIV @@ -12686,10 +13220,9 @@ CLASS="ANSWER" ><P ><B > </B -> In the Bugzilla administrator UI, edit the keyword and it - will let you replace the old keyword name with a new one. - This will cause a problem with the keyword cache. Run - sanitycheck.cgi to fix it. +> In the Bugzilla administrator UI, edit the keyword and it will let you + replace the old keyword name with a new one. This will cause a problem + with the keyword cache. Run sanitycheck.cgi to fix it. </P ></DIV ></DIV @@ -12707,7 +13240,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN2006" +NAME="AEN2134" ></A ><B >A.11.1. </B @@ -12722,19 +13255,26 @@ CLASS="ANSWER" > Try <A HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Webtools&component=Bugzilla" TARGET="_top" -> this link</A -> to view current bugs or requests for enhancement for Bugzilla. +> this link</A +> to view current bugs or requests for + enhancement for Bugzilla. </P ><P -> You can view bugs marked for 2.14 release <A +> You can view bugs marked for 2.14 release + <A HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bugzilla&target_milestone=Bugzilla+2.14" TARGET="_top" >here</A ->. This list includes bugs for the 2.14 release that have already been fixed and checked into CVS. Please consult the <A +>. + This list includes bugs for the 2.14 release that have already + been fixed and checked into CVS. Please consult the + <A HREF="http://www.mozilla.org/projects/bugzilla/" TARGET="_top" -> Bugzilla Project Page</A -> for details on how to check current sources out of CVS so you can have these bug fixes early! +> Bugzilla Project Page</A +> for details on how to + check current sources out of CVS so you can have these + bug fixes early! </P ></DIV ></DIV @@ -12744,13 +13284,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN2015" +NAME="AEN2143" ></A ><B >A.11.2. </B -> How can I change the default priority to a null value? - For instance, have the default priority be "---" instead - of "P2"? +> How can I change the default priority to a null value? For instance, have the default + priority be "---" instead of "P2"? </P ></DIV ><DIV @@ -12761,8 +13300,13 @@ CLASS="ANSWER" > This is well-documented here: <A HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862" TARGET="_top" -> http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A ->. 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... +> http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A +>. 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... </P ></DIV ></DIV @@ -12772,12 +13316,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN2021" +NAME="AEN2149" ></A ><B >A.11.3. </B -> What's the best way to submit patches? What guidelines - should I follow? +> What's the best way to submit patches? What guidelines should I follow? </P ></DIV ><DIV @@ -12791,49 +13334,44 @@ CLASS="ANSWER" TYPE="1" ><LI ><P -> Enter a bug into bugzilla.mozilla.org for the - "Webtools" product, "Bugzilla" component. +> Enter a bug into bugzilla.mozilla.org for the "Webtools" product, + "Bugzilla" component. </P ></LI ><LI ><P -> Upload your patch as a unified DIFF (having used - "diff -u" against the <EM ->current - sources</EM -> checked out of CVS), or new - source file by clicking "Create a new attachment" - link on the bug page you've just created, and - include any descriptions of database changes you may - make, into the bug ID you submitted in step #1. Be - sure and click the "Patch" radio button to indicate - the text you are sending is a patch! +> Upload your patch as a unified DIFF (having used "diff -u" against + the <EM +>current sources</EM +> checked out of CVS), + or new source file by clicking + "Create a new attachment" link on the bug page you've just created, and + include any descriptions of database changes you may make, into the bug + ID you submitted in step #1. Be sure and click the "Patch" radio + button to indicate the text you are sending is a patch! </P ></LI ><LI ><P > Announce your patch and the associated URL - (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) - for discussion in the newsgroup - (netscape.public.mozilla.webtools). You'll get a - really good, fairly immediate reaction to the - implications of your patch, which will also give us - an idea how well-received the change would be. + (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) for discussion in + the newsgroup (netscape.public.mozilla.webtools). You'll get a really + good, fairly immediate reaction to the implications of your patch, + which will also give us an idea how well-received the change would + be. </P ></LI ><LI ><P -> If it passes muster with minimal modification, the - person to whom the bug is assigned in Bugzilla is - responsible for seeing the patch is checked into - CVS. +> If it passes muster with minimal modification, the person to whom + the bug is assigned in Bugzilla is responsible for seeing the patch + is checked into CVS. </P ></LI ><LI ><P -> Bask in the glory of the fact that you helped write - the most successful open-source bug-tracking - software on the planet :) +> Bask in the glory of the fact that you helped write the most successful + open-source bug-tracking software on the planet :) </P ></LI ></OL @@ -13086,7 +13624,7 @@ CLASS="SECTION" ><HR><H2 CLASS="SECTION" ><A -NAME="AEN2089" +NAME="AEN2217" >C.2.1. Bugzilla Database Basics</A ></H2 ><P @@ -13209,7 +13747,7 @@ CLASS="SECTION" ><HR><H3 CLASS="SECTION" ><A -NAME="AEN2118" +NAME="AEN2246" >C.2.1.1. Bugzilla Database Tables</A ></H3 ><P @@ -13683,107 +14221,144 @@ CLASS="CHAPTER" ><HR><H1 ><A NAME="VARIANTS" ->Chapter 7. Bugzilla Variants</A +>Chapter 7. Bugzilla Variants and Competitors</A ></H1 -><DIV -CLASS="NOTE" ><P +>I created this section to answer questions about Bugzilla + competitors and variants, then found a wonderful site which covers + an awful lot of what I wanted to discuss. Rather than quote it in + its entirety, I'll simply refer you here: <A +HREF="http://linas.org/linux/pm.html" +TARGET="_top" +>http://linas.org/linux/pm.html</A ></P -><TABLE -CLASS="NOTE" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" +><DIV +CLASS="SECTION" +><HR><H1 +CLASS="SECTION" +><A +NAME="RHBUGZILLA" +>7.1. Red Hat Bugzilla</A +></H1 ><P -> 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. +> Red Hat Bugzilla is probably the most popular Bugzilla variant + on the planet. One of the major benefits of Red Hat Bugzilla is + the ability to work with Oracle, MySQL, and PostGreSQL databases + serving as the back-end, instead of just MySQL. Dave Lawrence + has worked very hard to keep Red Hat Bugzilla up-to-date, and + many people prefer the snappier-looking page layout of Red Hat + Bugzilla to the default Mozilla-standard formatting. </P -></TD -></TR -></TABLE +><P +>URL: <A +HREF="http://bugzilla.redhat.com/bugzilla/" +TARGET="_top" +>http://bugzilla.redhat.com/bugzilla/</A +></P ></DIV ><DIV CLASS="SECTION" ><HR><H1 CLASS="SECTION" ><A -NAME="RHBUGZILLA" ->7.1. Red Hat Bugzilla</A +NAME="VARIANT_FENRIS" +>7.2. Loki Bugzilla (Fenris)</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="AEN2143" -></A -><BLOCKQUOTE -CLASS="BLOCKQUOTE" +>Fenris can be found at <A +HREF="http://fenris.lokigames.com/" +TARGET="_top" +>http://fenris.lokigames.com</A +>. It is a fork from Bugzilla.</P +></DIV +><DIV +CLASS="SECTION" +><HR><H1 +CLASS="SECTION" +><A +NAME="VARIANT_ISSUEZILLA" +>7.3. Issuezilla</A +></H1 ><P -CLASS="LITERALLAYOUT" -> Hello. I apologize that I am getting back to you so late. It has been difficult to keep<br> -up with email this past week. I have checked out your updated documentation and I will<br> -have to say very good work. A few notes and additions as follows.<br> -<br> -(ed: from the FAQ)<br> ->For the record, we are not using any template type implementation for the cosmetic changes <br> ->maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have <br> ->gotten a little carried away with it but the corporate types asked for a more standardized <br> ->interface to match up with other projects relating to Red Hat web sites. A lot of other web <br> ->based internal tools I am working on also look like Bugzilla. <br> -<br> -<br> -This should probably be changed since we are now in fact using Text::Template for most<br> -of the html rendering. You actually state this later in your numbered list.<br> -<br> -Also number 6 contradicts number 8 where number 6 would be the most up to date status<br> -on the Oracle port.<br> -<br> -Additional Information:<br> ------------------------------<br> -1. Comments are now stored in varchar fields of 4k in size each. If the comment is more<br> -than 4k it is broken up into chunks and given a sort number so each comment can be re<br> -assembled in the correct order. This was done because originally I was storing the comments<br> -in a long datatype which unfortunately cannot be indexed or joined with another table. This<br> -cause the search of text within the long description to be disabled for a long time. That<br> -is now working and is nto showing any noticeble performance hit that I can tell. <br> -<br> -2. Work is being started on internationalizing the Bugzilla source we have to allow our<br> -Japanese customers to enter bug reports into a single bugzilla system. This will probably<br> -be done by using the nvarchar data types supported by Oracle which allows storage of<br> -double byte characters and also the use of the Accept-Language in the http header for <br> -detection by Bugilla of which language to render.<br> -<br> -3. Of course even more cosmetic changes. It is difficult to keep up with the ever <br> -changing faces of www.redhat.com.<br> -<br> -4. Some convenience enhancements in the administration utilities. And more integration<br> -with other internal/external Red Hat web sites.<br> -<br> -I hope this information may prove helpful for your documentation. Please contact<br> -me if you have any more question or I can do anything else.<br> -<br> -Regards<br> - </P -></BLOCKQUOTE -> +>Issuezilla is another fork from Bugzilla, and seems nearly + as popular as the Red Hat Bugzilla fork. Some Issuezilla team + members are regular contributors to the Bugzilla mailing + list/newsgroup. Issuezilla is not the primary focus of + bug-tracking at tigris.org, however. Their Java-based + bug-tracker, <A +HREF="#VARIANT_SCARAB" +>Scarab, a newfangled Java-based issue tracker</A +>, is under heavy development + and looks promising!</P +><P +>URL: <A +HREF="http://issuezilla.tigris.org/servlets/ProjectHome" +TARGET="_top" +>http://issuezilla.tigris.org/servlets/ProjectHome</A +></P +></DIV +><DIV +CLASS="SECTION" +><HR><H1 +CLASS="SECTION" +><A +NAME="VARIANT_SCARAB" +>7.4. Scarab</A +></H1 +><P +>Scarab is a promising new bug-tracking system built using + Java Serlet technology. As of this writing, no source code has + been released as a package, but you can obtain the code from + CVS. </P +><P +>URL: <A +HREF="http://scarab.tigris.org/" +TARGET="_top" +>http://scarab.tigris.org</A +></P +></DIV +><DIV +CLASS="SECTION" +><HR><H1 +CLASS="SECTION" +><A +NAME="VARIANT_PERFORCE" +>7.5. Perforce SCM</A +></H1 +><P +>Although Perforce isn't really a bug tracker, it can be used + as such through the <SPAN +CLASS="QUOTE" +>"jobs"</SPAN +> functionality.</P +><P +><A +HREF="http://www.perforce.com/perforce/technotes/note052.html" +TARGET="_top" +>http://www.perforce.com/perforce/technotes/note052.html</A +>http://www.perforce.com/perforce/technotes/note052.html</P +></DIV +><DIV +CLASS="SECTION" +><HR><H1 +CLASS="SECTION" +><A +NAME="VARIANT_SOURCEFORGE" +>7.6. SourceForge</A +></H1 +><P +>SourceForge is more of a way of coordinating geographically + distributed free software and open source projects over the + Internet than strictly a bug tracker, but if you're hunting for + bug-tracking for your open project, it may be just what the + software engineer ordered!</P +><P +>URL: <A +HREF="http://www.sourceforge.net" +TARGET="_top" +>http://www.sourceforge.net</A +></P ></DIV ></DIV ><DIV @@ -13793,13 +14368,79 @@ CLASS="APPENDIX" NAME="PATCHES" >Appendix D. Useful Patches and Utilities for Bugzilla</A ></H1 +><P +>Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</P ><DIV CLASS="SECTION" -><H1 +><HR><H1 +CLASS="SECTION" +><A +NAME="REWRITE" +>D.1. Apache <TT +CLASS="FILENAME" +>mod_rewrite</TT +> magic</A +></H1 +><P +>Apache's <TT +CLASS="FILENAME" +>mod_rewrite</TT +> module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</P +><P +></P +><OL +TYPE="1" +><LI +><P +> Make it so if someone types + <TT +CLASS="COMPUTEROUTPUT" +>http://www.foo.com/12345</TT +>, + Bugzilla spits back + http://www.foo.com/show_bug.cgi?id=12345. Try setting up + your VirtualHost section for Bugzilla with a rule like + this:</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +><VirtualHost 12.34.56.78> +RewriteEngine On +RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R] +</VirtualHost> + </PRE +></FONT +></TD +></TR +></TABLE +></LI +><LI +><P +>There are many, many more things you can do with + mod_rewrite. As time goes on, I will include many more in + the Guide. For now, though, please refer to the mod_rewrite + documentation at <A +HREF="http://www.apache.org" +TARGET="_top" +>http://www.apache.org</A +></P +></LI +></OL +></DIV +><DIV +CLASS="SECTION" +><HR><H1 CLASS="SECTION" ><A NAME="SETPERL" ->D.1. The setperl.csh Utility</A +>D.2. The setperl.csh Utility</A ></H1 ><P > You can use the "setperl.csh" utility to quickly and @@ -13944,7 +14585,7 @@ CLASS="COMMAND" <DIV CLASS="EXAMPLE" ><A -NAME="AEN2193" +NAME="AEN2360" ></A ><P ><B @@ -13977,7 +14618,7 @@ CLASS="SECTION" CLASS="SECTION" ><A NAME="CMDLINE" ->D.2. Command-line Bugzilla Queries</A +>D.3. Command-line Bugzilla Queries</A ></H1 ><P > Users can query Bugzilla from the command line using this suite @@ -14113,7 +14754,7 @@ CLASS="SECTION" CLASS="SECTION" ><A NAME="QUICKSEARCH" ->D.3. The Quicksearch Utility</A +>D.4. The Quicksearch Utility</A ></H1 ><P > Quicksearch is a new, experimental feature of the 2.12 release. @@ -14182,7 +14823,7 @@ NAME="GFDL" ><P >Version 1.1, March 2000</P ><A -NAME="AEN2249" +NAME="AEN2416" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -14681,7 +15322,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="AEN2339" +NAME="AEN2506" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" @@ -14720,7 +15361,7 @@ CLASS="GLOSSDIV" ><H1 CLASS="GLOSSDIV" ><A -NAME="AEN2344" +NAME="AEN2511" >0-9, high ascii</A ></H1 ><DL @@ -14762,11 +15403,27 @@ NAME="GLOSS_A" ><DL ><DT ><B ->There are no entries for A</B +>Apache</B ></DT ><DD ><P -></P +>In this context, Apache is the web server most + commonly used for serving up + <I +CLASS="GLOSSTERM" +>Bugzilla</I +> pages. Contrary to + popular belief, the apache web server has nothing to do + with the ancient and noble Native American tribe, but + instead derived its name from the fact that it was + <SPAN +CLASS="QUOTE" +>"a patchy"</SPAN +> version of the original + <SPAN +CLASS="ACRONYM" +>NCSA</SPAN +> world-wide-web server.</P ></DD ></DL ></DIV @@ -14831,6 +15488,139 @@ CLASS="QUOTE" > is moderately flexible according to the needs of the organization using it, though.</P ></DD +><DT +><B +>Bugzilla</B +></DT +><DD +><P +> Bugzilla is the industry-standard bug tracking system. It + is quite popular among Open Source enthusiasts. + </P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A +NAME="GLOSS_C" +></A +></H1 +><DL +><DT +><A +NAME="GLOSS_COMPONENT" +><B +>Component</B +></A +></DT +><DD +><P +> A Component is a subsection of a Product. It should be a + narrow category, tailored to your organization. All + Products must contain at least one Component (and, as a + matter of fact, creating a Product with no Components will + create an error in Bugzilla). + </P +></DD +><DT +><A +NAME="GLOSS_CPAN" +><B +><SPAN +CLASS="ACRONYM" +>CPAN</SPAN +></B +></A +></DT +><DD +><P +><SPAN +CLASS="ACRONYM" +>CPAN</SPAN +> stands for the + <SPAN +CLASS="QUOTE" +>"Comprehensive Perl Archive Network"</SPAN +>. CPAN + maintains a large number of extremely useful + <I +CLASS="GLOSSTERM" +>Perl</I +> modules. By themselves, Perl + modules generally do nothing, but when used as part of a + larger program, they provide much-needed algorithms and + functionality.</P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A +NAME="GLOSS_D" +>D</A +></H1 +><DL +><DT +><B +>daemon</B +></DT +><DD +><P +>A daemon is a computer program which runs in the + background. In general, most daemons are started at boot + time via System V init scripts, or through RC scripts on + BSD-based systems. <I +CLASS="GLOSSTERM" +>mysqld</I +>, the + MySQL server, and <I +CLASS="GLOSSTERM" +>apache</I +>, a web + server, are generally run as daemons.</P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A +NAME="GLOSS_G" +></A +></H1 +><DL +><DT +><B +>Groups</B +></DT +><DD +><P +>The word <SPAN +CLASS="QUOTE" +>"Groups"</SPAN +> has a very special + meaning to Bugzilla. Bugzilla's main security mechanism + comes by lumping users into groups, and assigning those + groups certain privileges to + <I +CLASS="GLOSSTERM" +>Products</I +> and + <I +CLASS="GLOSSTERM" +>Components</I +> in the + <I +CLASS="GLOSSTERM" +>Bugzilla</I +> database.</P +></DD ></DL ></DIV ><DIV @@ -14860,6 +15650,33 @@ CLASS="GLOSSDIV" ><H1 CLASS="GLOSSDIV" ><A +NAME="GLOSS_M" +>M</A +></H1 +><DL +><DT +><B +>mysqld</B +></DT +><DD +><P +>mysqld is the name of the + <I +CLASS="GLOSSTERM" +>daemon</I +> for the MySQL database. In + general, it is invoked automatically through the use of + the System V init scripts on GNU/Linux and AT&T System + V-based systems, such as Solaris and HP/UX, or through the + RC scripts on BSD-based systems.</P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A NAME="GLOSS_P" >P</A ></H1 @@ -14878,7 +15695,7 @@ NAME="GLOSS_P" ><DIV CLASS="EXAMPLE" ><A -NAME="AEN2389" +NAME="AEN2602" ></A ><P ><B @@ -14922,6 +15739,22 @@ CLASS="QUOTE" >.</P ></DIV ></DD +><DT +><B +>Perl</B +></DT +><DD +><P +>First written by Larry Wall, Perl is a remarkable + program language. It has the benefits of the flexibility + of an interpreted scripting language (such as shell + script), combined with the speed and power of a compiled + language, such as C. <I +CLASS="GLOSSTERM" +>Bugzilla</I +> is + maintained in Perl.</P +></DD ></DL ></DIV ><DIV @@ -14975,8 +15808,11 @@ NAME="GLOSS_R" ></H1 ><DL ><DT +><A +NAME="GLOSS_RECURSION" ><B >Recursion</B +></A ></DT ><DD ><P @@ -14999,13 +15835,114 @@ CLASS="GLOSSDIV" ><H1 CLASS="GLOSSDIV" ><A +NAME="GLOSS_S" +>S</A +></H1 +><DL +><DT +><B +><SPAN +CLASS="ACRONYM" +>SGML</SPAN +></B +></DT +><DD +><P +><SPAN +CLASS="ACRONYM" +>SGML</SPAN +> stands for <SPAN +CLASS="QUOTE" +>"Standard + Generalized Markup Language"</SPAN +>. Created in the + 1980's to provide an extensible means to maintain + documentation based upon content instead of presentation, + <SPAN +CLASS="ACRONYM" +>SGML</SPAN +> has withstood the test of time as + a robust, powerful language. + <I +CLASS="GLOSSTERM" +><SPAN +CLASS="ACRONYM" +>XML</SPAN +></I +> is the + <SPAN +CLASS="QUOTE" +>"baby brother"</SPAN +> of SGML; any valid + <SPAN +CLASS="ACRONYM" +>XML</SPAN +> document it, by definition, a valid + <SPAN +CLASS="ACRONYM" +>SGML</SPAN +> document. The document you are + reading is written and maintained in + <SPAN +CLASS="ACRONYM" +>SGML</SPAN +>, and is also valid + <SPAN +CLASS="ACRONYM" +>XML</SPAN +> if you modify the Document Type + Definition.</P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A +NAME="GLOSS_T" +>T</A +></H1 +><DL +><DT +><A +NAME="GLOSS_TARGET_MILESTONE" +><B +>Target Milestone</B +></A +></DT +><DD +><P +> Target Milestones are Product goals. They are + configurable on a per-Product basis. Most software + development houses have a concept of + <SPAN +CLASS="QUOTE" +>"milestones"</SPAN +> where the people funding a + project expect certain functionality on certain dates. + Bugzilla facilitates meeting these milestones by giving + you the ability to declare by which milestone a bug will be + fixed, or an enhancement will be implemented. + </P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A NAME="GLOSS_Z" >Z</A ></H1 ><DL ><DT +><A +NAME="ZARRO-BOOGS-FOUND" ><B >Zarro Boogs Found</B +></A ></DT ><DD ><P diff --git a/docs/html/aboutthisguide.html b/docs/html/aboutthisguide.html index cdaabe99e..0d5a74da5 100644 --- a/docs/html/aboutthisguide.html +++ b/docs/html/aboutthisguide.html @@ -81,16 +81,15 @@ NAME="ABOUTTHISGUIDE" document you see today. </P ><P -> Despite the lack of updates, Bugzilla is simply the best piece - of bug-tracking software the world has ever seen. This document - is intended to be the comprehensive guide to the installation, - administration, maintenance, and use of the Bugzilla - bug-tracking system. +> Bugzilla is simply the best piece of bug-tracking software the + world has ever seen. This document is intended to be the + comprehensive guide to the installation, administration, + maintenance, and use of the Bugzilla bug-tracking system. </P ><P > This release of the Bugzilla Guide is the <EM ->2.14.0</EM +>2.14</EM > release. It is so named that it may match the current version of Bugzilla. The numbering tradition stems from that used for many free software projects, @@ -120,7 +119,7 @@ TARGET="_top" of Bugzilla, as of this writing (August 10, 2001) is 2.14; if something were seriously wrong with that edition of the Guide, subsequent releases would receive an additional dotted-decimal - digit to indicate the update (2.14.0.1, 2.14.0.2, etc.). + digit to indicate the update (2.14.1, 2.14.2, etc.). Got it? Good. </P ><P diff --git a/docs/html/administration.html b/docs/html/administration.html index 4601f697b..6a107f712 100644 --- a/docs/html/administration.html +++ b/docs/html/administration.html @@ -177,11 +177,20 @@ COLOR="RED" do with it? </FONT ><P -> So you followed the installation instructions 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 business needs to be to setup the - operating parameters for bugzilla. +> So you followed <SPAN +CLASS="QUOTE" +>"<A +HREF="installation.html" +>Bugzilla Installation</A +>"</SPAN +> to the + letter, and logged into Bugzilla for the very first time with your + super-duper god account. You sit, contentedly staring at the + Bugzilla Query Screen, the worst of the whole mad business of + installing this terrific program behind you. It seems, though, you + have nothing yet to query! Your first act of business should be to + setup the operating parameters for Bugzilla so you can get busy + getting data into your bug tracker. </P ></DIV ><DIV diff --git a/docs/html/bonsai.html b/docs/html/bonsai.html index e37bf3ca3..5be34aff5 100644 --- a/docs/html/bonsai.html +++ b/docs/html/bonsai.html @@ -74,7 +74,23 @@ NAME="BONSAI" >5.1. Bonsai</A ></H1 ><P ->We need Bonsai integration information.</P +>Bonsai is a web-based tool for managing <A +HREF="cvs.html" +>CVS, the Concurrent Versioning System</A +> + . Using Bonsai, administrators can control open/closed status + of trees, query a fast relational database back-end for change, + branch, and comment information, and view changes made since the + last time the tree was closed. These kinds of changes cause the + engineer responsible to be <SPAN +CLASS="QUOTE" +>"on the hook"</SPAN +> (include + cool URL link here for Hook policies at mozilla.org). Bonsai + also includes gateways to <A +HREF="tinderbox.html" +>Tinderbox, the Mozilla automated build management system</A +> and Bugzilla </P ></DIV ><DIV CLASS="NAVFOOTER" diff --git a/docs/html/cmdline.html b/docs/html/cmdline.html index ed011a946..7a1e1ba44 100644 --- a/docs/html/cmdline.html +++ b/docs/html/cmdline.html @@ -71,7 +71,7 @@ CLASS="SECTION" CLASS="SECTION" ><A NAME="CMDLINE" ->D.2. Command-line Bugzilla Queries</A +>D.3. Command-line Bugzilla Queries</A ></H1 ><P > Users can query Bugzilla from the command line using this suite diff --git a/docs/html/conventions.html b/docs/html/conventions.html index 26c68f40a..c5bf9dcbc 100644 --- a/docs/html/conventions.html +++ b/docs/html/conventions.html @@ -79,7 +79,7 @@ NAME="CONVENTIONS" ><DIV CLASS="INFORMALTABLE" ><A -NAME="AEN135" +NAME="AEN129" ></A ><P ></P diff --git a/docs/html/copyright.html b/docs/html/copyright.html index 939b01b2c..e3de39020 100644 --- a/docs/html/copyright.html +++ b/docs/html/copyright.html @@ -74,7 +74,7 @@ NAME="COPYRIGHT" >1.2. Copyright Information</A ></H1 ><A -NAME="AEN76" +NAME="AEN70" ></A ><TABLE BORDER="0" diff --git a/docs/html/cvs.html b/docs/html/cvs.html index 36d2c6420..55eb0a261 100644 --- a/docs/html/cvs.html +++ b/docs/html/cvs.html @@ -74,7 +74,23 @@ NAME="CVS" >5.2. CVS</A ></H1 ><P ->CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</P +>CVS integration is best accomplished, at this point, using + the Bugzilla Email Gateway. There have been some files + submitted to allow greater CVS integration, but we need to make + certain that Bugzilla is not tied into one particular software + management package.</P +><P +> Follow the instructions in the FAQ for enabling Bugzilla e-mail + integration. Ensure that your check-in script sends an email to + your Bugzilla e-mail gateway with the subject of <SPAN +CLASS="QUOTE" +>"[Bug + XXXX]"</SPAN +>, and you can have CVS check-in comments append + to your Bugzilla bug. If you have your check-in script include + an @resolution field, you can even change the Bugzilla bug + state. + </P ></DIV ><DIV CLASS="NAVFOOTER" diff --git a/docs/html/dbdoc.html b/docs/html/dbdoc.html index f952c1751..a28d1f91f 100644 --- a/docs/html/dbdoc.html +++ b/docs/html/dbdoc.html @@ -137,7 +137,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN2089" +NAME="AEN2217" >C.2.1. Bugzilla Database Basics</A ></H2 ><P @@ -260,7 +260,7 @@ CLASS="SECTION" ><H3 CLASS="SECTION" ><A -NAME="AEN2118" +NAME="AEN2246" >C.2.1.1. Bugzilla Database Tables</A ></H3 ><P diff --git a/docs/html/faq.html b/docs/html/faq.html index 4977fc915..0765b564a 100644 --- a/docs/html/faq.html +++ b/docs/html/faq.html @@ -81,66 +81,65 @@ HREF="faq.html#FAQ_GENERAL" ><DL ><DT >A.1.1. <A -HREF="faq.html#AEN1481" +HREF="faq.html#AEN1620" > Where can I find information about Bugzilla?</A ></DT ><DT >A.1.2. <A -HREF="faq.html#AEN1487" +HREF="faq.html#AEN1626" > What license is Bugzilla distributed under? </A ></DT ><DT >A.1.3. <A -HREF="faq.html#AEN1493" +HREF="faq.html#AEN1632" > How do I get commercial support for Bugzilla? </A ></DT ><DT >A.1.4. <A -HREF="faq.html#AEN1500" -> What major companies or projects are currently using - Bugzilla for bug-tracking? +HREF="faq.html#AEN1639" +> What major companies or projects are currently using Bugzilla + for bug-tracking? </A ></DT ><DT >A.1.5. <A -HREF="faq.html#AEN1525" +HREF="faq.html#AEN1664" > Who maintains Bugzilla? </A ></DT ><DT >A.1.6. <A -HREF="faq.html#AEN1530" -> How does Bugzilla stack up against other bug-tracking - databases? +HREF="faq.html#AEN1670" +> How does Bugzilla stack up against other bug-tracking databases? </A ></DT ><DT >A.1.7. <A -HREF="faq.html#AEN1537" +HREF="faq.html#AEN1677" > How do I change my user name in Bugzilla? </A ></DT ><DT >A.1.8. <A -HREF="faq.html#AEN1542" -> Why doesn't Bugzilla offer this or that feature or - compatability with this other tracking software? +HREF="faq.html#AEN1682" +> Why doesn't Bugzilla offer this or that feature or compatability + with this other tracking software? </A ></DT ><DT >A.1.9. <A -HREF="faq.html#AEN1549" +HREF="faq.html#AEN1689" > Why MySQL? I'm interested in seeing Bugzilla run on Oracle/Sybase/Msql/PostgreSQL/MSSQL? </A ></DT ><DT >A.1.10. <A -HREF="faq.html#AEN1567" -> Why do the scripts say "/usr/bonsaitools/bin/perl" instead - of "/usr/bin/perl" or something else? +HREF="faq.html#AEN1707" +> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of + "/usr/bin/perl" or something else? </A ></DT ></DL @@ -154,19 +153,19 @@ HREF="faq.html#FAQ_REDHAT" ><DL ><DT >A.2.1. <A -HREF="faq.html#AEN1584" +HREF="faq.html#AEN1724" > What about Red Hat Bugzilla? </A ></DT ><DT >A.2.2. <A -HREF="faq.html#AEN1592" +HREF="faq.html#AEN1732" > What are the primary benefits of Red Hat Bugzilla? </A ></DT ><DT >A.2.3. <A -HREF="faq.html#AEN1620" +HREF="faq.html#AEN1760" > What's the current status of Red Hat Bugzilla? </A ></DT @@ -181,20 +180,8 @@ HREF="faq.html#FAQ_LOKI" ><DL ><DT >A.3.1. <A -HREF="faq.html#AEN1636" -> What about Loki Bugzilla? - </A -></DT -><DT ->A.3.2. <A -HREF="faq.html#AEN1643" -> Who maintains Fenris (Loki Bugzilla) now? - </A -></DT -><DT ->A.3.3. <A -HREF="faq.html#AEN1648" -> +HREF="faq.html#AEN1773" +> What is Loki Bugzilla (Fenris)? </A ></DT ></DL @@ -208,204 +195,192 @@ HREF="faq.html#FAQ_PHB" ><DL ><DT >A.4.1. <A -HREF="faq.html#AEN1656" -> Is Bugzilla web-based or do you have to have specific - software or specific operating system on your machine? +HREF="faq.html#AEN1784" +> Is Bugzilla web-based or do you have to have specific software or + specific operating system on your machine? </A ></DT ><DT >A.4.2. <A -HREF="faq.html#AEN1661" -> Has anyone you know of already done any Bugzilla - integration with Perforce (SCM software)? +HREF="faq.html#AEN1789" +> Has anyone you know of already done any Bugzilla integration with + Perforce (SCM software)? </A ></DT ><DT >A.4.3. <A -HREF="faq.html#AEN1666" +HREF="faq.html#AEN1794" > Does Bugzilla allow the user to track multiple projects? </A ></DT ><DT >A.4.4. <A -HREF="faq.html#AEN1671" -> If I am on many projects, and search for all bugs assigned - to me, will Bugzilla list them for me and allow me to sort - by project, severity etc? +HREF="faq.html#AEN1799" +> If I am on many projects, and search for all bugs assigned to me, will + Bugzilla list them for me and allow me to sort by project, severity etc? </A ></DT ><DT >A.4.5. <A -HREF="faq.html#AEN1676" -> Does Bugzilla allow attachments (text, screenshots, urls - etc)? If yes, are there any that are NOT allowed? +HREF="faq.html#AEN1804" +> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes, + are there any that are NOT allowed? </A ></DT ><DT >A.4.6. <A -HREF="faq.html#AEN1681" -> Does Bugzilla allow us to define our own priorities and - levels? Do we have complete freedom to change the labels - of fields and format of them, and the choice of acceptable - values? +HREF="faq.html#AEN1809" +> Does Bugzilla allow us to define our own priorities and levels? Do we + have complete freedom to change the labels of fields and format of them, and + the choice of acceptable values? </A ></DT ><DT >A.4.7. <A -HREF="faq.html#AEN1686" -> The index.html page doesn't show the footer. It's really - annoying to have to go to the querypage just to check my - "my bugs" link. How do I get a footer on static HTML - pages? +HREF="faq.html#AEN1814" +> The index.html page doesn't show the footer. It's really annoying to have + to go to the querypage just to check my "my bugs" link. How do I get a footer + on static HTML pages? </A ></DT ><DT >A.4.8. <A -HREF="faq.html#AEN1692" -> Does Bugzilla provide any reporting features, metrics, - graphs, etc? You know, the type of stuff that management - likes to see. :) +HREF="faq.html#AEN1820" +> Does Bugzilla provide any reporting features, metrics, graphs, etc? You + know, the type of stuff that management likes to see. :) </A ></DT ><DT >A.4.9. <A -HREF="faq.html#AEN1700" -> Is there email notification and if so, what do you see - when you get an email? Do you see bug number and title or - is it only the number? +HREF="faq.html#AEN1828" +> Is there email notification and if so, what do you see when you get an + email? Do you see bug number and title or is it only the number? </A ></DT ><DT >A.4.10. <A -HREF="faq.html#AEN1705" +HREF="faq.html#AEN1833" > Can email notification be set up to send to multiple people, some on the To List, CC List, BCC List etc? </A ></DT ><DT >A.4.11. <A -HREF="faq.html#AEN1710" -> If there is email notification, do users have to have any - particular type of email application? +HREF="faq.html#AEN1838" +> If there is email notification, do users have to have any particular + type of email application? </A ></DT ><DT >A.4.12. <A -HREF="faq.html#AEN1717" -> If I just wanted to track certain bugs, as they go - through life, can I set it up to alert me via email - whenever that bug changes, whether it be owner, status or - description etc.? +HREF="faq.html#AEN1845" +> If I just wanted to track certain bugs, as they go through life, can I + set it up to alert me via email whenever that bug changes, whether it be + owner, status or description etc.? </A ></DT ><DT >A.4.13. <A -HREF="faq.html#AEN1722" -> Does Bugzilla allow data to be imported and exported? If I - had outsiders write up a bug report using a MS Word bug - template, could that template be imported into "matching" - fields? If I wanted to take the results of a query and - export that data to MS Excel, could I do that? +HREF="faq.html#AEN1850" +> Does Bugzilla allow data to be imported and exported? If I had outsiders + write up a bug report using a MS Word bug template, could that template be + imported into "matching" fields? If I wanted to take the results of a query + and export that data to MS Excel, could I do that? </A ></DT ><DT >A.4.14. <A -HREF="faq.html#AEN1730" -> Does Bugzilla allow fields to be added, changed or - deleted? If I want to customize the bug submission form to - meet our needs, can I do that using our terminology? +HREF="faq.html#AEN1858" +> Does Bugzilla allow fields to be added, changed or deleted? If I want to + customize the bug submission form to meet our needs, can I do that using our + terminology? </A ></DT ><DT >A.4.15. <A -HREF="faq.html#AEN1735" -> Has anyone converted Bugzilla to another language to be - used in other countries? Is it localizable? +HREF="faq.html#AEN1863" +> Has anyone converted Bugzilla to another language to be used in other + countries? Is it localizable? </A ></DT ><DT >A.4.16. <A -HREF="faq.html#AEN1740" -> Can a user create and save reports? Can they do this in - Word format? Excel format? +HREF="faq.html#AEN1868" +> Can a user create and save reports? Can they do this in Word format? + Excel format? </A ></DT ><DT >A.4.17. <A -HREF="faq.html#AEN1745" +HREF="faq.html#AEN1873" > Can a user re-run a report with a new project, same query? </A ></DT ><DT >A.4.18. <A -HREF="faq.html#AEN1750" -> Can a user modify an existing report and then save it into - another name? +HREF="faq.html#AEN1878" +> Can a user modify an existing report and then save it into another name? </A ></DT ><DT >A.4.19. <A -HREF="faq.html#AEN1755" -> Does Bugzilla have the ability to search by word, phrase, - compound search? +HREF="faq.html#AEN1883" +> Does Bugzilla have the ability to search by word, phrase, compound + search? </A ></DT ><DT >A.4.20. <A -HREF="faq.html#AEN1760" -> Can the admin person establish separate group and - individual user privileges? +HREF="faq.html#AEN1888" +> Can the admin person establish separate group and individual user + privileges? </A ></DT ><DT >A.4.21. <A -HREF="faq.html#AEN1765" -> Does Bugzilla provide record locking when there is - simultaneous access to the same bug? Does the second - person get a notice that the bug is in use or how are they - notified? +HREF="faq.html#AEN1893" +> Does Bugzilla provide record locking when there is simultaneous access + to the same bug? Does the second person get a notice that the bug is in use + or how are they notified? </A ></DT ><DT >A.4.22. <A -HREF="faq.html#AEN1770" +HREF="faq.html#AEN1898" > Are there any backup features provided? </A ></DT ><DT >A.4.23. <A -HREF="faq.html#AEN1776" +HREF="faq.html#AEN1904" > Can users be on the system while a backup is in progress? </A ></DT ><DT >A.4.24. <A -HREF="faq.html#AEN1781" -> What type of human resources are needed to be on staff to - install and maintain Bugzilla? Specifically, what type of - skills does the person need to have? I need to find out if - we were to go with Bugzilla, what types of individuals - would we need to hire and how much would that cost vs - buying an "Out-of-the-Box" solution. +HREF="faq.html#AEN1909" +> What type of human resources are needed to be on staff to install and + maintain Bugzilla? Specifically, what type of skills does the person need to + have? I need to find out if we were to go with Bugzilla, what types of + individuals would we need to hire and how much would that cost vs buying an + "Out-of-the-Box" solution. </A ></DT ><DT >A.4.25. <A -HREF="faq.html#AEN1788" -> What time frame are we looking at if we decide to hire - people to install and maintain the Bugzilla? Is this - something that takes hours or weeks to install and a - couple of hours per week to maintain and customize or is - this a multi-week install process, plus a full time job - for 1 person, 2 people, etc? +HREF="faq.html#AEN1916" +> What time frame are we looking at if we decide to hire people to install + and maintain the Bugzilla? Is this something that takes hours or weeks to + install and a couple of hours per week to maintain and customize or is this + a multi-week install process, plus a full time job for 1 person, 2 people, + etc? </A ></DT ><DT >A.4.26. <A -HREF="faq.html#AEN1793" -> Is there any licensing fee or other fees for using - Bugzilla? Any out-of-pocket cost other than the bodies - needed as identified above? +HREF="faq.html#AEN1921" +> Is there any licensing fee or other fees for using Bugzilla? Any + out-of-pocket cost other than the bodies needed as identified above? </A ></DT ></DL @@ -419,19 +394,19 @@ HREF="faq.html#FAQ_INSTALL" ><DL ><DT >A.5.1. <A -HREF="faq.html#AEN1800" +HREF="faq.html#AEN1928" > How do I download and install Bugzilla? </A ></DT ><DT >A.5.2. <A -HREF="faq.html#AEN1806" +HREF="faq.html#AEN1934" > How do I install Bugzilla on Windows NT? </A ></DT ><DT >A.5.3. <A -HREF="faq.html#AEN1811" +HREF="faq.html#AEN1939" > Is there an easy way to change the Bugzilla cookie name? </A ></DT @@ -446,25 +421,23 @@ HREF="faq.html#FAQ_SECURITY" ><DL ><DT >A.6.1. <A -HREF="faq.html#AEN1818" -> How do I completely disable MySQL security if it's giving - me problems (I've followed the instructions in the - installation section of this guide!)? +HREF="faq.html#AEN1946" +> How do I completely disable MySQL security if it's giving me problems + (I've followed the instructions in the installation section of this guide!)? </A ></DT ><DT >A.6.2. <A -HREF="faq.html#AEN1824" +HREF="faq.html#AEN1952" > Are there any security problems with Bugzilla? </A ></DT ><DT >A.6.3. <A -HREF="faq.html#AEN1829" -> I've implemented the security fixes mentioned in Chris - Yeh's security advisory of 5/10/2000 advising not to run - MySQL as root, and am running into problems with MySQL no - longer working correctly. +HREF="faq.html#AEN1957" +> I've implemented the security fixes mentioned in Chris Yeh's security + advisory of 5/10/2000 advising not to run MySQL as root, and am running into + problems with MySQL no longer working correctly. </A ></DT ></DL @@ -478,49 +451,48 @@ HREF="faq.html#FAQ_EMAIL" ><DL ><DT >A.7.1. <A -HREF="faq.html#AEN1836" -> I have a user who doesn't want to receive any more email - from Bugzilla. How do I stop it entirely for this user? +HREF="faq.html#AEN1964" +> I have a user who doesn't want to receive any more email from Bugzilla. + How do I stop it entirely for this user? </A ></DT ><DT >A.7.2. <A -HREF="faq.html#AEN1841" -> I'm evaluating/testing Bugzilla, and don't want it to send - email to anyone but me. How do I do it? +HREF="faq.html#AEN1969" +> I'm evaluating/testing Bugzilla, and don't want it to send email to + anyone but me. How do I do it? </A ></DT ><DT >A.7.3. <A -HREF="faq.html#AEN1846" -> I want whineatnews.pl to whine at something more, or other - than, only new bugs. How do I do it? +HREF="faq.html#AEN1974" +> I want whineatnews.pl to whine at something more, or other than, only new + bugs. How do I do it? </A ></DT ><DT >A.7.4. <A -HREF="faq.html#AEN1852" -> I don't like/want to use Procmail to hand mail off to - bug_email.pl. What alternatives do I have? +HREF="faq.html#AEN1980" +> I don't like/want to use Procmail to hand mail off to bug_email.pl. + What alternatives do I have? </A ></DT ><DT >A.7.5. <A -HREF="faq.html#AEN1859" -> How do I set up the email interface to submit/change bugs - via email? +HREF="faq.html#AEN1987" +> How do I set up the email interface to submit/change bugs via email? </A ></DT ><DT >A.7.6. <A -HREF="faq.html#AEN1864" -> Email takes FOREVER to reach me from bugzilla -- it's - extremely slow. What gives? +HREF="faq.html#AEN1992" +> Email takes FOREVER to reach me from bugzilla -- it's extremely slow. + What gives? </A ></DT ><DT >A.7.7. <A -HREF="faq.html#AEN1871" +HREF="faq.html#AEN1999" > How come email never reaches me from bugzilla changes? </A ></DT @@ -535,64 +507,61 @@ HREF="faq.html#FAQ_DB" ><DL ><DT >A.8.1. <A -HREF="faq.html#AEN1879" +HREF="faq.html#AEN2007" > I've heard Bugzilla can be used with Oracle? </A ></DT ><DT >A.8.2. <A -HREF="faq.html#AEN1884" -> Bugs are missing from queries, but exist in the database - (and I can pull them up by specifying the bug ID). What's - wrong? +HREF="faq.html#AEN2012" +> Bugs are missing from queries, but exist in the database (and I can pull + them up by specifying the bug ID). What's wrong? </A ></DT ><DT >A.8.3. <A -HREF="faq.html#AEN1889" -> I think my database might be corrupted, or contain invalid - entries. What do I do? +HREF="faq.html#AEN2017" +> I think my database might be corrupted, or contain invalid entries. What + do I do? </A ></DT ><DT >A.8.4. <A -HREF="faq.html#AEN1894" +HREF="faq.html#AEN2022" > I want to manually edit some entries in my database. How? </A ></DT ><DT >A.8.5. <A -HREF="faq.html#AEN1899" -> I try to add myself as a user, but Bugzilla always tells - me my password is wrong. +HREF="faq.html#AEN2027" +> I try to add myself as a user, but Bugzilla always tells me my password is wrong. </A ></DT ><DT >A.8.6. <A -HREF="faq.html#AEN1904" -> I think I've set up MySQL permissions correctly, but - bugzilla still can't connect. +HREF="faq.html#AEN2032" +> I think I've set up MySQL permissions correctly, but bugzilla still can't + connect. </A ></DT ><DT >A.8.7. <A -HREF="faq.html#AEN1909" -> How do I synchronize bug information among multiple - different Bugzilla databases? +HREF="faq.html#AEN2037" +> How do I synchronize bug information among multiple different Bugzilla + databases? </A ></DT ><DT >A.8.8. <A -HREF="faq.html#AEN1916" -> Why do I get bizarre errors when trying to submit data, - particularly problems with "groupset"? +HREF="faq.html#AEN2044" +> Why do I get bizarre errors when trying to submit data, particularly problems + with "groupset"? </A ></DT ><DT >A.8.9. <A -HREF="faq.html#AEN1921" -> How come even after I delete bugs, the long descriptions - show up? +HREF="faq.html#AEN2049" +> How come even after I delete bugs, the long descriptions show up? </A ></DT ></DL @@ -606,36 +575,34 @@ HREF="faq.html#FAQ_NT" ><DL ><DT >A.9.1. <A -HREF="faq.html#AEN1928" -> What is the easiest way to run Bugzilla on Win32 - (Win98+/NT/2K)? +HREF="faq.html#AEN2056" +> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)? </A ></DT ><DT >A.9.2. <A -HREF="faq.html#AEN1933" +HREF="faq.html#AEN2061" > Is there a "Bundle::Bugzilla" equivalent for Win32? </A ></DT ><DT >A.9.3. <A -HREF="faq.html#AEN1938" -> CGI's are failing with a "something.cgi is not a valid - Windows NT application" error. Why? +HREF="faq.html#AEN2066" +> CGI's are failing with a "something.cgi is not a valid Windows NT + application" error. Why? </A ></DT ><DT >A.9.4. <A -HREF="faq.html#AEN1946" -> Can I have some general instructions on how to make - Bugzilla on Win32 work? +HREF="faq.html#AEN2074" +> Can I have some general instructions on how to make Bugzilla on Win32 work? </A ></DT ><DT >A.9.5. <A -HREF="faq.html#AEN1952" -> I'm having trouble with the perl modules for NT not being - able to talk to to the database. +HREF="faq.html#AEN2080" +> I'm having trouble with the perl modules for NT not being able to talk to + to the database. </A ></DT ></DL @@ -649,38 +616,35 @@ HREF="faq.html#FAQ_USE" ><DL ><DT >A.10.1. <A -HREF="faq.html#AEN1973" -> The query page is very confusing. Isn't there a simpler - way to query? +HREF="faq.html#AEN2101" +> The query page is very confusing. Isn't there a simpler way to query? </A ></DT ><DT >A.10.2. <A -HREF="faq.html#AEN1979" -> I'm confused by the behavior of the "accept" button in the - Show Bug form. Why doesn't it assign the bug to me when I - accept it? +HREF="faq.html#AEN2107" +> I'm confused by the behavior of the "accept" button in the Show Bug form. + Why doesn't it assign the bug to me when I accept it? </A ></DT ><DT >A.10.3. <A -HREF="faq.html#AEN1989" -> I can't upload anything into the database via the "Create - Attachment" link. What am I doing wrong? +HREF="faq.html#AEN2117" +> I can't upload anything into the database via the "Create Attachment" + link. What am I doing wrong? </A ></DT ><DT >A.10.4. <A -HREF="faq.html#AEN1994" -> Email submissions to Bugzilla that have attachments end up - asking me to save it as a "cgi" file. +HREF="faq.html#AEN2122" +> Email submissions to Bugzilla that have attachments end up asking me to + save it as a "cgi" file. </A ></DT ><DT >A.10.5. <A -HREF="faq.html#AEN1999" -> How do I change a keyword in Bugzilla, once some bugs are - using it? +HREF="faq.html#AEN2127" +> How do I change a keyword in Bugzilla, once some bugs are using it? </A ></DT ></DL @@ -694,23 +658,21 @@ HREF="faq.html#FAQ_HACKING" ><DL ><DT >A.11.1. <A -HREF="faq.html#AEN2006" +HREF="faq.html#AEN2134" > What bugs are in Bugzilla right now? </A ></DT ><DT >A.11.2. <A -HREF="faq.html#AEN2015" -> How can I change the default priority to a null value? - For instance, have the default priority be "---" instead - of "P2"? +HREF="faq.html#AEN2143" +> How can I change the default priority to a null value? For instance, have the default + priority be "---" instead of "P2"? </A ></DT ><DT >A.11.3. <A -HREF="faq.html#AEN2021" -> What's the best way to submit patches? What guidelines - should I follow? +HREF="faq.html#AEN2149" +> What's the best way to submit patches? What guidelines should I follow? </A ></DT ></DL @@ -729,7 +691,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1481" +NAME="AEN1620" ></A ><B >A.1.1. </B @@ -744,7 +706,7 @@ CLASS="ANSWER" information at <A HREF="http://www.mozilla.org/projects/bugzilla/" TARGET="_top" -> http://www.mozilla.org/projects/bugzilla/</A +> http://www.mozilla.org/projects/bugzilla/</A > </P ></DIV @@ -755,7 +717,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1487" +NAME="AEN1626" ></A ><B >A.1.2. </B @@ -767,11 +729,11 @@ CLASS="ANSWER" ><P ><B > </B -> Bugzilla is covered by the Mozilla Public License. See - details at <A +> Bugzilla is covered by the Mozilla Public License. + See details at <A HREF="http://www.mozilla.org/MPL/" TARGET="_top" -> http://www.mozilla.org/MPL/</A +> http://www.mozilla.org/MPL/</A > </P ></DIV @@ -782,7 +744,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1493" +NAME="AEN1632" ></A ><B >A.1.3. </B @@ -798,17 +760,16 @@ CLASS="ANSWER" HREF="http://www.collab.net/" TARGET="_top" >www.collab.net</A -> - offers Bugzilla as part of their standard offering to - large projects. They do have some minimum fees that are - pretty hefty, and generally aren't interested in small - projects. +> offers + Bugzilla as part of their standard offering to large projects. + They do have some minimum fees that are pretty hefty, and generally + aren't interested in small projects. </P ><P -> There are several experienced Bugzilla hackers on the - mailing list/newsgroup who are willing to whore themselves - out for generous compensation. Try sending a message to - the mailing list asking for a volunteer. +> There are several experienced + Bugzilla hackers on the mailing list/newsgroup who are willing + to whore themselves out for generous compensation. + Try sending a message to the mailing list asking for a volunteer. </P ></DIV ></DIV @@ -818,12 +779,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1500" +NAME="AEN1639" ></A ><B >A.1.4. </B -> What major companies or projects are currently using - Bugzilla for bug-tracking? +> What major companies or projects are currently using Bugzilla + for bug-tracking? </P ></DIV ><DIV @@ -833,9 +794,8 @@ CLASS="ANSWER" > </B > There are <EM >dozens</EM -> of major comapanies - with public Bugzilla sites to track bugs in their - products. A few include: +> of major comapanies with public + Bugzilla sites to track bugs in their products. A few include: <P ></P ><TABLE @@ -916,9 +876,8 @@ BORDER="0" > </P ><P -> Suffice to say, there are more than enough huge projects - using Bugzilla that we can safely say it's extremely - popular. +> Suffice to say, there are more than enough huge projects using Bugzilla + that we can safely say it's extremely popular. </P ></DIV ></DIV @@ -928,7 +887,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1525" +NAME="AEN1664" ></A ><B >A.1.5. </B @@ -940,16 +899,12 @@ CLASS="ANSWER" ><P ><B > </B -> There are many, many contributors from around the world - maintaining Bugzilla. The designated "Maintainer" is Tara - Hernandez, with QA support by Matthew Tuck. Dan Mosedale - and Dawn Endico are employees of Mozilla.org responsible - for the installation of Bugzilla there, and are very - frequent code contributors. Terry Weissman originally - ported Bugzilla, but "these days, Terry just hangs around - and heckles." The rest of us are mostly transient - developers; Bugzilla suits our needs, and we contribute - code as we have needs for updates. +> Bugzilla maintenance has been in a state of flux recently. + Please check <A +HREF="http://www.mozilla.org/projects/bugzilla/" +TARGET="_top" +>the Bugzilla Project Page for the latest details. </A +> </P ></DIV ></DIV @@ -959,12 +914,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1530" +NAME="AEN1670" ></A ><B >A.1.6. </B -> How does Bugzilla stack up against other bug-tracking - databases? +> How does Bugzilla stack up against other bug-tracking databases? </P ></DIV ><DIV @@ -985,7 +939,7 @@ CLASS="ANSWER" flexibility, and superior ease-of-use. </P ><P -> If you happen to be a commercial Bugzilla vendor, please +> If you happen to be a commercial bug-tracker vendor, please step forward with a rebuttal so I can include it in the FAQ. We're not in pursuit of Bugzilla ueber alles; we simply love having a powerful, open-source tool to get our @@ -999,7 +953,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1537" +NAME="AEN1677" ></A ><B >A.1.7. </B @@ -1011,9 +965,8 @@ CLASS="ANSWER" ><P ><B > </B -> You can't. However, the administrative account can, by - simply opening your user account in editusers.cgi and - changing the login name. +> You can't. However, the administrative account can, by simply opening + your user account in editusers.cgi and changing the login name. </P ></DIV ></DIV @@ -1023,12 +976,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1542" +NAME="AEN1682" ></A ><B >A.1.8. </B -> Why doesn't Bugzilla offer this or that feature or - compatability with this other tracking software? +> Why doesn't Bugzilla offer this or that feature or compatability + with this other tracking software? </P ></DIV ><DIV @@ -1036,19 +989,18 @@ CLASS="ANSWER" ><P ><B > </B -> It may be that the support has not been built yet, or that - you have not yet found it. Bugzilla is making tremendous - strides in usability, customizability, scalability, and - user interface. It is widely considered the most complete - and popular open-source bug-tracking software in - existence. +> It may be that the support has not been built yet, or that you + have not yet found it. Bugzilla is making tremendous strides in + usability, customizability, scalability, and user interface. It + is widely considered the most complete and popular open-source + bug-tracking software in existence. </P ><P -> That doesn't mean it can't use improvement! You can help - the project along by either hacking a patch yourself that - supports the functionality you require, or else submitting - a "Request for Enhancement" (RFE) using the bug submission - interface at <A +> That doesn't mean it can't use improvement! + You can help the project along by either hacking a patch yourself + that supports the functionality you require, or else submitting a + "Request for Enhancement" (RFE) using the bug submission interface + at <A HREF="http://bugzilla.mozilla.org/" TARGET="_top" >bugzilla.mozilla.org</A @@ -1062,7 +1014,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1549" +NAME="AEN1689" ></A ><B >A.1.9. </B @@ -1077,34 +1029,32 @@ CLASS="ANSWER" > </B >Terry Weissman answers, <A -NAME="AEN1553" +NAME="AEN1693" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P > You're not the only one. But <EM >I</EM -> am - not very interested. I'm not a real SQL or database - person. I just wanted to make a useful tool, and build - it on top of free software. So, I picked MySQL, and - learned SQL by staring at the MySQL manual and some - code lying around here, and wrote Bugzilla. I didn't - know that Enum's were non-standard SQL. I'm not sure - if I would have cared, but I didn't even know. So, to - me, things are "portable" because it uses MySQL, and - MySQL is portable enough. I fully understand (now) - that people want to be portable to other databases, - but that's never been a real concern of mine. +> am not very interested. I'm not + a real SQL or database person. I just wanted to make a useful tool, + and build it on top of free software. So, I picked MySQL, and + learned SQL by staring at the MySQL manual and some code lying + around here, and + wrote Bugzilla. I didn't know that Enum's were non-standard SQL. + I'm not sure if I would have cared, but I didn't even know. So, to + me, things are "portable" because it uses MySQL, and MySQL is + portable enough. I fully understand (now) that people want to be + portable to other databases, but that's never been a real concern + of mine. </P ></BLOCKQUOTE > </P ><P -> Things aren't quite that grim these days, however. Terry - pretty much sums up much of the thinking many of us have - for Bugzilla, but there is light on the horizon for - database-independence! Here are some options: +> Things aren't quite that grim these days, however. Terry pretty much + sums up much of the thinking many of us have for Bugzilla, but there + is light on the horizon for database-independence! Here are some options: </P ><P ></P @@ -1117,11 +1067,10 @@ BORDER="0" ><A HREF="http://bugzilla.redhat.com/" TARGET="_top" ->Red - Hat Bugzilla</A +>Red Hat Bugzilla</A ></EM ->: Runs a modified - Bugzilla 2.8 atop an Oracle database. +>: + Runs a modified Bugzilla 2.8 atop an Oracle database. </TD ></TR ><TR @@ -1132,15 +1081,16 @@ HREF="http://sourceforge.net/projects/interzilla" TARGET="_top" >Interzilla</A ></EM ->: A project to run Bugzilla on Interbase. No code released yet, however. +>: + A project to run Bugzilla on Interbase. No code released yet, however. </TD ></TR ><TR ><TD > <EM >Bugzilla 3.0</EM ->: One of the primary - stated goals is multiple database support. +>: One of the primary stated goals + is multiple database support. </TD ></TR ></TBODY @@ -1155,12 +1105,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1567" +NAME="AEN1707" ></A ><B >A.1.10. </B -> Why do the scripts say "/usr/bonsaitools/bin/perl" instead - of "/usr/bin/perl" or something else? +> Why do the scripts say "/usr/bonsaitools/bin/perl" instead of + "/usr/bin/perl" or something else? </P ></DIV ><DIV @@ -1168,25 +1118,22 @@ CLASS="ANSWER" ><P ><B > </B -> Mozilla.org uses /usr/bonsaitools/bin/perl. The prime - rule in making submissions is "don't break - bugzilla.mozilla.org". If it breaks it, your patch will be - reverted faster than you can do a diff. +> Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making + submissions is "don't break bugzilla.mozilla.org". If it breaks it, your + patch will be reverted faster than you can do a diff. </P ><P -> Here's Terry Weissman's comment, for some historical - context: +> Here's Terry Weissman's comment, for some historical context: <A -NAME="AEN1572" +NAME="AEN1712" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> [This was] purely my own convention. I wanted a place - to put a version of Perl and other tools that was - strictly under my control for the various webtools, - and not subject to anyone else. Edit it to point to - whatever you like. +> [This was] purely my own convention. I wanted a place to put a version of + Perl and other tools that was strictly under my control for the + various webtools, and not subject to anyone else. Edit it to point + to whatever you like. </P ><DIV CLASS="NOTE" @@ -1209,16 +1156,15 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> We always recommend that, if possible, you keep the - path as /usr/bonsaitools/bin/perl, and simply add a - /usr/bonsaitools and /usr/bonsaitools/bin directory, - then symlink your version of perl to - /usr/bonsaitools/bin/perl. This will make upgrading +> We always recommend that, if possible, you keep the path + as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools + and /usr/bonsaitools/bin directory, then symlink your version + of perl to /usr/bonsaitools/bin/perl. This will make upgrading your Bugzilla much easier in the future. </P ><P -> Obviously, if you do not have root access to your - Bugzilla box, our suggestion is irrelevant. +> Obviously, if you do not have root access to your Bugzilla + box, our suggestion is irrelevant. </P ></TD ></TR @@ -1262,8 +1208,7 @@ VALIGN="TOP" > <EM >This section is no longer up-to-date.</EM > - Please see the section on "Red Hat Bugzilla" under - "Variants" in The Bugzilla Guide. + Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide. </P ></TD ></TR @@ -1277,7 +1222,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1584" +NAME="AEN1724" ></A ><B >A.2.1. </B @@ -1289,34 +1234,32 @@ CLASS="ANSWER" ><P ><B > </B -> Red Hat Bugzilla is arguably more user-friendly, - customizable, and scalable than stock Bugzilla. Check it - out at http://bugzilla.redhat.com and the sources at - ftp://people.redhat.com/dkl/. They've set their Bugzilla - up to work with Oracle out of the box. Note that Redhat - Bugzilla is based upon the 2.8 Bugzilla tree; Bugzilla has - made some tremendous advances since the 2.8 release. Why - not download both Bugzillas to check out the differences - for yourself? +> Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable + than stock Bugzilla. Check it out at + http://bugzilla.redhat.com and the sources at ftp://people.redhat.com/dkl/. + They've set their Bugzilla up to work with Oracle out of the box. + Note that Redhat Bugzilla is based upon the 2.8 Bugzilla tree; + Bugzilla has made some tremendous advances since the 2.8 release. + Why not download both Bugzillas to check out the differences for + yourself? </P ><P -> Dave Lawrence, the original Red Hat Bugzilla maintainer, - mentions: +> Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions: <A -NAME="AEN1589" +NAME="AEN1729" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> Somebody needs to take the ball and run with it. I'm - the only maintainer and am very pressed for time. +> Somebody needs to take the ball and run with it. I'm the only + maintainer and am very pressed for time. </P ></BLOCKQUOTE -> If you, or someone you know, has the time - and expertise to do the integration work so main-tree - Bugzilla 2.12 and higher integrates the Red Hat Bugzilla - Oracle modifications, please donate your time to - supporting the Bugzilla project. +> + If you, or someone you know, has the time and expertise to do the integration + work so main-tree Bugzilla 2.12 and higher integrates the Red + Hat Bugzilla Oracle modifications, please donate your + time to supporting the Bugzilla project. </P ></DIV ></DIV @@ -1326,7 +1269,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1592" +NAME="AEN1732" ></A ><B >A.2.2. </B @@ -1342,36 +1285,30 @@ CLASS="ANSWER" >Dave Lawrence</EM >: <A -NAME="AEN1597" +NAME="AEN1737" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> 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. +> 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. </P ><P -> I do want to land the changes that I have made to - Bugzilla but I may have to back out a good deal and - make a different version of Red Hat's Bugzilla for - checking in to CVS. Especially the cosmetic changes - because it seems they may not fit the general public. - I will do that as soon as I can. I also still do my - regular QA responsibilities along with Bugzilla so - time is difficult sometimes to come by. +> I do want to land the changes that I have made to Bugzilla but I may + have to back out a good deal and make a different version of Red Hat's + Bugzilla for checking in to CVS. Especially the cosmetic changes because it + seems they may not fit the general public. I will do that as soon as I can. + I also still do my regular QA responsibilities along with Bugzilla so time + is difficult sometimes to come by. </P ><P -> There are also a good deal of other changes that were - requested by management for things like support - contracts and different permission groups for making - bugs private. Here is a short list of the major +> There are also a good deal of other changes that were requested by + management for things like support contracts and different permission + groups for making bugs private. Here is a short list of the major changes that have been made: </P ><P @@ -1380,93 +1317,78 @@ CLASS="BLOCKQUOTE" TYPE="1" ><LI ><P -> No enum types. All old enum types are now separate - smaller tables. +> No enum types. All old enum types are now separate smaller tables. </P ></LI ><LI ><P -> No bit wise operations. Not all databases support - this so they were changed to a more generic way of - doing this task +> No bit wise operations. Not all databases support this so they were + changed to a more generic way of doing this task </P ></LI ><LI ><P -> Bug reports can only be altered by the reporter, - assignee, or a privileged bugzilla user. The rest - of the world can see the bug but in a - non-changeable format (unless the bug has been - marked private). They can however add comments, - add and remove themselves from the CC list +> Bug reports can only be altered by the reporter, assignee, or a + privileged bugzilla user. The rest of the world can see the bug but in + a non-changeable format (unless the bug has been marked private). They + can however add comments, add and remove themselves from the CC list </P ></LI ><LI ><P -> Different group scheme. Each group has an id - number related to it. There is a user_group table - which contains userid to groupid mappings to - determine which groups each user belongs to. - Additionally there is a bug_group table that has - bugid to groupid mappings to show which groups can - see a particular bug. If there are no entries for - a bug in this table then the bug is public. +> Different group scheme. Each group has an id number related to it. + There is a user_group table which contains userid to groupid mappings + to determine which groups each user belongs to. Additionally there is + a bug_group table that has bugid to groupid mappings to show which + groups can see a particular bug. If there are no entries for a bug in + this table then the bug is public. </P ></LI ><LI ><P -> Product groups. product_table created to only - allow certain products to be visible for certain - groups in both bug entry and query. This was +> Product groups. product_table created to only allow certain products to + be visible for certain groups in both bug entry and query. This was particulary helpful for support contracts. </P ></LI ><LI ><P -> Of course many (too many) changes to Bugzilla code - itself to allow use with Oracle and still allow - operation with Mysql if so desired. Currently if - you use Mysql it is set to use Mysql's old - permission scheme to keep breakage to a minimum. - Hopefully one day this will standardize on one - style which may of course be something completely +> Of course many (too many) changes to Bugzilla code itself to allow use + with Oracle and still allow operation with Mysql if so desired. + Currently if you use Mysql it is set to use Mysql's old permission + scheme to keep breakage to a minimum. Hopefully one day this will + standardize on one style which may of course be something completely different. </P ></LI ><LI ><P -> Uses Text::Template perl module for rendering of - the dynamic HTML pages such as enter_bug.cgi, - query.cgi, bug_form.pl, and for the header and - footer parts of the page. This allows the html to - be separate from the perl code for customizing the - look and feel of the page to one's preference. +> Uses Text::Template perl module for rendering of the dynamic HTML pages + such as enter_bug.cgi, query.cgi, bug_form.pl, and for the header and + footer parts of the page. This allows the html to be separate from the + perl code for customizing the look and feel of the page to one's + preference. </P ></LI ><LI ><P -> There are many other smaller changes. There is - also a port to Oracle that I have been working on - as time permits but is not completely finished but - somewhat usable. I will merge it into our standard - code base when it becomes production quality. - Unfortunately there will have to be some - conditionals in the code to make it work with - other than Oracle due to some differences between - Oracle and Mysql. +> There are many other smaller changes. There is also a port to Oracle + that I have been working on as time permits but is not completely + finished but somewhat usable. I will merge it into our standard code + base when it becomes production quality. Unfortunately there will have + to be some conditionals in the code to make it work with other than + Oracle due to some differences between Oracle and Mysql. </P ></LI ></OL ><P -> Both the Mysql and Oracle versions of our current code - base are available from ftp://people.redhat.com/dkl. - If Terry/Tara wants I can submit patch files for all - of the changes I have made and he can determine what - is suitable for addition to the main bugzilla cade - base. But for me to commit changes to the actual CVS I - will need to back out alot of things that are not - suitable for the rest of the Bugzilla community. I am - open to suggestions. +> Both the Mysql and Oracle versions of our current code base are + available from ftp://people.redhat.com/dkl. If Terry/Tara wants I can submit + patch files for all of the changes I have made and he can determine what is + suitable for addition to the main bugzilla cade base. But for me to commit + changes to the actual CVS I will need to back out alot of things that are + not suitable for the rest of the Bugzilla community. I am open to + suggestions. </P ></BLOCKQUOTE > @@ -1479,7 +1401,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1620" +NAME="AEN1760" ></A ><B >A.2.3. </B @@ -1513,76 +1435,67 @@ ALIGN="LEFT" VALIGN="TOP" ><P > This information is somewhat dated; I last updated it - 7 June 2000. Please see the "Variants" section of - "The Bugzilla Guide" for more up-to-date information - regarding Red Hat Bugzilla. + 7 June 2000. Please see the "Variants" section of "The Bugzilla Guide" + for more up-to-date information regarding Red Hat Bugzilla. </P ></TD ></TR ></TABLE ></DIV -> <EM +> + <EM >Dave Lawrence</EM >: <A -NAME="AEN1627" +NAME="AEN1767" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> I suppose the current thread warrants an update - on the status of Oracle and bugzilla ;) We have now - been running Bugzilla 2.8 on Oracle for the last two - days in our production environment. I tried to do as - much testing as possible with it before going live - which is some of the reason for the long delay. I did - not get enough feedback as I would have liked from - internal developers to help weed out any bugs still - left so I said "Fine, i will take it live and then I - will get the feedback I want :)" So it is now starting - to stabilize and it running quite well after working - feverishly the last two days fixing problems as soon - as they came in from the outside world. The current - branch in cvs is up2date if anyone would like to grab - it and try it out. The oracle _setup.pl is broken - right now due to some last minute changes but I will - update that soon. Therefore you would probably need to - create the database tables the old fashioned way using - the supplied sql creation scripts located in the - ./oracle directory. We have heavy optimizations in the - database it self thanks to the in-house DBA here at - Red Hat so it is running quite fast. The database - itself is located on a dual PII450 with 1GB ram and 14 - high voltage differential raided scsi drives. The - tables and indexes are partitioned in 4 chuncks across - the raided drive which is nice because when ever you - need to do a full table scan, it is actually starting - in 4 different locations on 4 different drives - simultaneously. And the indexes of course are on - separate drives from the data so that speeds things up - tremendously. When I can find the time I will - document all that we have done to get this thing going - to help others that may need it. +> I suppose the current thread warrants an update on the status of + Oracle and bugzilla ;) We have now been running Bugzilla 2.8 on + Oracle for the last two days in our production environment. I + tried to do as much testing as possible with it before going live + which is some of the reason for the long delay. I did not get + enough feedback as I would have liked from internal developers to + help weed out any bugs still left so I said "Fine, i will take it + live and then I will get the feedback I want :)" So it is now + starting to stabilize and it running quite well after working + feverishly the last two days fixing problems as soon as they came + in from the outside world. The current branch in cvs is up2date if + anyone would like to grab it and try it out. The oracle _setup.pl + is broken right now due to some last minute changes but I will + update that soon. Therefore you would probably need to create the + database tables the old fashioned way using the supplied sql + creation scripts located in the ./oracle directory. We have heavy + optimizations in the database it self thanks to the in-house DBA + here at Red Hat so it is running quite fast. The database itself + is located on a dual PII450 with 1GB ram and 14 high voltage + differential raided scsi drives. The tables and indexes are + partitioned in 4 chuncks across the raided drive which is nice + because when ever you need to do a full table scan, it is actually + starting in 4 different locations on 4 different drives + simultaneously. And the indexes of course are on separate drives + from the data so that speeds things up tremendously. When I can + find the time I will document all that we have done to get this + thing going to help others that may need it. </P ><P -> 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 appreciated. What - we are using now is what I call a best first effort. - It definitely can be improved on and may even need - complete rewrites in a lot of areas. A lot of changes - may have to be made in the way Bugzilla does things - currently to make this transition to a more generic - database interface. Fortunately when making the - Oracle changes I made sure I didn't do anything that - I would consider Oracle specific and could not be - easily done with other databases. Alot of the sql - statements need to be broken up into smaller utilities - that themselves would need to make decisions on what - database they are using but the majority of the code - can be made database neutral. +> 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 + appreciated. What we are using now is what I call a best first + effort. It definitely can be improved on and may even need + complete rewrites in a lot of areas. A lot of changes may have to + be made in the way Bugzilla does things currently to make this + transition to a more generic database interface. Fortunately when + making the Oracle changes I made sure I didn't do anything that I + would consider Oracle specific and could not be easily done with + other databases. Alot of the sql statements need to be broken up + into smaller utilities that themselves would need to make + decisions on what database they are using but the majority of the + code can be made database neutral. </P ></BLOCKQUOTE > @@ -1597,55 +1510,17 @@ CLASS="QANDADIV" NAME="FAQ_LOKI" ></A >3. Loki Bugzilla (AKA Fenris)</H3 -><P -> <DIV -CLASS="NOTE" -><P -></P -><TABLE -CLASS="NOTE" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P -> 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. - </P -></TD -></TR -></TABLE -></DIV -> - </P ><DIV CLASS="QANDAENTRY" ><DIV CLASS="QUESTION" ><P ><A -NAME="AEN1636" +NAME="AEN1773" ></A ><B >A.3.1. </B -> What about Loki Bugzilla? +> What is Loki Bugzilla (Fenris)? </P ></DIV ><DIV @@ -1653,71 +1528,12 @@ CLASS="ANSWER" ><P ><B > </B -> Loki Games has a customized version of Bugzilla available - at http://fenris.lokigames.com. From that page, +> Loki Games has a customized version of Bugzilla available at <A -NAME="AEN1640" -></A -><BLOCKQUOTE -CLASS="BLOCKQUOTE" -><P -> You may have noticed that Fenris is a fork from - Bugzilla-- our patches weren't suitable for - integration --and a few people have expressed interest - in the code. Fenris has one major improvement over - Bugzilla, and that is individual comments are not - appended onto a string blob, they are stored as a - record in a separate table. This allows you to, for - instance, separate comments out according to privilege - levels in case your bug database could contain - sensitive information not for public eyes. We also - provide things like email hiding to protect user's - privacy, additional fields such as 'user_affected' in - case someone enters someone else's bug, comment - editing and deletion, and more conditional system - variables than Bugzilla does (turn off attachments, - qacontact, etc.). - </P -></BLOCKQUOTE -> - </P -></DIV -></DIV -><DIV -CLASS="QANDAENTRY" -><DIV -CLASS="QUESTION" -><P -><A -NAME="AEN1643" -></A -><B ->A.3.2. </B -> Who maintains Fenris (Loki Bugzilla) now? - </P -></DIV -><DIV -CLASS="ANSWER" -><P -><B -> </B -> Raphael Barrerro <raistlin@lokigames.com>. Michael - Vance created the initial fork, but no longer maintains - the project. - </P -></DIV -></DIV -><DIV -CLASS="QANDAENTRY" -><DIV -CLASS="QUESTION" -><P -><A -NAME="AEN1648" -></A -><B ->A.3.3. </B -> +HREF="http://fenris.lokigames.com/" +TARGET="_top" +>http://fenris.lokigames.com</A +>. There are some advantages to using Fenris, chief being separation of comments based upon user privacy level, data hiding, forced login for any data retrieval, and some additional fields. Loki has mainted their code, originally a fork from the Bugzilla 2.8 code base, and it is quite a bit different than stock Bugzilla at this point. I recommend you stick with official Bugzilla version 2.14 rather than using a fork, but it's up to you. </P ></DIV ></DIV @@ -1751,9 +1567,8 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> 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 - :) +> 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 :) </P ></TD ></TR @@ -1767,12 +1582,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1656" +NAME="AEN1784" ></A ><B >A.4.1. </B -> Is Bugzilla web-based or do you have to have specific - software or specific operating system on your machine? +> Is Bugzilla web-based or do you have to have specific software or + specific operating system on your machine? </P ></DIV ><DIV @@ -1780,9 +1595,8 @@ CLASS="ANSWER" ><P ><B > </B -> It is web and e-mail based. You can edit bugs by sending - specially formatted email to a properly configured - Bugzilla, or control via the web. +> It is web and e-mail based. You can edit bugs by sending specially + formatted email to a properly configured Bugzilla, or control via the web. </P ></DIV ></DIV @@ -1792,12 +1606,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1661" +NAME="AEN1789" ></A ><B >A.4.2. </B -> Has anyone you know of already done any Bugzilla - integration with Perforce (SCM software)? +> Has anyone you know of already done any Bugzilla integration with + Perforce (SCM software)? </P ></DIV ><DIV @@ -1805,12 +1619,8 @@ CLASS="ANSWER" ><P ><B > </B -> Yes! You can find more information elsewhere in "The - Bugzilla Guide" in the "Integration with Third-Party - Products" section. The section on Perforce isn't very - large, but as the maintainer of the Guide is charged with - Perforce/Bugzilla integration by his company, you can - expect this section to grow. +> Yes! You can find more information elsewhere in "The Bugzilla + Guide" in the "Integration with Third-Party Products" section. </P ></DIV ></DIV @@ -1820,7 +1630,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1666" +NAME="AEN1794" ></A ><B >A.4.3. </B @@ -1835,8 +1645,8 @@ CLASS="ANSWER" > Absolutely! You can track up to a "soft-limit" of around 64 individual "Products", that can each be composed of as many "Components" as you want. Check the Administration - section of the Bugzilla Guide for more information - regarding setting up Products and Components. + section of the Bugzilla Guide for more information regarding + setting up Products and Components. </P ></DIV ></DIV @@ -1846,13 +1656,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1671" +NAME="AEN1799" ></A ><B >A.4.4. </B -> If I am on many projects, and search for all bugs assigned - to me, will Bugzilla list them for me and allow me to sort - by project, severity etc? +> If I am on many projects, and search for all bugs assigned to me, will + Bugzilla list them for me and allow me to sort by project, severity etc? </P ></DIV ><DIV @@ -1870,12 +1679,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1676" +NAME="AEN1804" ></A ><B >A.4.5. </B -> Does Bugzilla allow attachments (text, screenshots, urls - etc)? If yes, are there any that are NOT allowed? +> Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes, + are there any that are NOT allowed? </P ></DIV ><DIV @@ -1883,14 +1692,12 @@ CLASS="ANSWER" ><P ><B > </B -> Yes. There are many specific MIME-types that are - pre-defined by Bugzilla, but you may specify any arbitrary - MIME-type you need when you upload the file. Since all - attachments are stored in the database, however, I - recommend storing large binary attachments elsewhere in - the web server's file system and providing a hyperlink as - a comment, or in the provided "URL" field in the bug - report. +> Yes. There are many specific MIME-types that are pre-defined by Bugzilla, + but you may specify any arbitrary MIME-type you need when you + upload the file. Since all attachments are stored in the database, + however, I recommend storing large binary attachments elsewhere + in the web server's file system and providing a hyperlink + as a comment, or in the provided "URL" field in the bug report. </P ></DIV ></DIV @@ -1900,14 +1707,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1681" +NAME="AEN1809" ></A ><B >A.4.6. </B -> Does Bugzilla allow us to define our own priorities and - levels? Do we have complete freedom to change the labels - of fields and format of them, and the choice of acceptable - values? +> Does Bugzilla allow us to define our own priorities and levels? Do we + have complete freedom to change the labels of fields and format of them, and + the choice of acceptable values? </P ></DIV ><DIV @@ -1915,9 +1721,9 @@ CLASS="ANSWER" ><P ><B > </B -> Yes. However, modifying some fields, notably those - related to bug progression states, also require adjusting - the program logic to compensate for the change. +> Yes. However, modifying some fields, notably those related to bug + progression states, also require adjusting the program logic to + compensate for the change. </P ></DIV ></DIV @@ -1927,14 +1733,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1686" +NAME="AEN1814" ></A ><B >A.4.7. </B -> The index.html page doesn't show the footer. It's really - annoying to have to go to the querypage just to check my - "my bugs" link. How do I get a footer on static HTML - pages? +> The index.html page doesn't show the footer. It's really annoying to have + to go to the querypage just to check my "my bugs" link. How do I get a footer + on static HTML pages? </P ></DIV ><DIV @@ -1942,32 +1747,40 @@ CLASS="ANSWER" ><P ><B > </B -> This was a late-breaking question for the Guide, so I just - have to quote the relevant newsgroup thread on it. +> This was a late-breaking question for the Guide, so I just have to + quote the relevant newsgroup thread on it. </P ><P CLASS="LITERALLAYOUT" ->> AFAIK, most sites (even if they have SSI enabled) won't have #exec<br> - cmd > enabled. Perhaps what would be better is a #include<br> - virtual and a > footer.cgi the basically has the "require<br> - 'CGI.pl' and PutFooter command. > > Please note that under<br> - most configurations, this also requires naming > the file<br> - from index.html to index.shtml (and making sure that it<br> - will > still be reconized as an index). Personally, I<br> - think this is better on > a per-installation basis<br> - (perhaps add something to the FAQ that says how > to do<br> - this). Good point. Yeah, easy enough to do, that it<br> - shouldn't be a big deal for someone to take it on if they<br> - want it. FAQ is a good place for it. > Dave Miller wrote:<br> - > >> I did a little experimenting with getting the command<br> - menu and footer on >> the end of the index page while<br> - leaving it as an HTML file... >> >> I was successful. :)<br> - >> >> I added this line: >> >> >> >> Just before the<br> - </BODY> </HTML> at the end of the file. And<br> - it worked. >> >> Thought I'd toss that out there. Should<br> - I check this in? For those that >> have SSI disabled,<br> - it'll act like a comment, so I wouldn't think it would >><br> - break anything.<br> +>> AFAIK, most sites (even if they have SSI enabled) won't have #exec cmd<br> +> enabled. Perhaps what would be better is a #include virtual and a<br> +> footer.cgi the basically has the "require 'CGI.pl' and PutFooter command.<br> +><br> +> Please note that under most configurations, this also requires naming<br> +> the file from index.html to index.shtml (and making sure that it will<br> +> still be reconized as an index). Personally, I think this is better on<br> +> a per-installation basis (perhaps add something to the FAQ that says how<br> +> to do this).<br> +<br> +Good point. Yeah, easy enough to do, that it shouldn't be a big deal for<br> +someone to take it on if they want it. FAQ is a good place for it.<br> +<br> +> Dave Miller wrote:<br> +><br> +>> I did a little experimenting with getting the command menu and footer on<br> +>> the end of the index page while leaving it as an HTML file...<br> +>><br> +>> I was successful. :)<br> +>><br> +>> I added this line:<br> +>><br> +>> <br> +>><br> +>> Just before the </BODY> </HTML> at the end of the file. And it worked.<br> +>><br> +>> Thought I'd toss that out there. Should I check this in? For those that<br> +>> have SSI disabled, it'll act like a comment, so I wouldn't think it would<br> +>> break anything.<br> </P ></DIV ></DIV @@ -1977,13 +1790,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1692" +NAME="AEN1820" ></A ><B >A.4.8. </B -> Does Bugzilla provide any reporting features, metrics, - graphs, etc? You know, the type of stuff that management - likes to see. :) +> Does Bugzilla provide any reporting features, metrics, graphs, etc? You + know, the type of stuff that management likes to see. :) </P ></DIV ><DIV @@ -1994,17 +1806,17 @@ CLASS="ANSWER" > Yes. Look at <A HREF="http://bugzilla.mozilla.org/reports.cgi" TARGET="_top" -> http://bugzilla.mozilla.org/reports.cgi</A -> for basic reporting facilities. +> http://bugzilla.mozilla.org/reports.cgi</A +> for basic reporting + facilities. </P ><P -> For more advanced reporting, I recommend hooking up a - professional reporting package, such as Crystal Reports, - and use ODBC to access the MySQL database. You can do a - lot through the Query page of Bugzilla as well, but right - now Advanced Reporting is much better accomplished through - third-party utilities that can interface with the database - directly. +> For more advanced reporting, I recommend hooking up a professional + reporting package, such as Crystal Reports, and use ODBC to access + the MySQL database. You can do a lot through the Query page of + Bugzilla as well, but right now Advanced Reporting is much + better accomplished through third-party utilities that can + interface with the database directly. </P ><P > Advanced Reporting is a Bugzilla 3.X proposed feature. @@ -2017,13 +1829,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1700" +NAME="AEN1828" ></A ><B >A.4.9. </B -> Is there email notification and if so, what do you see - when you get an email? Do you see bug number and title or - is it only the number? +> Is there email notification and if so, what do you see when you get an + email? Do you see bug number and title or is it only the number? </P ></DIV ><DIV @@ -2031,9 +1842,9 @@ CLASS="ANSWER" ><P ><B > </B -> Email notification is user-configurable. The bug id and - Topic of the bug report accompany each email notification, - along with a list of the changes made. +> Email notification is user-configurable. The bug id and Topic + of the bug report accompany each email notification, along with + a list of the changes made. </P ></DIV ></DIV @@ -2043,7 +1854,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1705" +NAME="AEN1833" ></A ><B >A.4.10. </B @@ -2066,12 +1877,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1710" +NAME="AEN1838" ></A ><B >A.4.11. </B -> If there is email notification, do users have to have any - particular type of email application? +> If there is email notification, do users have to have any particular + type of email application? </P ></DIV ><DIV @@ -2079,8 +1890,8 @@ CLASS="ANSWER" ><P ><B > </B -> Bugzilla email is sent in plain text, the most compatible - mail format on the planet. +> Bugzilla email is sent in plain text, the most compatible mail format + on the planet. <DIV CLASS="NOTE" ><P @@ -2102,14 +1913,12 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> If you decide to use the bugzilla_email integration - features to allow Bugzilla to record responses to mail - with the associated bug, you may need to caution your - users to set their mailer to "respond to messages in - the format in which they were sent". For security - reasons Bugzilla ignores HTML tags in comments, and if - a user sends HTML-based email into Bugzilla the - resulting comment looks downright awful. +> If you decide to use the bugzilla_email integration features + to allow Bugzilla to record responses to mail with the associated bug, + you may need to caution your users to set their mailer to "respond + to messages in the format in which they were sent". For security reasons + Bugzilla ignores HTML tags in comments, and if a user sends HTML-based + email into Bugzilla the resulting comment looks downright awful. </P ></TD ></TR @@ -2125,14 +1934,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1717" +NAME="AEN1845" ></A ><B >A.4.12. </B -> If I just wanted to track certain bugs, as they go - through life, can I set it up to alert me via email - whenever that bug changes, whether it be owner, status or - description etc.? +> If I just wanted to track certain bugs, as they go through life, can I + set it up to alert me via email whenever that bug changes, whether it be + owner, status or description etc.? </P ></DIV ><DIV @@ -2140,11 +1948,10 @@ CLASS="ANSWER" ><P ><B > </B -> Yes. Place yourself in the "cc" field of the bug you wish - to monitor. Then change your "Notify me of changes to" - field in the Email Settings tab of the User Preferences - screen in Bugzilla to the "Only those bugs which I am - listed on the CC line" option. +> Yes. Place yourself in the "cc" field of the bug you wish to monitor. + Then change your "Notify me of changes to" field in the Email Settings + tab of the User Preferences screen in Bugzilla to the "Only those + bugs which I am listed on the CC line" option. </P ></DIV ></DIV @@ -2154,15 +1961,14 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1722" +NAME="AEN1850" ></A ><B >A.4.13. </B -> Does Bugzilla allow data to be imported and exported? If I - had outsiders write up a bug report using a MS Word bug - template, could that template be imported into "matching" - fields? If I wanted to take the results of a query and - export that data to MS Excel, could I do that? +> Does Bugzilla allow data to be imported and exported? If I had outsiders + write up a bug report using a MS Word bug template, could that template be + imported into "matching" fields? If I wanted to take the results of a query + and export that data to MS Excel, could I do that? </P ></DIV ><DIV @@ -2170,27 +1976,26 @@ CLASS="ANSWER" ><P ><B > </B -> Mozilla allows data export through a custom DTD in XML - format. It does not, however, export to specific formats - other than the XML Mozilla DTD. Importing the data into - Excel or any other application is left as an exercise for - the reader. +> Mozilla allows data export through a custom DTD in XML format. + It does not, however, export to specific formats other than the + XML Mozilla DTD. Importing the data into Excel or any other application + is left as an exercise for the reader. </P ><P -> If you create import filters to other applications from - Mozilla's XML, please submit your modifications for - inclusion in future Bugzilla distributions. +> If you create import filters to other applications from Mozilla's XML, + please submit your modifications for inclusion in future Bugzilla + distributions. </P ><P -> As for data import, any application can send data to - Bugzilla through the HTTP protocol, or through Mozilla's - XML API. However, it seems kind of silly to put another - front-end in front of Bugzilla; it makes more sense to - create a simplified bug submission form in HTML. You can - find an excellent example at <A +> As for data import, any application can send data to Bugzilla through + the HTTP protocol, or through Mozilla's XML API. However, it seems + kind of silly to put another front-end in front of Bugzilla; + it makes more sense to create a simplified bug submission form in + HTML. You can find an excellent example at + <A HREF="http://www.mozilla.org/quality/help/bugzilla-helper.html" TARGET="_top" -> http://www.mozilla.org/quality/help/bugzilla-helper.html</A +> http://www.mozilla.org/quality/help/bugzilla-helper.html</A > </P ></DIV @@ -2201,13 +2006,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1730" +NAME="AEN1858" ></A ><B >A.4.14. </B -> Does Bugzilla allow fields to be added, changed or - deleted? If I want to customize the bug submission form to - meet our needs, can I do that using our terminology? +> Does Bugzilla allow fields to be added, changed or deleted? If I want to + customize the bug submission form to meet our needs, can I do that using our + terminology? </P ></DIV ><DIV @@ -2225,12 +2030,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1735" +NAME="AEN1863" ></A ><B >A.4.15. </B -> Has anyone converted Bugzilla to another language to be - used in other countries? Is it localizable? +> Has anyone converted Bugzilla to another language to be used in other + countries? Is it localizable? </P ></DIV ><DIV @@ -2238,10 +2043,10 @@ CLASS="ANSWER" ><P ><B > </B -> Currently, no. Internationalization support for Perl did - not exist in a robust fashion until the recent release of - version 5.6.0; Bugzilla is, and likely will remain (until - 3.X) completely non-localized. +> Currently, no. Internationalization support for Perl did not + exist in a robust fashion until the recent release of version 5.6.0; + Bugzilla is, and likely will remain (until 3.X) completely + non-localized. </P ></DIV ></DIV @@ -2251,12 +2056,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1740" +NAME="AEN1868" ></A ><B >A.4.16. </B -> Can a user create and save reports? Can they do this in - Word format? Excel format? +> Can a user create and save reports? Can they do this in Word format? + Excel format? </P ></DIV ><DIV @@ -2274,7 +2079,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1745" +NAME="AEN1873" ></A ><B >A.4.17. </B @@ -2296,12 +2101,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1750" +NAME="AEN1878" ></A ><B >A.4.18. </B -> Can a user modify an existing report and then save it into - another name? +> Can a user modify an existing report and then save it into another name? </P ></DIV ><DIV @@ -2309,9 +2113,8 @@ CLASS="ANSWER" ><P ><B > </B -> You can save an unlimited number of queries in Bugzilla. - You are free to modify them and rename them to your - heart's desire. +> You can save an unlimited number of queries in Bugzilla. You are free + to modify them and rename them to your heart's desire. </P ></DIV ></DIV @@ -2321,12 +2124,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1755" +NAME="AEN1883" ></A ><B >A.4.19. </B -> Does Bugzilla have the ability to search by word, phrase, - compound search? +> Does Bugzilla have the ability to search by word, phrase, compound + search? </P ></DIV ><DIV @@ -2334,9 +2137,8 @@ CLASS="ANSWER" ><P ><B > </B -> You have no idea. Bugzilla's query interface, - particularly with the advanced Boolean operators, is - incredibly versatile. +> You have no idea. Bugzilla's query interface, particularly with the + advanced Boolean operators, is incredibly versatile. </P ></DIV ></DIV @@ -2346,12 +2148,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1760" +NAME="AEN1888" ></A ><B >A.4.20. </B -> Can the admin person establish separate group and - individual user privileges? +> Can the admin person establish separate group and individual user + privileges? </P ></DIV ><DIV @@ -2369,14 +2171,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1765" +NAME="AEN1893" ></A ><B >A.4.21. </B -> Does Bugzilla provide record locking when there is - simultaneous access to the same bug? Does the second - person get a notice that the bug is in use or how are they - notified? +> Does Bugzilla provide record locking when there is simultaneous access + to the same bug? Does the second person get a notice that the bug is in use + or how are they notified? </P ></DIV ><DIV @@ -2384,9 +2185,8 @@ CLASS="ANSWER" ><P ><B > </B -> Bugzilla does not lock records. It provides mid-air - collision detection, and offers the offending user a - choice of options to deal with the conflict. +> Bugzilla does not lock records. It provides mid-air collision detection, + and offers the offending user a choice of options to deal with the conflict. </P ></DIV ></DIV @@ -2396,7 +2196,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1770" +NAME="AEN1898" ></A ><B >A.4.22. </B @@ -2408,12 +2208,12 @@ CLASS="ANSWER" ><P ><B > </B -> MySQL, the database back-end for Bugzilla, allows - hot-backup of data. You can find strategies for dealing - with backup considerations at <A +> MySQL, the database back-end for Bugzilla, allows hot-backup of data. + You can find strategies for dealing with backup considerations + at <A HREF="http://www.mysql.com/doc/B/a/Backup.html" TARGET="_top" -> http://www.mysql.com/doc/B/a/Backup.html</A +> http://www.mysql.com/doc/B/a/Backup.html</A > </P ></DIV @@ -2424,7 +2224,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1776" +NAME="AEN1904" ></A ><B >A.4.23. </B @@ -2436,8 +2236,8 @@ CLASS="ANSWER" ><P ><B > </B -> Yes. However, commits to the database must wait until the - tables are unlocked. Bugzilla databases are typically +> Yes. However, commits to the database must wait + until the tables are unlocked. Bugzilla databases are typically very small, and backups routinely take less than a minute. </P ></DIV @@ -2448,16 +2248,15 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1781" +NAME="AEN1909" ></A ><B >A.4.24. </B -> What type of human resources are needed to be on staff to - install and maintain Bugzilla? Specifically, what type of - skills does the person need to have? I need to find out if - we were to go with Bugzilla, what types of individuals - would we need to hire and how much would that cost vs - buying an "Out-of-the-Box" solution. +> What type of human resources are needed to be on staff to install and + maintain Bugzilla? Specifically, what type of skills does the person need to + have? I need to find out if we were to go with Bugzilla, what types of + individuals would we need to hire and how much would that cost vs buying an + "Out-of-the-Box" solution. </P ></DIV ><DIV @@ -2465,23 +2264,20 @@ CLASS="ANSWER" ><P ><B > </B -> If Bugzilla is set up correctly from the start, continuing - maintenance needs are minimal and can be completed by - unskilled labor. Things like rotate backup tapes and - check log files for the word "error". +> If Bugzilla is set up correctly from the start, continuing maintenance needs + are minimal and can be completed by unskilled labor. Things like rotate + backup tapes and check log files for the word "error". </P ><P -> Commercial Bug-tracking software typically costs somewhere - upwards of $20,000 or more for 5-10 floating licenses. - Bugzilla consultation is available from skilled members of - the newsgroup. +> Commercial Bug-tracking software typically costs somewhere upwards + of $20,000 or more for 5-10 floating licenses. Bugzilla consultation + is available from skilled members of the newsgroup. </P ><P -> As an example, as of this writing I typically charge $115 - for the first hour, and $89 each hour thereafter for - consulting work. It takes me three to five hours to make - Bugzilla happy on a Development installation of - Linux-Mandrake. +> As an example, as of this writing I typically charge + $115 for the first hour, and $89 each hour thereafter + for consulting work. It takes me three to five hours to make Bugzilla + happy on a Development installation of Linux-Mandrake. </P ></DIV ></DIV @@ -2491,16 +2287,15 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1788" +NAME="AEN1916" ></A ><B >A.4.25. </B -> What time frame are we looking at if we decide to hire - people to install and maintain the Bugzilla? Is this - something that takes hours or weeks to install and a - couple of hours per week to maintain and customize or is - this a multi-week install process, plus a full time job - for 1 person, 2 people, etc? +> What time frame are we looking at if we decide to hire people to install + and maintain the Bugzilla? Is this something that takes hours or weeks to + install and a couple of hours per week to maintain and customize or is this + a multi-week install process, plus a full time job for 1 person, 2 people, + etc? </P ></DIV ><DIV @@ -2508,12 +2303,11 @@ CLASS="ANSWER" ><P ><B > </B -> It all depends on your level of commitment. Someone with - much Bugzilla experience can get you up and running in - less than a day, and your Bugzilla install can run - untended for years. If your Bugzilla strategy is critical - to your business workflow, hire somebody with reasonable - UNIX or Perl skills to handle your process management and +> It all depends on your level of commitment. Someone with much Bugzilla + experience can get you up and running in less than a day, and + your Bugzilla install can run untended for years. If your + Bugzilla strategy is critical to your business workflow, hire somebody + with reasonable UNIX or Perl skills to handle your process management and bug-tracking maintenance & customization. </P ></DIV @@ -2524,13 +2318,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1793" +NAME="AEN1921" ></A ><B >A.4.26. </B -> Is there any licensing fee or other fees for using - Bugzilla? Any out-of-pocket cost other than the bodies - needed as identified above? +> Is there any licensing fee or other fees for using Bugzilla? Any + out-of-pocket cost other than the bodies needed as identified above? </P ></DIV ><DIV @@ -2538,9 +2331,8 @@ CLASS="ANSWER" ><P ><B > </B -> No. MySQL asks, if you find their product valuable, that - you purchase a support contract from them that suits your - needs. +> No. MySQL asks, if you find their product valuable, that you purchase + a support contract from them that suits your needs. </P ></DIV ></DIV @@ -2558,7 +2350,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1800" +NAME="AEN1928" ></A ><B >A.5.1. </B @@ -2573,8 +2365,9 @@ CLASS="ANSWER" > Check <A HREF="http://www.mozilla.org/projects/bugzilla/" TARGET="_top" -> http://www.mozilla.org/projects/bugzilla/</A -> for details. Once you download it, untar it, read the Bugzilla Guide. +> http://www.mozilla.org/projects/bugzilla/</A +> for details. + Once you download it, untar it, read the Bugzilla Guide. </P ></DIV ></DIV @@ -2584,7 +2377,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1806" +NAME="AEN1934" ></A ><B >A.5.2. </B @@ -2596,8 +2389,8 @@ CLASS="ANSWER" ><P ><B > </B -> Installation on Windows NT has its own section in "The - Bugzilla Guide". +> Installation on Windows NT has its own section in + "The Bugzilla Guide". </P ></DIV ></DIV @@ -2607,7 +2400,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1811" +NAME="AEN1939" ></A ><B >A.5.3. </B @@ -2637,13 +2430,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1818" +NAME="AEN1946" ></A ><B >A.6.1. </B -> How do I completely disable MySQL security if it's giving - me problems (I've followed the instructions in the - installation section of this guide!)? +> How do I completely disable MySQL security if it's giving me problems + (I've followed the instructions in the installation section of this guide!)? </P ></DIV ><DIV @@ -2651,14 +2443,12 @@ CLASS="ANSWER" ><P ><B > </B -> Run mysql like this: "mysqld --skip-grant-tables". Please - remember <EM ->this makes mysql as secure as taping a - $100 to the floor of a football stadium bathroom for - safekeeping.</EM -> Please read the Security - section of the Administration chapter of "The Bugzilla - Guide" before proceeding. +> Run mysql like this: "mysqld --skip-grant-tables". Please remember <EM +>this + makes mysql as secure as taping a $100 to the floor of a football stadium + bathroom for safekeeping.</EM +> Please read the Security section of the + Administration chapter of "The Bugzilla Guide" before proceeding. </P ></DIV ></DIV @@ -2668,7 +2458,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1824" +NAME="AEN1952" ></A ><B >A.6.2. </B @@ -2680,11 +2470,10 @@ CLASS="ANSWER" ><P ><B > </B -> The Bugzilla code has not undergone a complete security - audit. It is recommended that you closely examine - permissions on your Bugzilla installation, and follow the - recommended security guidelines found in The Bugzilla - Guide. +> The Bugzilla code has not undergone a complete security audit. + It is recommended that you closely examine permissions on your Bugzilla + installation, and follow the recommended security guidelines found + in The Bugzilla Guide. </P ></DIV ></DIV @@ -2694,14 +2483,13 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1829" +NAME="AEN1957" ></A ><B >A.6.3. </B -> I've implemented the security fixes mentioned in Chris - Yeh's security advisory of 5/10/2000 advising not to run - MySQL as root, and am running into problems with MySQL no - longer working correctly. +> I've implemented the security fixes mentioned in Chris Yeh's security + advisory of 5/10/2000 advising not to run MySQL as root, and am running into + problems with MySQL no longer working correctly. </P ></DIV ><DIV @@ -2709,9 +2497,9 @@ CLASS="ANSWER" ><P ><B > </B -> This is a common problem, related to running out of file - descriptors. Simply add "ulimit -n unlimited" to the - script which starts mysqld. +> This is a common problem, related to running out of file descriptors. + Simply add "ulimit -n unlimited" to the script which starts + mysqld. </P ></DIV ></DIV @@ -2729,12 +2517,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1836" +NAME="AEN1964" ></A ><B >A.7.1. </B -> I have a user who doesn't want to receive any more email - from Bugzilla. How do I stop it entirely for this user? +> I have a user who doesn't want to receive any more email from Bugzilla. + How do I stop it entirely for this user? </P ></DIV ><DIV @@ -2742,8 +2530,8 @@ CLASS="ANSWER" ><P ><B > </B -> With the email changes to 2.12, the user should be able to - set this in user email preferences. +> With the email changes to 2.12, the user should be able to set + this in user email preferences. </P ></DIV ></DIV @@ -2753,12 +2541,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1841" +NAME="AEN1969" ></A ><B >A.7.2. </B -> I'm evaluating/testing Bugzilla, and don't want it to send - email to anyone but me. How do I do it? +> I'm evaluating/testing Bugzilla, and don't want it to send email to + anyone but me. How do I do it? </P ></DIV ><DIV @@ -2766,9 +2554,8 @@ CLASS="ANSWER" ><P ><B > </B -> Edit the param for the mail text. Replace "To:" with - "X-Real-To:", replace "Cc:" with "X-Real-CC:", and add a - "To: (myemailaddress)". +> Edit the param for the mail text. Replace "To:" with "X-Real-To:", + replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)". </P ></DIV ></DIV @@ -2778,12 +2565,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1846" +NAME="AEN1974" ></A ><B >A.7.3. </B -> I want whineatnews.pl to whine at something more, or other - than, only new bugs. How do I do it? +> I want whineatnews.pl to whine at something more, or other than, only new + bugs. How do I do it? </P ></DIV ><DIV @@ -2791,12 +2578,14 @@ CLASS="ANSWER" ><P ><B > </B -> Try Klaas Freitag's excellent patch for "whineatassigned" - functionality. You can find it at<A -HREF=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679" +> Try Klaas Freitag's excellent patch for "whineatassigned" functionality. + You can find it at<A +HREF=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679" TARGET="_top" -> http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A ->. This patch is against an older version of Bugzilla, so you must apply the diffs manually. +> http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A +>. This + patch is against an older version of Bugzilla, so you must apply + the diffs manually. </P ></DIV ></DIV @@ -2806,12 +2595,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1852" +NAME="AEN1980" ></A ><B >A.7.4. </B -> I don't like/want to use Procmail to hand mail off to - bug_email.pl. What alternatives do I have? +> I don't like/want to use Procmail to hand mail off to bug_email.pl. + What alternatives do I have? </P ></DIV ><DIV @@ -2819,22 +2608,21 @@ CLASS="ANSWER" ><P ><B > </B -> You can call bug_email.pl directly from your aliases file, - with an entry like this: +> You can call bug_email.pl directly from your aliases file, with + an entry like this: <A -NAME="AEN1856" +NAME="AEN1984" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> bugzilla-daemon: - "|/usr/local/bin/bugzilla/contrib/bug_email.pl" +> bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" </P ></BLOCKQUOTE -> However, this is fairly nasty and subject to - problems; you also need to set up your smrsh (sendmail - restricted shell) to allow it. In a pinch, though, it can - work. +> + However, this is fairly nasty and subject to problems; you also + need to set up your smrsh (sendmail restricted shell) to allow + it. In a pinch, though, it can work. </P ></DIV ></DIV @@ -2844,12 +2632,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1859" +NAME="AEN1987" ></A ><B >A.7.5. </B -> How do I set up the email interface to submit/change bugs - via email? +> How do I set up the email interface to submit/change bugs via email? </P ></DIV ><DIV @@ -2857,9 +2644,8 @@ CLASS="ANSWER" ><P ><B > </B -> You can find an updated README.mailif file in the contrib/ - directory of your Bugzilla distribution that walks you - through the setup. +> You can find an updated README.mailif file in the contrib/ directory + of your Bugzilla distribution that walks you through the setup. </P ></DIV ></DIV @@ -2869,12 +2655,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1864" +NAME="AEN1992" ></A ><B >A.7.6. </B -> Email takes FOREVER to reach me from bugzilla -- it's - extremely slow. What gives? +> Email takes FOREVER to reach me from bugzilla -- it's extremely slow. + What gives? </P ></DIV ><DIV @@ -2882,23 +2668,22 @@ CLASS="ANSWER" ><P ><B > </B -> If you are using an alternate Mail Transport Agent (MTA - other than sendmail), make sure the options given in the - "processmail" script for all instances of "sendmail" are - correct for your MTA. If you are using Sendmail, you may - wish to delete the "-ODeliveryMode=deferred" option in the - "processmail" script for every invocation of "sendmail". - (Be sure and leave the "-t" option, though!) +> If you are using an alternate Mail Transport Agent (MTA other than + sendmail), make sure the options given in the "processmail" script for all + instances of "sendmail" are correct for your MTA. If you are using Sendmail, + you may wish to delete the "-ODeliveryMode=deferred" option in the + "processmail" script for every invocation of "sendmail". (Be sure and leave + the "-t" option, though!) </P ><P > A better alternative is to change the "-O" option to - "-ODeliveryMode=background". This prevents Sendmail from - hanging your Bugzilla Perl processes if the domain to - which it must send mail is unavailable. + "-ODeliveryMode=background". This prevents Sendmail from hanging your + Bugzilla Perl processes if the domain to which it must send mail + is unavailable. </P ><P -> This is now a configurable parameter called "sendmailnow", - available from editparams.cgi. +> This is now a configurable parameter called "sendmailnow", available + from editparams.cgi. </P ></DIV ></DIV @@ -2908,7 +2693,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1871" +NAME="AEN1999" ></A ><B >A.7.7. </B @@ -2920,16 +2705,15 @@ CLASS="ANSWER" ><P ><B > </B -> Double-check that you have not turned off email in your - user preferences. Confirm that Bugzilla is able to send - email by visiting the "Log In" link of your Bugzilla - installation and clicking the "Email me a password" button - after entering your email address. +> Double-check that you have not turned off email in your user preferences. + Confirm that Bugzilla is able to send email by visiting the "Log In" + link of your Bugzilla installation and clicking the "Email me a password" + button after entering your email address. </P ><P -> If you never receive mail from Bugzilla, chances you do - not have sendmail in "/usr/lib/sendmail". Ensure sendmail - lives in, or is symlinked to, "/usr/lib/sendmail". +> If you never receive mail from Bugzilla, chances you do not have + sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked + to, "/usr/lib/sendmail". </P ></DIV ></DIV @@ -2947,7 +2731,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1879" +NAME="AEN2007" ></A ><B >A.8.1. </B @@ -2959,11 +2743,10 @@ CLASS="ANSWER" ><P ><B > </B -> Red Hat Bugzilla, mentioned above, works with Oracle. The - current version from Mozilla.org does not have this - capability. Unfortunately, though you will sacrifice a - lot of the really great features available in Bugzilla - 2.10 and 2.12 if you go with the 2.8-based Redhat version. +> Red Hat Bugzilla, mentioned above, works with Oracle. The current version + from Mozilla.org does not have this capability. Unfortunately, though + you will sacrifice a lot of the really great features available in + Bugzilla 2.10 and 2.12 if you go with the 2.8-based Redhat version. </P ></DIV ></DIV @@ -2973,13 +2756,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1884" +NAME="AEN2012" ></A ><B >A.8.2. </B -> Bugs are missing from queries, but exist in the database - (and I can pull them up by specifying the bug ID). What's - wrong? +> Bugs are missing from queries, but exist in the database (and I can pull + them up by specifying the bug ID). What's wrong? </P ></DIV ><DIV @@ -2987,23 +2769,19 @@ CLASS="ANSWER" ><P ><B > </B -> You've almost certainly enabled the "shadow database", - but for some reason it hasn't been updated for all your - bugs. This is the database against which queries are run, - so that really complex or slow queries won't lock up - portions of the database for other users. You can turn off - the shadow database in editparams.cgi. If you wish to - continue using the shadow database, then as your "bugs" - user run "./syncshadowdb -syncall" from the command line - in the bugzilla installation directory to recreate your - shadow database. After it finishes, be sure to check the - params and make sure that "queryagainstshadowdb" is still - turned on. The syncshadowdb program turns it off if it was - on, and is supposed to turn it back on when completed; - that way, if it crashes in the middle of recreating the - database, it will stay off forever until someone turns it - back on by hand. Apparently, it doesn't always do that - yet. +> You've almost certainly enabled the "shadow database", but for some + reason it hasn't been updated for all your bugs. This is the database + against which queries are run, so that really complex or slow queries won't + lock up portions of the database for other users. You can turn off the + shadow database in editparams.cgi. If you wish to continue using the shadow + database, then as your "bugs" user run "./syncshadowdb -syncall" from the + command line in the bugzilla installation directory to recreate your shadow + database. After it finishes, be sure to check the params and make sure that + "queryagainstshadowdb" is still turned on. The syncshadowdb program turns it + off if it was on, and is supposed to turn it back on when completed; that + way, if it crashes in the middle of recreating the database, it will stay + off forever until someone turns it back on by hand. Apparently, it doesn't + always do that yet. </P ></DIV ></DIV @@ -3013,12 +2791,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1889" +NAME="AEN2017" ></A ><B >A.8.3. </B -> I think my database might be corrupted, or contain invalid - entries. What do I do? +> I think my database might be corrupted, or contain invalid entries. What + do I do? </P ></DIV ><DIV @@ -3026,14 +2804,12 @@ CLASS="ANSWER" ><P ><B > </B -> Run the "sanity check" utility (./sanitycheck.cgi in the - bugzilla_home directory) to see! If it all comes back, - you're OK. If it doesn't come back OK (i.e. any red - letters), there are certain things Bugzilla can recover - from and certain things it can't. If it can't - auto-recover, I hope you're familiar with mysqladmin - commands or have installed another way to manage your - database... +> Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home + directory) to see! If it all comes back, you're OK. If it doesn't come back + OK (i.e. any red letters), there are certain things Bugzilla can recover + from and certain things it can't. If it can't auto-recover, I hope you're + familiar with mysqladmin commands or have installed another way to manage + your database... </P ></DIV ></DIV @@ -3043,7 +2819,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1894" +NAME="AEN2022" ></A ><B >A.8.4. </B @@ -3055,14 +2831,12 @@ CLASS="ANSWER" ><P ><B > </B -> There is no facility in Bugzilla itself to do this. It's - also generally not a smart thing to do if you don't know - exactly what you're doing. However, if you understand SQL - you can use the mysqladmin utility to manually insert, - delete, and modify table information. Personally, I use - "phpMyAdmin". You have to compile a PHP module with MySQL - support to make it work, but it's very clean and easy to - use. +> There is no facility in Bugzilla itself to do this. It's also generally + not a smart thing to do if you don't know exactly what you're doing. + However, if you understand SQL you can use the mysqladmin utility to + manually insert, delete, and modify table information. Personally, I + use "phpMyAdmin". You have to compile a PHP module with MySQL + support to make it work, but it's very clean and easy to use. </P ></DIV ></DIV @@ -3072,12 +2846,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1899" +NAME="AEN2027" ></A ><B >A.8.5. </B -> I try to add myself as a user, but Bugzilla always tells - me my password is wrong. +> I try to add myself as a user, but Bugzilla always tells me my password is wrong. </P ></DIV ><DIV @@ -3085,11 +2858,9 @@ CLASS="ANSWER" ><P ><B > </B -> Certain version of MySQL (notably, 3.23.29 and 3.23.30) - accidentally disabled the "crypt()" function. This - prevented MySQL from storing encrypted passwords. Upgrade - to the "3.23 stable" version of MySQL and you should be - good to go. +> Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled + the "crypt()" function. This prevented MySQL from storing encrypted passwords. + Upgrade to the "3.23 stable" version of MySQL and you should be good to go. </P ></DIV ></DIV @@ -3099,12 +2870,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1904" +NAME="AEN2032" ></A ><B >A.8.6. </B -> I think I've set up MySQL permissions correctly, but - bugzilla still can't connect. +> I think I've set up MySQL permissions correctly, but bugzilla still can't + connect. </P ></DIV ><DIV @@ -3112,12 +2883,11 @@ CLASS="ANSWER" ><P ><B > </B -> Try running MySQL from its binary: "mysqld - --skip-grant-tables". This will allow you to completely - rule out grant tables as the cause of your frustration. - However, I do not recommend you run it this way on a - regular basis, unless you really want your web site - defaced and your machine cracked. +> Try running MySQL from its binary: "mysqld --skip-grant-tables". This + will allow you to completely rule out grant tables as the cause of your + frustration. However, I do not recommend you run it this way on a regular + basis, unless you really want your web site defaced and your machine + cracked. </P ></DIV ></DIV @@ -3127,12 +2897,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1909" +NAME="AEN2037" ></A ><B >A.8.7. </B -> How do I synchronize bug information among multiple - different Bugzilla databases? +> How do I synchronize bug information among multiple different Bugzilla + databases? </P ></DIV ><DIV @@ -3140,22 +2910,20 @@ CLASS="ANSWER" ><P ><B > </B -> Well, you can synchronize or you can move bugs. - Synchronization will only work one way -- you can create a - read-only copy of the database at one site, and have it - regularly updated at intervals from the main database. +> Well, you can synchronize or you can move bugs. Synchronization will + only work one way -- you can create a read-only copy of the database + at one site, and have it regularly updated at intervals from the main + database. </P ><P -> MySQL has some synchronization features builtin to the - latest releases. It would be great if someone looked into - the possibilities there and provided a report to the - newsgroup on how to effectively synchronize two Bugzilla - installations. +> MySQL has some synchronization features builtin to the latest releases. + It would be great if someone looked into the possibilities there + and provided a report to the newsgroup on how to effectively + synchronize two Bugzilla installations. </P ><P -> If you simply need to transfer bugs from one Bugzilla to - another, checkout the "move.pl" script in the Bugzilla - distribution. +> If you simply need to transfer bugs from one Bugzilla to another, + checkout the "move.pl" script in the Bugzilla distribution. </P ></DIV ></DIV @@ -3165,12 +2933,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1916" +NAME="AEN2044" ></A ><B >A.8.8. </B -> Why do I get bizarre errors when trying to submit data, - particularly problems with "groupset"? +> Why do I get bizarre errors when trying to submit data, particularly problems + with "groupset"? </P ></DIV ><DIV @@ -3178,10 +2946,9 @@ CLASS="ANSWER" ><P ><B > </B -> If you're sure your MySQL parameters are correct, you - might want turn "strictvaluechecks" OFF in editparams.cgi. - If you have "usebugsentry" set "On", you also cannot - submit a bug as readable by more than one group with +> If you're sure your MySQL parameters are correct, you might want turn + "strictvaluechecks" OFF in editparams.cgi. If you have "usebugsentry" set + "On", you also cannot submit a bug as readable by more than one group with "strictvaluechecks" ON. </P ></DIV @@ -3192,12 +2959,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1921" +NAME="AEN2049" ></A ><B >A.8.9. </B -> How come even after I delete bugs, the long descriptions - show up? +> How come even after I delete bugs, the long descriptions show up? </P ></DIV ><DIV @@ -3205,11 +2971,10 @@ CLASS="ANSWER" ><P ><B > </B -> Delete everything from $BUZILLA_HOME/shadow. Bugzilla - creates shadow files there, with each filename - corresponding to a bug number. Also be sure to run - syncshadowdb to make sure, if you are using a shadow - database, that the shadow database is current. +> Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow + files there, with each filename corresponding to a + bug number. Also be sure to run syncshadowdb to make sure, if you are using + a shadow database, that the shadow database is current. </P ></DIV ></DIV @@ -3227,12 +2992,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1928" +NAME="AEN2056" ></A ><B >A.9.1. </B -> What is the easiest way to run Bugzilla on Win32 - (Win98+/NT/2K)? +> What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)? </P ></DIV ><DIV @@ -3240,8 +3004,8 @@ CLASS="ANSWER" ><P ><B > </B -> Remove Windows. Install Linux. Install Bugzilla. The boss - will never know the difference. +> Remove Windows. Install Linux. Install Bugzilla. + The boss will never know the difference. </P ></DIV ></DIV @@ -3251,7 +3015,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1933" +NAME="AEN2061" ></A ><B >A.9.2. </B @@ -3263,10 +3027,9 @@ CLASS="ANSWER" ><P ><B > </B -> Not currently. Bundle::Bugzilla enormously simplifies - Bugzilla installation on UNIX systems. If someone can - volunteer to create a suitable PPM bundle for Win32, it - would be appreciated. +> Not currently. Bundle::Bugzilla enormously simplifies Bugzilla + installation on UNIX systems. If someone can volunteer to + create a suitable PPM bundle for Win32, it would be appreciated. </P ></DIV ></DIV @@ -3276,12 +3039,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1938" +NAME="AEN2066" ></A ><B >A.9.3. </B -> CGI's are failing with a "something.cgi is not a valid - Windows NT application" error. Why? +> CGI's are failing with a "something.cgi is not a valid Windows NT + application" error. Why? </P ></DIV ><DIV @@ -3289,32 +3052,27 @@ CLASS="ANSWER" ><P ><B > </B -> Depending on what Web server you are using, you will have - to configure the Web server to treat *.cgi files as CGI - scripts. In IIS, you do this by adding *.cgi to the App - Mappings with the <path>\perl.exe %s %s as the +> Depending on what Web server you are using, you will have to configure + the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by + adding *.cgi to the App Mappings with the <path>\perl.exe %s %s as the executable. </P ><P > Microsoft has some advice on this matter, as well: <A -NAME="AEN1943" +NAME="AEN2071" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> "Set application mappings. In the ISM, map the - extension for the script file(s) to the executable for - the script interpreter. For example, you might map the - extension .py to Python.exe, the executable for the - Python script interpreter. Note For the ActiveState - Perl script interpreter, the extension .pl is - associated with PerlIS.dll by default. If you want to - change the association of .pl to perl.exe, you need to - change the application mapping. In the mapping, you - must add two percent (%) characters to the end of the - pathname for perl.exe, as shown in this example: - c:\perl\bin\perl.exe %s %s" +> "Set application mappings. In the ISM, map the extension for the script + file(s) to the executable for the script interpreter. For example, you might + map the extension .py to Python.exe, the executable for the Python script + interpreter. Note For the ActiveState Perl script interpreter, the extension + .pl is associated with PerlIS.dll by default. If you want to change the + association of .pl to perl.exe, you need to change the application mapping. + In the mapping, you must add two percent (%) characters to the end of the + pathname for perl.exe, as shown in this example: c:\perl\bin\perl.exe %s %s" </P ></BLOCKQUOTE > @@ -3327,12 +3085,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1946" +NAME="AEN2074" ></A ><B >A.9.4. </B -> Can I have some general instructions on how to make - Bugzilla on Win32 work? +> Can I have some general instructions on how to make Bugzilla on Win32 work? </P ></DIV ><DIV @@ -3340,56 +3097,95 @@ CLASS="ANSWER" ><P ><B > </B -> The following couple entries are deprecated in favor of - the Windows installation instructions available in the - "Administration" portion of "The Bugzilla Guide". However, - they are provided here for historical interest and - insight. <P +> The following couple entries are deprecated in favor of the Windows installation + instructions available in the "Administration" portion of "The Bugzilla Guide". + However, they are provided here for historical interest and insight. + <P CLASS="LITERALLAYOUT" -> 1. #!C:/perl/bin/perl had to be<br> - added to every perl file. 2. Converted to Net::SMTP to<br> - handle mail messages instead of /usr/bin/sendmail. 3.<br> - The crypt function isn't available on Windows NT (at<br> - least none that I am aware), so I made encrypted<br> - passwords = plaintext passwords. 4. The system call to<br> - diff had to be changed to the Cygwin diff. 5. This was<br> - just to get a demo running under NT, it seems to be<br> - working good, and I have inserted almost 100 bugs from<br> - another bug tracking system. Since this work was done<br> - just to get an in-house demo, I am NOT planning on<br> - making a patch for submission to Bugzilla. If you would<br> - like a zip file, let me know. Q: Hmm, couldn't figure it<br> - out from the general instructions above. How about<br> - step-by-step? A: Sure! Here ya go! 1. Install IIS 4.0<br> - from the NT Option Pack #4. 2. Download and install<br> - Active Perl. 3. Install the Windows GNU tools from<br> - Cygwin. Make sure to add the bin directory to your<br> - system path. (Everyone should have these, whether they<br> - decide to use Bugzilla or not. :-) ) 4. Download<br> - relevant packages from ActiveState at<br> - http://www.activestate.com/packages/zips/. +<br> - DBD-Mysql.zip 5. Extract each zip file with WinZip, and<br> - install each ppd file using the notation: ppm install<br> - <module>.ppd 6. Install Mysql. *Note: If you move<br> - the default install from c:\mysql, you must add the<br> - appropriate startup parameters to the NT service. (ex.<br> - -b e:\\programs\\mysql) 7. Download any Mysql client.<br> - http://www.mysql.com/download_win.html 8. Setup MySql.<br> - (These are the commands that I used.) I. Cleanup default<br> - database settings. C:\mysql\bin\mysql -u root mysql<br> - mysql> DELETE FROM user WHERE Host='localhost' AND<br> - User=''; mysql> quit C:\mysql\bin\mysqladmin reload II.<br> - Set password for root. C:\mysql\bin\mysql -u root mysql<br> - mysql> UPDATE user SET Password=PASSWORD('new_password')<br> - WHERE user='root'; mysql> FLUSH PRIVILEGES; mysql> quit<br> - C:\mysql\bin\mysqladmin -u root reload III. Create bugs<br> - user. C:\mysql\bin\mysql -u root -p mysql> insert into<br> - user (host,user,password) values('localhost','bugs','');<br> - mysql> quit C:\mysql\bin\mysqladmin -u root reload IV.<br> - Create the bugs database. C:\mysql\bin\mysql -u root -p<br> - mysql> create database bugs; V. Give the bugs user<br> - access to the bugs database. mysql> insert into db<br> - (host,db,user,select_priv,insert_priv,update_priv,delete_priv,create_priv,drop_priv) values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N') mysql> quit C:\mysql\bin\mysqladmin -u root reload 9. Run the table scripts to setup the bugs database. 10. Change CGI.pm to use the following regular expression because of differing backslashes in NT versus UNIX. o $0 =~ m:[^\\]*$:; 11. Had to make the crypt password = plain text password in the database. (Thanks to Andrew Lahser" <andrew_lahser@merck.com>" on this one.) The files that I changed were: o globals.pl o CGI.pl o alternately, you can try commenting all references to 'crypt' string and replace them with similar lines but without encrypt() or crypr() functions insida all files. 12. Replaced sendmail with Windmail. Basically, you have to come up with a sendmail substitute for NT. Someone said that they used a Perl module (Net::SMTP), but I was trying to save time and do as little Perl coding as possible. 13. Added "perl" to the beginning of all Perl system calls that use a perl script as an argument and renamed processmail to processmail.pl. 14. In processmail.pl, I added binmode(HANDLE) before all read() calls. I'm not sure about this one, but the read() under NT wasn't counting the EOLs without the binary read." </P +> 1. #!C:/perl/bin/perl had to be added to every perl file.<br> + 2. Converted to Net::SMTP to handle mail messages instead of<br> + /usr/bin/sendmail.<br> + 3. The crypt function isn't available on Windows NT (at least none that I<br> + am aware), so I made encrypted passwords = plaintext passwords.<br> + 4. The system call to diff had to be changed to the Cygwin diff.<br> + 5. This was just to get a demo running under NT, it seems to be working<br> + good, and I have inserted almost 100 bugs from another bug tracking<br> + system. Since this work was done just to get an in-house demo, I am NOT<br> + planning on making a patch for submission to Bugzilla. If you would<br> + like a zip file, let me know.<br> +<br> +Q: Hmm, couldn't figure it out from the general instructions above. How<br> +about step-by-step?<br> +A: Sure! Here ya go!<br> +<br> + 1. Install IIS 4.0 from the NT Option Pack #4.<br> + 2. Download and install Active Perl.<br> + 3. Install the Windows GNU tools from Cygwin. Make sure to add the bin<br> + directory to your system path. (Everyone should have these, whether<br> + they decide to use Bugzilla or not. :-) )<br> + 4. Download relevant packages from ActiveState at<br> + http://www.activestate.com/packages/zips/. + DBD-Mysql.zip<br> + 5. Extract each zip file with WinZip, and install each ppd file using the<br> + notation: ppm install <module>.ppd<br> + 6. Install Mysql. *Note: If you move the default install from c:\mysql,<br> + you must add the appropriate startup parameters to the NT service. (ex.<br> + -b e:\\programs\\mysql)<br> + 7. Download any Mysql client. http://www.mysql.com/download_win.html<br> + 8. Setup MySql. (These are the commands that I used.)<br> +<br> + I. Cleanup default database settings.<br> + C:\mysql\bin\mysql -u root mysql<br> + mysql> DELETE FROM user WHERE Host='localhost' AND User='';<br> + mysql> quit<br> + C:\mysql\bin\mysqladmin reload<br> +<br> + II. Set password for root.<br> + C:\mysql\bin\mysql -u root mysql<br> + mysql> UPDATE user SET Password=PASSWORD('new_password')<br> + WHERE user='root';<br> + mysql> FLUSH PRIVILEGES;<br> + mysql> quit<br> + C:\mysql\bin\mysqladmin -u root reload<br> +<br> + III. Create bugs user.<br> + C:\mysql\bin\mysql -u root -p<br> + mysql> insert into user (host,user,password)<br> + values('localhost','bugs','');<br> + mysql> quit<br> + C:\mysql\bin\mysqladmin -u root reload<br> +<br> + IV. Create the bugs database.<br> + C:\mysql\bin\mysql -u root -p<br> + mysql> create database bugs;<br> +<br> + V. Give the bugs user access to the bugs database.<br> + mysql> insert into db<br> + (host,db,user,select_priv,insert_priv,update_priv,delete_priv,create_priv,drop_priv)<br> + values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N')<br> + mysql> quit<br> + C:\mysql\bin\mysqladmin -u root reload<br> + 9. Run the table scripts to setup the bugs database.<br> + 10. Change CGI.pm to use the following regular expression because of<br> + differing backslashes in NT versus UNIX.<br> + o $0 =~ m:[^\\]*$:;<br> + 11. Had to make the crypt password = plain text password in the database.<br> + (Thanks to Andrew Lahser" <andrew_lahser@merck.com>" on this one.) The<br> + files that I changed were:<br> + o globals.pl<br> + o CGI.pl<br> + o alternately, you can try commenting all references to 'crypt'<br> + string and replace them with similar lines but without encrypt()<br> + or crypr() functions insida all files.<br> + 12. Replaced sendmail with Windmail. Basically, you have to come up with a<br> + sendmail substitute for NT. Someone said that they used a Perl module<br> + (Net::SMTP), but I was trying to save time and do as little Perl coding<br> + as possible.<br> + 13. Added "perl" to the beginning of all Perl system calls that use a perl<br> + script as an argument and renamed processmail to processmail.pl.<br> + 14. In processmail.pl, I added binmode(HANDLE) before all read() calls. I'm<br> + not sure about this one, but the read() under NT wasn't counting the<br> + EOLs without the binary read."<br> + </P > </P ></DIV @@ -3400,12 +3196,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1952" +NAME="AEN2080" ></A ><B >A.9.5. </B -> I'm having trouble with the perl modules for NT not being - able to talk to to the database. +> I'm having trouble with the perl modules for NT not being able to talk to + to the database. </P ></DIV ><DIV @@ -3445,18 +3241,18 @@ CLASS="PROMPT" >PPM></TT > <B CLASS="COMMAND" ->install DBI DBD-mysql - GD</B +>install DBI DBD-mysql GD</B > </P ></LI ></OL -> I reckon TimeDate and Data::Dumper come - with the activeperl. You can check the ActiveState site - for packages for installation through PPM. <A -HREF=" http://www.activestate.com/Packages/" +> + I reckon TimeDate and Data::Dumper come with the activeperl. You can check + the ActiveState site for packages for installation through PPM. + <A +HREF=" http://www.activestate.com/Packages/" TARGET="_top" -> http://www.activestate.com/Packages/</A +> http://www.activestate.com/Packages/</A > </P ></DIV @@ -3475,12 +3271,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1973" +NAME="AEN2101" ></A ><B >A.10.1. </B -> The query page is very confusing. Isn't there a simpler - way to query? +> The query page is very confusing. Isn't there a simpler way to query? </P ></DIV ><DIV @@ -3488,12 +3283,13 @@ CLASS="ANSWER" ><P ><B > </B -> We are developing in that direction. You can follow - progress on this at <A +> We are developing in that direction. You can follow progress on this + at <A HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=16775" TARGET="_top" -> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A ->. Some functionality is available in Bugzilla 2.12, and is available as "quicksearch.html" +> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</A +>. Some functionality + is available in Bugzilla 2.12, and is available as "quicksearch.html" </P ></DIV ></DIV @@ -3503,13 +3299,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1979" +NAME="AEN2107" ></A ><B >A.10.2. </B -> I'm confused by the behavior of the "accept" button in the - Show Bug form. Why doesn't it assign the bug to me when I - accept it? +> I'm confused by the behavior of the "accept" button in the Show Bug form. + Why doesn't it assign the bug to me when I accept it? </P ></DIV ><DIV @@ -3517,9 +3312,9 @@ CLASS="ANSWER" ><P ><B > </B -> The current behavior is acceptable to bugzilla.mozilla.org - and most users. I personally don't like it. You have - your choice of patches to change this behavior, however. +> The current behavior is acceptable to bugzilla.mozilla.org and most + users. I personally don't like it. You have your choice of patches + to change this behavior, however. <P ></P ><TABLE @@ -3530,7 +3325,7 @@ BORDER="0" ><A HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029" TARGET="_top" -> Add a "and accept bug" radio button</A +> Add a "and accept bug" radio button</A ></TD ></TR ><TR @@ -3538,16 +3333,16 @@ TARGET="_top" ><A HREF="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153" TARGET="_top" -> "Accept" button automatically assigns to you</A +> "Accept" button automatically assigns to you</A ></TD ></TR ></TBODY ></TABLE ><P ></P -> Note that these patches are somewhat dated. - You will need to do the find and replace manually to apply - them. They are very small, though. It is easy. +> + Note that these patches are somewhat dated. You will need to do the find + and replace manually to apply them. They are very small, though. It is easy. </P ></DIV ></DIV @@ -3557,12 +3352,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1989" +NAME="AEN2117" ></A ><B >A.10.3. </B -> I can't upload anything into the database via the "Create - Attachment" link. What am I doing wrong? +> I can't upload anything into the database via the "Create Attachment" + link. What am I doing wrong? </P ></DIV ><DIV @@ -3570,10 +3365,9 @@ CLASS="ANSWER" ><P ><B > </B -> The most likely cause is a very old browser or a browser - that is incompatible with file upload via POST. Download - the latest Netscape, Microsoft, or Mozilla browser to - handle uploads correctly. +> The most likely cause is a very old browser or a browser that is + incompatible with file upload via POST. Download the latest Netscape, + Microsoft, or Mozilla browser to handle uploads correctly. </P ></DIV ></DIV @@ -3583,12 +3377,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1994" +NAME="AEN2122" ></A ><B >A.10.4. </B -> Email submissions to Bugzilla that have attachments end up - asking me to save it as a "cgi" file. +> Email submissions to Bugzilla that have attachments end up asking me to + save it as a "cgi" file. </P ></DIV ><DIV @@ -3596,10 +3390,9 @@ CLASS="ANSWER" ><P ><B > </B -> Yup. Just rename it once you download it, or save it - under a different filename. This will not be fixed - anytime too soon, because it would cripple some other - functionality. +> Yup. Just rename it once you download it, or save it under a different + filename. This will not be fixed anytime too soon, because it would + cripple some other functionality. </P ></DIV ></DIV @@ -3609,12 +3402,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN1999" +NAME="AEN2127" ></A ><B >A.10.5. </B -> How do I change a keyword in Bugzilla, once some bugs are - using it? +> How do I change a keyword in Bugzilla, once some bugs are using it? </P ></DIV ><DIV @@ -3622,10 +3414,9 @@ CLASS="ANSWER" ><P ><B > </B -> In the Bugzilla administrator UI, edit the keyword and it - will let you replace the old keyword name with a new one. - This will cause a problem with the keyword cache. Run - sanitycheck.cgi to fix it. +> In the Bugzilla administrator UI, edit the keyword and it will let you + replace the old keyword name with a new one. This will cause a problem + with the keyword cache. Run sanitycheck.cgi to fix it. </P ></DIV ></DIV @@ -3643,7 +3434,7 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN2006" +NAME="AEN2134" ></A ><B >A.11.1. </B @@ -3658,19 +3449,26 @@ CLASS="ANSWER" > Try <A HREF="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Webtools&component=Bugzilla" TARGET="_top" -> this link</A -> to view current bugs or requests for enhancement for Bugzilla. +> this link</A +> to view current bugs or requests for + enhancement for Bugzilla. </P ><P -> You can view bugs marked for 2.14 release <A +> You can view bugs marked for 2.14 release + <A HREF="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bugzilla&target_milestone=Bugzilla+2.14" TARGET="_top" >here</A ->. This list includes bugs for the 2.14 release that have already been fixed and checked into CVS. Please consult the <A +>. + This list includes bugs for the 2.14 release that have already + been fixed and checked into CVS. Please consult the + <A HREF="http://www.mozilla.org/projects/bugzilla/" TARGET="_top" -> Bugzilla Project Page</A -> for details on how to check current sources out of CVS so you can have these bug fixes early! +> Bugzilla Project Page</A +> for details on how to + check current sources out of CVS so you can have these + bug fixes early! </P ></DIV ></DIV @@ -3680,13 +3478,12 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN2015" +NAME="AEN2143" ></A ><B >A.11.2. </B -> How can I change the default priority to a null value? - For instance, have the default priority be "---" instead - of "P2"? +> How can I change the default priority to a null value? For instance, have the default + priority be "---" instead of "P2"? </P ></DIV ><DIV @@ -3697,8 +3494,13 @@ CLASS="ANSWER" > This is well-documented here: <A HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862" TARGET="_top" -> http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A ->. 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... +> http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A +>. 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... </P ></DIV ></DIV @@ -3708,12 +3510,11 @@ CLASS="QANDAENTRY" CLASS="QUESTION" ><P ><A -NAME="AEN2021" +NAME="AEN2149" ></A ><B >A.11.3. </B -> What's the best way to submit patches? What guidelines - should I follow? +> What's the best way to submit patches? What guidelines should I follow? </P ></DIV ><DIV @@ -3727,49 +3528,44 @@ CLASS="ANSWER" TYPE="1" ><LI ><P -> Enter a bug into bugzilla.mozilla.org for the - "Webtools" product, "Bugzilla" component. +> Enter a bug into bugzilla.mozilla.org for the "Webtools" product, + "Bugzilla" component. </P ></LI ><LI ><P -> Upload your patch as a unified DIFF (having used - "diff -u" against the <EM ->current - sources</EM -> checked out of CVS), or new - source file by clicking "Create a new attachment" - link on the bug page you've just created, and - include any descriptions of database changes you may - make, into the bug ID you submitted in step #1. Be - sure and click the "Patch" radio button to indicate - the text you are sending is a patch! +> Upload your patch as a unified DIFF (having used "diff -u" against + the <EM +>current sources</EM +> checked out of CVS), + or new source file by clicking + "Create a new attachment" link on the bug page you've just created, and + include any descriptions of database changes you may make, into the bug + ID you submitted in step #1. Be sure and click the "Patch" radio + button to indicate the text you are sending is a patch! </P ></LI ><LI ><P > Announce your patch and the associated URL - (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) - for discussion in the newsgroup - (netscape.public.mozilla.webtools). You'll get a - really good, fairly immediate reaction to the - implications of your patch, which will also give us - an idea how well-received the change would be. + (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) for discussion in + the newsgroup (netscape.public.mozilla.webtools). You'll get a really + good, fairly immediate reaction to the implications of your patch, + which will also give us an idea how well-received the change would + be. </P ></LI ><LI ><P -> If it passes muster with minimal modification, the - person to whom the bug is assigned in Bugzilla is - responsible for seeing the patch is checked into - CVS. +> If it passes muster with minimal modification, the person to whom + the bug is assigned in Bugzilla is responsible for seeing the patch + is checked into CVS. </P ></LI ><LI ><P -> Bask in the glory of the fact that you helped write - the most successful open-source bug-tracking - software on the planet :) +> Bask in the glory of the fact that you helped write the most successful + open-source bug-tracking software on the planet :) </P ></LI ></OL diff --git a/docs/html/future.html b/docs/html/future.html index 8c19ed418..314f0e050 100644 --- a/docs/html/future.html +++ b/docs/html/future.html @@ -10,7 +10,7 @@ REL="HOME" TITLE="The Bugzilla Guide" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="Tinderbox" +TITLE="Tinderbox/Tinderbox2" HREF="tinderbox.html"><LINK REL="NEXT" TITLE="The Bugzilla FAQ" @@ -85,11 +85,12 @@ CLASS="SYNOPSIS" ></TR ></TABLE ><P ->The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do +> The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do not have more information about it right now, and most of what went into the "future" section is now present. That stuff was blue-sky a year ago; MattyT should have me a new document - sometime...</P + sometime... + </P ></DIV ><DIV CLASS="NAVFOOTER" @@ -131,7 +132,7 @@ HREF="faq.html" WIDTH="33%" ALIGN="left" VALIGN="top" ->Tinderbox</TD +>Tinderbox/Tinderbox2</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/geninstall.html b/docs/html/geninstall.html index fc9c99720..b8f25789a 100644 --- a/docs/html/geninstall.html +++ b/docs/html/geninstall.html @@ -78,7 +78,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN837" +NAME="AEN916" >3.5.1. Modifying Your Running System</A ></H2 ><P @@ -111,7 +111,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN844" +NAME="AEN923" >3.5.2. Upgrading From Previous Versions</A ></H2 ><P @@ -228,33 +228,132 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN865" ->3.5.4. UNIX Installation Instructions History</A +NAME="MOD_THROTTLE" +>3.5.4. <TT +CLASS="FILENAME" +>mod_throttle</TT +> and Security</A +></H2 +><P +> It is possible for a user, by mistake or on purpose, to access + the database many times in a row which can result in very slow + access speeds for other users. If your Bugzilla installation + is experiencing this problem , you may install the Apache + module <TT +CLASS="FILENAME" +>mod_throttle</TT +> which can limit + connections by ip-address. You may download this module at + <A +HREF="http://www.snert.com/Software/Throttle/" +TARGET="_top" +>http://www.snert.com/Software/Throttle/</A +>. Follow the instructions to install into your Apache install. <EM +>This module only functions with the Apache web server!</EM +>. You may use the <B +CLASS="COMMAND" +>ThrottleClientIP</B +> command provided by this module to accomplish this goal. See the <A +HREF="http://www.snert.com/Software/Throttle/" +TARGET="_top" +>Module Instructions</A +> for more information. </P +></DIV +><DIV +CLASS="SECTION" +><H2 +CLASS="SECTION" +><A +NAME="CONTENT_TYPE" +>3.5.5. Preventing untrusted Bugzilla content from executing malicious Javascript code</A +></H2 +><P +>It is possible for a Bugzilla to execute malicious + Javascript code. Due to internationalization concerns, we are + unable to incorporate the code changes necessary to fulfill + the CERT advisory requirements mentioned in <A +HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3" +TARGET="_top" +>http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A +>. Executing the following code snippet from a UNIX command shell will rectify the problem if your Bugzilla installation is intended for an English-speaking audience. As always, be sure your Bugzilla installation has a good backup before making changes, and I recommend you understand what the script is doing before executing it. </P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ + do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' >$i.tmp; \ + mv $i.tmp $i; done + </PRE +></FONT +></TD +></TR +></TABLE +></P +><P +> All this one-liner command does is search for all instances of + <SPAN +CLASS="QUOTE" +>"Content-type: text/html"</SPAN +> and replaces it with + <SPAN +CLASS="QUOTE" +>"Content-Type: text/html; charset=ISO-8859-1"</SPAN +>. + This specification prevents possible Javascript attacks on the + browser, and is suggested for all English-speaking sites. For + non-english-speaking Bugzilla sites, I suggest changing + <SPAN +CLASS="QUOTE" +>"ISO-8859-1"</SPAN +>, above, to <SPAN +CLASS="QUOTE" +>"UTF-8"</SPAN +>. + </P +></DIV +><DIV +CLASS="SECTION" +><H2 +CLASS="SECTION" +><A +NAME="AEN964" +>3.5.6. UNIX Installation Instructions History</A ></H2 ><P -> This document was originally adapted from the Bonsai installation - instructions by Terry Weissman <terry@mozilla.org>. +> This document was originally adapted from the Bonsai + installation instructions by Terry Weissman + <terry@mozilla.org>. </P ><P -> The February 25, 1999 re-write of this page was done by Ry4an Brase - <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt, - Martin Pool, & Dan Mosedale (But don't send bug reports to them; - report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi , - project Webtools, component Bugzilla). +> The February 25, 1999 re-write of this page was done by Ry4an + Brase <ry4an@ry4an.org>, with some edits by Terry + Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But + don't send bug reports to them; report them using bugzilla, at + http://bugzilla.mozilla.org/enter_bug.cgi , project Webtools, + component Bugzilla). </P ><P -> This document was heavily modified again Wednesday, March 07 2001 to - reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The - securing MySQL section should be changed to become standard procedure - for Bugzilla installations. +> This document was heavily modified again Wednesday, March 07 + 2001 to reflect changes for Bugzilla 2.12 release by Matthew + P. Barnson. The securing MySQL section should be changed to + become standard procedure for Bugzilla installations. </P ><P -> Finally, the README in its entirety was marked up in SGML and included into - the Guide on April 24, 2001 by Matt Barnson. Since that time, it's undergone - extensive modification as Bugzilla grew. +> Finally, the README in its entirety was marked up in SGML and + included into the Guide on April 24, 2001 by Matt Barnson. + Since that time, it's undergone extensive modification as + Bugzilla grew. </P ><P -> Comments from people using this Guide for the first time are particularly welcome. +> Comments from people using this Guide for the first time are + particularly welcome. </P ></DIV ></DIV diff --git a/docs/html/gfdl.html b/docs/html/gfdl.html index 5d166a1b5..966c2b9d1 100644 --- a/docs/html/gfdl.html +++ b/docs/html/gfdl.html @@ -141,7 +141,7 @@ HREF="gfdl_howto.html" ><P >Version 1.1, March 2000</P ><A -NAME="AEN2249" +NAME="AEN2416" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" diff --git a/docs/html/gfdl_howto.html b/docs/html/gfdl_howto.html index 1161d4779..7dac6f4c6 100644 --- a/docs/html/gfdl_howto.html +++ b/docs/html/gfdl_howto.html @@ -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="AEN2339" +NAME="AEN2506" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" diff --git a/docs/html/glossary.html b/docs/html/glossary.html index 1b585065e..d689a8f76 100644 --- a/docs/html/glossary.html +++ b/docs/html/glossary.html @@ -68,7 +68,7 @@ CLASS="GLOSSDIV" ><H1 CLASS="GLOSSDIV" ><A -NAME="AEN2344" +NAME="AEN2511" >0-9, high ascii</A ></H1 ><DL @@ -110,11 +110,27 @@ NAME="GLOSS_A" ><DL ><DT ><B ->There are no entries for A</B +>Apache</B ></DT ><DD ><P -></P +>In this context, Apache is the web server most + commonly used for serving up + <I +CLASS="GLOSSTERM" +>Bugzilla</I +> pages. Contrary to + popular belief, the apache web server has nothing to do + with the ancient and noble Native American tribe, but + instead derived its name from the fact that it was + <SPAN +CLASS="QUOTE" +>"a patchy"</SPAN +> version of the original + <SPAN +CLASS="ACRONYM" +>NCSA</SPAN +> world-wide-web server.</P ></DD ></DL ></DIV @@ -179,6 +195,139 @@ CLASS="QUOTE" > is moderately flexible according to the needs of the organization using it, though.</P ></DD +><DT +><B +>Bugzilla</B +></DT +><DD +><P +> Bugzilla is the industry-standard bug tracking system. It + is quite popular among Open Source enthusiasts. + </P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A +NAME="GLOSS_C" +></A +></H1 +><DL +><DT +><A +NAME="GLOSS_COMPONENT" +><B +>Component</B +></A +></DT +><DD +><P +> A Component is a subsection of a Product. It should be a + narrow category, tailored to your organization. All + Products must contain at least one Component (and, as a + matter of fact, creating a Product with no Components will + create an error in Bugzilla). + </P +></DD +><DT +><A +NAME="GLOSS_CPAN" +><B +><SPAN +CLASS="ACRONYM" +>CPAN</SPAN +></B +></A +></DT +><DD +><P +><SPAN +CLASS="ACRONYM" +>CPAN</SPAN +> stands for the + <SPAN +CLASS="QUOTE" +>"Comprehensive Perl Archive Network"</SPAN +>. CPAN + maintains a large number of extremely useful + <I +CLASS="GLOSSTERM" +>Perl</I +> modules. By themselves, Perl + modules generally do nothing, but when used as part of a + larger program, they provide much-needed algorithms and + functionality.</P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A +NAME="GLOSS_D" +>D</A +></H1 +><DL +><DT +><B +>daemon</B +></DT +><DD +><P +>A daemon is a computer program which runs in the + background. In general, most daemons are started at boot + time via System V init scripts, or through RC scripts on + BSD-based systems. <I +CLASS="GLOSSTERM" +>mysqld</I +>, the + MySQL server, and <I +CLASS="GLOSSTERM" +>apache</I +>, a web + server, are generally run as daemons.</P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A +NAME="GLOSS_G" +></A +></H1 +><DL +><DT +><B +>Groups</B +></DT +><DD +><P +>The word <SPAN +CLASS="QUOTE" +>"Groups"</SPAN +> has a very special + meaning to Bugzilla. Bugzilla's main security mechanism + comes by lumping users into groups, and assigning those + groups certain privileges to + <I +CLASS="GLOSSTERM" +>Products</I +> and + <I +CLASS="GLOSSTERM" +>Components</I +> in the + <I +CLASS="GLOSSTERM" +>Bugzilla</I +> database.</P +></DD ></DL ></DIV ><DIV @@ -208,6 +357,33 @@ CLASS="GLOSSDIV" ><H1 CLASS="GLOSSDIV" ><A +NAME="GLOSS_M" +>M</A +></H1 +><DL +><DT +><B +>mysqld</B +></DT +><DD +><P +>mysqld is the name of the + <I +CLASS="GLOSSTERM" +>daemon</I +> for the MySQL database. In + general, it is invoked automatically through the use of + the System V init scripts on GNU/Linux and AT&T System + V-based systems, such as Solaris and HP/UX, or through the + RC scripts on BSD-based systems.</P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A NAME="GLOSS_P" >P</A ></H1 @@ -226,7 +402,7 @@ NAME="GLOSS_P" ><DIV CLASS="EXAMPLE" ><A -NAME="AEN2389" +NAME="AEN2602" ></A ><P ><B @@ -270,6 +446,22 @@ CLASS="QUOTE" >.</P ></DIV ></DD +><DT +><B +>Perl</B +></DT +><DD +><P +>First written by Larry Wall, Perl is a remarkable + program language. It has the benefits of the flexibility + of an interpreted scripting language (such as shell + script), combined with the speed and power of a compiled + language, such as C. <I +CLASS="GLOSSTERM" +>Bugzilla</I +> is + maintained in Perl.</P +></DD ></DL ></DIV ><DIV @@ -323,8 +515,11 @@ NAME="GLOSS_R" ></H1 ><DL ><DT +><A +NAME="GLOSS_RECURSION" ><B >Recursion</B +></A ></DT ><DD ><P @@ -347,13 +542,114 @@ CLASS="GLOSSDIV" ><H1 CLASS="GLOSSDIV" ><A +NAME="GLOSS_S" +>S</A +></H1 +><DL +><DT +><B +><SPAN +CLASS="ACRONYM" +>SGML</SPAN +></B +></DT +><DD +><P +><SPAN +CLASS="ACRONYM" +>SGML</SPAN +> stands for <SPAN +CLASS="QUOTE" +>"Standard + Generalized Markup Language"</SPAN +>. Created in the + 1980's to provide an extensible means to maintain + documentation based upon content instead of presentation, + <SPAN +CLASS="ACRONYM" +>SGML</SPAN +> has withstood the test of time as + a robust, powerful language. + <I +CLASS="GLOSSTERM" +><SPAN +CLASS="ACRONYM" +>XML</SPAN +></I +> is the + <SPAN +CLASS="QUOTE" +>"baby brother"</SPAN +> of SGML; any valid + <SPAN +CLASS="ACRONYM" +>XML</SPAN +> document it, by definition, a valid + <SPAN +CLASS="ACRONYM" +>SGML</SPAN +> document. The document you are + reading is written and maintained in + <SPAN +CLASS="ACRONYM" +>SGML</SPAN +>, and is also valid + <SPAN +CLASS="ACRONYM" +>XML</SPAN +> if you modify the Document Type + Definition.</P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A +NAME="GLOSS_T" +>T</A +></H1 +><DL +><DT +><A +NAME="GLOSS_TARGET_MILESTONE" +><B +>Target Milestone</B +></A +></DT +><DD +><P +> Target Milestones are Product goals. They are + configurable on a per-Product basis. Most software + development houses have a concept of + <SPAN +CLASS="QUOTE" +>"milestones"</SPAN +> where the people funding a + project expect certain functionality on certain dates. + Bugzilla facilitates meeting these milestones by giving + you the ability to declare by which milestone a bug will be + fixed, or an enhancement will be implemented. + </P +></DD +></DL +></DIV +><DIV +CLASS="GLOSSDIV" +><H1 +CLASS="GLOSSDIV" +><A NAME="GLOSS_Z" >Z</A ></H1 ><DL ><DT +><A +NAME="ZARRO-BOOGS-FOUND" ><B >Zarro Boogs Found</B +></A ></DT ><DD ><P diff --git a/docs/html/granttables.html b/docs/html/granttables.html index f8f4e9d7b..79cdf736f 100644 --- a/docs/html/granttables.html +++ b/docs/html/granttables.html @@ -16,7 +16,7 @@ REL="PREVIOUS" TITLE="MySQL Bugzilla Database Introduction" HREF="dbdoc.html"><LINK REL="NEXT" -TITLE="Bugzilla Variants" +TITLE="Bugzilla Variants and Competitors" HREF="variants.html"></HEAD ><BODY CLASS="SECTION" @@ -335,7 +335,7 @@ HREF="database.html" WIDTH="33%" ALIGN="right" VALIGN="top" ->Bugzilla Variants</TD +>Bugzilla Variants and Competitors</TD ></TR ></TABLE ></DIV diff --git a/docs/html/how.html b/docs/html/how.html index b7ac8f17b..7f9501755 100644 --- a/docs/html/how.html +++ b/docs/html/how.html @@ -16,7 +16,7 @@ REL="PREVIOUS" TITLE="Why Should We Use Bugzilla?" HREF="why.html"><LINK REL="NEXT" -TITLE="What's in it for me?" +TITLE="Where can I find my user preferences?" HREF="init4me.html"></HEAD ><BODY CLASS="SECTION" @@ -98,19 +98,21 @@ VALIGN="TOP" ></TABLE ><P > 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 - developing end-user mastery of Bugzilla, so you may fully enjoy the benefits - afforded by using this reliable open-source bug-tracking software. + 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 developing end-user + mastery of Bugzilla, so you may fully enjoy the benefits + afforded by using this reliable open-source bug-tracking + software. </P ><P -> Throughout this portion of the Guide, we will refer to user account - options available at the Bugzilla test installation, +> Throughout this portion of the Guide, we will refer to user + account options available at the Bugzilla test installation, <A HREF="http://landfill.tequilarista.org/" TARGET="_top" -> landfill.tequilarista.org</A +> landfill.tequilarista.org</A >. <DIV CLASS="NOTE" @@ -133,32 +135,29 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> Some people have run into difficulties completing this tutorial. If - you run into problems, please check the updated, online documentation available - at <A +> 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 +>. 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 +> news://news.mozilla.org/netscape.public.mozilla.webtools</A > </P ></TD ></TR ></TABLE ></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. Additionally, - Landfill often runs cutting-edge versions of Bugzilla for testing, so some things - may work slightly differently than mentioned here. +> 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. 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" @@ -169,14 +168,14 @@ NAME="MYACCOUNT" >2.3.1. Create a Bugzilla Account</A ></H2 ><P -> First things first! If you want to use Bugzilla, first you need to create - an account. Consult with the administrator responsible for your installation - of Bugzilla for the URL you should use to access it. - If you're test-driving the end-user Bugzilla experience, use this URL: - <A +> First things first! If you want to use Bugzilla, first you + need to create an account. Consult with the administrator + responsible for your installation of Bugzilla for the URL you + should use to access it. If you're test-driving the end-user + Bugzilla experience, use this URL: <A HREF="http://landfill.tequilarista.org/bugzilla-tip/" TARGET="_top" -> http://landfill.tequilarista.org/bugzilla-tip/</A +> http://landfill.tequilarista.org/bugzilla-tip/</A > </P ><P @@ -190,23 +189,40 @@ TYPE="1" ></LI ><LI ><P -> Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself) - in the spaces provided, then select the "Create Account" button. +> Enter your "E-mail address" and "Real Name" (or whatever + name you want to call yourself) in the spaces provided, + then select the "Create Account" button. </P ></LI ><LI ><P -> Within 5-10 minutes, you should receive an email to the address you provided above, - which contains your login name (generally the same as the email address), and - a password you can use to access your account. This password is randomly generated, - and should be changed at your nearest opportunity (we'll go into how to do it later). +> Within moments, you should receive an email to the address + you provided above, which contains your login name + (generally the same as the email address), and a password + you can use to access your account. This password is + randomly generated, and should be changed at your nearest + opportunity (we'll go into how to do it later). </P ></LI ><LI ><P -> Click the "Log In" link in the yellow area at the bottom of the page in your browser, - then enter your "E-mail address" and "Password" you just received into the spaces provided, - and select "Login". +> Click the <SPAN +CLASS="QUOTE" +>"Log In"</SPAN +> link in the yellow area at + the bottom of the page in your browser, then enter your + <SPAN +CLASS="QUOTE" +>"E-mail address"</SPAN +> and <SPAN +CLASS="QUOTE" +>"Password"</SPAN +> + you just received into the spaces provided, and select + <SPAN +CLASS="QUOTE" +>"Login"</SPAN +>. <DIV CLASS="NOTE" ><P @@ -228,9 +244,17 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> If you ever forget your password, you can come back to this page, enter your - "E-mail address", then select the "E-mail me a password" button to have your password - mailed to you again so that you can login. +> If you ever forget your password, you can come back to + this page, enter your <SPAN +CLASS="QUOTE" +>"E-mail address"</SPAN +>, + then select the <SPAN +CLASS="QUOTE" +>"E-mail me a password"</SPAN +> + button to have your password mailed to you again so + that you can login. </P ></TD ></TR @@ -258,11 +282,21 @@ ALT="Caution"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> Many modern browsers include an "Auto-Complete" or "Form Fill" feature to - remember the user names and passwords you type in at many sites. Unfortunately, - sometimes they attempt to "guess" what you will put in as your password, and guess - wrong. If you notice a text box is already filled out, please overwrite the contents - of the text box so you can be sure to input the correct information. +> Many modern browsers include an + <SPAN +CLASS="QUOTE" +>"Auto-Complete"</SPAN +> or <SPAN +CLASS="QUOTE" +>"Form + Fill"</SPAN +> feature to remember the user names and + passwords you type in at many sites. Unfortunately, + sometimes they attempt to guess what you will put in + as your password, and guess wrong. If you notice a + text box is already filled out, please overwrite the + contents of the text box so you can be sure to input + the correct information. </P ></TD ></TR @@ -273,11 +307,15 @@ VALIGN="TOP" ></LI ></OL ><P -> Congratulations! If you followed these directions, you now are the - proud owner of a user account on landfill.tequilarista.org (Landfill) or - your local Bugzilla install. You should now see in your browser a - page called the "Bugzilla Query Page". It may look daunting, but - with this Guide to walk you through it, you will master it in no time. +> Congratulations! If you followed these directions, you now + are the proud owner of a user account on + landfill.tequilarista.org (Landfill) or your local Bugzilla + install. You should now see in your browser a page called the + <SPAN +CLASS="QUOTE" +>"Bugzilla Query Page"</SPAN +>. It may look daunting, but with this + Guide to walk you through it, you will master it in no time. </P ></DIV ><DIV @@ -289,16 +327,27 @@ NAME="QUERY" >2.3.2. The Bugzilla Query Page</A ></H2 ><P -> The Bugzilla Query Page is the heart and soul of Bugzilla. It is the master - interface where you can find any bug report, comment, or patch currently in the Bugzilla - system. We'll go into how to create your own bug report later on. +> The Bugzilla Query Page is the heart and soul of the Bugzilla + user experience. It is the master interface where you can + find any bug report, comment, or patch currently in the + Bugzilla system. We'll go into how to create your own bug + report later on. </P ><P -> There are efforts underway to simplify query usage. If you have a local installation - of Bugzilla 2.12 or higher, you should have "quicksearch.html" available - to use and simplify your searches. There is also, or shortly will be, a helper - for the query interface, called "queryhelp.cgi". Landfill tends to run the latest code, - so these two utilities should be available there for your perusal. +> There are efforts underway to simplify query usage. If you + have a local installation of Bugzilla 2.12 or higher, you + should have <TT +CLASS="FILENAME" +>quicksearch.html</TT +> available to + use and simplify your searches. There is also a helper for + the query interface, called + <TT +CLASS="FILENAME" +>queryhelp.cgi</TT +>. Landfill tends to run the + latest code, so these two utilities should be available there + for your perusal. </P ><P > At this point, please visit the main Bugzilla site, @@ -309,23 +358,32 @@ TARGET="_top" >, to see a more fleshed-out query page. </P ><P -> The first thing you need to notice about the Bugzilla Query Page is that - nearly every box you see on your screen has a hyperlink nearby, explaining what - it is or what it does. Near the upper-left-hand corner of your browser window - you should see the word "Status" underlined. Select it. +> The first thing you need to notice about the Bugzilla Query + Page is that nearly every box you see on your screen has a + hyperlink nearby, explaining what it is or what it does. Near + the upper-left-hand corner of your browser window you should + see the word <SPAN +CLASS="QUOTE" +>"Status"</SPAN +> underlined. Select it. </P ><P -> Notice the page that popped up? Every underlined word you see on your screen - is a hyperlink that will take you to context-sensitive help. - Click around for a while, and learn what everything here does. To return - to the query interface after pulling up a help page, use the "Back" button in - your browser. +> Notice the page that popped up? Every underlined word you see + on your screen is a hyperlink that will take you to + context-sensitive help. Click around for a while, and learn + what everything here does. To return to the query interface + after pulling up a help page, use the <SPAN +CLASS="QUOTE" +>"Back"</SPAN +> + button in your browser. </P ><P -> I'm sure that after checking out the online help, you are now an Expert - on the Bugzilla Query Page. If, however, you feel you haven't mastered it yet, - let me walk you through making a few successful queries to find out what there - are in the Bugzilla bug-tracking system itself. +> I'm sure that after checking out the online help, you are now + an expert on the Bugzilla Query Page. If, however, you feel + you haven't mastered it yet, let me walk you through making a + few successful queries to find out what there are in the + Bugzilla bug-tracking system itself. </P ><P ></P @@ -333,27 +391,37 @@ TARGET="_top" TYPE="1" ><LI ><P -> Ensure you are back on the "Bugzilla Query Page" - Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys", - "Priority", or "Severity". The default query for "Status" is to find all bugs that - are NEW, ASSIGNED, or REOPENED, which is what we want. If you don't select anything - in the other 5 scrollboxes there, then you are saying that "any of these are OK"; - we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95" - OpSys (Operating System). You're smart, I think you have it figured out. +> Ensure you are back on the <SPAN +CLASS="QUOTE" +>"Bugzilla Query + Page"</SPAN +>. Do nothing in the boxes marked "Status", + "Resolution", "Platform", "OpSys", "Priority", or + "Severity". The default query for "Status" is to find all + bugs that are NEW, ASSIGNED, or REOPENED, which is what we + want. If you don't select anything in the other 5 + scrollboxes there, then you are saying that "any of these + are OK"; we're not locking ourselves into only finding + bugs on the "DEC" Platform, or "Windows 95" OpSys + (Operating System). You're smart, I think you have it + figured out. </P ><P > Basically, selecting <EM >anything</EM -> on the query page narrows your search - down. Leaving stuff unselected, or text boxes unfilled, broadens your search! +> on the + query page narrows your search down. Leaving stuff + unselected, or text boxes unfilled, broadens your search. </P ></LI ><LI ><P -> You see the box immediately below the top six boxes that contains an "Email" text box, - with the words "matching as", a drop-down selection box, then some checkboxes with - "Assigned To" checked by default? This allows you to filter your search down based upon - email address. Let's put my email address in there, and see what happens. +> You see the box immediately below the top six boxes that + contains an "Email" text box, with the words "matching + as", a drop-down selection box, then some checkboxes with + "Assigned To" checked by default? This allows you to + filter your search down based upon email address. Let's + put my email address in there, and see what happens. </P ><P > Type "barnboy@trilobyte.net" in the top Email text box. @@ -361,24 +429,29 @@ TYPE="1" ></LI ><LI ><P -> Let's narrow the search some more. Scroll down until you find the box with the word - "Program" over the top of it. This is where we can narrow our search down to only - specific products (software programs or product lines) in our Bugzilla database. - Please notice the box is a <EM +> Let's narrow the search some more. Scroll down until you + find the box with the word "Program" over the top of it. + This is where we can narrow our search down to only + specific products (software programs or product lines) in + our Bugzilla database. Please notice the box is a + <EM >scrollbox</EM ->. Using the down arrow on the - scrollbox, scroll down until you can see an entry called "Webtools". Select this entry. +>. Using the down arrow on + the scrollbox, scroll down until you can see an entry + called "Webtools". Select this entry. </P ></LI ><LI ><P -> Did you notice that some of the boxes to the right changed when you selected "Webtools"? - Every Program (or Product) has different Versions, Components, and Target Milestones associated - with it. A "Version" is the number of a software program. +> Did you notice that some of the boxes to the right changed + when you selected "Webtools"? Every Program (or Product) + has different Versions, Components, and Target Milestones + associated with it. A "Version" is the number of a + software program. <DIV CLASS="EXAMPLE" ><A -NAME="AEN297" +NAME="AEN307" ></A ><P ><B @@ -387,42 +460,45 @@ NAME="AEN297" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN299" +NAME="AEN309" ></A ><P ></P ><P -> Do you remember the hype in 1995 when Microsoft Windows 95(r) was released? - It may have been several years - ago, but Microsoft(tm) spent over $300 Million advertising this new Version of their - software. Three years later, they released Microsoft Windows 98(r), - another new version, to great fanfare, and then in 2000 quietly - released Microsoft Windows ME(Millenium Edition)(r). +> Do you remember the hype in 1995 when Microsoft + Windows 95(r) was released? It may have been several + years ago, but Microsoft(tm) spent over $300 Million + advertising this new Version of their software. + Three years later, they released Microsoft Windows + 98(r), another new version, to great fanfare, and + then in 2000 quietly released Microsoft Windows + ME(Millenium Edition)(r). </P ><P -> Software "Versions" help a manufacturer differentiate - their current product from their - previous products. Most do not identify their products - by the year they were released. - Instead, the "original" version of their software will - often be numbered "1.0", with - small bug-fix releases on subsequent tenths of a digit. In most cases, it's not - a decimal number; for instance, often 1.9 is an <EM +> Software "Versions" help a manufacturer + differentiate their current product from their + previous products. Most do not identify their + products by the year they were released. Instead, + the "original" version of their software will often + be numbered "1.0", with small bug-fix releases on + subsequent tenths of a digit. In most cases, it's + not a decimal number; for instance, often 1.9 is an + <EM >older</EM -> version - of the software than 1.11, - but is a <EM +> version of the software + than 1.11, but is a <EM >newer</EM -> version than 1.1.1. +> + version than 1.1.1. </P ><P -> In general, a "Version" in Bugzilla should refer to +> In general, a "Version" in Bugzilla should refer to <EM >released</EM -> - products, not products that have not yet been released - to the public. Forthcoming products - are what the Target Milestone field is for. +> products, not products + that have not yet been released to the public. + Forthcoming products are what the Target Milestone + field is for. </P ><P ></P @@ -439,7 +515,7 @@ NAME="AEN299" <DIV CLASS="EXAMPLE" ><A -NAME="AEN307" +NAME="AEN317" ></A ><P ><B @@ -448,7 +524,7 @@ NAME="AEN307" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN309" +NAME="AEN319" ></A ><P ></P @@ -535,26 +611,25 @@ BORDER="0" > </P ><P -> A "Milestone", or "Target Milestone" is a often a planned future "Version" of a - product. In many cases, though, Milestones simply represent significant dates for - a developer. Having certain features in your Product is frequently - tied to revenue (money) - the developer will receive if the features work by the time she - reaches the Target Milestone. - Target Milestones are a great tool to organize your time. - If someone will pay you $100,000 for - incorporating certain features by a certain date, - those features by that Milestone date become - a very high priority. Milestones tend to be highly malleable creatures, - though, that appear - to be in reach but are out of reach by the time the important day arrives. +> A "Milestone", or "Target Milestone" is a often a planned + future "Version" of a product. In many cases, though, + Milestones simply represent significant dates for a + developer. Having certain features in your Product is + frequently tied to revenue (money) the developer will + receive if the features work by the time she reaches the + Target Milestone. Target Milestones are a great tool to + organize your time. If someone will pay you $100,000 for + incorporating certain features by a certain date, those + features by that Milestone date become a very high + priority. Milestones tend to be highly malleable + creatures, though, that appear to be in reach but are out + of reach by the time the important day arrives. </P ><P -> The Bugzilla Project has set up Milestones for future - Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, - a Target Milestone can just as easily be a specific date, - code name, or weird alphanumeric - combination, like "M19". +> The Bugzilla Project has set up Milestones for future + Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a + Target Milestone can just as easily be a specific date, + code name, or weird alphanumeric combination, like "M19". </P ></LI ><LI @@ -571,25 +646,25 @@ BORDER="0" ></LI ><LI ><P -> Congratulations! You've completed your first Query, and have before you the Bug List - of the author of this Guide, Matthew P. Barnson (barnboy@trilobyte.net). If I'm - doing well, - you'll have a cryptic "Zarro Boogs Found" message on your screen. It is just - a happy hacker's way of saying "Zero Bugs Found". However, I am fairly certain I will +> Congratulations! You've completed your first Query, and + have before you the Bug List of the author of this Guide, + Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing + well, you'll have a cryptic "Zarro Boogs Found" message on + your screen. It is just a happy hacker's way of saying + "Zero Bugs Found". However, I am fairly certain I will always have some bugs assigned to me that aren't done yet, so you won't often see that message! </P ></LI ></OL ><P -> I encourage you to click the bug numbers in the left-hand column and examine - my bugs. Also notice that if you click the underlined - links near the top of this page, they do - not take you to context-sensitive help here, - but instead sort the columns of bugs on the screen! - When you need to sort your bugs by priority, severity, - or the people they are assigned to, this - is a tremendous timesaver. +> I encourage you to click the bug numbers in the left-hand + column and examine my bugs. Also notice that if you click the + underlined links near the top of this page, they do not take + you to context-sensitive help here, but instead sort the + columns of bugs on the screen! When you need to sort your bugs + by priority, severity, or the people they are assigned to, + this is a tremendous timesaver. </P ><P > A couple more interesting things about the Bug List page: @@ -602,37 +677,37 @@ BORDER="0" ><TD ><EM >Change Columns</EM ->: - by selecting this link, you can show all kinds - of information in the Bug List</TD +>: by selecting + this link, you can show all kinds of information in the + Bug List</TD ></TR ><TR ><TD ><EM >Change several bugs at once</EM ->: - If you have sufficient rights to change all - the bugs shown in the Bug List, you can mass-modify them. - This is a big time-saver.</TD +>: If + you have sufficient rights to change all the bugs shown in + the Bug List, you can mass-modify them. This is a big + time-saver.</TD ></TR ><TR ><TD ><EM >Send mail to bug owners</EM ->: - If you have many related bugs, you can request - an update from every person who owns the bugs in - the Bug List asking them the status.</TD +>: If you + have many related bugs, you can request an update from + every person who owns the bugs in the Bug List asking them + the status.</TD ></TR ><TR ><TD ><EM >Edit this query</EM ->: - If you didn't get exactly the results you were looking for, - you can return to the Query page through this link and make - small revisions to the query you just made so - you get more accurate results.</TD +>: If you didn't + get exactly the results you were looking for, you can + return to the Query page through this link and make small + revisions to the query you just made so you get more + accurate results.</TD ></TR ></TBODY ></TABLE @@ -661,17 +736,14 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> There are many more options to the Bugzilla Query Page - and the Bug List than I have shown you. - But this should be enough for you to learn to get around. - I encourage you to check out the - <A +> There are many more options to the Bugzilla Query Page and + the Bug List than I have shown you. But this should be + enough for you to learn to get around. I encourage you to + check out the <A HREF="http://www.mozilla.org/bugs/" TARGET="_top" >Bugzilla Home Page</A -> - to learn about the Anatomy - and Life Cycle of a Bug before continuing. +> to learn about the Anatomy and Life Cycle of a Bug before continuing. </P ></TD ></TR @@ -720,30 +792,33 @@ NAME="BUG_WRITING" >2.3.3.1. Writing a Great Bug Report</A ></H3 ><P -> Before we plunge into writing your first bug report, I encourage you to read - <A +> Before we plunge into writing your first bug report, I + encourage you to read some bug-writing guidelines. If you + are reading this document as part of a Bugzilla CVS checkout + or un-tarred Bugzilla distribution, you should be able to + read them by clicking <A +HREF="../../bugwritinghelp.html" +TARGET="_top" +>here</A +>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <A HREF="http://www.mozilla.org/quality/bug-writing-guidelines.html" TARGET="_top" ->Mozilla.org's Bug - Writing Guidelines</A ->. While some of the advice is Mozilla-specific, the basic - principles of reporting Reproducible, Specific bugs, isolating the Product you are - using, the Version of the Product, the Component which failed, the Hardware Platform, and - Operating System you were using at the time of the failure go a long way toward ensuring accurate, - responsible fixes for the bug that bit you. +>http://www.mozilla.org/quality/bug-writing-guidelines.html</A +>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you. </P ><P -> While you are at it, why not learn how to find previously reported bugs? Mozilla.org - has published a great tutorial on finding duplicate bugs, available at - <A +> While you are at it, why not learn how to find previously + reported bugs? Mozilla.org has published a great tutorial + on finding duplicate bugs, available at <A HREF="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html" TARGET="_top" -> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A +> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</A >. </P ><P -> I realize this was a lot to read. However, understanding the mentality of writing - great bug reports will help us on the next part! +> I realize this was a lot to read. However, understanding + the mentality of writing great bug reports will help us on + the next part! </P ><P ></P @@ -754,18 +829,16 @@ TYPE="1" > Go back to <A HREF="http://landfill.tequilarista.org/bugzilla-tip/" TARGET="_top" -> http://landfill.tequilarista.org/bugzilla-tip/</A -> - in your browser. +> http://landfill.tequilarista.org/bugzilla-tip/</A +> in your browser. </P ></LI ><LI ><P -> Select the - <A +> Select the <A HREF="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi" TARGET="_top" -> Enter a new bug report</A +> Enter a new bug report</A > link. </P ></LI @@ -776,11 +849,11 @@ TARGET="_top" ></LI ><LI ><P -> Now you should be at the "Enter Bug" form. - The "reporter" should have been automatically filled out - for you (or else Bugzilla prompted you to Log In again - -- you did keep the email with your username - and password, didn't you?). +> Now you should be at the "Enter Bug" form. The + "reporter" should have been automatically filled out for + you (or else Bugzilla prompted you to Log In again -- + you did keep the email with your username and password, + didn't you?). </P ></LI ><LI @@ -790,36 +863,37 @@ TARGET="_top" ></LI ><LI ><P -> Bugzilla should have made reasonable guesses, based upon your browser, - for the "Platform" and "OS" drop-down - boxes. If those are wrong, change them -- if you're on an SGI box - running IRIX, we want to know! +> Bugzilla should have made reasonable guesses, based upon + your browser, for the "Platform" and "OS" drop-down + boxes. If those are wrong, change them -- if you're on + an SGI box running IRIX, we want to know! </P ></LI ><LI ><P -> Fill in the "Assigned To" box with the email address you provided earlier. - This way you don't end up sending copies of your bug to lots of other people, - since it's just a test bug. +> Fill in the "Assigned To" box with the email address you + provided earlier. This way you don't end up sending + copies of your bug to lots of other people, since it's + just a test bug. </P ></LI ><LI ><P -> Leave the "CC" text box blank. - Fill in the "URL" box with "http://www.mozilla.org". +> Leave the "CC" text box blank. Fill in the "URL" box + with "http://www.mozilla.org". </P ></LI ><LI ><P -> Enter "The Bugzilla Guide" in the Summary text box, - and place any comments you have on this - tutorial, or the Guide in general, into the Description box. +> Enter "The Bugzilla Guide" in the Summary text box, and + place any comments you have on this tutorial, or the + Guide in general, into the Description box. </P ></LI ></OL ><P -> Voila! Select "Commit" and send in your bug report! - Next we'll look at resolving bugs. +> Voila! Select "Commit" and send in your bug report! Next + we'll look at resolving bugs. </P ></DIV ><DIV @@ -831,10 +905,10 @@ NAME="BUG_MANAGE" >2.3.3.2. Managing your Bug Reports</A ></H3 ><P -> OK, you should have a link to the bug you just created near the top of your page. - It should say - "Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX". - Select this link. +> OK, you should have a link to the bug you just created near + the top of your page. It should say "Bug XXXX posted", with + a link to the right saying "Back to BUG# XXXX". Select this + link. </P ><P ></P @@ -842,35 +916,32 @@ NAME="BUG_MANAGE" TYPE="1" ><LI ><P -> Scroll down a bit on the subsequent page, - until you see the "Resolve bug, changing resolution to (dropdown box). - Normally, you would - "Accept bug (change status to ASSIGNED)", fix it, and then resolve. - But in this case, we're - going to short-circuit the process because this wasn't a real bug. - Change the dropdown next to - "Resolve Bug" to "INVALID", make sure the radio button is - marked next to "Resolve Bug", then - click "Commit". +> Scroll down a bit on the subsequent page, until you see + the "Resolve bug, changing resolution to (dropdown box). + Normally, you would "Accept bug (change status to + ASSIGNED)", fix it, and then resolve. But in this case, + we're going to short-circuit the process because this + wasn't a real bug. Change the dropdown next to "Resolve + Bug" to "INVALID", make sure the radio button is marked + next to "Resolve Bug", then click "Commit". </P ></LI ><LI ><P -> Hey! It said it couldn't take the change in a big red box! - That's right, you must specify - a Comment in order to make this change. Select the "Back" - button in your browser, add a - Comment, then try Resolving the bug with INVALID status again. - This time it should work. +> Hey! It said it couldn't take the change in a big red + box! That's right, you must specify a Comment in order + to make this change. Select the "Back" button in your + browser, add a Comment, then try Resolving the bug with + INVALID status again. This time it should work. </P ></LI ></OL ><P > You have now learned the basics of Bugzilla navigation, - entering a bug, and bug maintenance. - I encourage you to explore these features, and see what you can do with them! - We'll spend no more time on individual Bugs or Queries from this point on, so you are - on your own there. + entering a bug, and bug maintenance. I encourage you to + explore these features, and see what you can do with them! + We'll spend no more time on individual Bugs or Queries from + this point on, so you are on your own there. </P ><P > But I'll give a few last hints! @@ -880,41 +951,29 @@ TYPE="1" HREF="http://bugzilla.mozilla.org/help.html" TARGET="_top" >CLUE</A -> - on the Query page - that will teach you more how to use the form. +> on the Query page that will teach you more how to use the form. </P ><P -> If you click the hyperlink on the - <A +> If you click the hyperlink on the <A HREF="http://bugzilla.mozilla.org/describecomponents.cgi" TARGET="_top" >Component</A -> - box of the Query page, you will be presented a form that will describe what all - the components are. +> box of the Query page, you will be presented a form that will describe what all the components are. </P ><P -> Possibly the most powerful feature of the Query page is the +> Possibly the most powerful feature of the Query page is the <A HREF="http://bugzilla.mozilla.org/booleanchart.html" TARGET="_top" >Boolean Chart</A -> section. - It's a bit confusing to use the first time, but can provide unparalleled - flexibility in your queries, - allowing you to build extremely powerful requests. +> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests. </P ><P -> Finally, you can build some nifty - <A +> Finally, you can build some nifty <A HREF="http://bugzilla.mozilla.org/reports.cgi" TARGET="_top" >Reports</A -> - using the "Bug Reports" link near the bottom of the query page, and also - available via the "Reports" link - at the footer of each page. +> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page. </P ></DIV ></DIV @@ -972,7 +1031,7 @@ HREF="using.html" WIDTH="33%" ALIGN="right" VALIGN="top" ->What's in it for me?</TD +>Where can I find my user preferences?</TD ></TR ></TABLE ></DIV diff --git a/docs/html/index.html b/docs/html/index.html index 4be428554..8cc084540 100644 --- a/docs/html/index.html +++ b/docs/html/index.html @@ -77,12 +77,6 @@ CLASS="ADDRESS" ></DIV ></DIV ><BR></SPAN -><H4 -CLASS="EDITEDBY" ->Edited by</H4 -><H3 -CLASS="EDITOR" ->I. P. Freely</H3 ><DIV CLASS="REVHISTORY" ><TABLE @@ -192,7 +186,7 @@ COLSPAN="3" ><DIV CLASS="ABSTRACT" ><A -NAME="AEN46" +NAME="AEN39" ></A ><P ></P @@ -213,6 +207,12 @@ NAME="AEN46" Bugzilla. </P ><P +> THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT. + IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN + TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT + ADDITIONS TO THE GUIDE WRITTEN IN HTML! + </P +><P ></P ></DIV ></DIV @@ -336,7 +336,7 @@ HREF="how.html#BUG_MANAGE" ><DT >2.4. <A HREF="init4me.html" ->What's in it for me?</A +>Where can I find my user preferences?</A ></DT ><DD ><DL @@ -409,12 +409,12 @@ HREF="stepbystep.html" ><DL ><DT >3.2.1. <A -HREF="stepbystep.html#AEN478" +HREF="stepbystep.html#AEN486" >Introduction</A ></DT ><DT >3.2.2. <A -HREF="stepbystep.html#AEN484" +HREF="stepbystep.html#AEN492" >Installing the Prerequisites</A ></DT ><DT @@ -429,77 +429,80 @@ HREF="stepbystep.html#INSTALL-PERL" ></DT ><DT >3.2.5. <A -HREF="stepbystep.html#AEN537" +HREF="stepbystep.html#AEN579" >DBI Perl Module</A ></DT ><DT >3.2.6. <A -HREF="stepbystep.html#AEN574" +HREF="stepbystep.html#AEN617" >Data::Dumper Perl Module</A ></DT ><DT >3.2.7. <A -HREF="stepbystep.html#AEN578" +HREF="stepbystep.html#AEN622" >MySQL related Perl Module Collection</A ></DT ><DT >3.2.8. <A -HREF="stepbystep.html#AEN587" +HREF="stepbystep.html#AEN631" >TimeDate Perl Module Collection</A ></DT ><DT >3.2.9. <A -HREF="stepbystep.html#AEN590" +HREF="stepbystep.html#AEN635" >GD Perl Module (1.8.3)</A ></DT ><DT >3.2.10. <A -HREF="stepbystep.html#AEN596" +HREF="stepbystep.html#AEN644" >Chart::Base Perl Module (0.99c)</A ></DT ><DT >3.2.11. <A -HREF="stepbystep.html#AEN599" +HREF="stepbystep.html#AEN648" >DB_File Perl Module</A ></DT ><DT >3.2.12. <A -HREF="stepbystep.html#AEN602" +HREF="stepbystep.html#AEN651" >HTTP Server</A ></DT ><DT >3.2.13. <A -HREF="stepbystep.html#AEN616" +HREF="stepbystep.html#AEN669" >Installing the Bugzilla Files</A ></DT ><DT >3.2.14. <A -HREF="stepbystep.html#AEN636" +HREF="stepbystep.html#AEN696" >Setting Up the MySQL Database</A ></DT ><DT >3.2.15. <A -HREF="stepbystep.html#AEN675" ->Tweaking "localconfig"</A +HREF="stepbystep.html#AEN743" +>Tweaking <TT +CLASS="FILENAME" +>localconfig</TT +></A ></DT ><DT >3.2.16. <A -HREF="stepbystep.html#AEN704" +HREF="stepbystep.html#AEN781" >Setting Up Maintainers Manually (Optional)</A ></DT ><DT >3.2.17. <A -HREF="stepbystep.html#AEN713" +HREF="stepbystep.html#AEN792" >The Whining Cron (Optional)</A ></DT ><DT >3.2.18. <A -HREF="stepbystep.html#AEN723" +HREF="stepbystep.html#AEN802" >Bug Graphs (Optional)</A ></DT ><DT >3.2.19. <A -HREF="stepbystep.html#AEN735" +HREF="stepbystep.html#AEN814" >Securing MySQL</A ></DT ></DL @@ -523,12 +526,12 @@ HREF="geninstall.html" ><DL ><DT >3.5.1. <A -HREF="geninstall.html#AEN837" +HREF="geninstall.html#AEN916" >Modifying Your Running System</A ></DT ><DT >3.5.2. <A -HREF="geninstall.html#AEN844" +HREF="geninstall.html#AEN923" >Upgrading From Previous Versions</A ></DT ><DT @@ -541,7 +544,20 @@ CLASS="FILENAME" ></DT ><DT >3.5.4. <A -HREF="geninstall.html#AEN865" +HREF="geninstall.html#MOD_THROTTLE" +><TT +CLASS="FILENAME" +>mod_throttle</TT +> and Security</A +></DT +><DT +>3.5.5. <A +HREF="geninstall.html#CONTENT_TYPE" +>Preventing untrusted Bugzilla content from executing malicious Javascript code</A +></DT +><DT +>3.5.6. <A +HREF="geninstall.html#AEN964" >UNIX Installation Instructions History</A ></DT ></DL @@ -694,7 +710,7 @@ HREF="scm.html" ><DT >5.4. <A HREF="tinderbox.html" ->Tinderbox</A +>Tinderbox/Tinderbox2</A ></DT ></DL ></DD @@ -734,14 +750,14 @@ HREF="dbdoc.html" ><DL ><DT >C.2.1. <A -HREF="dbdoc.html#AEN2089" +HREF="dbdoc.html#AEN2217" >Bugzilla Database Basics</A ></DT ><DD ><DL ><DT >C.2.1.1. <A -HREF="dbdoc.html#AEN2118" +HREF="dbdoc.html#AEN2246" >Bugzilla Database Tables</A ></DT ></DL @@ -758,7 +774,7 @@ HREF="granttables.html" ><DT >7. <A HREF="variants.html" ->Bugzilla Variants</A +>Bugzilla Variants and Competitors</A ></DT ><DD ><DL @@ -767,6 +783,31 @@ HREF="variants.html" HREF="rhbugzilla.html" >Red Hat Bugzilla</A ></DT +><DT +>7.2. <A +HREF="variant_fenris.html" +>Loki Bugzilla (Fenris)</A +></DT +><DT +>7.3. <A +HREF="variant_issuezilla.html" +>Issuezilla</A +></DT +><DT +>7.4. <A +HREF="variant_scarab.html" +>Scarab</A +></DT +><DT +>7.5. <A +HREF="variant_perforce.html" +>Perforce SCM</A +></DT +><DT +>7.6. <A +HREF="variant_sourceforge.html" +>SourceForge</A +></DT ></DL ></DD ><DT @@ -778,16 +819,24 @@ HREF="patches.html" ><DL ><DT >D.1. <A +HREF="rewrite.html" +>Apache <TT +CLASS="FILENAME" +>mod_rewrite</TT +> magic</A +></DT +><DT +>D.2. <A HREF="setperl.html" >The setperl.csh Utility</A ></DT ><DT ->D.2. <A +>D.3. <A HREF="cmdline.html" >Command-line Bugzilla Queries</A ></DT ><DT ->D.3. <A +>D.4. <A HREF="quicksearch.html" >The Quicksearch Utility</A ></DT @@ -879,72 +928,73 @@ CLASS="LOT" ></DT ><DT >2-1. <A -HREF="how.html#AEN297" +HREF="how.html#AEN307" >Some Famous Software Versions</A ></DT ><DT >2-2. <A -HREF="how.html#AEN307" +HREF="how.html#AEN317" >Mozilla Webtools Components</A ></DT ><DT >3-1. <A -HREF="stepbystep.html#AEN625" +HREF="stepbystep.html#AEN685" >Setting up bonsaitools symlink</A ></DT ><DT >3-2. <A -HREF="stepbystep.html#AEN697" +HREF="stepbystep.html#AEN774" >Running checksetup.pl as the web user</A ></DT ><DT >3-3. <A -HREF="win32.html#AEN910" +HREF="win32.html#AEN1012" >Installing ActivePerl ppd Modules on Microsoft Windows</A ></DT ><DT >3-4. <A -HREF="win32.html#AEN1084" ->Removing encrypt() for Windows NT installations</A +HREF="win32.html#AEN1180" +>Removing encrypt() for Windows NT Bugzilla version + 2.12 or earlier</A ></DT ><DT >4-1. <A -HREF="programadmin.html#AEN1279" +HREF="programadmin.html#AEN1413" >Creating some Components</A ></DT ><DT >4-2. <A -HREF="programadmin.html#AEN1308" +HREF="programadmin.html#AEN1442" >Common Use of Versions</A ></DT ><DT >4-3. <A -HREF="programadmin.html#AEN1312" +HREF="programadmin.html#AEN1446" >A Different Use of Versions</A ></DT ><DT >4-4. <A -HREF="programadmin.html#AEN1340" +HREF="programadmin.html#AEN1474" >Using SortKey with Target Milestone</A ></DT ><DT >4-5. <A -HREF="programadmin.html#AEN1376" +HREF="programadmin.html#AEN1510" >When to Use Group Security</A ></DT ><DT >4-6. <A -HREF="programadmin.html#AEN1393" +HREF="programadmin.html#AEN1527" >Creating a New Group</A ></DT ><DT >D-1. <A -HREF="setperl.html#AEN2193" +HREF="setperl.html#AEN2360" >Using Setperl to set your perl path</A ></DT ><DT >1. <A -HREF="glossary.html#AEN2389" +HREF="glossary.html#AEN2602" >A Sample Product</A ></DT ></DL diff --git a/docs/html/init4me.html b/docs/html/init4me.html index ffc54f7cb..d400108b2 100644 --- a/docs/html/init4me.html +++ b/docs/html/init4me.html @@ -1,7 +1,7 @@ <HTML ><HEAD ><TITLE ->What's in it for me?</TITLE +>Where can I find my user preferences?</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.61 @@ -71,7 +71,7 @@ CLASS="SECTION" CLASS="SECTION" ><A NAME="INIT4ME" ->2.4. What's in it for me?</A +>2.4. Where can I find my user preferences?</A ></H1 ><TABLE BORDER="0" @@ -101,15 +101,13 @@ VALIGN="TOP" ></TR ></TABLE ><P -> Customized User Preferences offer tremendous versatility to - your individual Bugzilla experience. - Let's plunge into what you can do! The first step is to click - the "Edit prefs" link at the footer of each page once you - have logged in to - <A +> Customized User Preferences offer tremendous versatility to your + individual Bugzilla experience. Let's plunge into what you can + do! The first step is to click the "Edit prefs" link at the + footer of each page once you have logged in to <A HREF="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1" TARGET="_top" -> Landfill</A +> Landfill</A >. </P ><DIV @@ -122,16 +120,29 @@ NAME="ACCOUNTSETTINGS" ></H2 ><P > On this page, you can change your basic Account Settings, - including your password and full name. - For security reasons, in order to change anything on this page you - must type your <EM + including your password and full name. For security reasons, + in order to change anything on this page you must type your + <EM >current</EM -> - password into the "Old Password" field. - If you wish to change your password, type the new password you - want into the "New Password" field and again into the "Re-enter - new password" field to ensure - you typed your new password correctly. Select the "Submit" button and you're done! +> password into the <SPAN +CLASS="QUOTE" +>"Old + Password"</SPAN +> field. If you wish to change your + password, type the new password you want into the <SPAN +CLASS="QUOTE" +>"New + Password"</SPAN +> field and again into the <SPAN +CLASS="QUOTE" +>"Re-enter + new password"</SPAN +> field to ensure you typed your new + password correctly. Select the <SPAN +CLASS="QUOTE" +>"Submit"</SPAN +> button + and you are done. </P ></DIV ><DIV @@ -150,78 +161,30 @@ CLASS="SECTION" NAME="NOTIFICATION" >2.4.2.1. Email Notification</A ></H3 -><DIV -CLASS="NOTE" ><P -></P -><TABLE -CLASS="NOTE" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P -> 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 -></TD -></TR -></TABLE -></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 - <P -></P -><TABLE -BORDER="0" -><TBODY -><TR -><TD -><EM ->All qualifying bugs</EM ->: sends you every change to every bug - where your name is somewhere on it, regardless of who changed it.</TD -></TR -><TR -><TD -><EM ->Only those bugs which I am listed in the CC line</EM ->: prevents - you from receiving mail for which you are the reporter,' - owner, or QA contact. If you are on the CC - list, presumably someone had a <EM ->good</EM -> - reason for you to get the email.</TD -></TR -><TR -><TD -><EM ->All qulifying bugs except those which I change</EM ->: - This is the default, and - a sensible setting. If someone else changes your bugs, you will get emailed, - but if you change bugs - yourself you will receive no notification of the change.</TD -></TR -></TBODY -></TABLE -><P -></P -> +> Here you can reduce or increase the amount of email sent you + from Bugzilla. Although this is referred to as + <SPAN +CLASS="QUOTE" +>"Advanced Email Filtering Options"</SPAN +>, they are, + in fact, the standard email filter set. All of them are + self-explanatory, but you can use the filters in interesting + ways. For instance, some people (notably Quality Assurance + personnel) often only care to receive updates regarding a + bug when the bug changes state, so they can track bugs on + their flow charts and know when it is time to pull the bug + onto a quality assurance platform for inspection. Other + people set up email gateways to + <A +HREF="bonsai.html" +>Bonsai, the Mozilla automated CVS management system</A +> or <A +HREF="tinderbox.html" +>Tinderbox, the Mozilla automated build management system</A +>, and + restrict which types of Bugzilla information are fed to + these systems.. </P ></DIV ><DIV @@ -253,27 +216,30 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> This option may not be available in all Bugzilla installations, depending upon - the preferences of the systems administrator responsible for the setup of your Bugzilla. - However, if you really want this functionality, ask her to "enable newemailtech - in Params" - and "make it the default for all new users", referring her to the Administration section - of this Guide. +> This option may not be available in all Bugzilla + installations, depending upon the preferences of the + systems administrator responsible for the setup of your + Bugzilla. However, if you really want this functionality, + ask her to "enable newemailtech in Params" and "make it + the default for all new users", referring her to the + Administration section of this Guide. </P ></TD ></TR ></TABLE ></DIV ><P -> Disregard the warnings about "experimental and bleeding edge"; the code to handle email - in a cleaner manner than that historically used for Bugzilla is - quite robust and well-tested now. +> Disregard the warnings about "experimental and bleeding + edge"; the code to handle email in a cleaner manner than + that historically used for Bugzilla is quite robust and + well-tested now. </P ><P -> I recommend you enable the option, "Click here to sign up (and risk any bugs)". - Your email-box - will thank you for it. The fundamental shift in "newemailtech" is away from standard UNIX - "diff" output, which is quite ugly, to a prettier, better laid-out email. +> I recommend you enable the option, "Click here to sign up + (and risk any bugs)". Your email-box will thank you for it. + The fundamental shift in "newemailtech" is away from + standard UNIX "diff" output, which is quite ugly, to a + prettier, better laid-out email. </P ></DIV ><DIV @@ -305,20 +271,25 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> This option may not be available in all Bugzilla installations, depending upon - the preferences of the systems administrator responsible for the setup of your Bugzilla. - However, if you really want this functionality, ask her to "enable watchers in Params". +> This option may not be available in all Bugzilla + installations, depending upon the preferences of the + systems administrator responsible for the setup of your + Bugzilla. However, if you really want this functionality, + ask her to "enable watchers in Params". </P ></TD ></TR ></TABLE ></DIV ><P -> By entering user email names into the "Users to watch" text entry box, delineated by commas, - you can watch bugs of other users. This powerful functionality enables seamless transitions - as developers change projects, managers wish to get in touch with the issues faced by their - direct reports, or users go on vacation. If any of these three situations apply - to you, you will undoubtedly find this feature quite convenient. +> By entering user email names into the "Users to watch" text + entry box, delineated by commas, you can watch bugs of other + users. This powerful functionality enables seamless + transitions as developers change projects, managers wish to + get in touch with the issues faced by their direct reports, + or users go on vacation. If any of these three situations + apply to you, you will undoubtedly find this feature quite + convenient. </P ></DIV ></DIV @@ -351,20 +322,24 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> By default, this page is quite barren. However, go explore the Query Page some more; you will - find that you can store numerous queries on the server, so if you regularly run a particular query - it is just a drop-down menu away. On this page of Preferences, if you have many stored - queries you can elect to have them always one-click away! +> By default, this page is quite barren. However, go explore + the Query Page some more; you will find that you can store + numerous queries on the server, so if you regularly run a + particular query it is just a drop-down menu away. On this + page of Preferences, if you have many stored queries you can + elect to have them always one-click away! </P ></TD ></TR ></TABLE ></DIV ><P -> If you have many stored queries on the server, here you will find individual drop-downs for each - stored query. Each drop-down gives you the option of that query appearing on the footer of every - page in Bugzilla! This gives you powerful one-click access to any complex searches you may set up, - and is an excellent way to impress your boss... +> If you have many stored queries on the server, here you will + find individual drop-downs for each stored query. Each + drop-down gives you the option of that query appearing on the + footer of every page in Bugzilla! This gives you powerful + one-click access to any complex searches you may set up, and + is an excellent way to impress your boss... </P ><DIV CLASS="TIP" @@ -387,13 +362,18 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->By default, the "My Bugs" link appears at the bottom of each page. However, this query - gives you both the bugs you have reported, as well as those you are assigned. One of the most - common uses for this page is to remove the "My Bugs" link, replacing it with two other queries, - commonly called "My Bug Reports" and "My Bugs" (but only referencing bugs assigned to you). This - allows you to distinguish those bugs you have reported from those you are assigned. I commonly - set up complex Boolean queries in the Query page and link them to my footer in this page. When - they are significantly complex, a one-click reference can save hours of work.</P +>By default, the "My Bugs" link appears at the bottom of + each page. However, this query gives you both the bugs you + have reported, as well as those you are assigned. One of + the most common uses for this page is to remove the "My + Bugs" link, replacing it with two other queries, commonly + called "My Bug Reports" and "My Bugs" (but only referencing + bugs assigned to you). This allows you to distinguish those + bugs you have reported from those you are assigned. I + commonly set up complex Boolean queries in the Query page + and link them to my footer in this page. When they are + significantly complex, a one-click reference can save hours + of work.</P ></TD ></TR ></TABLE @@ -408,11 +388,12 @@ NAME="PERMISSIONSETTINGS" >2.4.4. Permissions</A ></H2 ><P -> This is a purely informative page which outlines your current permissions on - this installation of Bugzilla. If you have permissions to grant certain permissions to - other users, the "other users" link appears on this page as well as the footer. - For more information regarding user administration, please consult the Administration - section of this Guide. +> This is a purely informative page which outlines your current + permissions on this installation of Bugzilla. If you have + permissions to grant certain permissions to other users, the + "other users" link appears on this page as well as the footer. + For more information regarding user administration, please + consult the Administration section of this Guide. </P ></DIV ></DIV diff --git a/docs/html/installation.html b/docs/html/installation.html index e89260c71..1561b6b5f 100644 --- a/docs/html/installation.html +++ b/docs/html/installation.html @@ -90,12 +90,12 @@ HREF="stepbystep.html" ><DL ><DT >3.2.1. <A -HREF="stepbystep.html#AEN478" +HREF="stepbystep.html#AEN486" >Introduction</A ></DT ><DT >3.2.2. <A -HREF="stepbystep.html#AEN484" +HREF="stepbystep.html#AEN492" >Installing the Prerequisites</A ></DT ><DT @@ -110,77 +110,80 @@ HREF="stepbystep.html#INSTALL-PERL" ></DT ><DT >3.2.5. <A -HREF="stepbystep.html#AEN537" +HREF="stepbystep.html#AEN579" >DBI Perl Module</A ></DT ><DT >3.2.6. <A -HREF="stepbystep.html#AEN574" +HREF="stepbystep.html#AEN617" >Data::Dumper Perl Module</A ></DT ><DT >3.2.7. <A -HREF="stepbystep.html#AEN578" +HREF="stepbystep.html#AEN622" >MySQL related Perl Module Collection</A ></DT ><DT >3.2.8. <A -HREF="stepbystep.html#AEN587" +HREF="stepbystep.html#AEN631" >TimeDate Perl Module Collection</A ></DT ><DT >3.2.9. <A -HREF="stepbystep.html#AEN590" +HREF="stepbystep.html#AEN635" >GD Perl Module (1.8.3)</A ></DT ><DT >3.2.10. <A -HREF="stepbystep.html#AEN596" +HREF="stepbystep.html#AEN644" >Chart::Base Perl Module (0.99c)</A ></DT ><DT >3.2.11. <A -HREF="stepbystep.html#AEN599" +HREF="stepbystep.html#AEN648" >DB_File Perl Module</A ></DT ><DT >3.2.12. <A -HREF="stepbystep.html#AEN602" +HREF="stepbystep.html#AEN651" >HTTP Server</A ></DT ><DT >3.2.13. <A -HREF="stepbystep.html#AEN616" +HREF="stepbystep.html#AEN669" >Installing the Bugzilla Files</A ></DT ><DT >3.2.14. <A -HREF="stepbystep.html#AEN636" +HREF="stepbystep.html#AEN696" >Setting Up the MySQL Database</A ></DT ><DT >3.2.15. <A -HREF="stepbystep.html#AEN675" ->Tweaking "localconfig"</A +HREF="stepbystep.html#AEN743" +>Tweaking <TT +CLASS="FILENAME" +>localconfig</TT +></A ></DT ><DT >3.2.16. <A -HREF="stepbystep.html#AEN704" +HREF="stepbystep.html#AEN781" >Setting Up Maintainers Manually (Optional)</A ></DT ><DT >3.2.17. <A -HREF="stepbystep.html#AEN713" +HREF="stepbystep.html#AEN792" >The Whining Cron (Optional)</A ></DT ><DT >3.2.18. <A -HREF="stepbystep.html#AEN723" +HREF="stepbystep.html#AEN802" >Bug Graphs (Optional)</A ></DT ><DT >3.2.19. <A -HREF="stepbystep.html#AEN735" +HREF="stepbystep.html#AEN814" >Securing MySQL</A ></DT ></DL @@ -204,12 +207,12 @@ HREF="geninstall.html" ><DL ><DT >3.5.1. <A -HREF="geninstall.html#AEN837" +HREF="geninstall.html#AEN916" >Modifying Your Running System</A ></DT ><DT >3.5.2. <A -HREF="geninstall.html#AEN844" +HREF="geninstall.html#AEN923" >Upgrading From Previous Versions</A ></DT ><DT @@ -222,7 +225,20 @@ CLASS="FILENAME" ></DT ><DT >3.5.4. <A -HREF="geninstall.html#AEN865" +HREF="geninstall.html#MOD_THROTTLE" +><TT +CLASS="FILENAME" +>mod_throttle</TT +> and Security</A +></DT +><DT +>3.5.5. <A +HREF="geninstall.html#CONTENT_TYPE" +>Preventing untrusted Bugzilla content from executing malicious Javascript code</A +></DT +><DT +>3.5.6. <A +HREF="geninstall.html#AEN964" >UNIX Installation Instructions History</A ></DT ></DL diff --git a/docs/html/integration.html b/docs/html/integration.html index 19bc0476c..69648fdf2 100644 --- a/docs/html/integration.html +++ b/docs/html/integration.html @@ -94,7 +94,7 @@ HREF="scm.html" ><DT >5.4. <A HREF="tinderbox.html" ->Tinderbox</A +>Tinderbox/Tinderbox2</A ></DT ></DL ></DIV diff --git a/docs/html/newversions.html b/docs/html/newversions.html index 416dba347..ab287d22e 100644 --- a/docs/html/newversions.html +++ b/docs/html/newversions.html @@ -74,7 +74,7 @@ NAME="NEWVERSIONS" >1.4. New Versions</A ></H1 ><P -> This is the 2.14.0 version of The Bugzilla Guide. If you are +> This is the 2.14 version of The Bugzilla Guide. If you are reading this from any source other than those below, please check one of these mirrors to make sure you are reading an up-to-date version of the Guide. diff --git a/docs/html/patches.html b/docs/html/patches.html index b9e6520db..e90e3d10f 100644 --- a/docs/html/patches.html +++ b/docs/html/patches.html @@ -10,11 +10,11 @@ REL="HOME" TITLE="The Bugzilla Guide" HREF="index.html"><LINK REL="PREVIOUS" -TITLE="Red Hat Bugzilla" -HREF="rhbugzilla.html"><LINK +TITLE="SourceForge" +HREF="variant_sourceforge.html"><LINK REL="NEXT" -TITLE="The setperl.csh Utility" -HREF="setperl.html"></HEAD +TITLE="Apache mod_rewrite magic" +HREF="rewrite.html"></HEAD ><BODY CLASS="APPENDIX" BGCOLOR="#FFFFFF" @@ -41,7 +41,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="rhbugzilla.html" +HREF="variant_sourceforge.html" >Prev</A ></TD ><TD @@ -54,7 +54,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="setperl.html" +HREF="rewrite.html" >Next</A ></TD ></TR @@ -78,21 +78,31 @@ CLASS="TOC" ></DT ><DT >D.1. <A +HREF="rewrite.html" +>Apache <TT +CLASS="FILENAME" +>mod_rewrite</TT +> magic</A +></DT +><DT +>D.2. <A HREF="setperl.html" >The setperl.csh Utility</A ></DT ><DT ->D.2. <A +>D.3. <A HREF="cmdline.html" >Command-line Bugzilla Queries</A ></DT ><DT ->D.3. <A +>D.4. <A HREF="quicksearch.html" >The Quicksearch Utility</A ></DT ></DL ></DIV +><P +>Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</P ></DIV ><DIV CLASS="NAVFOOTER" @@ -109,7 +119,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="rhbugzilla.html" +HREF="variant_sourceforge.html" >Prev</A ></TD ><TD @@ -125,7 +135,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="setperl.html" +HREF="rewrite.html" >Next</A ></TD ></TR @@ -134,7 +144,7 @@ HREF="setperl.html" WIDTH="33%" ALIGN="left" VALIGN="top" ->Red Hat Bugzilla</TD +>SourceForge</TD ><TD WIDTH="34%" ALIGN="center" @@ -144,7 +154,10 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->The setperl.csh Utility</TD +>Apache <TT +CLASS="FILENAME" +>mod_rewrite</TT +> magic</TD ></TR ></TABLE ></DIV diff --git a/docs/html/postinstall-check.html b/docs/html/postinstall-check.html index 9a1f52c36..5b0cbbb7a 100644 --- a/docs/html/postinstall-check.html +++ b/docs/html/postinstall-check.html @@ -74,8 +74,8 @@ NAME="POSTINSTALL-CHECK" >4.1. Post-Installation Checklist</A ></H1 ><P -> After installation, follow the checklist below to ensure that - you have a successful installation. If you do not see a +> After installation, follow the checklist below to help ensure + that you have a successful installation. If you do not see a recommended setting for a parameter, consider leaving it at the default while you perform your initial tests on your Bugzilla setup. @@ -86,20 +86,34 @@ 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. +> Bring up <TT +CLASS="FILENAME" +>editparams.cgi</TT +> in your web + browser. This should be available as the <SPAN +CLASS="QUOTE" +>"edit + parameters"</SPAN +> link from any Bugzilla screen once you + have logged in. </P ></LI ><LI ><P -> Set "maintainer" to <EM +>The <SPAN +CLASS="QUOTE" +>"maintainer"</SPAN +> is the email address of + the person responsible for maintaining this Bugzilla + installation. The maintainer need not be a valid Bugzilla + user. Error pages, error emails, and administrative mail + will be sent with the maintainer as the return email + address.</P +><P +> Set <SPAN +CLASS="QUOTE" +>"maintainer"</SPAN +> to <EM >your</EM > email address. This allows Bugzilla's error messages to display your email @@ -108,28 +122,59 @@ TARGET="_top" ></LI ><LI ><P -> Set "urlbase" to the URL reference for your Bugzilla - installation. If your bugzilla query page is at - http://www.foo.com/bugzilla/query.cgi, your url base is - http://www.foo.com/bugzilla/ +>The <SPAN +CLASS="QUOTE" +>"urlbase"</SPAN +> parameter defines the fully + qualified domain name and web server path to your Bugzilla + installation.</P +><P +> For example, if your bugzilla query page is + http://www.foo.com/bugzilla/query.cgi, set your + <SPAN +CLASS="QUOTE" +>"urlbase"</SPAN +> is http://www.foo.com/bugzilla/. </P ></LI ><LI ><P +><SPAN +CLASS="QUOTE" +>"usebuggroups"</SPAN +> dictates whether or not to + implement group-based security for Bugzilla. If set, + Bugzilla bugs can have an associated groupmask defining + which groups of users are allowed to see and edit the + bug.</P +><P > Set "usebuggroups" to "on" <EM >only</EM > if you - need to restrict access to products. I suggest leaving this - parameter <EM + may wish to restrict access to products. I suggest leaving + this parameter <EM >off</EM -> while initially testing - your Bugzilla. +> while initially + testing your Bugzilla. </P ></LI ><LI ><P -> Set "usebuggroupsentry" to "on" if you want to restrict - access to products. Once again, if you are simply testing +> <SPAN +CLASS="QUOTE" +>"usebuggroupsentry"</SPAN +>, when set to + <SPAN +CLASS="QUOTE" +>"on"</SPAN +>, requires that all bugs have an associated + groupmask when submitted. This parameter is made for those + installations where product isolation is a necessity. + </P +><P +> Set "usebuggroupsentry" to "on" if you absolutely need to + restrict access to bugs from the moment they are submitted + through resolution. 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. @@ -137,6 +182,24 @@ TARGET="_top" ></LI ><LI ><P +> You run into an interesting problem when Bugzilla reaches a + high level of continuous activity. MySQL supports only + table-level write locking. What this means is that if + someone needs to make a change to a bug, they will lock the + entire table until the operation is complete. Locking for + write also blocks reads until the write is complete. The + <SPAN +CLASS="QUOTE" +>"shadowdb"</SPAN +> parameter was designed to get around + this limitation. While only a single user is allowed to + write to a table at a time, reads can continue unimpeded on + a read-only shadow copy of the database. Although your + database size will double, a shadow database can cause an + enormous performance improvement when implemented on + extremely high-traffic Bugzilla databases. + </P +><P > Set "shadowdb" to "bug_shadowdb" if you will be running a *very* large installation of Bugzilla. The shadow database enables many simultaneous users to read and write to the @@ -163,9 +226,13 @@ ALIGN="LEFT" VALIGN="TOP" ><P > Enabling "shadowdb" can adversely affect the stability - of your installation of Bugzilla. You may frequently - need to manually synchronize your databases, or schedule - nightly syncs via "cron" + of your installation of Bugzilla. You should regularly + check that your database is in sync. It is often + advisable to force a shadow database sync nightly via + <SPAN +CLASS="QUOTE" +>"cron"</SPAN +>. </P ></TD ></TR @@ -177,7 +244,13 @@ VALIGN="TOP" > to use it, and have repeatedly run into the problem it was designed to solve -- very long wait times while attempting to commit - a change to the database. + a change to the database. Mozilla.org began needing + <SPAN +CLASS="QUOTE" +>"shadowdb"</SPAN +> when they reached around 40,000 + Bugzilla users with several hundred Bugzilla bug changes and + comments per day. </P ><P > If you use the "shadowdb" option, it is only natural that @@ -188,6 +261,40 @@ VALIGN="TOP" ></LI ><LI ><P +><SPAN +CLASS="QUOTE" +>"headerhtml"</SPAN +>, <SPAN +CLASS="QUOTE" +>"footerhtml"</SPAN +>, + <SPAN +CLASS="QUOTE" +>"errorhtml"</SPAN +>, <SPAN +CLASS="QUOTE" +>"bannerhtml"</SPAN +>, and + <SPAN +CLASS="QUOTE" +>"blurbhtml"</SPAN +> are all templates which control + display of headers, footers, errors, banners, and additional + data. We could go into some detail regarding the usage of + these, but it is really best just to monkey around with them + a bit to see what they do. I strongly recommend you copy + your <TT +CLASS="FILENAME" +>data/params</TT +> file somewhere safe + before playing with these values, though. If they are + changed dramatically, it may make it impossible for you to + display Bugzilla pages to fix the problem until you have + restored your <TT +CLASS="FILENAME" +>data/params</TT +> file.</P +><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", @@ -216,10 +323,11 @@ VALIGN="TOP" > 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 settings at - the defaults initially. +> any other code on the page, + except the CONTENT-TYPE header sent by the Bugzilla + engine. 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 ></TD ></TR @@ -230,6 +338,14 @@ VALIGN="TOP" ></LI ><LI ><P +><SPAN +CLASS="QUOTE" +>"passwordmail"</SPAN +> is rather simple. Every + time a user creates an account, the text of this parameter + is read as the text to send to the new user along with their + password message.</P +><P > Add any text you wish to the "passwordmail" parameter box. For instance, many people choose to use this box to give a quick training blurb about how to use Bugzilla at your site. @@ -237,19 +353,48 @@ VALIGN="TOP" ></LI ><LI ><P -> 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 +><SPAN +CLASS="QUOTE" +>"useqacontact"</SPAN +> allows you to define an + email address for each component, in addition to that of the + default owner, who will be sent carbon copies of incoming + bugs. The critical difference between a QA Contact and an + Owner is that the QA Contact follows the component. If you + reassign a bug from component A to component B, the QA + Contact for that bug will change with the reassignment, + regardless of owner.</P +><P +><SPAN +CLASS="QUOTE" +>"usestatuswhiteboard"</SPAN +> defines whether you + wish to have a free-form, overwritable field associated with + each bug. The advantage of the Status Whiteboard is that it + can be deleted or modified with ease, and provides an + easily-searchable field for indexing some bugs that have + some trait in common. Many people will put <SPAN +CLASS="QUOTE" +>"help + wanted"</SPAN +>, <SPAN +CLASS="QUOTE" +>"stalled"</SPAN +>, or <SPAN +CLASS="QUOTE" +>"waiting + on reply from somebody"</SPAN +> messages into the Status + Whiteboard field so those who peruse the bugs are aware of + their status even more than that which can be indicated by + the Resolution fields.</P ><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 Quality Assurance and/or Release Engineering team, but they may not be needed - for smaller installations. + for many smaller installations. </P ></LI ><LI @@ -259,14 +404,26 @@ VALIGN="TOP" 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 installation instructions, or set this - value to "0". + value to "0" (never whine). </P ></LI ><LI ><P +><SPAN +CLASS="QUOTE" +>"commenton"</SPAN +> fields allow you to dictate + what changes can pass without comment, and which must have a + comment from the person who changed them. Often, + administrators will allow users to add themselves to the CC + list, accept bugs, or change the Status Whiteboard without + adding a comment as to their reasons for the change, yet + require that most other changes come with an + explanation.</P +><P > Set the "commenton" options according to your site policy. It is a wise idea to require comments when users resolve, - reassign, or reopen bugs. + reassign, or reopen bugs at the very least. <DIV CLASS="NOTE" ><P @@ -303,11 +460,38 @@ VALIGN="TOP" ></LI ><LI ><P -> Set "supportwatchers" to "On". This feature is helpful for - team leads to monitor progress in their respective areas, - and can offer many other benefits, such as allowing a - developer to pick up a former engineer's bugs without - requiring her to change all the information in the bug. +>The <SPAN +CLASS="QUOTE" +>"supportwatchers"</SPAN +> option can be an + exceptionally powerful tool in the hands of a power Bugzilla + user. By enabling this option, you allow users to receive + email updates whenever other users receive email updates. + This is, of course, subject to the groupset restrictions on + the bug; if the <SPAN +CLASS="QUOTE" +>"watcher"</SPAN +> would not normally be + allowed to view a bug, the watcher cannot get around the + system by setting herself up to watch the bugs of someone + with bugs outside her priveleges. She would still only + receive email updates for those bugs she could normally + view.</P +><P +>For Bugzilla sites which require strong inter-Product + security to prevent snooping, watchers are not a good + idea.</P +><P +> However, for most sites you should set + <SPAN +CLASS="QUOTE" +>"supportwatchers"</SPAN +> to "On". This feature is + helpful for team leads to monitor progress in their + respective areas, and can offer many other benefits, such as + allowing a developer to pick up a former engineer's bugs + without requiring her to change all the information in the + bug. </P ></LI ></OL diff --git a/docs/html/programadmin.html b/docs/html/programadmin.html index 2ebb4e126..d8409c743 100644 --- a/docs/html/programadmin.html +++ b/docs/html/programadmin.html @@ -232,7 +232,7 @@ NAME="COMPONENTS" <DIV CLASS="EXAMPLE" ><A -NAME="AEN1279" +NAME="AEN1413" ></A ><P ><B @@ -241,7 +241,7 @@ NAME="AEN1279" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1281" +NAME="AEN1415" ></A ><P ></P @@ -387,7 +387,7 @@ NAME="VERSIONS" <DIV CLASS="EXAMPLE" ><A -NAME="AEN1308" +NAME="AEN1442" ></A ><P ><B @@ -396,7 +396,7 @@ NAME="AEN1308" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1310" +NAME="AEN1444" ></A ><P ></P @@ -418,7 +418,7 @@ NAME="AEN1310" <DIV CLASS="EXAMPLE" ><A -NAME="AEN1312" +NAME="AEN1446" ></A ><P ><B @@ -427,7 +427,7 @@ NAME="AEN1312" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1314" +NAME="AEN1448" ></A ><P ></P @@ -564,7 +564,7 @@ TYPE="1" ><DIV CLASS="EXAMPLE" ><A -NAME="AEN1340" +NAME="AEN1474" ></A ><P ><B @@ -573,7 +573,7 @@ NAME="AEN1340" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1342" +NAME="AEN1476" ></A ><P ></P @@ -787,7 +787,7 @@ NAME="GROUPS" <DIV CLASS="EXAMPLE" ><A -NAME="AEN1376" +NAME="AEN1510" ></A ><P ><B @@ -796,7 +796,7 @@ NAME="AEN1376" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1378" +NAME="AEN1512" ></A ><P ></P @@ -913,7 +913,7 @@ TYPE="1" <DIV CLASS="EXAMPLE" ><A -NAME="AEN1393" +NAME="AEN1527" ></A ><P ><B @@ -922,7 +922,7 @@ NAME="AEN1393" ><DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN1395" +NAME="AEN1529" ></A ><P ></P diff --git a/docs/html/quicksearch.html b/docs/html/quicksearch.html index e4ff6528d..68596a202 100644 --- a/docs/html/quicksearch.html +++ b/docs/html/quicksearch.html @@ -71,7 +71,7 @@ CLASS="SECTION" CLASS="SECTION" ><A NAME="QUICKSEARCH" ->D.3. The Quicksearch Utility</A +>D.4. The Quicksearch Utility</A ></H1 ><P > Quicksearch is a new, experimental feature of the 2.12 release. diff --git a/docs/html/rewrite.html b/docs/html/rewrite.html new file mode 100644 index 000000000..053474069 --- /dev/null +++ b/docs/html/rewrite.html @@ -0,0 +1,191 @@ +<HTML +><HEAD +><TITLE +>Apache mod_rewrite magic</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.61 +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide" +HREF="index.html"><LINK +REL="UP" +TITLE="Useful Patches and Utilities for Bugzilla" +HREF="patches.html"><LINK +REL="PREVIOUS" +TITLE="Useful Patches and Utilities for Bugzilla" +HREF="patches.html"><LINK +REL="NEXT" +TITLE="The setperl.csh Utility" +HREF="setperl.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="patches.html" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Appendix D. Useful Patches and Utilities for Bugzilla</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="setperl.html" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="SECTION" +><H1 +CLASS="SECTION" +><A +NAME="REWRITE" +>D.1. Apache <TT +CLASS="FILENAME" +>mod_rewrite</TT +> magic</A +></H1 +><P +>Apache's <TT +CLASS="FILENAME" +>mod_rewrite</TT +> module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</P +><P +></P +><OL +TYPE="1" +><LI +><P +> Make it so if someone types + <TT +CLASS="COMPUTEROUTPUT" +>http://www.foo.com/12345</TT +>, + Bugzilla spits back + http://www.foo.com/show_bug.cgi?id=12345. Try setting up + your VirtualHost section for Bugzilla with a rule like + this:</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +><VirtualHost 12.34.56.78> +RewriteEngine On +RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R] +</VirtualHost> + </PRE +></FONT +></TD +></TR +></TABLE +></LI +><LI +><P +>There are many, many more things you can do with + mod_rewrite. As time goes on, I will include many more in + the Guide. For now, though, please refer to the mod_rewrite + documentation at <A +HREF="http://www.apache.org" +TARGET="_top" +>http://www.apache.org</A +></P +></LI +></OL +></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="patches.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="setperl.html" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Useful Patches and Utilities for Bugzilla</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="patches.html" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>The setperl.csh Utility</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/rhbugzilla.html b/docs/html/rhbugzilla.html index 38d67d26d..c0412cced 100644 --- a/docs/html/rhbugzilla.html +++ b/docs/html/rhbugzilla.html @@ -10,14 +10,14 @@ REL="HOME" TITLE="The Bugzilla Guide" HREF="index.html"><LINK REL="UP" -TITLE="Bugzilla Variants" +TITLE="Bugzilla Variants and Competitors" HREF="variants.html"><LINK REL="PREVIOUS" -TITLE="Bugzilla Variants" +TITLE="Bugzilla Variants and Competitors" HREF="variants.html"><LINK REL="NEXT" -TITLE="Useful Patches and Utilities for Bugzilla" -HREF="patches.html"></HEAD +TITLE="Loki Bugzilla (Fenris)" +HREF="variant_fenris.html"></HEAD ><BODY CLASS="SECTION" BGCOLOR="#FFFFFF" @@ -51,13 +51,13 @@ HREF="variants.html" WIDTH="80%" ALIGN="center" VALIGN="bottom" ->Chapter 7. Bugzilla Variants</TD +>Chapter 7. Bugzilla Variants and Competitors</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="patches.html" +HREF="variant_fenris.html" >Next</A ></TD ></TR @@ -74,65 +74,20 @@ 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="AEN2143" -></A -><BLOCKQUOTE -CLASS="BLOCKQUOTE" -><P -CLASS="LITERALLAYOUT" -> Hello. I apologize that I am getting back to you so late. It has been difficult to keep<br> -up with email this past week. I have checked out your updated documentation and I will<br> -have to say very good work. A few notes and additions as follows.<br> -<br> -(ed: from the FAQ)<br> ->For the record, we are not using any template type implementation for the cosmetic changes <br> ->maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have <br> ->gotten a little carried away with it but the corporate types asked for a more standardized <br> ->interface to match up with other projects relating to Red Hat web sites. A lot of other web <br> ->based internal tools I am working on also look like Bugzilla. <br> -<br> -<br> -This should probably be changed since we are now in fact using Text::Template for most<br> -of the html rendering. You actually state this later in your numbered list.<br> -<br> -Also number 6 contradicts number 8 where number 6 would be the most up to date status<br> -on the Oracle port.<br> -<br> -Additional Information:<br> ------------------------------<br> -1. Comments are now stored in varchar fields of 4k in size each. If the comment is more<br> -than 4k it is broken up into chunks and given a sort number so each comment can be re<br> -assembled in the correct order. This was done because originally I was storing the comments<br> -in a long datatype which unfortunately cannot be indexed or joined with another table. This<br> -cause the search of text within the long description to be disabled for a long time. That<br> -is now working and is nto showing any noticeble performance hit that I can tell. <br> -<br> -2. Work is being started on internationalizing the Bugzilla source we have to allow our<br> -Japanese customers to enter bug reports into a single bugzilla system. This will probably<br> -be done by using the nvarchar data types supported by Oracle which allows storage of<br> -double byte characters and also the use of the Accept-Language in the http header for <br> -detection by Bugilla of which language to render.<br> -<br> -3. Of course even more cosmetic changes. It is difficult to keep up with the ever <br> -changing faces of www.redhat.com.<br> -<br> -4. Some convenience enhancements in the administration utilities. And more integration<br> -with other internal/external Red Hat web sites.<br> -<br> -I hope this information may prove helpful for your documentation. Please contact<br> -me if you have any more question or I can do anything else.<br> -<br> -Regards<br> - </P -></BLOCKQUOTE -> +> Red Hat Bugzilla is probably the most popular Bugzilla variant + on the planet. One of the major benefits of Red Hat Bugzilla is + the ability to work with Oracle, MySQL, and PostGreSQL databases + serving as the back-end, instead of just MySQL. Dave Lawrence + has worked very hard to keep Red Hat Bugzilla up-to-date, and + many people prefer the snappier-looking page layout of Red Hat + Bugzilla to the default Mozilla-standard formatting. </P +><P +>URL: <A +HREF="http://bugzilla.redhat.com/bugzilla/" +TARGET="_top" +>http://bugzilla.redhat.com/bugzilla/</A +></P ></DIV ><DIV CLASS="NAVFOOTER" @@ -165,7 +120,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="patches.html" +HREF="variant_fenris.html" >Next</A ></TD ></TR @@ -174,7 +129,7 @@ HREF="patches.html" WIDTH="33%" ALIGN="left" VALIGN="top" ->Bugzilla Variants</TD +>Bugzilla Variants and Competitors</TD ><TD WIDTH="34%" ALIGN="center" @@ -187,7 +142,7 @@ HREF="variants.html" WIDTH="33%" ALIGN="right" VALIGN="top" ->Useful Patches and Utilities for Bugzilla</TD +>Loki Bugzilla (Fenris)</TD ></TR ></TABLE ></DIV diff --git a/docs/html/scm.html b/docs/html/scm.html index 3aa515b35..c96598b81 100644 --- a/docs/html/scm.html +++ b/docs/html/scm.html @@ -16,7 +16,7 @@ REL="PREVIOUS" TITLE="CVS" HREF="cvs.html"><LINK REL="NEXT" -TITLE="Tinderbox" +TITLE="Tinderbox/Tinderbox2" HREF="tinderbox.html"></HEAD ><BODY CLASS="SECTION" @@ -74,36 +74,28 @@ NAME="SCM" >5.3. Perforce SCM</A ></H1 ><P -> You can find the project page for Bugzilla and Teamtrack Perforce integration at: - <A +> You can find the project page for Bugzilla and Teamtrack + Perforce integration (p4dti) at: <A 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 +> http://www.ravenbrook.com/project/p4dti</A +> . <SPAN +CLASS="QUOTE" +>"p4dti"</SPAN +> 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 +> 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. +> Integration of Perforce with Bugzilla, once patches are applied, + is seamless. Perforce replication information will appear below + the comments of each bug. Be certain you have a matching set of + patches for the Bugzilla version you are installing. p4dti is + designed to support multiple defect trackers, and maintains its + own documentation for it. Please consult the pages linked above + for further information. </P ></DIV ><DIV @@ -159,7 +151,7 @@ HREF="integration.html" WIDTH="33%" ALIGN="right" VALIGN="top" ->Tinderbox</TD +>Tinderbox/Tinderbox2</TD ></TR ></TABLE ></DIV diff --git a/docs/html/setperl.html b/docs/html/setperl.html index 76b0fdf91..b863a204b 100644 --- a/docs/html/setperl.html +++ b/docs/html/setperl.html @@ -13,8 +13,8 @@ REL="UP" TITLE="Useful Patches and Utilities for Bugzilla" HREF="patches.html"><LINK REL="PREVIOUS" -TITLE="Useful Patches and Utilities for Bugzilla" -HREF="patches.html"><LINK +TITLE="Apache mod_rewrite magic" +HREF="rewrite.html"><LINK REL="NEXT" TITLE="Command-line Bugzilla Queries" HREF="cmdline.html"></HEAD @@ -44,7 +44,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="patches.html" +HREF="rewrite.html" >Prev</A ></TD ><TD @@ -71,7 +71,7 @@ CLASS="SECTION" CLASS="SECTION" ><A NAME="SETPERL" ->D.1. The setperl.csh Utility</A +>D.2. The setperl.csh Utility</A ></H1 ><P > You can use the "setperl.csh" utility to quickly and @@ -216,7 +216,7 @@ CLASS="COMMAND" <DIV CLASS="EXAMPLE" ><A -NAME="AEN2193" +NAME="AEN2360" ></A ><P ><B @@ -258,7 +258,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="patches.html" +HREF="rewrite.html" >Prev</A ></TD ><TD @@ -283,7 +283,10 @@ HREF="cmdline.html" WIDTH="33%" ALIGN="left" VALIGN="top" ->Useful Patches and Utilities for Bugzilla</TD +>Apache <TT +CLASS="FILENAME" +>mod_rewrite</TT +> magic</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/stepbystep.html b/docs/html/stepbystep.html index 4cbac778a..60e0ec84e 100644 --- a/docs/html/stepbystep.html +++ b/docs/html/stepbystep.html @@ -78,7 +78,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN478" +NAME="AEN486" >3.2.1. Introduction</A ></H2 ><P @@ -109,7 +109,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN484" +NAME="AEN492" >3.2.2. Installing the Prerequisites</A ></H2 ><DIV @@ -248,6 +248,111 @@ VALIGN="TOP" ></TABLE ></DIV > + <DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>Linux-Mandrake 8.0, the author's test system, includes + every required and optional library for Bugzilla. The + easiest way to install them is by using the + <TT +CLASS="FILENAME" +>urpmi</TT +> utility. If you follow these + commands, you should have everything you need for + Bugzilla, and <TT +CLASS="FILENAME" +>checksetup.pl</TT +> should + not complain about any missing libraries. You may already + have some of these installed.</P +><P +></P +><TABLE +BORDER="0" +><TBODY +><TR +><TD +><TT +CLASS="PROMPT" +>bash#</TT +><B +CLASS="COMMAND" +> urpmi + perl-mysql</B +></TD +></TR +><TR +><TD +><TT +CLASS="PROMPT" +>bash#</TT +><B +CLASS="COMMAND" +> urpmi + perl-chart</B +></TD +></TR +><TR +><TD +><TT +CLASS="PROMPT" +>bash#</TT +><B +CLASS="COMMAND" +> urpmi + perl-gd</B +></TD +></TR +><TR +><TD +><TT +CLASS="PROMPT" +>bash#</TT +><B +CLASS="COMMAND" +> urpmi + perl-MailTools</B +> (for Bugzilla email + integration)</TD +></TR +><TR +><TD +><TT +CLASS="PROMPT" +>bash#</TT +><B +CLASS="COMMAND" +> urpmi + apache-modules</B +></TD +></TR +></TBODY +></TABLE +><P +></P +></TD +></TR +></TABLE +></DIV +> </P ></DIV @@ -260,26 +365,79 @@ NAME="INSTALL-MYSQL" >3.2.3. Installing MySQL Database</A ></H2 ><P -> Visit MySQL homepage at http://www.mysql.com/ and grab the - latest stable release of the server. Both binaries and source - are available and which you get shouldn't matter. Be aware - that many of the binary versions of MySQL store their data - files in /var which on many installations (particularly common - with linux installations) is part of a smaller root partition. - If you decide to build from sources you can easily set the - dataDir as an option to configure. +> Visit MySQL homepage at <A +HREF="http://www.mysql.com" +TARGET="_top" +>www.mysql.com</A +> and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <TT +CLASS="FILENAME" +>/var</TT +> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <TT +CLASS="FILENAME" +>configure</TT +>. </P ><P -> If you've installed from source or non-package (RPM, deb, - etc.) binaries you'll want to make sure to add mysqld to your +> If you install from source or non-package (RPM, deb, etc.) + binaries you need to add + <I +CLASS="FIRSTTERM" +>mysqld</I +> to your init scripts so the server daemon will come back up whenever - your machine reboots. You also may want to edit those init - scripts, to make sure that mysqld will accept large packets. - By default, mysqld is set up to only accept packets up to 64K - long. This limits the size of attachments you may put on - bugs. If you add something like "-O max_allowed_packet=1M" to - the command that starts mysqld (or safe_mysqld), then you will - be able to have attachments up to about 1 megabyte. + your machine reboots. Further discussion of UNIX init + sequences are beyond the scope of this guide. + <DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>You should have your init script start + <I +CLASS="GLOSSTERM" +>mysqld</I +> with the ability to accept + large packets. By default, <TT +CLASS="FILENAME" +>mysqld</TT +> + only accepts packets up to 64K long. This limits the size + of attachments you may put on bugs. If you add <TT +CLASS="OPTION" +>-O + max_allowed_packet=1M</TT +> to the command that starts + <TT +CLASS="FILENAME" +>mysqld</TT +> (or + <TT +CLASS="FILENAME" +>safe_mysqld</TT +>), then you will be able + to have attachments up to about 1 megabyte.</P +></TD +></TR +></TABLE +></DIV +> + </P ><DIV CLASS="NOTE" @@ -303,9 +461,12 @@ ALIGN="LEFT" VALIGN="TOP" ><P > If you plan on running Bugzilla and MySQL on the same - machine, consider using the "--skip-networking" option in - the init script. This enhances security by preventing - network access to MySQL. + machine, consider using the <TT +CLASS="OPTION" +>--skip-networking</TT +> + option in the init script. This enhances security by + preventing network access to MySQL. </P ></TD ></TR @@ -406,9 +567,19 @@ ALIGN="LEFT" VALIGN="TOP" ><P > You can skip the following Perl module installation steps by - installing "Bundle::Bugzilla" from CPAN, which includes - them. All Perl module installation steps require you have an - active Internet connection. If you wish to use + installing <SPAN +CLASS="PRODUCTNAME" +>Bundle::Bugzilla</SPAN +> from + <A +HREF="glossary.html#GLOSS_CPAN" +><I +CLASS="GLOSSTERM" +>CPAN</I +></A +>, which + includes them. All Perl module installation steps require + you have an active Internet connection. If you wish to use Bundle::Bugzilla, however, you must be using the latest version of Perl (at this writing, version 5.6.1) </P @@ -442,7 +613,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN537" +NAME="AEN579" >3.2.5. DBI Perl Module</A ></H2 ><P @@ -456,7 +627,10 @@ NAME="AEN537" > Like almost all Perl modules DBI can be found on the Comprehensive Perl Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a real tendency to bog down, so please use mirrors. The current location - at the time of this writing (02/17/99) can be found in Appendix A. + at the time of this writing can be found in <A +HREF="downloadlinks.html" +>Appendix B</A +>. </P ><P > Quality, general Perl module installation instructions can be found on @@ -468,7 +642,7 @@ NAME="AEN537" <DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN543" +NAME="AEN586" ></A ><P ></P @@ -522,7 +696,7 @@ VALIGN="TOP" <DIV CLASS="INFORMALEXAMPLE" ><A -NAME="AEN550" +NAME="AEN593" ></A ><P ></P @@ -615,7 +789,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN574" +NAME="AEN617" >3.2.6. Data::Dumper Perl Module</A ></H2 ><P @@ -625,9 +799,14 @@ NAME="AEN574" hurt anything. </P ><P -> Data::Dumper is used by the MySQL-related Perl modules. It can be - found on CPAN (link in Appendix A) and can be installed by following - the same four step make sequence used for the DBI module. +> Data::Dumper is used by the MySQL-related Perl modules. It + can be found on CPAN (see <A +HREF="downloadlinks.html" +>Appendix B</A +>) and + can be + installed by following the same four step make sequence used + for the DBI module. </P ></DIV ><DIV @@ -635,7 +814,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN578" +NAME="AEN622" >3.2.7. MySQL related Perl Module Collection</A ></H2 ><P @@ -681,18 +860,21 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN587" +NAME="AEN631" >3.2.8. TimeDate Perl Module Collection</A ></H2 ><P -> Many of the more common date/time/calendar related Perl modules have - been grouped into a bundle similar to the MySQL modules bundle. This - bundle is stored on the CPAN under the name TimeDate. A link - link may be found in Appendix B, Software Download Links. - The component module we're - most interested in is the Date::Format module, but installing all of them - is probably a good idea anyway. The standard Perl module installation - instructions should work perfectly for this simple package. +> Many of the more common date/time/calendar related Perl + modules have been grouped into a bundle similar to the MySQL + modules bundle. This bundle is stored on the CPAN under the + name TimeDate (see link: <A +HREF="downloadlinks.html" +>Appendix B</A +>). The + component module we're most interested in is the Date::Format + module, but installing all of them is probably a good idea + anyway. The standard Perl module installation instructions + should work perfectly for this simple package. </P ></DIV ><DIV @@ -700,21 +882,26 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN590" +NAME="AEN635" >3.2.9. GD Perl Module (1.8.3)</A ></H2 ><P -> The GD library was written by Thomas Boutell a long while ago to - programatically generate images in C. Since then it's become almost a - defacto standard for programatic image construction. The Perl bindings - to it found in the GD library are used on a million web pages to generate - graphs on the fly. That's what bugzilla will be using it for so you'd - better install it if you want any of the graphing to work. +> The GD library was written by Thomas Boutell a long while + ago to programatically generate images in C. Since then it's + become the defacto standard for programatic image + construction. The Perl bindings to it found in the GD library + are used on millions of web pages to generate graphs on the + fly. That's what bugzilla will be using it for so you must + install it if you want any of the graphing to work. </P ><P -> Actually bugzilla uses the Graph module which relies on GD itself, - but isn't that always the way with OOP. At any rate, you can find the - GD library on CPAN (link in Appendix B, Software Download Links). +> Actually bugzilla uses the Graph module which relies on GD + itself. Isn't that always the way with object-oriented + programming? At any rate, you can find the GD library on CPAN + in <A +HREF="downloadlinks.html" +>Appendix B</A +>. </P ><DIV CLASS="NOTE" @@ -737,10 +924,19 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> The Perl GD library requires some other libraries that may or may not be - installed on your system, including "libpng" and "libgd". The full requirements - are listed in the Perl GD library README. Just realize that if compiling GD fails, - it's probably because you're missing a required library. +> The Perl GD library requires some other libraries that may + or may not be installed on your system, including + <TT +CLASS="CLASSNAME" +>libpng</TT +> and + <TT +CLASS="CLASSNAME" +>libgd</TT +>. The full requirements are + listed in the Perl GD library README. Just realize that if + compiling GD fails, it's probably because you're missing a + required library. </P ></TD ></TR @@ -752,19 +948,20 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN596" +NAME="AEN644" >3.2.10. Chart::Base Perl Module (0.99c)</A ></H2 ><P > The Chart module provides bugzilla with on-the-fly charting - abilities. It can be installed in the usual fashion after it has been - fetched from CPAN where it is found as the Chart-x.x... tarball in a - directory to be listed in Appendix B, "Software Download Links". - Note that as with the GD perl - module, only the version listed above, or newer, will work. - Earlier - versions used GIF's, which are no longer supported by the latest - versions of GD. + abilities. It can be installed in the usual fashion after it + has been fetched from CPAN where it is found as the + Chart-x.x... tarball, linked in <A +HREF="downloadlinks.html" +>Appendix B</A +>. Note that + as with the GD perl module, only the version listed above, or + newer, will work. Earlier versions used GIF's, which are no + longer supported by the latest versions of GD. </P ></DIV ><DIV @@ -772,13 +969,15 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN599" +NAME="AEN648" >3.2.11. DB_File Perl Module</A ></H2 ><P -> DB_File is a module which allows Perl programs to make use of the facilities provided by - Berkeley DB version 1.x. This module is required by collectstats.pl which is used for - bug charting. If you plan to make use of bug charting, you must install this module. +> DB_File is a module which allows Perl programs to make use + of the facilities provided by Berkeley DB version 1.x. This + module is required by collectstats.pl which is used for bug + charting. If you plan to make use of bug charting, you must + install this module. </P ></DIV ><DIV @@ -786,40 +985,124 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN602" +NAME="AEN651" >3.2.12. HTTP Server</A ></H2 ><P -> You have a freedom of choice here - Apache, Netscape or any other - server on UNIX would do. You can easily run the web server on a different - machine than MySQL, but need to adjust the MySQL "bugs" user permissions - accordingly. +> You have a freedom of choice here - Apache, Netscape or any + other server on UNIX would do. You can easily run the web + server on a different machine than MySQL, but need to adjust + the MySQL <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> user permissions accordingly. + <DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>I strongly recommend Apache as the web server to use. + The Bugzilla Guide installation instructions, in general, + assume you are using Apache. As more users use different + webservers and send me information on the peculiarities of + installing using their favorite webserver, I will provide + notes for them.</P +></TD +></TR +></TABLE +></DIV +> </P ><P -> You'll want to make sure that your web server will run any file - with the .cgi extension as a cgi and not just display it. If you're using - apache that means uncommenting the following line in the srm.conf file: - <TT -CLASS="COMPUTEROUTPUT" ->AddHandler cgi-script .cgi</TT +> You'll want to make sure that your web server will run any + file with the .cgi extension as a cgi and not just display it. + If you're using apache that means uncommenting the following + line in the srm.conf file: + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>AddHandler cgi-script .cgi + </PRE +></FONT +></TD +></TR +></TABLE > </P ><P -> With apache you'll also want to make sure that within the access.conf - file the line: - <TT -CLASS="COMPUTEROUTPUT" -> Options ExecCGI - </TT +> With apache you'll also want to make sure that within the + access.conf file the line: + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>Options ExecCGI</PRE +></FONT +></TD +></TR +></TABLE > - is in the stanza that covers the directories you intend to put the bugzilla - .html and .cgi files into. + is in the stanza that covers the directories into which + you intend to put the bugzilla .html and .cgi files. </P +><DIV +CLASS="NOTE" ><P -> If you are using a newer version of Apache, both of the above lines will be - (or will need to be) in the httpd.conf file, rather than srm.conf or - access.conf. +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="../images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +> Users of newer versions of Apache will generally find both + of the above lines will be in the httpd.conf file, rather + than srm.conf or access.conf. </P +></TD +></TR +></TABLE +></DIV ><DIV CLASS="WARNING" ><P @@ -841,24 +1124,27 @@ ALT="Warning"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> There are two critical directories and a file that should not be a served by - the HTTP server. These are the <SPAN +> There are important files and directories that should not + be a served by the HTTP server. These are most files in the + <SPAN CLASS="QUOTE" >"data"</SPAN > and <SPAN CLASS="QUOTE" >"shadow"</SPAN -> - directories and the - <SPAN +> directories + and the <SPAN CLASS="QUOTE" >"localconfig"</SPAN -> file. You should configure your HTTP server to not serve - content from these files. Failure to do so will expose critical passwords - and other data. Please see <A +> file. You should + configure your HTTP server to not serve content from these + files. Failure to do so will expose critical passwords and + other data. Please see <A HREF="geninstall.html#HTACCESS" >.htaccess files and security</A -> for details. +> for details + on how to do this for Apache. I appreciate notes on how to + get this same functionality using other webservers. </P ></TD ></TR @@ -870,22 +1156,25 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN616" +NAME="AEN669" >3.2.13. Installing the Bugzilla Files</A ></H2 ><P -> You should untar the Bugzilla files into a directory that you're - willing to make writable by the default web server user (probably - <SPAN +> You should untar the Bugzilla files into a directory that + you're willing to make writable by the default web server user + (probably <SPAN CLASS="QUOTE" >"nobody"</SPAN ->). You may decide to put the files off of the main web space - for your web server or perhaps off of /usr/local with a symbolic link - in the web space that points to the bugzilla directory. At any rate, - just dump all the files in the same place (optionally omitting the CVS - directories if they were accidentally tarred up with the rest of Bugzilla) - and make sure you can access the files in that directory through your - web server. +>). You may decide to put the + files off of the main web space for your web server or perhaps + off of <TT +CLASS="FILENAME" +>/usr/local</TT +> with a symbolic link in + the web space that points to the Bugzilla directory. At any + rate, just dump all the files in the same place, and make sure + you can access the files in that directory through your web + server. </P ><DIV CLASS="TIP" @@ -909,55 +1198,79 @@ ALIGN="LEFT" VALIGN="TOP" ><P > If you symlink the bugzilla directory into your Apache's - HTML heirarchy, you may receive "Forbidden" errors unless you - add the "FollowSymLinks" directive to the <Directory> entry - for the HTML root. + HTML heirarchy, you may receive + <SPAN +CLASS="ERRORNAME" +>Forbidden</SPAN +> errors unless you add the + <SPAN +CLASS="QUOTE" +>"FollowSymLinks"</SPAN +> directive to the + <Directory> entry for the HTML root. </P ></TD ></TR ></TABLE ></DIV ><P -> Once all the files are in a web accessible directory, make that - directory writable by your webserver's user (which may require just - making it world writable). This is a temporary step until you run - the post-install <SPAN -CLASS="QUOTE" ->"checksetup.pl"</SPAN +> Once all the files are in a web accessible directory, make + that directory writable by your webserver's user. This is a + temporary step until you run the post-install + <TT +CLASS="FILENAME" +>checksetup.pl</TT > script, which locks down your - installation. - </P + installation. + </P ><P -> Lastly, you'll need to set up a symbolic link to /usr/bonsaitools/bin/perl - for the correct location of your perl executable (probably /usr/bin/perl). - Otherwise you must hack all the .cgi files to change where they look - for perl. To make future upgrades easier, you should use the symlink - approach. - <DIV +> Lastly, you'll need to set up a symbolic link to + <TT +CLASS="FILENAME" +>/usr/bonsaitools/bin/perl</TT +> for the correct + location of your perl executable (probably + <TT +CLASS="FILENAME" +>/usr/bin/perl</TT +>). Otherwise you must hack + all the .cgi files to change where they look for perl, or use + <A +HREF="setperl.html" +>The setperl.csh Utility</A +>, found in + <A +HREF="patches.html" +>Useful Patches and Utilities for Bugzilla</A +>. I suggest using the symlink + approach for future release compatability. + <DIV CLASS="EXAMPLE" ><A -NAME="AEN625" +NAME="AEN685" ></A ><P ><B >Example 3-1. Setting up bonsaitools symlink</B ></P ><P -> Here's how you set up the Perl symlink on Linux to make Bugzilla work. - Your mileage may vary; if you are running on Solaris, you probably need to subsitute - <SPAN +> Here's how you set up the Perl symlink on Linux to make + Bugzilla work. Your mileage may vary. For some UNIX + operating systems, you probably need to subsitute + <SPAN CLASS="QUOTE" >"/usr/local/bin/perl"</SPAN -> for <SPAN +> for + <SPAN CLASS="QUOTE" >"/usr/bin/perl"</SPAN -> - below; if on certain other UNIX systems, - Perl may live in weird places like <SPAN +> below; if on certain other + UNIX systems, Perl may live in weird places like + <SPAN CLASS="QUOTE" >"/opt/perl"</SPAN >. As root, run these commands: - <TABLE + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -967,19 +1280,19 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" ->bash# mkdir /usr/bonsaitools -bash# mkdir /usr/bonsaitools/bin +>bash# mkdir /usr/bonsaitools +bash# mkdir /usr/bonsaitools/bin bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl - </PRE + </PRE ></FONT ></TD ></TR ></TABLE > - </P + </P ></DIV > - <DIV + <DIV CLASS="TIP" ><P ></P @@ -1000,7 +1313,7 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> If you don't have root access to set this symlink up, +> If you don't have root access to set this symlink up, check out the <A HREF="setperl.html" @@ -1008,9 +1321,8 @@ HREF="setperl.html" >, listed in <A HREF="patches.html" >Useful Patches and Utilities for Bugzilla</A ->. - It will change the path to perl in all your Bugzilla files for you. - </P +>. It will change the path to perl in all your Bugzilla files for you. + </P ></TD ></TR ></TABLE @@ -1023,7 +1335,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN636" +NAME="AEN696" >3.2.14. Setting Up the MySQL Database</A ></H2 ><P @@ -1032,10 +1344,14 @@ NAME="AEN636" quality bug tracker. </P ><P -> First, you'll want to fix MySQL permissions to allow access from - Bugzilla. For the purpose of this Installation section, the Bugzilla username - will be "bugs", and will have minimal permissions. - +> First, you'll want to fix MySQL permissions to allow access + from Bugzilla. For the purpose of this Installation section, + the Bugzilla username will be <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +>, and will + have minimal permissions. + <DIV CLASS="WARNING" ><P @@ -1072,242 +1388,281 @@ CLASS="COMMAND" ></TABLE ></DIV > - </P + </P ><P -> Give the MySQL root user a password. MySQL passwords are - limited to 16 characters. - <P +> Give the MySQL root user a password. MySQL passwords are + limited to 16 characters. + <P ></P ><TABLE BORDER="0" ><TBODY ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" >bash#</TT -> - <B +> <B CLASS="COMMAND" ->mysql -u root mysql</B -> - </TT +>mysql + -u root mysql</B +> </TT > - </TD + </TD ></TR ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" >mysql></TT -> - <B +> <B CLASS="COMMAND" -> UPDATE user SET Password=PASSWORD ('new_password') - WHERE user='root'; - </B -> - </TT +> UPDATE user SET Password=PASSWORD ('new_password') + WHERE user='root'; </B +> </TT > - </TD + </TD ></TR ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" >mysql></TT -> - <B +> <B CLASS="COMMAND" ->FLUSH PRIVILEGES;</B -> - </TT +>FLUSH + PRIVILEGES;</B +> </TT > - </TD + </TD ></TR ></TBODY ></TABLE ><P ></P -> - From this point on, if you need to access MySQL as the - MySQL root user, you will need to use "mysql -u root -p" and - enter your new_password. Remember that MySQL user names have - nothing to do with Unix user names (login names). - </P +> From this point on, if you need to access + MySQL as the MySQL root user, you will need to use + <B +CLASS="COMMAND" +>mysql -u root -p</B +> and enter your + new_password. Remember that MySQL user names have nothing to + do with Unix user names (login names). + </P ><P -> Next, we create the "bugs" user, and grant sufficient - permissions for checksetup.pl, which we'll use later, to work - its magic. This also restricts the "bugs" user to operations - within a database called "bugs", and only allows the account - to connect from "localhost". Modify it to reflect your setup - if you will be connecting from another machine or as a different - user. - </P +> Next, we create the <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> user, and grant + sufficient permissions for checksetup.pl, which we'll use + later, to work its magic. This also restricts the + <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> user to operations within a database + called <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +>, and only allows the account to + connect from <SPAN +CLASS="QUOTE" +>"localhost"</SPAN +>. Modify it to reflect + your setup if you will be connecting from another machine or + as a different user. + </P ><P -> Remember to set bugs_password to some unique password. - <P +> Remember to set bugs_password to some unique password. + <P ></P ><TABLE BORDER="0" ><TBODY ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" >mysql></TT > - <B + <B CLASS="COMMAND" >GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, - ALTER,CREATE,DROP,REFERENCES - ON bugs.* TO bugs@localhost - IDENTIFIED BY 'bugs_password';</B + ALTER,CREATE,DROP,REFERENCES + ON bugs.* TO bugs@localhost + IDENTIFIED BY 'bugs_password';</B > - </TT + </TT > - </TD + </TD ></TR ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" -> mysql> - </TT +> mysql> + </TT > - <B + <B CLASS="COMMAND" -> FLUSH PRIVILEGES; - </B +> FLUSH PRIVILEGES; + </B > - </TT + </TT > - </TD + </TD ></TR ></TBODY ></TABLE ><P ></P > - </P + </P ><P -> Next, run the magic checksetup.pl script. (Many thanks to Holger - Schurig <holgerschurig@nikocity.de> for writing this script!) - It will make sure Bugzilla files and directories have reasonable - permissions, set up the "data" directory, and create all the MySQL - tables. - <P +> Next, run the magic checksetup.pl script. (Many thanks to + Holger Schurig <holgerschurig@nikocity.de> for writing + this script!) It will make sure Bugzilla files and directories + have reasonable permissions, set up the + <TT +CLASS="FILENAME" +>data</TT +> directory, and create all the MySQL + tables. + <P ></P ><TABLE BORDER="0" ><TBODY ><TR ><TD -> <TT +> <TT CLASS="COMPUTEROUTPUT" -> <TT +> <TT CLASS="PROMPT" >bash#</TT > - <B + <B CLASS="COMMAND" >./checksetup.pl</B +> </TT > - </TT -> - </TD + </TD ></TR ></TBODY ></TABLE ><P ></P -> - The first time you run it, it will create a file called "localconfig". - </P +> The first time you run it, it will create a + file called <TT +CLASS="FILENAME" +>localconfig</TT +>. + </P ></DIV ><DIV CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN675" ->3.2.15. Tweaking "localconfig"</A +NAME="AEN743" +>3.2.15. Tweaking <TT +CLASS="FILENAME" +>localconfig</TT +></A ></H2 ><P -> This file contains a variety of settings you may need to tweak including - how Bugzilla should connect to the MySQL database. - </P +> This file contains a variety of settings you may need to tweak including + how Bugzilla should connect to the MySQL database. + </P ><P -> The connection settings include: - <P +> The connection settings include: + <P ></P ><OL TYPE="1" ><LI ><P -> server's host: just use "localhost" if the MySQL server is - local - </P +> server's host: just use <SPAN +CLASS="QUOTE" +>"localhost"</SPAN +> if the + MySQL server is local + </P ></LI ><LI ><P -> database name: "bugs" if you're following these directions - </P +> database name: <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> if you're following + these directions + </P ></LI ><LI ><P -> MySQL username: "bugs" if you're following these directions - </P +> MySQL username: <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> if you're following + these directions + </P ></LI ><LI ><P -> Password for the "bugs" MySQL account above - </P +> Password for the <SPAN +CLASS="QUOTE" +>"bugs"</SPAN +> MySQL account above + </P ></LI ></OL > - </P + </P ><P -> You may also install .htaccess files that the Apache webserver will use - to restrict access to Bugzilla data files. See <A +> You should also install .htaccess files that the Apache + webserver will use to restrict access to Bugzilla data files. + See <A HREF="geninstall.html#HTACCESS" >.htaccess files and security</A >. - </P -><P -> Once you are happy with the settings, re-run checksetup.pl. On this - second run, it will create the database and an administrator account - for which you will be prompted to provide information. - </P + </P ><P -> When logged into an administrator account once Bugzilla is running, - if you go to the query page (off of the bugzilla main menu), you'll - find an 'edit parameters' option that is filled with editable treats. - </P +> Once you are happy with the settings, re-run + <TT +CLASS="FILENAME" +>checksetup.pl</TT +>. On this second run, it will + create the database and an administrator account for which + you will be prompted to provide information. + </P ><P -> Should everything work, you should have a nearly empty copy of the bug - tracking setup. - </P +> When logged into an administrator account once Bugzilla is + running, if you go to the query page (off of the Bugzilla main + menu), you'll find an <SPAN +CLASS="QUOTE" +>"edit parameters"</SPAN +> option + that is filled with editable treats. + </P ><P -> The second time around, checksetup.pl will stall if it is on a - filesystem that does not fully support file locking via flock(), such as - NFS mounts. This support is required for Bugzilla to operate safely with - multiple instances. If flock() is not fully supported, it will stall at: - <SPAN -CLASS="ERRORCODE" ->Now regenerating the shadow database for all bugs.</SPAN +> Should everything work, you will have a nearly empty Bugzilla + database and a newly-created <TT +CLASS="FILENAME" +>localconfig</TT > - <DIV + file in your Bugzilla root directory. + </P +><P +> <DIV CLASS="NOTE" ><P ></P @@ -1328,34 +1683,37 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> The second time you run checksetup.pl, you should become the - user your web server runs as, and that you ensure that you set the - "webservergroup" parameter in localconfig to match the web - server's group - name, if any. I believe, for the next release of Bugzilla, - this will - be fixed so that Bugzilla supports a "webserveruser" parameter - in localconfig - as well. - <DIV +> The second time you run checksetup.pl, you should become + the user your web server runs as, and that you ensure that + you set the <SPAN +CLASS="QUOTE" +>"webservergroup"</SPAN +> parameter in localconfig to + match the web server's group name, if any. I believe, + for the next release of Bugzilla, this will be fixed so + that Bugzilla supports a <SPAN +CLASS="QUOTE" +>"webserveruser"</SPAN +> parameter in + localconfig as well. + <DIV CLASS="EXAMPLE" ><A -NAME="AEN697" +NAME="AEN774" ></A ><P ><B >Example 3-2. Running checksetup.pl as the web user</B ></P ><P -> Assuming your web server runs as user "apache", - and Bugzilla is installed in - "/usr/local/bugzilla", here's one way to run checksetup.pl - as the web server user. - As root, for the <EM +> Assuming your web server runs as user "apache", and + Bugzilla is installed in "/usr/local/bugzilla", here's + one way to run checksetup.pl as the web server user. + As root, for the <EM >second run</EM -> - of checksetup.pl, do this: - <TABLE +> of + checksetup.pl, do this: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1365,26 +1723,27 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" ->bash# chown -R apache:apache /usr/local/bugzilla -bash# su - apache -bash# cd /usr/local/bugzilla -bash# ./checksetup.pl - </PRE +> +bash# chown -R apache:apache /usr/local/bugzilla +bash# su - apache +bash# cd /usr/local/bugzilla +bash# ./checksetup.pl + </PRE ></FONT ></TD ></TR ></TABLE > - </P + </P ></DIV > - </P + </P ></TD ></TR ></TABLE ></DIV > - </P + </P ><DIV CLASS="NOTE" ><P @@ -1406,10 +1765,10 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> The checksetup.pl script is designed so that you can run +> The checksetup.pl script is designed so that you can run it at any time without causing harm. You should run it after any upgrade to Bugzilla. - </P + </P ></TD ></TR ></TABLE @@ -1420,16 +1779,16 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN704" +NAME="AEN781" >3.2.16. Setting Up Maintainers Manually (Optional)</A ></H2 ><P -> If you want to add someone else to every group by hand, you +> If you want to add someone else to every group by hand, you can do it by typing the appropriate MySQL commands. Run - '<TT -CLASS="COMPUTEROUTPUT" -> mysql -u root -p bugs</TT ->' You + <B +CLASS="COMMAND" +> mysql -u root -p bugs</B +> You may need different parameters, depending on your security settings. Then: <P @@ -1450,7 +1809,12 @@ CLASS="COMMAND" profiles set groupset=0x7fffffffffffffff where login_name = 'XXX';</B > </TT -> +> (yes, that's <EM +>fifteen</EM +><SPAN +CLASS="QUOTE" +>"f"</SPAN +>'s. </TD ></TR ></TBODY @@ -1465,7 +1829,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN713" +NAME="AEN792" >3.2.17. The Whining Cron (Optional)</A ></H2 ><P @@ -1551,7 +1915,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN723" +NAME="AEN802" >3.2.18. Bug Graphs (Optional)</A ></H2 ><P @@ -1608,7 +1972,7 @@ CLASS="SECTION" ><H2 CLASS="SECTION" ><A -NAME="AEN735" +NAME="AEN814" >3.2.19. Securing MySQL</A ></H2 ><P diff --git a/docs/html/tinderbox.html b/docs/html/tinderbox.html index 1c6ea48b0..239548421 100644 --- a/docs/html/tinderbox.html +++ b/docs/html/tinderbox.html @@ -1,7 +1,7 @@ <HTML ><HEAD ><TITLE ->Tinderbox</TITLE +>Tinderbox/Tinderbox2</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.61 @@ -71,10 +71,10 @@ CLASS="SECTION" CLASS="SECTION" ><A NAME="TINDERBOX" ->5.4. Tinderbox</A +>5.4. Tinderbox/Tinderbox2</A ></H1 ><P ->We need Tinderbox integration information</P +>We need Tinderbox integration information.</P ></DIV ><DIV CLASS="NAVFOOTER" diff --git a/docs/html/useradmin.html b/docs/html/useradmin.html index 6b3e87d97..a57ed8bbb 100644 --- a/docs/html/useradmin.html +++ b/docs/html/useradmin.html @@ -137,6 +137,15 @@ CLASS="PROMPT" login name)"; </B > </P +><P +>Yes, that is <EM +>fourteen</EM +> + <SPAN +CLASS="QUOTE" +>"f"</SPAN +>'s. A whole lot of f-ing going on if you + want to create a new administator.</P ></TD ></TR ></TABLE @@ -245,13 +254,16 @@ VALIGN="TOP" right-hand side of the text entry box. You can match what you type as a case-insensitive substring (the default) of all users on your system, a case-sensitive - regular expression (please see the "man regexp" manual - page for details on regular expression syntax), or a - <EM + regular expression (please see the <B +CLASS="COMMAND" +>man + regexp</B +> manual page for details on regular + expression syntax), or a <EM >reverse</EM -> regular expression match, - where every user name which does NOT match the regular - expression is selected. +> + regular expression match, where every user name which + does NOT match the regular expression is selected. </P ></TD ></TR @@ -294,10 +306,17 @@ VALIGN="TOP" >not</EM > send an email informing them of their username and - password. In general, it is preferable to log out and - use the "New Account" button to create users, as it - will pre-populate all the required fields and also - notify the user of her account name and password. + password. While useful for creating dummy accounts + (watchers which shuttle mail to another system, for + instance, or email addresses which are a mailing + list), in general it is preferable to log out and use + the <SPAN +CLASS="QUOTE" +>"New Account"</SPAN +> button to create users, + as it will pre-populate all the required fields and + also notify the user of her account name and + password. </P ></TD ></TR @@ -346,6 +365,15 @@ VALIGN="TOP" > Don't disable your own administrative account, or you will hate life! </P +><P +>At this time, <SPAN +CLASS="QUOTE" +>"Disabled Text"</SPAN +> does not + prevent a user from using the email interface. If you + have the email interface enabled, they can still + continue to submit bugs and comments that way. We need + a patch to fix this.</P ></TD ></TR ></TABLE @@ -419,9 +447,8 @@ VALIGN="TOP" ><P > <EM >Password</EM ->: You will only see - asterisks in versions of Bugzilla newer than 2.10 or - early 2.11. You can change the user password here. +>: You can change the user + password here. It is normal to only see asterisks. </P ></LI ><LI diff --git a/docs/html/using.html b/docs/html/using.html index 83050ed83..51e333451 100644 --- a/docs/html/using.html +++ b/docs/html/using.html @@ -86,7 +86,7 @@ VALIGN="TOP" ><I ><P ><I ->What, Why, How, & What's in it for me?</I +>What, Why, How, & Where?</I ></P ></I ></TD @@ -150,7 +150,7 @@ HREF="how.html#BUG_MANAGE" ><DT >2.4. <A HREF="init4me.html" ->What's in it for me?</A +>Where can I find my user preferences?</A ></DT ><DD ><DL diff --git a/docs/html/usingbz-conc.html b/docs/html/usingbz-conc.html index b3ebe5b60..ced0648ee 100644 --- a/docs/html/usingbz-conc.html +++ b/docs/html/usingbz-conc.html @@ -13,7 +13,7 @@ REL="UP" TITLE="Using Bugzilla" HREF="using.html"><LINK REL="PREVIOUS" -TITLE="What's in it for me?" +TITLE="Where can I find my user preferences?" HREF="init4me.html"><LINK REL="NEXT" TITLE="Installation" @@ -74,16 +74,14 @@ NAME="USINGBZ-CONC" >2.5. Using Bugzilla-Conclusion</A ></H1 ><P -> Thank you for reading through this portion of the Bugzilla Guide. I anticipate - it may not yet meet the needs of all readers. If you have additional comments or - corrections to make, please submit your contributions to the - <A +> Thank you for reading through this portion of the Bugzilla + Guide. I anticipate it may not yet meet the needs of all + readers. If you have additional comments or corrections to + make, please submit your contributions to the <A HREF="mailto://mozilla-webtools@mozilla.org" TARGET="_top" >mozilla-webtools</A -> - mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools - newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org +> mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org </P ></DIV ><DIV @@ -126,7 +124,7 @@ HREF="installation.html" WIDTH="33%" ALIGN="left" VALIGN="top" ->What's in it for me?</TD +>Where can I find my user preferences?</TD ><TD WIDTH="34%" ALIGN="center" diff --git a/docs/html/variant_fenris.html b/docs/html/variant_fenris.html new file mode 100644 index 000000000..3dd120fe0 --- /dev/null +++ b/docs/html/variant_fenris.html @@ -0,0 +1,142 @@ +<HTML +><HEAD +><TITLE +>Loki Bugzilla (Fenris)</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.61 +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide" +HREF="index.html"><LINK +REL="UP" +TITLE="Bugzilla Variants and Competitors" +HREF="variants.html"><LINK +REL="PREVIOUS" +TITLE="Red Hat Bugzilla" +HREF="rhbugzilla.html"><LINK +REL="NEXT" +TITLE="Issuezilla" +HREF="variant_issuezilla.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="rhbugzilla.html" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 7. Bugzilla Variants and Competitors</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="variant_issuezilla.html" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="SECTION" +><H1 +CLASS="SECTION" +><A +NAME="VARIANT_FENRIS" +>7.2. Loki Bugzilla (Fenris)</A +></H1 +><P +>Fenris can be found at <A +HREF="http://fenris.lokigames.com/" +TARGET="_top" +>http://fenris.lokigames.com</A +>. It is a fork from Bugzilla.</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="rhbugzilla.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="variant_issuezilla.html" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Red Hat Bugzilla</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="variants.html" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Issuezilla</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/variant_issuezilla.html b/docs/html/variant_issuezilla.html new file mode 100644 index 000000000..83cf31704 --- /dev/null +++ b/docs/html/variant_issuezilla.html @@ -0,0 +1,153 @@ +<HTML +><HEAD +><TITLE +>Issuezilla</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.61 +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide" +HREF="index.html"><LINK +REL="UP" +TITLE="Bugzilla Variants and Competitors" +HREF="variants.html"><LINK +REL="PREVIOUS" +TITLE="Loki Bugzilla (Fenris)" +HREF="variant_fenris.html"><LINK +REL="NEXT" +TITLE="Scarab" +HREF="variant_scarab.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="variant_fenris.html" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 7. Bugzilla Variants and Competitors</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="variant_scarab.html" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="SECTION" +><H1 +CLASS="SECTION" +><A +NAME="VARIANT_ISSUEZILLA" +>7.3. Issuezilla</A +></H1 +><P +>Issuezilla is another fork from Bugzilla, and seems nearly + as popular as the Red Hat Bugzilla fork. Some Issuezilla team + members are regular contributors to the Bugzilla mailing + list/newsgroup. Issuezilla is not the primary focus of + bug-tracking at tigris.org, however. Their Java-based + bug-tracker, <A +HREF="variant_scarab.html" +>Scarab, a newfangled Java-based issue tracker</A +>, is under heavy development + and looks promising!</P +><P +>URL: <A +HREF="http://issuezilla.tigris.org/servlets/ProjectHome" +TARGET="_top" +>http://issuezilla.tigris.org/servlets/ProjectHome</A +></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="variant_fenris.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="variant_scarab.html" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Loki Bugzilla (Fenris)</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="variants.html" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Scarab</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/variant_perforce.html b/docs/html/variant_perforce.html new file mode 100644 index 000000000..13944a65b --- /dev/null +++ b/docs/html/variant_perforce.html @@ -0,0 +1,148 @@ +<HTML +><HEAD +><TITLE +>Perforce SCM</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.61 +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide" +HREF="index.html"><LINK +REL="UP" +TITLE="Bugzilla Variants and Competitors" +HREF="variants.html"><LINK +REL="PREVIOUS" +TITLE="Scarab" +HREF="variant_scarab.html"><LINK +REL="NEXT" +TITLE="SourceForge" +HREF="variant_sourceforge.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="variant_scarab.html" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 7. Bugzilla Variants and Competitors</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="variant_sourceforge.html" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="SECTION" +><H1 +CLASS="SECTION" +><A +NAME="VARIANT_PERFORCE" +>7.5. Perforce SCM</A +></H1 +><P +>Although Perforce isn't really a bug tracker, it can be used + as such through the <SPAN +CLASS="QUOTE" +>"jobs"</SPAN +> functionality.</P +><P +><A +HREF="http://www.perforce.com/perforce/technotes/note052.html" +TARGET="_top" +>http://www.perforce.com/perforce/technotes/note052.html</A +>http://www.perforce.com/perforce/technotes/note052.html</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="variant_scarab.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="variant_sourceforge.html" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Scarab</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="variants.html" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>SourceForge</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/variant_scarab.html b/docs/html/variant_scarab.html new file mode 100644 index 000000000..57a085052 --- /dev/null +++ b/docs/html/variant_scarab.html @@ -0,0 +1,148 @@ +<HTML +><HEAD +><TITLE +>Scarab</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.61 +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide" +HREF="index.html"><LINK +REL="UP" +TITLE="Bugzilla Variants and Competitors" +HREF="variants.html"><LINK +REL="PREVIOUS" +TITLE="Issuezilla" +HREF="variant_issuezilla.html"><LINK +REL="NEXT" +TITLE="Perforce SCM" +HREF="variant_perforce.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="variant_issuezilla.html" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 7. Bugzilla Variants and Competitors</TD +><TD +WIDTH="10%" +ALIGN="right" +VALIGN="bottom" +><A +HREF="variant_perforce.html" +>Next</A +></TD +></TR +></TABLE +><HR +ALIGN="LEFT" +WIDTH="100%"></DIV +><DIV +CLASS="SECTION" +><H1 +CLASS="SECTION" +><A +NAME="VARIANT_SCARAB" +>7.4. Scarab</A +></H1 +><P +>Scarab is a promising new bug-tracking system built using + Java Serlet technology. As of this writing, no source code has + been released as a package, but you can obtain the code from + CVS. + </P +><P +>URL: <A +HREF="http://scarab.tigris.org/" +TARGET="_top" +>http://scarab.tigris.org</A +></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="variant_issuezilla.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="variant_perforce.html" +>Next</A +></TD +></TR +><TR +><TD +WIDTH="33%" +ALIGN="left" +VALIGN="top" +>Issuezilla</TD +><TD +WIDTH="34%" +ALIGN="center" +VALIGN="top" +><A +HREF="variants.html" +>Up</A +></TD +><TD +WIDTH="33%" +ALIGN="right" +VALIGN="top" +>Perforce SCM</TD +></TR +></TABLE +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/html/variant_sourceforge.html b/docs/html/variant_sourceforge.html new file mode 100644 index 000000000..d26098477 --- /dev/null +++ b/docs/html/variant_sourceforge.html @@ -0,0 +1,148 @@ +<HTML +><HEAD +><TITLE +>SourceForge</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.61 +"><LINK +REL="HOME" +TITLE="The Bugzilla Guide" +HREF="index.html"><LINK +REL="UP" +TITLE="Bugzilla Variants and Competitors" +HREF="variants.html"><LINK +REL="PREVIOUS" +TITLE="Perforce SCM" +HREF="variant_perforce.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="variant_perforce.html" +>Prev</A +></TD +><TD +WIDTH="80%" +ALIGN="center" +VALIGN="bottom" +>Chapter 7. Bugzilla Variants and Competitors</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="VARIANT_SOURCEFORGE" +>7.6. SourceForge</A +></H1 +><P +>SourceForge is more of a way of coordinating geographically + distributed free software and open source projects over the + Internet than strictly a bug tracker, but if you're hunting for + bug-tracking for your open project, it may be just what the + software engineer ordered!</P +><P +>URL: <A +HREF="http://www.sourceforge.net" +TARGET="_top" +>http://www.sourceforge.net</A +></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="variant_perforce.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" +>Perforce SCM</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 diff --git a/docs/html/variants.html b/docs/html/variants.html index a2c2349a5..7a679b216 100644 --- a/docs/html/variants.html +++ b/docs/html/variants.html @@ -1,7 +1,7 @@ <HTML ><HEAD ><TITLE ->Bugzilla Variants</TITLE +>Bugzilla Variants and Competitors</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.61 @@ -67,39 +67,56 @@ CLASS="CHAPTER" ><H1 ><A NAME="VARIANTS" ->Chapter 7. Bugzilla Variants</A +>Chapter 7. Bugzilla Variants and Competitors</A ></H1 ><DIV -CLASS="NOTE" +CLASS="TOC" +><DL +><DT +><B +>Table of Contents</B +></DT +><DT +>7.1. <A +HREF="rhbugzilla.html" +>Red Hat Bugzilla</A +></DT +><DT +>7.2. <A +HREF="variant_fenris.html" +>Loki Bugzilla (Fenris)</A +></DT +><DT +>7.3. <A +HREF="variant_issuezilla.html" +>Issuezilla</A +></DT +><DT +>7.4. <A +HREF="variant_scarab.html" +>Scarab</A +></DT +><DT +>7.5. <A +HREF="variant_perforce.html" +>Perforce SCM</A +></DT +><DT +>7.6. <A +HREF="variant_sourceforge.html" +>SourceForge</A +></DT +></DL +></DIV ><P +>I created this section to answer questions about Bugzilla + competitors and variants, then found a wonderful site which covers + an awful lot of what I wanted to discuss. Rather than quote it in + its entirety, I'll simply refer you here: <A +HREF="http://linas.org/linux/pm.html" +TARGET="_top" +>http://linas.org/linux/pm.html</A ></P -><TABLE -CLASS="NOTE" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/note.gif" -HSPACE="5" -ALT="Note"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P -> 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 -></TD -></TR -></TABLE -></DIV ></DIV ><DIV CLASS="NAVFOOTER" diff --git a/docs/html/whatis.html b/docs/html/whatis.html index 81a8cd49a..248467ef5 100644 --- a/docs/html/whatis.html +++ b/docs/html/whatis.html @@ -130,8 +130,10 @@ system against which all others are measured. ></LI ><LI ><P -> available integration with automated software configuration management systems, including - Perforce and CVS +> available integration with automated software + configuration management systems, including Perforce and + CVS (through the Bugzilla email interface and + checkin/checkout scripts) </P ></LI ><LI @@ -143,25 +145,33 @@ system against which all others are measured. > </P ><P -> Despite its current robustness and popularity, however, Bugzilla - faces some near-term challenges, such as reliance on a single database, a lack of - abstraction of the user interface and program logic, verbose email bug - notifications, a powerful but daunting query interface, little reporting configurability, - problems with extremely large queries, some unsupportable bug resolution options, - no internationalization, and dependence on some nonstandard libraries. +> Despite its current robustness and popularity, Bugzilla faces + some near-term challenges, such as reliance on a single + database, a lack of abstraction of the user interface and + program logic, verbose email bug notifications, a powerful but + daunting query interface, little reporting configurability, + problems with extremely large queries, some unsupportable bug + resolution options, little internationalization (although non-US + character sets are accepted for comments), 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". +> Some recent headway has been made on the query front, however. + If you are using the latest version of Bugzilla, you should see + a <SPAN +CLASS="QUOTE" +>"simple search"</SPAN +> 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 +> Despite these small problems, Bugzilla is very hard to beat. It + is under <EM >very</EM -> - 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. +> active development to address + the current issues, and continually gains new features. </P ></DIV ><DIV diff --git a/docs/html/why.html b/docs/html/why.html index b5f6b04b0..dbbb4668b 100644 --- a/docs/html/why.html +++ b/docs/html/why.html @@ -97,23 +97,25 @@ VALIGN="TOP" ></TR ></TABLE ><P -> For many years, defect-tracking software has remained principally the domain - of large software development houses. Even then, most shops never bothered - with bug-tracking software, and instead simply relied on shared lists and - email to monitor the status of defects. This procedure is error-prone and - tends to cause those bugs judged least significant by developers to be +> For many years, defect-tracking software has remained + principally the domain of large software development houses. + Even then, most shops never bothered with bug-tracking software, + and instead simply relied on shared lists and email to monitor + the status of defects. This procedure is error-prone and tends + to cause those bugs judged least significant by developers to be dropped or ignored. </P ><P -> These days, many companies are finding that integrated defect-tracking - systems reduce downtime, increase productivity, and raise customer - satisfaction with their systems. Along with full disclosure, an open - bug-tracker allows manufacturers to keep in touch with their clients - and resellers, to communicate about problems effectively throughout - the data management chain. Many corporations have also discovered that - defect-tracking helps reduce costs by providing IT support accountability, - telephone support knowledge bases, and a common, well-understood system - for accounting for unusual system or software issues. +> These days, many companies are finding that integrated + defect-tracking systems reduce downtime, increase productivity, + and raise customer satisfaction with their systems. Along with + full disclosure, an open bug-tracker allows manufacturers to + keep in touch with their clients and resellers, to communicate + about problems effectively throughout the data management chain. + Many corporations have also discovered that defect-tracking + helps reduce costs by providing IT support accountability, + telephone support knowledge bases, and a common, well-understood + system for accounting for unusual system or software issues. </P ><P > But why should <EM @@ -121,28 +123,35 @@ VALIGN="TOP" > use Bugzilla? </P ><P -> 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 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 +> 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 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 </P ><P -> Bugzilla can dramatically increase the productivity and accountability - of individual employees by providing a documented workflow and positive - feedback for good performance. How many times do you wake up in the - morning, remembering that you were supposed to do *something* today, - but you just can't quite remember? Put it in Bugzilla, and you have a record - of it from which you can extrapolate milestones, predict product versions - for integration, and by using Bugzilla's e-mail integration features - be able to follow the discussion trail that led to critical decisions. +> Bugzilla can dramatically increase the productivity and + accountability of individual employees by providing a documented + workflow and positive feedback for good performance. How many + times do you wake up in the morning, remembering that you were + supposed to do <EM +>something</EM +> today, but you + just can't quite remember? Put it in Bugzilla, and you have a + record of it from which you can extrapolate milestones, predict + product versions for integration, and by using Bugzilla's e-mail + integration features be able to follow the discussion trail that + led to critical decisions. </P ><P -> Ultimately, Bugzilla puts the power in your hands to improve your value - to your employer or business while providing a usable framework for your natural - attention to detail and knowledge store to flourish. +> Ultimately, Bugzilla puts the power in your hands to improve + your value to your employer or business while providing a usable + framework for your natural attention to detail and knowledge + store to flourish. </P ></DIV ><DIV diff --git a/docs/html/win32.html b/docs/html/win32.html index d0c1c8064..32f2515e8 100644 --- a/docs/html/win32.html +++ b/docs/html/win32.html @@ -126,7 +126,7 @@ VALIGN="TOP" of the <A HREF="installation.html" ->Chapter 3</A +>Bugzilla Installation</A > section while performing your Win32 installation. </P @@ -137,13 +137,14 @@ HREF="installation.html" be a <EM >very</EM > skilled Windows Systems - Administrator with both strong troubleshooting abilities and - a high tolerance for pain. Bugzilla on NT requires hacking - source code and implementing some advanced utilities. What - follows is the recommended installation procedure for Win32; - additional suggestions are provided in <A + Administrator with strong troubleshooting abilities, a high + tolerance for pain, and moderate perl skills. Bugzilla on NT + requires hacking source code and implementing some advanced + utilities. What follows is the recommended installation + procedure for Win32; additional suggestions are provided in + <A HREF="faq.html" ->The Bugzilla FAQ</A +>Appendix A</A >. </P ></TD @@ -159,9 +160,23 @@ TYPE="1" > Install <A HREF="http://www.apache.org/" TARGET="_top" ->Apache Web Server</A +>Apache Web + Server</A +> for Windows, and copy the Bugzilla files + somewhere Apache can serve them. Please follow all the + instructions referenced in <A +HREF="installation.html" +>Bugzilla Installation</A +> + regarding your Apache configuration, particularly + instructions regarding the <SPAN +CLASS="QUOTE" +>"AddHandler"</SPAN > - for Windows. + parameter and <SPAN +CLASS="QUOTE" +>"ExecCGI"</SPAN +>. </P ><DIV CLASS="NOTE" @@ -184,13 +199,13 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> You may also use Internet Information Server or Personal Web - Server for this purpose. However, setup is slightly more - difficult. If ActivePerl doesn't seem to handle your file - associations correctly (for .cgi and .pl files), please - consult <A +> You may also use Internet Information Server or Personal + Web Server for this purpose. However, setup is quite + different. If ActivePerl doesn't seem to handle your + file associations correctly (for .cgi and .pl files), + please consult <A HREF="faq.html" ->The Bugzilla FAQ</A +>Appendix A</A >. </P ><P @@ -286,7 +301,7 @@ CLASS="COMMAND" ><DIV CLASS="EXAMPLE" ><A -NAME="AEN910" +NAME="AEN1012" ></A ><P ><B @@ -526,13 +541,63 @@ CLASS="FILENAME" this line: </P ><P -> "my $webservergid = getgrnam($my_webservergroup); " +> <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>my $webservergid = getgrnam($my_webservergroup); + </PRE +></FONT +></TD +></TR +></TABLE +> </P ><P > to </P ><P -> "my $webservergid = $my_webservergroup; " +> <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>my $webservergid = $my_webservergroup; + </PRE +></FONT +></TD +></TR +></TABLE +> +or the name of the group you wish to own the files explicitly: + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>my $webservergid = 'Administrators' + </PRE +></FONT +></TD +></TR +></TABLE +> </P ></LI ><LI @@ -841,7 +906,31 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->The code above needs testing as well to make sure it is correct.</P +> Some have found success using the commercial product, + <SPAN +CLASS="PRODUCTNAME" +>Windmail</SPAN +>. + You could try replacing your sendmail calls with: + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><FONT +COLOR="#000000" +><PRE +CLASS="PROGRAMLISTING" +>open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log"; + </PRE +></FONT +></TD +></TR +></TABLE +> + or something to that effect. + </P ></TD ></TR ></TABLE @@ -1002,9 +1091,9 @@ ALT="Note"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> This step is completely optional if you are using IIS or - another web server which only decides on an interpreter - based upon the file extension (.pl), rather than the +> This step is optional if you are using IIS or another + web server which only decides on an interpreter based + upon the file extension (.pl), rather than the <SPAN CLASS="QUOTE" >"shebang"</SPAN @@ -1102,10 +1191,11 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P -> If you are using IIS 5.0 or higher, you must add cgi +> If you are using IIS or Personal Web Server, you must add cgi relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), - such as: <TABLE + such as: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1164,18 +1254,17 @@ VALIGN="TOP" ><P > From Andrew Pearson: <A -NAME="AEN1062" +NAME="AEN1169" ></A ><BLOCKQUOTE CLASS="BLOCKQUOTE" ><P -> "You can make Bugzilla work with Personal Web Server for - Windows 98 and higher, as well as for IIS 4.0. Microsoft has - information available at - <A -HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP" +> You can make Bugzilla work with Personal Web Server for + Windows 98 and higher, as well as for IIS 4.0. + Microsoft has information available at <A +HREF=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP" TARGET="_top" -> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A +> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</A > </P ><P @@ -1225,79 +1314,25 @@ ALT="Tip"></TD ALIGN="LEFT" VALIGN="TOP" ><P ->"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</P -><A -NAME="AEN1072" -></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 -><FONT -COLOR="#000000" -><PRE -CLASS="PROGRAMLISTING" ->my $webservergid = getgrnam($my_webservergroup); - </PRE -></FONT -></TD -></TR -></TABLE -><P ->to</P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><FONT -COLOR="#000000" -><PRE -CLASS="PROGRAMLISTING" ->my $webservergid = 'Administrators' - </PRE -></FONT -></TD -></TR -></TABLE -></LI -><LI -><P -> I then ran checksetup.pl - </P -></LI -><LI -><P -> I removed all the encrypt() - <DIV +> If attempting to run Bugzilla 2.12 or older, you will need + to remove encrypt() calls from the Perl source. This is + <EM +>not necessary</EM +> for Bugzilla 2.13 and + later. + <DIV CLASS="EXAMPLE" ><A -NAME="AEN1084" +NAME="AEN1180" ></A ><P ><B ->Example 3-4. Removing encrypt() for Windows NT installations</B +>Example 3-4. Removing encrypt() for Windows NT Bugzilla version + 2.12 or earlier</B ></P ><P -> Replace this: - <TABLE +> Replace this: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1307,17 +1342,17 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" ->SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . - SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); -my $enteredcryptpwd = FetchOneColumn(); - </PRE +> +SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); +my $enteredcryptpwd = FetchOneColumn(); + </PRE ></FONT ></TD ></TR ></TABLE > - with this: - <TABLE + with this: + <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" @@ -1327,125 +1362,18 @@ WIDTH="100%" COLOR="#000000" ><PRE CLASS="PROGRAMLISTING" ->my $enteredcryptpwd = $enteredpwd - </PRE +> +my $enteredcryptpwd = $enteredpwd + </PRE ></FONT ></TD ></TR ></TABLE > - in cgi.pl. - </P + 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 -><FONT -COLOR="#000000" -><PRE -CLASS="PROGRAMLISTING" -> -open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log"; - </PRE -></FONT -></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 -></TD -></TR -></TABLE -></DIV -><DIV -CLASS="TIP" -><P -></P -><TABLE -CLASS="TIP" -WIDTH="100%" -BORDER="0" -><TR -><TD -WIDTH="25" -ALIGN="CENTER" -VALIGN="TOP" -><IMG -SRC="../images/tip.gif" -HSPACE="5" -ALT="Tip"></TD -><TD -ALIGN="LEFT" -VALIGN="TOP" -><P -> This was some late breaking information from Jan Evert. Sorry for the lack of formatting. - </P -><P -CLASS="LITERALLAYOUT" ->I'm busy installing bugzilla on a WinNT machine and I thought I'd notify you<br> -at this moment of the commments I have to section 2.2.1 of the bugzilla<br> -guide (at http://www.trilobyte.net/barnsons/html/).<br> -<br> -Step 1:<br> -I've used apache, installation is really straightforward.<br> -After reading the Unix installation instructions, I found that it is<br> -necessary to add the ExecCGI option to the bugzilla directory. Also the<br> -'AddHandler' line for .cgi is by default commented out.<br> -<br> -Step 3: although just a detail, 'ppm install <module%gt;' will also work<br> -(without .ppd). And, it can also download these automatically from<br> -ActiveState.<br> -<br> -Step 4: although I have cygwin installed, it seems that it is not necessary.<br> -On my machine cygwin is not in the PATH and everything seems to work as<br> -expected.<br> -However, I've not used everything yet.<br> -<br> -Step 6: the 'bugs_password' given in SQL command d needs to be edited into<br> -localconfig later on (Step 7) if the password is not empty. I've also edited<br> -it into globals.pl, but I'm not sure that is needed. In both places, the<br> -variable is named db_pass.<br> -<br> -Step 8: all the sendmail replacements mentioned are not as simple as<br> -described there. Since I am not familiar (yet) with perl, I don't have any<br> -mail working yet.<br> -<br> -Step 9: in globals.pl the encrypt() call can be replaced by just the<br> -unencrypted password. In CGI.pl, the complete SQL command can be removed.<br> -<br> -Step 11: I've only changed the #! lines in *.cgi. I haven't noticed problems<br> -with the system() call yet.<br> -There seem to be only four system() called programs: processmail.pl (handled<br> -by step 10), syncshadowdb (which should probably get the same treatment as<br> -processmail.pl), diff and mysqldump. The last one is only needed with the<br> -shadowdb feature (which I don't use).<br> -<br> -There seems to be one step missing: copying the bugzilla files somehwere<br> -that apache can serve them.<br> -<br> -Just noticed the updated guide... Brian's comment is new. His first comment<br> -will work, but opens up a huge security hole.<br> </P ></TD ></TR diff --git a/docs/sgml/Bugzilla-Guide.sgml b/docs/sgml/Bugzilla-Guide.sgml index 30deb5c4a..59befaf0a 100644 --- a/docs/sgml/Bugzilla-Guide.sgml +++ b/docs/sgml/Bugzilla-Guide.sgml @@ -23,7 +23,7 @@ <!ENTITY bz-ver "2.14"> <!ENTITY bz-cvs-ver "2.15"> <!ENTITY bzg-date "August 10, 2001"> -<!ENTITY bzg-ver "2.14.0"> +<!ENTITY bzg-ver "2.14"> <!ENTITY bzg-cvs-ver "2.15.0"> <!ENTITY bzg-auth "Matthew P. Barnson"> <!ENTITY bzg-auth-email "<email>barnboy@NOSPAM.trilobyte.net</email>"> @@ -137,15 +137,6 @@ try to avoid clutter and feel free to waste space in the code to make it more re </affiliation> </collab> - <editor> - <firstname>I.</firstname> - <surname>Freely</surname> - <othername>P.</othername> - <affiliation> - <address><email>ipfreely@freely.eye-p.net</email></address> - </affiliation> - </editor> - </authorgroup> <abstract> @@ -165,6 +156,12 @@ try to avoid clutter and feel free to waste space in the code to make it more re professional on operating system upon which you install Bugzilla. </para> + <para> + THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT. + IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN + TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT + ADDITIONS TO THE GUIDE WRITTEN IN HTML! + </para> </abstract> diff --git a/docs/sgml/about.sgml b/docs/sgml/about.sgml index d92fa9b30..89f7bb127 100644 --- a/docs/sgml/about.sgml +++ b/docs/sgml/about.sgml @@ -14,11 +14,10 @@ document you see today. </para> <para> - Despite the lack of updates, Bugzilla is simply the best piece - of bug-tracking software the world has ever seen. This document - is intended to be the comprehensive guide to the installation, - administration, maintenance, and use of the Bugzilla - bug-tracking system. + Bugzilla is simply the best piece of bug-tracking software the + world has ever seen. This document is intended to be the + comprehensive guide to the installation, administration, + maintenance, and use of the Bugzilla bug-tracking system. </para> <para> This release of the Bugzilla Guide is the diff --git a/docs/sgml/administration.sgml b/docs/sgml/administration.sgml index 0f290da31..54f984fbc 100644 --- a/docs/sgml/administration.sgml +++ b/docs/sgml/administration.sgml @@ -8,18 +8,21 @@ </subtitle> <para> - So you followed the installation instructions 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 business needs to be to setup the - operating parameters for bugzilla. + So you followed <quote><xref linkend="installation"></quote> to the + letter, and logged into Bugzilla for the very first time with your + super-duper god account. You sit, contentedly staring at the + Bugzilla Query Screen, the worst of the whole mad business of + installing this terrific program behind you. It seems, though, you + have nothing yet to query! Your first act of business should be to + setup the operating parameters for Bugzilla so you can get busy + getting data into your bug tracker. </para> <section id="postinstall-check"> <title>Post-Installation Checklist</title> <para> - After installation, follow the checklist below to ensure that - you have a successful installation. If you do not see a + After installation, follow the checklist below to help ensure + that you have a successful installation. If you do not see a recommended setting for a parameter, consider leaving it at the default while you perform your initial tests on your Bugzilla setup. @@ -30,47 +33,80 @@ <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. + Bring up <filename>editparams.cgi</filename> in your web + browser. This should be available as the <quote>edit + parameters</quote> link from any Bugzilla screen once you + have logged in. </para> </step> <step> + <para>The <quote>maintainer</quote> is the email address of + the person responsible for maintaining this Bugzilla + installation. The maintainer need not be a valid Bugzilla + user. Error pages, error emails, and administrative mail + will be sent with the maintainer as the return email + address.</para> <para> - Set "maintainer" to <emphasis>your</emphasis> email address. + Set <quote>maintainer</quote> to <emphasis>your</emphasis> email address. This allows Bugzilla's error messages to display your email address and allow people to contact you for help. </para> </step> <step> + <para>The <quote>urlbase</quote> parameter defines the fully + qualified domain name and web server path to your Bugzilla + installation.</para> <para> - Set "urlbase" to the URL reference for your Bugzilla - installation. If your bugzilla query page is at - http://www.foo.com/bugzilla/query.cgi, your url base is - http://www.foo.com/bugzilla/ + For example, if your bugzilla query page is + http://www.foo.com/bugzilla/query.cgi, set your + <quote>urlbase</quote> is http://www.foo.com/bugzilla/. </para> </step> <step> + <para><quote>usebuggroups</quote> dictates whether or not to + implement group-based security for Bugzilla. If set, + Bugzilla bugs can have an associated groupmask defining + which groups of users are allowed to see and edit the + bug.</para> <para> Set "usebuggroups" to "on" <emphasis>only</emphasis> if you - need to restrict access to products. I suggest leaving this - parameter <emphasis>off</emphasis> while initially testing - your Bugzilla. + may wish to restrict access to products. I suggest leaving + this parameter <emphasis>off</emphasis> while initially + testing your Bugzilla. </para> </step> <step> <para> - Set "usebuggroupsentry" to "on" if you want to restrict - access to products. Once again, if you are simply testing + <quote>usebuggroupsentry</quote>, when set to + <quote>on</quote>, requires that all bugs have an associated + groupmask when submitted. This parameter is made for those + installations where product isolation is a necessity. + </para> + <para> + Set "usebuggroupsentry" to "on" if you absolutely need to + restrict access to bugs from the moment they are submitted + through resolution. 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. </para> </step> <step> + <para> + You run into an interesting problem when Bugzilla reaches a + high level of continuous activity. MySQL supports only + table-level write locking. What this means is that if + someone needs to make a change to a bug, they will lock the + entire table until the operation is complete. Locking for + write also blocks reads until the write is complete. The + <quote>shadowdb</quote> parameter was designed to get around + this limitation. While only a single user is allowed to + write to a table at a time, reads can continue unimpeded on + a read-only shadow copy of the database. Although your + database size will double, a shadow database can cause an + enormous performance improvement when implemented on + extremely high-traffic Bugzilla databases. + </para> <para> Set "shadowdb" to "bug_shadowdb" if you will be running a *very* large installation of Bugzilla. The shadow database @@ -79,15 +115,19 @@ <note> <para> Enabling "shadowdb" can adversely affect the stability - of your installation of Bugzilla. You may frequently - need to manually synchronize your databases, or schedule - nightly syncs via "cron" + of your installation of Bugzilla. You should regularly + check that your database is in sync. It is often + advisable to force a shadow database sync nightly via + <quote>cron</quote>. </para> </note> Once again, in testing you should avoid this option -- use it if or when you <emphasis>need</emphasis> to use it, and have repeatedly run into the problem it was designed to solve -- very long wait times while attempting to commit - a change to the database. + a change to the database. Mozilla.org began needing + <quote>shadowdb</quote> when they reached around 40,000 + Bugzilla users with several hundred Bugzilla bug changes and + comments per day. </para> <para> If you use the "shadowdb" option, it is only natural that @@ -97,6 +137,18 @@ </para> </step> <step> + <para><quote>headerhtml</quote>, <quote>footerhtml</quote>, + <quote>errorhtml</quote>, <quote>bannerhtml</quote>, and + <quote>blurbhtml</quote> are all templates which control + display of headers, footers, errors, banners, and additional + data. We could go into some detail regarding the usage of + these, but it is really best just to monkey around with them + a bit to see what they do. I strongly recommend you copy + your <filename>data/params</filename> file somewhere safe + before playing with these values, though. If they are + changed dramatically, it may make it impossible for you to + display Bugzilla pages to fix the problem until you have + restored your <filename>data/params</filename> file.</para> <para> If you have custom logos or HTML you must put in place to fit within your site design guidelines, place the code in @@ -105,15 +157,20 @@ <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 settings at - the defaults initially. + <emphasis>before</emphasis> any other code on the page, + except the CONTENT-TYPE header sent by the Bugzilla + engine. 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> </para> </step> <step> + <para><quote>passwordmail</quote> is rather simple. Every + time a user creates an account, the text of this parameter + is read as the text to send to the new user along with their + password message.</para> <para> Add any text you wish to the "passwordmail" parameter box. For instance, many people choose to use this box to give a @@ -121,20 +178,32 @@ </para> </step> <step> - <para> - 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><quote>useqacontact</quote> allows you to define an + email address for each component, in addition to that of the + default owner, who will be sent carbon copies of incoming + bugs. The critical difference between a QA Contact and an + Owner is that the QA Contact follows the component. If you + reassign a bug from component A to component B, the QA + Contact for that bug will change with the reassignment, + regardless of owner.</para> + <para><quote>usestatuswhiteboard</quote> defines whether you + wish to have a free-form, overwritable field associated with + each bug. The advantage of the Status Whiteboard is that it + can be deleted or modified with ease, and provides an + easily-searchable field for indexing some bugs that have + some trait in common. Many people will put <quote>help + wanted</quote>, <quote>stalled</quote>, or <quote>waiting + on reply from somebody</quote> messages into the Status + Whiteboard field so those who peruse the bugs are aware of + their status even more than that which can be indicated by + the Resolution fields.</para> <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 Quality Assurance and/or Release Engineering team, but they may not be needed - for smaller installations. + for many smaller installations. </para> </step> <step> @@ -144,14 +213,22 @@ 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 installation instructions, or set this - value to "0". + value to "0" (never whine). </para> </step> <step> + <para><quote>commenton</quote> fields allow you to dictate + what changes can pass without comment, and which must have a + comment from the person who changed them. Often, + administrators will allow users to add themselves to the CC + list, accept bugs, or change the Status Whiteboard without + adding a comment as to their reasons for the change, yet + require that most other changes come with an + explanation.</para> <para> Set the "commenton" options according to your site policy. It is a wise idea to require comments when users resolve, - reassign, or reopen bugs. + reassign, or reopen bugs at the very least. <note> <para> It is generally far better to require a developer @@ -164,12 +241,28 @@ </para> </step> <step> + <para>The <quote>supportwatchers</quote> option can be an + exceptionally powerful tool in the hands of a power Bugzilla + user. By enabling this option, you allow users to receive + email updates whenever other users receive email updates. + This is, of course, subject to the groupset restrictions on + the bug; if the <quote>watcher</quote> would not normally be + allowed to view a bug, the watcher cannot get around the + system by setting herself up to watch the bugs of someone + with bugs outside her priveleges. She would still only + receive email updates for those bugs she could normally + view.</para> + <para>For Bugzilla sites which require strong inter-Product + security to prevent snooping, watchers are not a good + idea.</para> <para> - Set "supportwatchers" to "On". This feature is helpful for - team leads to monitor progress in their respective areas, - and can offer many other benefits, such as allowing a - developer to pick up a former engineer's bugs without - requiring her to change all the information in the bug. + However, for most sites you should set + <quote>supportwatchers</quote> to "On". This feature is + helpful for team leads to monitor progress in their + respective areas, and can offer many other benefits, such as + allowing a developer to pick up a former engineer's bugs + without requiring her to change all the information in the + bug. </para> </step> </procedure> @@ -205,6 +298,9 @@ groupset=0x7ffffffffffffff where login_name = "(user's login name)"; </command> </para> + <para>Yes, that is <emphasis>fourteen</emphasis> + <quote>f</quote>'s. A whole lot of f-ing going on if you + want to create a new administator.</para> </tip> </section> @@ -269,11 +365,11 @@ right-hand side of the text entry box. You can match what you type as a case-insensitive substring (the default) of all users on your system, a case-sensitive - regular expression (please see the "man regexp" manual - page for details on regular expression syntax), or a - <emphasis>reverse</emphasis> regular expression match, - where every user name which does NOT match the regular - expression is selected. + regular expression (please see the <command>man + regexp</command> manual page for details on regular + expression syntax), or a <emphasis>reverse</emphasis> + regular expression match, where every user name which + does NOT match the regular expression is selected. </para> </tip> </listitem> @@ -292,10 +388,14 @@ <para> Adding a user this way will <emphasis>not</emphasis> send an email informing them of their username and - password. In general, it is preferable to log out and - use the "New Account" button to create users, as it - will pre-populate all the required fields and also - notify the user of her account name and password. + password. While useful for creating dummy accounts + (watchers which shuttle mail to another system, for + instance, or email addresses which are a mailing + list), in general it is preferable to log out and use + the <quote>New Account</quote> button to create users, + as it will pre-populate all the required fields and + also notify the user of her account name and + password. </para> </note> </listitem> @@ -317,6 +417,11 @@ Don't disable your own administrative account, or you will hate life! </para> + <para>At this time, <quote>Disabled Text</quote> does not + prevent a user from using the email interface. If you + have the email interface enabled, they can still + continue to submit bugs and comments that way. We need + a patch to fix this.</para> </warning> </para> </section> @@ -350,9 +455,8 @@ </listitem> <listitem> <para> - <emphasis>Password</emphasis>: You will only see - asterisks in versions of Bugzilla newer than 2.10 or - early 2.11. You can change the user password here. + <emphasis>Password</emphasis>: You can change the user + password here. It is normal to only see asterisks. </para> </listitem> <listitem> diff --git a/docs/sgml/faq.sgml b/docs/sgml/faq.sgml index f01b43053..34b952b01 100644 --- a/docs/sgml/faq.sgml +++ b/docs/sgml/faq.sgml @@ -1,6 +1,6 @@ <!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> --> -<appendix id="faq" xreflabel="The Bugzilla FAQ"> +<appendix id="faq"> <title>The Bugzilla FAQ</title> <qandaset> @@ -17,8 +17,8 @@ <answer> <para> You can stay up-to-date with the latest Bugzilla - information at <ulink - url="http://www.mozilla.org/projects/bugzilla/"> http://www.mozilla.org/projects/bugzilla/</ulink> + information at <ulink url="http://www.mozilla.org/projects/bugzilla/"> + http://www.mozilla.org/projects/bugzilla/</ulink> </para> </answer> </qandaentry> @@ -31,9 +31,9 @@ </question> <answer> <para> - Bugzilla is covered by the Mozilla Public License. See - details at <ulink url="http://www.mozilla.org/MPL/"> - http://www.mozilla.org/MPL/</ulink> + Bugzilla is covered by the Mozilla Public License. + See details at <ulink url="http://www.mozilla.org/MPL/"> + http://www.mozilla.org/MPL/</ulink> </para> </answer> </qandaentry> @@ -46,17 +46,16 @@ </question> <answer> <para> - <ulink url="http://www.collab.net/">www.collab.net</ulink> - offers Bugzilla as part of their standard offering to - large projects. They do have some minimum fees that are - pretty hefty, and generally aren't interested in small - projects. + <ulink url="http://www.collab.net/">www.collab.net</ulink> offers + Bugzilla as part of their standard offering to large projects. + They do have some minimum fees that are pretty hefty, and generally + aren't interested in small projects. </para> <para> - There are several experienced Bugzilla hackers on the - mailing list/newsgroup who are willing to whore themselves - out for generous compensation. Try sending a message to - the mailing list asking for a volunteer. + There are several experienced + Bugzilla hackers on the mailing list/newsgroup who are willing + to whore themselves out for generous compensation. + Try sending a message to the mailing list asking for a volunteer. </para> </answer> </qandaentry> @@ -64,15 +63,14 @@ <qandaentry> <question> <para> - What major companies or projects are currently using - Bugzilla for bug-tracking? + What major companies or projects are currently using Bugzilla + for bug-tracking? </para> </question> <answer> <para> - There are <emphasis>dozens</emphasis> of major comapanies - with public Bugzilla sites to track bugs in their - products. A few include: + There are <emphasis>dozens</emphasis> of major comapanies with public + Bugzilla sites to track bugs in their products. A few include: <simplelist> <member>Netscape/AOL</member> <member>Mozilla.org</member> @@ -94,9 +92,8 @@ </simplelist> </para> <para> - Suffice to say, there are more than enough huge projects - using Bugzilla that we can safely say it's extremely - popular. + Suffice to say, there are more than enough huge projects using Bugzilla + that we can safely say it's extremely popular. </para> </answer> </qandaentry> @@ -109,16 +106,9 @@ </question> <answer> <para> - There are many, many contributors from around the world - maintaining Bugzilla. The designated "Maintainer" is Tara - Hernandez, with QA support by Matthew Tuck. Dan Mosedale - and Dawn Endico are employees of Mozilla.org responsible - for the installation of Bugzilla there, and are very - frequent code contributors. Terry Weissman originally - ported Bugzilla, but "these days, Terry just hangs around - and heckles." The rest of us are mostly transient - developers; Bugzilla suits our needs, and we contribute - code as we have needs for updates. + Bugzilla maintenance has been in a state of flux recently. + Please check <ulink + url="http://www.mozilla.org/projects/bugzilla/">the Bugzilla Project Page for the latest details. </ulink> </para> </answer> </qandaentry> @@ -126,8 +116,7 @@ <qandaentry> <question> <para> - How does Bugzilla stack up against other bug-tracking - databases? + How does Bugzilla stack up against other bug-tracking databases? </para> </question> <answer> @@ -143,7 +132,7 @@ flexibility, and superior ease-of-use. </para> <para> - If you happen to be a commercial Bugzilla vendor, please + If you happen to be a commercial bug-tracker vendor, please step forward with a rebuttal so I can include it in the FAQ. We're not in pursuit of Bugzilla ueber alles; we simply love having a powerful, open-source tool to get our @@ -160,9 +149,8 @@ </question> <answer> <para> - You can't. However, the administrative account can, by - simply opening your user account in editusers.cgi and - changing the login name. + You can't. However, the administrative account can, by simply opening + your user account in editusers.cgi and changing the login name. </para> </answer> </qandaentry> @@ -170,26 +158,24 @@ <qandaentry> <question> <para> - Why doesn't Bugzilla offer this or that feature or - compatability with this other tracking software? + Why doesn't Bugzilla offer this or that feature or compatability + with this other tracking software? </para> </question> <answer> <para> - It may be that the support has not been built yet, or that - you have not yet found it. Bugzilla is making tremendous - strides in usability, customizability, scalability, and - user interface. It is widely considered the most complete - and popular open-source bug-tracking software in - existence. + It may be that the support has not been built yet, or that you + have not yet found it. Bugzilla is making tremendous strides in + usability, customizability, scalability, and user interface. It + is widely considered the most complete and popular open-source + bug-tracking software in existence. </para> <para> - That doesn't mean it can't use improvement! You can help - the project along by either hacking a patch yourself that - supports the functionality you require, or else submitting - a "Request for Enhancement" (RFE) using the bug submission - interface at <ulink - url="http://bugzilla.mozilla.org/">bugzilla.mozilla.org</ulink>. + That doesn't mean it can't use improvement! + You can help the project along by either hacking a patch yourself + that supports the functionality you require, or else submitting a + "Request for Enhancement" (RFE) using the bug submission interface + at <ulink url="http://bugzilla.mozilla.org/">bugzilla.mozilla.org</ulink>. </para> </answer> </qandaentry> @@ -205,40 +191,37 @@ <para>Terry Weissman answers, <blockquote> <para> - You're not the only one. But <emphasis>I</emphasis> am - not very interested. I'm not a real SQL or database - person. I just wanted to make a useful tool, and build - it on top of free software. So, I picked MySQL, and - learned SQL by staring at the MySQL manual and some - code lying around here, and wrote Bugzilla. I didn't - know that Enum's were non-standard SQL. I'm not sure - if I would have cared, but I didn't even know. So, to - me, things are "portable" because it uses MySQL, and - MySQL is portable enough. I fully understand (now) - that people want to be portable to other databases, - but that's never been a real concern of mine. + You're not the only one. But <emphasis>I</emphasis> am not very interested. I'm not + a real SQL or database person. I just wanted to make a useful tool, + and build it on top of free software. So, I picked MySQL, and + learned SQL by staring at the MySQL manual and some code lying + around here, and + wrote Bugzilla. I didn't know that Enum's were non-standard SQL. + I'm not sure if I would have cared, but I didn't even know. So, to + me, things are "portable" because it uses MySQL, and MySQL is + portable enough. I fully understand (now) that people want to be + portable to other databases, but that's never been a real concern + of mine. </para> </blockquote> </para> <para> - Things aren't quite that grim these days, however. Terry - pretty much sums up much of the thinking many of us have - for Bugzilla, but there is light on the horizon for - database-independence! Here are some options: + Things aren't quite that grim these days, however. Terry pretty much + sums up much of the thinking many of us have for Bugzilla, but there + is light on the horizon for database-independence! Here are some options: </para> <simplelist> <member> - <emphasis><ulink url="http://bugzilla.redhat.com/">Red - Hat Bugzilla</ulink></emphasis>: Runs a modified - Bugzilla 2.8 atop an Oracle database. + <emphasis><ulink url="http://bugzilla.redhat.com/">Red Hat Bugzilla</ulink></emphasis>: + Runs a modified Bugzilla 2.8 atop an Oracle database. </member> <member> - <emphasis><ulink - url="http://sourceforge.net/projects/interzilla">Interzilla</ulink></emphasis>: A project to run Bugzilla on Interbase. No code released yet, however. + <emphasis><ulink url="http://sourceforge.net/projects/interzilla">Interzilla</ulink></emphasis>: + A project to run Bugzilla on Interbase. No code released yet, however. </member> <member> - <emphasis>Bugzilla 3.0</emphasis>: One of the primary - stated goals is multiple database support. + <emphasis>Bugzilla 3.0</emphasis>: One of the primary stated goals + is multiple database support. </member> </simplelist> </answer> @@ -247,40 +230,36 @@ <qandaentry> <question> <para> - Why do the scripts say "/usr/bonsaitools/bin/perl" instead - of "/usr/bin/perl" or something else? + Why do the scripts say "/usr/bonsaitools/bin/perl" instead of + "/usr/bin/perl" or something else? </para> </question> <answer> <para> - Mozilla.org uses /usr/bonsaitools/bin/perl. The prime - rule in making submissions is "don't break - bugzilla.mozilla.org". If it breaks it, your patch will be - reverted faster than you can do a diff. + Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making + submissions is "don't break bugzilla.mozilla.org". If it breaks it, your + patch will be reverted faster than you can do a diff. </para> <para> - Here's Terry Weissman's comment, for some historical - context: + Here's Terry Weissman's comment, for some historical context: <blockquote> <para> - [This was] purely my own convention. I wanted a place - to put a version of Perl and other tools that was - strictly under my control for the various webtools, - and not subject to anyone else. Edit it to point to - whatever you like. + [This was] purely my own convention. I wanted a place to put a version of + Perl and other tools that was strictly under my control for the + various webtools, and not subject to anyone else. Edit it to point + to whatever you like. </para> <note> <para> - We always recommend that, if possible, you keep the - path as /usr/bonsaitools/bin/perl, and simply add a - /usr/bonsaitools and /usr/bonsaitools/bin directory, - then symlink your version of perl to - /usr/bonsaitools/bin/perl. This will make upgrading + We always recommend that, if possible, you keep the path + as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools + and /usr/bonsaitools/bin directory, then symlink your version + of perl to /usr/bonsaitools/bin/perl. This will make upgrading your Bugzilla much easier in the future. </para> <para> - Obviously, if you do not have root access to your - Bugzilla box, our suggestion is irrelevant. + Obviously, if you do not have root access to your Bugzilla + box, our suggestion is irrelevant. </para> </note> </blockquote> @@ -297,8 +276,7 @@ <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. + Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide. </para> </note> </para> @@ -310,29 +288,27 @@ </question> <answer> <para> - Red Hat Bugzilla is arguably more user-friendly, - customizable, and scalable than stock Bugzilla. Check it - out at http://bugzilla.redhat.com and the sources at - ftp://people.redhat.com/dkl/. They've set their Bugzilla - up to work with Oracle out of the box. Note that Redhat - Bugzilla is based upon the 2.8 Bugzilla tree; Bugzilla has - made some tremendous advances since the 2.8 release. Why - not download both Bugzillas to check out the differences - for yourself? + Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable + than stock Bugzilla. Check it out at + http://bugzilla.redhat.com and the sources at ftp://people.redhat.com/dkl/. + They've set their Bugzilla up to work with Oracle out of the box. + Note that Redhat Bugzilla is based upon the 2.8 Bugzilla tree; + Bugzilla has made some tremendous advances since the 2.8 release. + Why not download both Bugzillas to check out the differences for + yourself? </para> <para> - Dave Lawrence, the original Red Hat Bugzilla maintainer, - mentions: + Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions: <blockquote> <para> - Somebody needs to take the ball and run with it. I'm - the only maintainer and am very pressed for time. + Somebody needs to take the ball and run with it. I'm the only + maintainer and am very pressed for time. </para> - </blockquote> If you, or someone you know, has the time - and expertise to do the integration work so main-tree - Bugzilla 2.12 and higher integrates the Red Hat Bugzilla - Oracle modifications, please donate your time to - supporting the Bugzilla project. + </blockquote> + If you, or someone you know, has the time and expertise to do the integration + work so main-tree Bugzilla 2.12 and higher integrates the Red + Hat Bugzilla Oracle modifications, please donate your + time to supporting the Bugzilla project. </para> </answer> </qandaentry> @@ -348,123 +324,102 @@ <emphasis>Dave Lawrence</emphasis>: <blockquote> <para> - 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. + 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. </para> <para> - I do want to land the changes that I have made to - Bugzilla but I may have to back out a good deal and - make a different version of Red Hat's Bugzilla for - checking in to CVS. Especially the cosmetic changes - because it seems they may not fit the general public. - I will do that as soon as I can. I also still do my - regular QA responsibilities along with Bugzilla so - time is difficult sometimes to come by. + I do want to land the changes that I have made to Bugzilla but I may + have to back out a good deal and make a different version of Red Hat's + Bugzilla for checking in to CVS. Especially the cosmetic changes because it + seems they may not fit the general public. I will do that as soon as I can. + I also still do my regular QA responsibilities along with Bugzilla so time + is difficult sometimes to come by. </para> <para> - There are also a good deal of other changes that were - requested by management for things like support - contracts and different permission groups for making - bugs private. Here is a short list of the major + There are also a good deal of other changes that were requested by + management for things like support contracts and different permission + groups for making bugs private. Here is a short list of the major changes that have been made: </para> <orderedlist> <listitem> <para> - No enum types. All old enum types are now separate - smaller tables. + No enum types. All old enum types are now separate smaller tables. </para> </listitem> <listitem> <para> - No bit wise operations. Not all databases support - this so they were changed to a more generic way of - doing this task + No bit wise operations. Not all databases support this so they were + changed to a more generic way of doing this task </para> </listitem> <listitem> <para> - Bug reports can only be altered by the reporter, - assignee, or a privileged bugzilla user. The rest - of the world can see the bug but in a - non-changeable format (unless the bug has been - marked private). They can however add comments, - add and remove themselves from the CC list + Bug reports can only be altered by the reporter, assignee, or a + privileged bugzilla user. The rest of the world can see the bug but in + a non-changeable format (unless the bug has been marked private). They + can however add comments, add and remove themselves from the CC list </para> </listitem> <listitem> <para> - Different group scheme. Each group has an id - number related to it. There is a user_group table - which contains userid to groupid mappings to - determine which groups each user belongs to. - Additionally there is a bug_group table that has - bugid to groupid mappings to show which groups can - see a particular bug. If there are no entries for - a bug in this table then the bug is public. + Different group scheme. Each group has an id number related to it. + There is a user_group table which contains userid to groupid mappings + to determine which groups each user belongs to. Additionally there is + a bug_group table that has bugid to groupid mappings to show which + groups can see a particular bug. If there are no entries for a bug in + this table then the bug is public. </para> </listitem> <listitem> <para> - Product groups. product_table created to only - allow certain products to be visible for certain - groups in both bug entry and query. This was + Product groups. product_table created to only allow certain products to + be visible for certain groups in both bug entry and query. This was particulary helpful for support contracts. </para> </listitem> <listitem> <para> - Of course many (too many) changes to Bugzilla code - itself to allow use with Oracle and still allow - operation with Mysql if so desired. Currently if - you use Mysql it is set to use Mysql's old - permission scheme to keep breakage to a minimum. - Hopefully one day this will standardize on one - style which may of course be something completely + Of course many (too many) changes to Bugzilla code itself to allow use + with Oracle and still allow operation with Mysql if so desired. + Currently if you use Mysql it is set to use Mysql's old permission + scheme to keep breakage to a minimum. Hopefully one day this will + standardize on one style which may of course be something completely different. </para> </listitem> <listitem> <para> - Uses Text::Template perl module for rendering of - the dynamic HTML pages such as enter_bug.cgi, - query.cgi, bug_form.pl, and for the header and - footer parts of the page. This allows the html to - be separate from the perl code for customizing the - look and feel of the page to one's preference. + Uses Text::Template perl module for rendering of the dynamic HTML pages + such as enter_bug.cgi, query.cgi, bug_form.pl, and for the header and + footer parts of the page. This allows the html to be separate from the + perl code for customizing the look and feel of the page to one's + preference. </para> </listitem> <listitem> <para> - There are many other smaller changes. There is - also a port to Oracle that I have been working on - as time permits but is not completely finished but - somewhat usable. I will merge it into our standard - code base when it becomes production quality. - Unfortunately there will have to be some - conditionals in the code to make it work with - other than Oracle due to some differences between - Oracle and Mysql. + There are many other smaller changes. There is also a port to Oracle + that I have been working on as time permits but is not completely + finished but somewhat usable. I will merge it into our standard code + base when it becomes production quality. Unfortunately there will have + to be some conditionals in the code to make it work with other than + Oracle due to some differences between Oracle and Mysql. </para> </listitem> </orderedlist> <para> - Both the Mysql and Oracle versions of our current code - base are available from ftp://people.redhat.com/dkl. - If Terry/Tara wants I can submit patch files for all - of the changes I have made and he can determine what - is suitable for addition to the main bugzilla cade - base. But for me to commit changes to the actual CVS I - will need to back out alot of things that are not - suitable for the rest of the Bugzilla community. I am - open to suggestions. + Both the Mysql and Oracle versions of our current code base are + available from ftp://people.redhat.com/dkl. If Terry/Tara wants I can submit + patch files for all of the changes I have made and he can determine what is + suitable for addition to the main bugzilla cade base. But for me to commit + changes to the actual CVS I will need to back out alot of things that are + not suitable for the rest of the Bugzilla community. I am open to + suggestions. </para> </blockquote> </para> @@ -482,66 +437,57 @@ <note> <para> This information is somewhat dated; I last updated it - 7 June 2000. Please see the "Variants" section of - "The Bugzilla Guide" for more up-to-date information - regarding Red Hat Bugzilla. + 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>: + </note> + <emphasis>Dave Lawrence</emphasis>: <blockquote> <para> - I suppose the current thread warrants an update - on the status of Oracle and bugzilla ;) We have now - been running Bugzilla 2.8 on Oracle for the last two - days in our production environment. I tried to do as - much testing as possible with it before going live - which is some of the reason for the long delay. I did - not get enough feedback as I would have liked from - internal developers to help weed out any bugs still - left so I said "Fine, i will take it live and then I - will get the feedback I want :)" So it is now starting - to stabilize and it running quite well after working - feverishly the last two days fixing problems as soon - as they came in from the outside world. The current - branch in cvs is up2date if anyone would like to grab - it and try it out. The oracle _setup.pl is broken - right now due to some last minute changes but I will - update that soon. Therefore you would probably need to - create the database tables the old fashioned way using - the supplied sql creation scripts located in the - ./oracle directory. We have heavy optimizations in the - database it self thanks to the in-house DBA here at - Red Hat so it is running quite fast. The database - itself is located on a dual PII450 with 1GB ram and 14 - high voltage differential raided scsi drives. The - tables and indexes are partitioned in 4 chuncks across - the raided drive which is nice because when ever you - need to do a full table scan, it is actually starting - in 4 different locations on 4 different drives - simultaneously. And the indexes of course are on - separate drives from the data so that speeds things up - tremendously. When I can find the time I will - document all that we have done to get this thing going - to help others that may need it. + I suppose the current thread warrants an update on the status of + Oracle and bugzilla ;) We have now been running Bugzilla 2.8 on + Oracle for the last two days in our production environment. I + tried to do as much testing as possible with it before going live + which is some of the reason for the long delay. I did not get + enough feedback as I would have liked from internal developers to + help weed out any bugs still left so I said "Fine, i will take it + live and then I will get the feedback I want :)" So it is now + starting to stabilize and it running quite well after working + feverishly the last two days fixing problems as soon as they came + in from the outside world. The current branch in cvs is up2date if + anyone would like to grab it and try it out. The oracle _setup.pl + is broken right now due to some last minute changes but I will + update that soon. Therefore you would probably need to create the + database tables the old fashioned way using the supplied sql + creation scripts located in the ./oracle directory. We have heavy + optimizations in the database it self thanks to the in-house DBA + here at Red Hat so it is running quite fast. The database itself + is located on a dual PII450 with 1GB ram and 14 high voltage + differential raided scsi drives. The tables and indexes are + partitioned in 4 chuncks across the raided drive which is nice + because when ever you need to do a full table scan, it is actually + starting in 4 different locations on 4 different drives + simultaneously. And the indexes of course are on separate drives + from the data so that speeds things up tremendously. When I can + find the time I will document all that we have done to get this + 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 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 appreciated. What - we are using now is what I call a best first effort. - It definitely can be improved on and may even need - complete rewrites in a lot of areas. A lot of changes - may have to be made in the way Bugzilla does things - currently to make this transition to a more generic - database interface. Fortunately when making the - Oracle changes I made sure I didn't do anything that - I would consider Oracle specific and could not be - easily done with other databases. Alot of the sql - statements need to be broken up into smaller utilities - that themselves would need to make decisions on what - database they are using but the majority of the code - can be made database neutral. + 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 + appreciated. What we are using now is what I call a best first + effort. It definitely can be improved on and may even need + complete rewrites in a lot of areas. A lot of changes may have to + be made in the way Bugzilla does things currently to make this + transition to a more generic database interface. Fortunately when + making the Oracle changes I made sure I didn't do anything that I + would consider Oracle specific and could not be easily done with + other databases. Alot of the sql statements need to be broken up + into smaller utilities that themselves would need to make + decisions on what database they are using but the majority of the + code can be made database neutral. </para> </blockquote> </para> @@ -552,78 +498,21 @@ <qandadiv id="faq_loki"> <title>Loki Bugzilla (AKA Fenris)</title> - <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> - <para> - What about Loki Bugzilla? - </para> - </question> - <answer> - <para> - Loki Games has a customized version of Bugzilla available - at http://fenris.lokigames.com. From that page, - <blockquote> - <para> - You may have noticed that Fenris is a fork from - Bugzilla-- our patches weren't suitable for - integration --and a few people have expressed interest - in the code. Fenris has one major improvement over - Bugzilla, and that is individual comments are not - appended onto a string blob, they are stored as a - record in a separate table. This allows you to, for - instance, separate comments out according to privilege - levels in case your bug database could contain - sensitive information not for public eyes. We also - provide things like email hiding to protect user's - privacy, additional fields such as 'user_affected' in - case someone enters someone else's bug, comment - editing and deletion, and more conditional system - variables than Bugzilla does (turn off attachments, - qacontact, etc.). - </para> - </blockquote> - </para> - </answer> - </qandaentry> <qandaentry> <question> <para> - Who maintains Fenris (Loki Bugzilla) now? + What is Loki Bugzilla (Fenris)? </para> </question> <answer> <para> - Raphael Barrerro <raistlin@lokigames.com>. Michael - Vance created the initial fork, but no longer maintains - the project. + Loki Games has a customized version of Bugzilla available at + <ulink url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. There are some advantages to using Fenris, chief being separation of comments based upon user privacy level, data hiding, forced login for any data retrieval, and some additional fields. Loki has mainted their code, originally a fork from the Bugzilla 2.8 code base, and it is quite a bit different than stock Bugzilla at this point. I recommend you stick with official Bugzilla version &bz-ver; rather than using a fork, but it's up to you. </para> </answer> </qandaentry> - <qandaentry> - <question> - <para> - - </para> - </question> - </qandaentry> </qandadiv> <qandadiv id="faq_phb"> @@ -631,9 +520,8 @@ <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 - :) + 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> @@ -641,15 +529,14 @@ <qandaentry> <question> <para> - Is Bugzilla web-based or do you have to have specific - software or specific operating system on your machine? + Is Bugzilla web-based or do you have to have specific software or + specific operating system on your machine? </para> </question> <answer> <para> - It is web and e-mail based. You can edit bugs by sending - specially formatted email to a properly configured - Bugzilla, or control via the web. + It is web and e-mail based. You can edit bugs by sending specially + formatted email to a properly configured Bugzilla, or control via the web. </para> </answer> </qandaentry> @@ -657,18 +544,14 @@ <qandaentry> <question> <para> - Has anyone you know of already done any Bugzilla - integration with Perforce (SCM software)? + Has anyone you know of already done any Bugzilla integration with + Perforce (SCM software)? </para> </question> <answer> <para> - Yes! You can find more information elsewhere in "The - Bugzilla Guide" in the "Integration with Third-Party - Products" section. The section on Perforce isn't very - large, but as the maintainer of the Guide is charged with - Perforce/Bugzilla integration by his company, you can - expect this section to grow. + Yes! You can find more information elsewhere in "The Bugzilla + Guide" in the "Integration with Third-Party Products" section. </para> </answer> </qandaentry> @@ -684,8 +567,8 @@ Absolutely! You can track up to a "soft-limit" of around 64 individual "Products", that can each be composed of as many "Components" as you want. Check the Administration - section of the Bugzilla Guide for more information - regarding setting up Products and Components. + section of the Bugzilla Guide for more information regarding + setting up Products and Components. </para> </answer> </qandaentry> @@ -693,9 +576,8 @@ <qandaentry> <question> <para> - If I am on many projects, and search for all bugs assigned - to me, will Bugzilla list them for me and allow me to sort - by project, severity etc? + If I am on many projects, and search for all bugs assigned to me, will + Bugzilla list them for me and allow me to sort by project, severity etc? </para> </question> <answer> @@ -708,20 +590,18 @@ <qandaentry> <question> <para> - Does Bugzilla allow attachments (text, screenshots, urls - etc)? If yes, are there any that are NOT allowed? + Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes, + are there any that are NOT allowed? </para> </question> <answer> <para> - Yes. There are many specific MIME-types that are - pre-defined by Bugzilla, but you may specify any arbitrary - MIME-type you need when you upload the file. Since all - attachments are stored in the database, however, I - recommend storing large binary attachments elsewhere in - the web server's file system and providing a hyperlink as - a comment, or in the provided "URL" field in the bug - report. + Yes. There are many specific MIME-types that are pre-defined by Bugzilla, + but you may specify any arbitrary MIME-type you need when you + upload the file. Since all attachments are stored in the database, + however, I recommend storing large binary attachments elsewhere + in the web server's file system and providing a hyperlink + as a comment, or in the provided "URL" field in the bug report. </para> </answer> </qandaentry> @@ -729,17 +609,16 @@ <qandaentry> <question> <para> - Does Bugzilla allow us to define our own priorities and - levels? Do we have complete freedom to change the labels - of fields and format of them, and the choice of acceptable - values? + Does Bugzilla allow us to define our own priorities and levels? Do we + have complete freedom to change the labels of fields and format of them, and + the choice of acceptable values? </para> </question> <answer> <para> - Yes. However, modifying some fields, notably those - related to bug progression states, also require adjusting - the program logic to compensate for the change. + Yes. However, modifying some fields, notably those related to bug + progression states, also require adjusting the program logic to + compensate for the change. </para> </answer> </qandaentry> @@ -748,65 +627,70 @@ <qandaentry> <question> <para> - The index.html page doesn't show the footer. It's really - annoying to have to go to the querypage just to check my - "my bugs" link. How do I get a footer on static HTML - pages? + The index.html page doesn't show the footer. It's really annoying to have + to go to the querypage just to check my "my bugs" link. How do I get a footer + on static HTML pages? </para> </question> <answer> <para> - This was a late-breaking question for the Guide, so I just - have to quote the relevant newsgroup thread on it. + This was a late-breaking question for the Guide, so I just have to + quote the relevant newsgroup thread on it. </para> <literallayout> -> AFAIK, most sites (even if they have SSI enabled) won't have #exec - cmd > enabled. Perhaps what would be better is a #include - virtual and a > footer.cgi the basically has the "require - 'CGI.pl' and PutFooter command. > > Please note that under - most configurations, this also requires naming > the file - from index.html to index.shtml (and making sure that it - will > still be reconized as an index). Personally, I - think this is better on > a per-installation basis - (perhaps add something to the FAQ that says how > to do - this). Good point. Yeah, easy enough to do, that it - shouldn't be a big deal for someone to take it on if they - want it. FAQ is a good place for it. > Dave Miller wrote: - > >> I did a little experimenting with getting the command - menu and footer on >> the end of the index page while - leaving it as an HTML file... >> >> I was successful. :) - >> >> I added this line: >> >> <!--#exec - cmd="/usr/bin/perl -e "require 'CGI.pl'; - >>PutFooter();"" --> >> >> Just before the - </BODY> </HTML> at the end of the file. And - it worked. >> >> Thought I'd toss that out there. Should - I check this in? For those that >> have SSI disabled, - it'll act like a comment, so I wouldn't think it would >> - break anything. +> AFAIK, most sites (even if they have SSI enabled) won't have #exec cmd +> enabled. Perhaps what would be better is a #include virtual and a +> footer.cgi the basically has the "require 'CGI.pl' and PutFooter command. +> +> Please note that under most configurations, this also requires naming +> the file from index.html to index.shtml (and making sure that it will +> still be reconized as an index). Personally, I think this is better on +> a per-installation basis (perhaps add something to the FAQ that says how +> to do this). + +Good point. Yeah, easy enough to do, that it shouldn't be a big deal for +someone to take it on if they want it. FAQ is a good place for it. + +> Dave Miller wrote: +> +>> I did a little experimenting with getting the command menu and footer on +>> the end of the index page while leaving it as an HTML file... +>> +>> I was successful. :) +>> +>> I added this line: +>> +>> <!--#exec cmd="/usr/bin/perl -e "require 'CGI.pl'; +>>PutFooter();"" --> +>> +>> Just before the </BODY> </HTML> at the end of the file. And it worked. +>> +>> Thought I'd toss that out there. Should I check this in? For those that +>> have SSI disabled, it'll act like a comment, so I wouldn't think it would +>> break anything. </literallayout> </answer> </qandaentry> <qandaentry> <question> <para> - Does Bugzilla provide any reporting features, metrics, - graphs, etc? You know, the type of stuff that management - likes to see. :) + Does Bugzilla provide any reporting features, metrics, graphs, etc? You + know, the type of stuff that management likes to see. :) </para> </question> <answer> <para> - Yes. Look at <ulink - url="http://bugzilla.mozilla.org/reports.cgi"> http://bugzilla.mozilla.org/reports.cgi</ulink> for basic reporting facilities. + Yes. Look at <ulink url="http://bugzilla.mozilla.org/reports.cgi"> + http://bugzilla.mozilla.org/reports.cgi</ulink> for basic reporting + facilities. </para> <para> - For more advanced reporting, I recommend hooking up a - professional reporting package, such as Crystal Reports, - and use ODBC to access the MySQL database. You can do a - lot through the Query page of Bugzilla as well, but right - now Advanced Reporting is much better accomplished through - third-party utilities that can interface with the database - directly. + For more advanced reporting, I recommend hooking up a professional + reporting package, such as Crystal Reports, and use ODBC to access + the MySQL database. You can do a lot through the Query page of + Bugzilla as well, but right now Advanced Reporting is much + better accomplished through third-party utilities that can + interface with the database directly. </para> <para> Advanced Reporting is a Bugzilla 3.X proposed feature. @@ -817,16 +701,15 @@ <qandaentry> <question> <para> - Is there email notification and if so, what do you see - when you get an email? Do you see bug number and title or - is it only the number? + Is there email notification and if so, what do you see when you get an + email? Do you see bug number and title or is it only the number? </para> </question> <answer> <para> - Email notification is user-configurable. The bug id and - Topic of the bug report accompany each email notification, - along with a list of the changes made. + Email notification is user-configurable. The bug id and Topic + of the bug report accompany each email notification, along with + a list of the changes made. </para> </answer> </qandaentry> @@ -848,24 +731,22 @@ <qandaentry> <question> <para> - If there is email notification, do users have to have any - particular type of email application? + If there is email notification, do users have to have any particular + type of email application? </para> </question> <answer> <para> - Bugzilla email is sent in plain text, the most compatible - mail format on the planet. + Bugzilla email is sent in plain text, the most compatible mail format + on the planet. <note> <para> - If you decide to use the bugzilla_email integration - features to allow Bugzilla to record responses to mail - with the associated bug, you may need to caution your - users to set their mailer to "respond to messages in - the format in which they were sent". For security - reasons Bugzilla ignores HTML tags in comments, and if - a user sends HTML-based email into Bugzilla the - resulting comment looks downright awful. + If you decide to use the bugzilla_email integration features + to allow Bugzilla to record responses to mail with the associated bug, + you may need to caution your users to set their mailer to "respond + to messages in the format in which they were sent". For security reasons + Bugzilla ignores HTML tags in comments, and if a user sends HTML-based + email into Bugzilla the resulting comment looks downright awful. </para> </note> </para> @@ -875,19 +756,17 @@ <qandaentry> <question> <para> - If I just wanted to track certain bugs, as they go - through life, can I set it up to alert me via email - whenever that bug changes, whether it be owner, status or - description etc.? + If I just wanted to track certain bugs, as they go through life, can I + set it up to alert me via email whenever that bug changes, whether it be + owner, status or description etc.? </para> </question> <answer> <para> - Yes. Place yourself in the "cc" field of the bug you wish - to monitor. Then change your "Notify me of changes to" - field in the Email Settings tab of the User Preferences - screen in Bugzilla to the "Only those bugs which I am - listed on the CC line" option. + Yes. Place yourself in the "cc" field of the bug you wish to monitor. + Then change your "Notify me of changes to" field in the Email Settings + tab of the User Preferences screen in Bugzilla to the "Only those + bugs which I am listed on the CC line" option. </para> </answer> </qandaentry> @@ -895,34 +774,32 @@ <qandaentry> <question> <para> - Does Bugzilla allow data to be imported and exported? If I - had outsiders write up a bug report using a MS Word bug - template, could that template be imported into "matching" - fields? If I wanted to take the results of a query and - export that data to MS Excel, could I do that? + Does Bugzilla allow data to be imported and exported? If I had outsiders + write up a bug report using a MS Word bug template, could that template be + imported into "matching" fields? If I wanted to take the results of a query + and export that data to MS Excel, could I do that? </para> </question> <answer> <para> - Mozilla allows data export through a custom DTD in XML - format. It does not, however, export to specific formats - other than the XML Mozilla DTD. Importing the data into - Excel or any other application is left as an exercise for - the reader. + Mozilla allows data export through a custom DTD in XML format. + It does not, however, export to specific formats other than the + XML Mozilla DTD. Importing the data into Excel or any other application + is left as an exercise for the reader. </para> <para> - If you create import filters to other applications from - Mozilla's XML, please submit your modifications for - inclusion in future Bugzilla distributions. + If you create import filters to other applications from Mozilla's XML, + please submit your modifications for inclusion in future Bugzilla + distributions. </para> <para> - As for data import, any application can send data to - Bugzilla through the HTTP protocol, or through Mozilla's - XML API. However, it seems kind of silly to put another - front-end in front of Bugzilla; it makes more sense to - create a simplified bug submission form in HTML. You can - find an excellent example at <ulink - url="http://www.mozilla.org/quality/help/bugzilla-helper.html"> http://www.mozilla.org/quality/help/bugzilla-helper.html</ulink> + As for data import, any application can send data to Bugzilla through + the HTTP protocol, or through Mozilla's XML API. However, it seems + kind of silly to put another front-end in front of Bugzilla; + it makes more sense to create a simplified bug submission form in + HTML. You can find an excellent example at + <ulink url="http://www.mozilla.org/quality/help/bugzilla-helper.html"> + http://www.mozilla.org/quality/help/bugzilla-helper.html</ulink> </para> </answer> </qandaentry> @@ -930,9 +807,9 @@ <qandaentry> <question> <para> - Does Bugzilla allow fields to be added, changed or - deleted? If I want to customize the bug submission form to - meet our needs, can I do that using our terminology? + Does Bugzilla allow fields to be added, changed or deleted? If I want to + customize the bug submission form to meet our needs, can I do that using our + terminology? </para> </question> <answer> @@ -945,16 +822,16 @@ <qandaentry> <question> <para> - Has anyone converted Bugzilla to another language to be - used in other countries? Is it localizable? + Has anyone converted Bugzilla to another language to be used in other + countries? Is it localizable? </para> </question> <answer> <para> - Currently, no. Internationalization support for Perl did - not exist in a robust fashion until the recent release of - version 5.6.0; Bugzilla is, and likely will remain (until - 3.X) completely non-localized. + Currently, no. Internationalization support for Perl did not + exist in a robust fashion until the recent release of version 5.6.0; + Bugzilla is, and likely will remain (until 3.X) completely + non-localized. </para> </answer> </qandaentry> @@ -962,8 +839,8 @@ <qandaentry> <question> <para> - Can a user create and save reports? Can they do this in - Word format? Excel format? + Can a user create and save reports? Can they do this in Word format? + Excel format? </para> </question> <answer> @@ -989,15 +866,13 @@ <qandaentry> <question> <para> - Can a user modify an existing report and then save it into - another name? + Can a user modify an existing report and then save it into another name? </para> </question> <answer> <para> - You can save an unlimited number of queries in Bugzilla. - You are free to modify them and rename them to your - heart's desire. + You can save an unlimited number of queries in Bugzilla. You are free + to modify them and rename them to your heart's desire. </para> </answer> </qandaentry> @@ -1005,15 +880,14 @@ <qandaentry> <question> <para> - Does Bugzilla have the ability to search by word, phrase, - compound search? + Does Bugzilla have the ability to search by word, phrase, compound + search? </para> </question> <answer> <para> - You have no idea. Bugzilla's query interface, - particularly with the advanced Boolean operators, is - incredibly versatile. + You have no idea. Bugzilla's query interface, particularly with the + advanced Boolean operators, is incredibly versatile. </para> </answer> </qandaentry> @@ -1021,8 +895,8 @@ <qandaentry> <question> <para> - Can the admin person establish separate group and - individual user privileges? + Can the admin person establish separate group and individual user + privileges? </para> </question> <answer> @@ -1035,17 +909,15 @@ <qandaentry> <question> <para> - Does Bugzilla provide record locking when there is - simultaneous access to the same bug? Does the second - person get a notice that the bug is in use or how are they - notified? + Does Bugzilla provide record locking when there is simultaneous access + to the same bug? Does the second person get a notice that the bug is in use + or how are they notified? </para> </question> <answer> <para> - Bugzilla does not lock records. It provides mid-air - collision detection, and offers the offending user a - choice of options to deal with the conflict. + Bugzilla does not lock records. It provides mid-air collision detection, + and offers the offending user a choice of options to deal with the conflict. </para> </answer> </qandaentry> @@ -1058,10 +930,10 @@ </question> <answer> <para> - MySQL, the database back-end for Bugzilla, allows - hot-backup of data. You can find strategies for dealing - with backup considerations at <ulink - url="http://www.mysql.com/doc/B/a/Backup.html"> http://www.mysql.com/doc/B/a/Backup.html</ulink> + MySQL, the database back-end for Bugzilla, allows hot-backup of data. + You can find strategies for dealing with backup considerations + at <ulink url="http://www.mysql.com/doc/B/a/Backup.html"> + http://www.mysql.com/doc/B/a/Backup.html</ulink> </para> </answer> </qandaentry> @@ -1074,8 +946,8 @@ </question> <answer> <para> - Yes. However, commits to the database must wait until the - tables are unlocked. Bugzilla databases are typically + Yes. However, commits to the database must wait + until the tables are unlocked. Bugzilla databases are typically very small, and backups routinely take less than a minute. </para> </answer> @@ -1084,33 +956,29 @@ <qandaentry> <question> <para> - What type of human resources are needed to be on staff to - install and maintain Bugzilla? Specifically, what type of - skills does the person need to have? I need to find out if - we were to go with Bugzilla, what types of individuals - would we need to hire and how much would that cost vs - buying an "Out-of-the-Box" solution. + What type of human resources are needed to be on staff to install and + maintain Bugzilla? Specifically, what type of skills does the person need to + have? I need to find out if we were to go with Bugzilla, what types of + individuals would we need to hire and how much would that cost vs buying an + "Out-of-the-Box" solution. </para> </question> <answer> <para> - If Bugzilla is set up correctly from the start, continuing - maintenance needs are minimal and can be completed by - unskilled labor. Things like rotate backup tapes and - check log files for the word "error". + If Bugzilla is set up correctly from the start, continuing maintenance needs + are minimal and can be completed by unskilled labor. Things like rotate + backup tapes and check log files for the word "error". </para> <para> - Commercial Bug-tracking software typically costs somewhere - upwards of $20,000 or more for 5-10 floating licenses. - Bugzilla consultation is available from skilled members of - the newsgroup. + Commercial Bug-tracking software typically costs somewhere upwards + of $20,000 or more for 5-10 floating licenses. Bugzilla consultation + is available from skilled members of the newsgroup. </para> <para> - As an example, as of this writing I typically charge $115 - for the first hour, and $89 each hour thereafter for - consulting work. It takes me three to five hours to make - Bugzilla happy on a Development installation of - Linux-Mandrake. + As an example, as of this writing I typically charge + $115 for the first hour, and $89 each hour thereafter + for consulting work. It takes me three to five hours to make Bugzilla + happy on a Development installation of Linux-Mandrake. </para> </answer> </qandaentry> @@ -1118,22 +986,20 @@ <qandaentry> <question> <para> - What time frame are we looking at if we decide to hire - people to install and maintain the Bugzilla? Is this - something that takes hours or weeks to install and a - couple of hours per week to maintain and customize or is - this a multi-week install process, plus a full time job - for 1 person, 2 people, etc? + What time frame are we looking at if we decide to hire people to install + and maintain the Bugzilla? Is this something that takes hours or weeks to + install and a couple of hours per week to maintain and customize or is this + a multi-week install process, plus a full time job for 1 person, 2 people, + etc? </para> </question> <answer> <para> - It all depends on your level of commitment. Someone with - much Bugzilla experience can get you up and running in - less than a day, and your Bugzilla install can run - untended for years. If your Bugzilla strategy is critical - to your business workflow, hire somebody with reasonable - UNIX or Perl skills to handle your process management and + It all depends on your level of commitment. Someone with much Bugzilla + experience can get you up and running in less than a day, and + your Bugzilla install can run untended for years. If your + Bugzilla strategy is critical to your business workflow, hire somebody + with reasonable UNIX or Perl skills to handle your process management and bug-tracking maintenance & customization. </para> </answer> @@ -1142,16 +1008,14 @@ <qandaentry> <question> <para> - Is there any licensing fee or other fees for using - Bugzilla? Any out-of-pocket cost other than the bodies - needed as identified above? + Is there any licensing fee or other fees for using Bugzilla? Any + out-of-pocket cost other than the bodies needed as identified above? </para> </question> <answer> <para> - No. MySQL asks, if you find their product valuable, that - you purchase a support contract from them that suits your - needs. + No. MySQL asks, if you find their product valuable, that you purchase + a support contract from them that suits your needs. </para> </answer> </qandaentry> @@ -1167,8 +1031,9 @@ </question> <answer> <para> - Check <ulink - url="http://www.mozilla.org/projects/bugzilla/"> http://www.mozilla.org/projects/bugzilla/</ulink> for details. Once you download it, untar it, read the Bugzilla Guide. + Check <ulink url="http://www.mozilla.org/projects/bugzilla/"> + http://www.mozilla.org/projects/bugzilla/</ulink> for details. + Once you download it, untar it, read the Bugzilla Guide. </para> </answer> </qandaentry> @@ -1181,8 +1046,8 @@ </question> <answer> <para> - Installation on Windows NT has its own section in "The - Bugzilla Guide". + Installation on Windows NT has its own section in + "The Bugzilla Guide". </para> </answer> </qandaentry> @@ -1208,19 +1073,16 @@ <qandaentry> <question> <para> - How do I completely disable MySQL security if it's giving - me problems (I've followed the instructions in the - installation section of this guide!)? + How do I completely disable MySQL security if it's giving me problems + (I've followed the instructions in the installation section of this guide!)? </para> </question> <answer> <para> - Run mysql like this: "mysqld --skip-grant-tables". Please - remember <emphasis>this makes mysql as secure as taping a - $100 to the floor of a football stadium bathroom for - safekeeping.</emphasis> Please read the Security - section of the Administration chapter of "The Bugzilla - Guide" before proceeding. + Run mysql like this: "mysqld --skip-grant-tables". Please remember <emphasis>this + makes mysql as secure as taping a $100 to the floor of a football stadium + bathroom for safekeeping.</emphasis> Please read the Security section of the + Administration chapter of "The Bugzilla Guide" before proceeding. </para> </answer> </qandaentry> @@ -1233,11 +1095,10 @@ </question> <answer> <para> - The Bugzilla code has not undergone a complete security - audit. It is recommended that you closely examine - permissions on your Bugzilla installation, and follow the - recommended security guidelines found in The Bugzilla - Guide. + The Bugzilla code has not undergone a complete security audit. + It is recommended that you closely examine permissions on your Bugzilla + installation, and follow the recommended security guidelines found + in The Bugzilla Guide. </para> </answer> </qandaentry> @@ -1246,17 +1107,16 @@ <qandaentry> <question> <para> - I've implemented the security fixes mentioned in Chris - Yeh's security advisory of 5/10/2000 advising not to run - MySQL as root, and am running into problems with MySQL no - longer working correctly. + I've implemented the security fixes mentioned in Chris Yeh's security + advisory of 5/10/2000 advising not to run MySQL as root, and am running into + problems with MySQL no longer working correctly. </para> </question> <answer> <para> - This is a common problem, related to running out of file - descriptors. Simply add "ulimit -n unlimited" to the - script which starts mysqld. + This is a common problem, related to running out of file descriptors. + Simply add "ulimit -n unlimited" to the script which starts + mysqld. </para> </answer> </qandaentry> @@ -1268,14 +1128,14 @@ <qandaentry> <question> <para> - I have a user who doesn't want to receive any more email - from Bugzilla. How do I stop it entirely for this user? + I have a user who doesn't want to receive any more email from Bugzilla. + How do I stop it entirely for this user? </para> </question> <answer> <para> - With the email changes to 2.12, the user should be able to - set this in user email preferences. + With the email changes to 2.12, the user should be able to set + this in user email preferences. </para> </answer> </qandaentry> @@ -1283,15 +1143,14 @@ <qandaentry> <question> <para> - I'm evaluating/testing Bugzilla, and don't want it to send - email to anyone but me. How do I do it? + I'm evaluating/testing Bugzilla, and don't want it to send email to + anyone but me. How do I do it? </para> </question> <answer> <para> - Edit the param for the mail text. Replace "To:" with - "X-Real-To:", replace "Cc:" with "X-Real-CC:", and add a - "To: (myemailaddress)". + Edit the param for the mail text. Replace "To:" with "X-Real-To:", + replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)". </para> </answer> </qandaentry> @@ -1299,15 +1158,17 @@ <qandaentry> <question> <para> - I want whineatnews.pl to whine at something more, or other - than, only new bugs. How do I do it? + I want whineatnews.pl to whine at something more, or other than, only new + bugs. How do I do it? </para> </question> <answer> <para> - Try Klaas Freitag's excellent patch for "whineatassigned" - functionality. You can find it at<ulink url=" - http://bugzilla.mozilla.org/show_bug.cgi?id=6679"> http://bugzilla.mozilla.org/show_bug.cgi?id=6679</ulink>. This patch is against an older version of Bugzilla, so you must apply the diffs manually. + Try Klaas Freitag's excellent patch for "whineatassigned" functionality. + You can find it at<ulink url=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679"> + http://bugzilla.mozilla.org/show_bug.cgi?id=6679</ulink>. This + patch is against an older version of Bugzilla, so you must apply + the diffs manually. </para> </answer> </qandaentry> @@ -1315,23 +1176,22 @@ <qandaentry> <question> <para> - I don't like/want to use Procmail to hand mail off to - bug_email.pl. What alternatives do I have? + I don't like/want to use Procmail to hand mail off to bug_email.pl. + What alternatives do I have? </para> </question> <answer> <para> - You can call bug_email.pl directly from your aliases file, - with an entry like this: + You can call bug_email.pl directly from your aliases file, with + an entry like this: <blockquote> <para> - bugzilla-daemon: - "|/usr/local/bin/bugzilla/contrib/bug_email.pl" + bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" </para> - </blockquote> However, this is fairly nasty and subject to - problems; you also need to set up your smrsh (sendmail - restricted shell) to allow it. In a pinch, though, it can - work. + </blockquote> + However, this is fairly nasty and subject to problems; you also + need to set up your smrsh (sendmail restricted shell) to allow + it. In a pinch, though, it can work. </para> </answer> </qandaentry> @@ -1339,15 +1199,13 @@ <qandaentry> <question> <para> - How do I set up the email interface to submit/change bugs - via email? + How do I set up the email interface to submit/change bugs via email? </para> </question> <answer> <para> - You can find an updated README.mailif file in the contrib/ - directory of your Bugzilla distribution that walks you - through the setup. + You can find an updated README.mailif file in the contrib/ directory + of your Bugzilla distribution that walks you through the setup. </para> </answer> </qandaentry> @@ -1355,29 +1213,28 @@ <qandaentry> <question> <para> - Email takes FOREVER to reach me from bugzilla -- it's - extremely slow. What gives? + Email takes FOREVER to reach me from bugzilla -- it's extremely slow. + What gives? </para> </question> <answer> <para> - If you are using an alternate Mail Transport Agent (MTA - other than sendmail), make sure the options given in the - "processmail" script for all instances of "sendmail" are - correct for your MTA. If you are using Sendmail, you may - wish to delete the "-ODeliveryMode=deferred" option in the - "processmail" script for every invocation of "sendmail". - (Be sure and leave the "-t" option, though!) + If you are using an alternate Mail Transport Agent (MTA other than + sendmail), make sure the options given in the "processmail" script for all + instances of "sendmail" are correct for your MTA. If you are using Sendmail, + you may wish to delete the "-ODeliveryMode=deferred" option in the + "processmail" script for every invocation of "sendmail". (Be sure and leave + the "-t" option, though!) </para> <para> A better alternative is to change the "-O" option to - "-ODeliveryMode=background". This prevents Sendmail from - hanging your Bugzilla Perl processes if the domain to - which it must send mail is unavailable. + "-ODeliveryMode=background". This prevents Sendmail from hanging your + Bugzilla Perl processes if the domain to which it must send mail + is unavailable. </para> <para> - This is now a configurable parameter called "sendmailnow", - available from editparams.cgi. + This is now a configurable parameter called "sendmailnow", available + from editparams.cgi. </para> </answer> </qandaentry> @@ -1390,16 +1247,15 @@ </question> <answer> <para> - Double-check that you have not turned off email in your - user preferences. Confirm that Bugzilla is able to send - email by visiting the "Log In" link of your Bugzilla - installation and clicking the "Email me a password" button - after entering your email address. + Double-check that you have not turned off email in your user preferences. + Confirm that Bugzilla is able to send email by visiting the "Log In" + link of your Bugzilla installation and clicking the "Email me a password" + button after entering your email address. </para> <para> - If you never receive mail from Bugzilla, chances you do - not have sendmail in "/usr/lib/sendmail". Ensure sendmail - lives in, or is symlinked to, "/usr/lib/sendmail". + If you never receive mail from Bugzilla, chances you do not have + sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked + to, "/usr/lib/sendmail". </para> </answer> </qandaentry> @@ -1416,11 +1272,10 @@ </question> <answer> <para> - Red Hat Bugzilla, mentioned above, works with Oracle. The - current version from Mozilla.org does not have this - capability. Unfortunately, though you will sacrifice a - lot of the really great features available in Bugzilla - 2.10 and 2.12 if you go with the 2.8-based Redhat version. + Red Hat Bugzilla, mentioned above, works with Oracle. The current version + from Mozilla.org does not have this capability. Unfortunately, though + you will sacrifice a lot of the really great features available in + Bugzilla 2.10 and 2.12 if you go with the 2.8-based Redhat version. </para> </answer> </qandaentry> @@ -1428,30 +1283,25 @@ <qandaentry> <question> <para> - Bugs are missing from queries, but exist in the database - (and I can pull them up by specifying the bug ID). What's - wrong? + Bugs are missing from queries, but exist in the database (and I can pull + them up by specifying the bug ID). What's wrong? </para> </question> <answer> <para> - You've almost certainly enabled the "shadow database", - but for some reason it hasn't been updated for all your - bugs. This is the database against which queries are run, - so that really complex or slow queries won't lock up - portions of the database for other users. You can turn off - the shadow database in editparams.cgi. If you wish to - continue using the shadow database, then as your "bugs" - user run "./syncshadowdb -syncall" from the command line - in the bugzilla installation directory to recreate your - shadow database. After it finishes, be sure to check the - params and make sure that "queryagainstshadowdb" is still - turned on. The syncshadowdb program turns it off if it was - on, and is supposed to turn it back on when completed; - that way, if it crashes in the middle of recreating the - database, it will stay off forever until someone turns it - back on by hand. Apparently, it doesn't always do that - yet. + You've almost certainly enabled the "shadow database", but for some + reason it hasn't been updated for all your bugs. This is the database + against which queries are run, so that really complex or slow queries won't + lock up portions of the database for other users. You can turn off the + shadow database in editparams.cgi. If you wish to continue using the shadow + database, then as your "bugs" user run "./syncshadowdb -syncall" from the + command line in the bugzilla installation directory to recreate your shadow + database. After it finishes, be sure to check the params and make sure that + "queryagainstshadowdb" is still turned on. The syncshadowdb program turns it + off if it was on, and is supposed to turn it back on when completed; that + way, if it crashes in the middle of recreating the database, it will stay + off forever until someone turns it back on by hand. Apparently, it doesn't + always do that yet. </para> </answer> </qandaentry> @@ -1459,20 +1309,18 @@ <qandaentry> <question> <para> - I think my database might be corrupted, or contain invalid - entries. What do I do? + I think my database might be corrupted, or contain invalid entries. What + do I do? </para> </question> <answer> <para> - Run the "sanity check" utility (./sanitycheck.cgi in the - bugzilla_home directory) to see! If it all comes back, - you're OK. If it doesn't come back OK (i.e. any red - letters), there are certain things Bugzilla can recover - from and certain things it can't. If it can't - auto-recover, I hope you're familiar with mysqladmin - commands or have installed another way to manage your - database... + Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home + directory) to see! If it all comes back, you're OK. If it doesn't come back + OK (i.e. any red letters), there are certain things Bugzilla can recover + from and certain things it can't. If it can't auto-recover, I hope you're + familiar with mysqladmin commands or have installed another way to manage + your database... </para> </answer> </qandaentry> @@ -1485,14 +1333,12 @@ </question> <answer> <para> - There is no facility in Bugzilla itself to do this. It's - also generally not a smart thing to do if you don't know - exactly what you're doing. However, if you understand SQL - you can use the mysqladmin utility to manually insert, - delete, and modify table information. Personally, I use - "phpMyAdmin". You have to compile a PHP module with MySQL - support to make it work, but it's very clean and easy to - use. + There is no facility in Bugzilla itself to do this. It's also generally + not a smart thing to do if you don't know exactly what you're doing. + However, if you understand SQL you can use the mysqladmin utility to + manually insert, delete, and modify table information. Personally, I + use "phpMyAdmin". You have to compile a PHP module with MySQL + support to make it work, but it's very clean and easy to use. </para> </answer> </qandaentry> @@ -1500,17 +1346,14 @@ <qandaentry> <question> <para> - I try to add myself as a user, but Bugzilla always tells - me my password is wrong. + I try to add myself as a user, but Bugzilla always tells me my password is wrong. </para> </question> <answer> <para> - Certain version of MySQL (notably, 3.23.29 and 3.23.30) - accidentally disabled the "crypt()" function. This - prevented MySQL from storing encrypted passwords. Upgrade - to the "3.23 stable" version of MySQL and you should be - good to go. + Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled + the "crypt()" function. This prevented MySQL from storing encrypted passwords. + Upgrade to the "3.23 stable" version of MySQL and you should be good to go. </para> </answer> </qandaentry> @@ -1518,18 +1361,17 @@ <qandaentry> <question> <para> - I think I've set up MySQL permissions correctly, but - bugzilla still can't connect. + I think I've set up MySQL permissions correctly, but bugzilla still can't + connect. </para> </question> <answer> <para> - Try running MySQL from its binary: "mysqld - --skip-grant-tables". This will allow you to completely - rule out grant tables as the cause of your frustration. - However, I do not recommend you run it this way on a - regular basis, unless you really want your web site - defaced and your machine cracked. + Try running MySQL from its binary: "mysqld --skip-grant-tables". This + will allow you to completely rule out grant tables as the cause of your + frustration. However, I do not recommend you run it this way on a regular + basis, unless you really want your web site defaced and your machine + cracked. </para> </answer> </qandaentry> @@ -1537,28 +1379,26 @@ <qandaentry> <question> <para> - How do I synchronize bug information among multiple - different Bugzilla databases? + How do I synchronize bug information among multiple different Bugzilla + databases? </para> </question> <answer> <para> - Well, you can synchronize or you can move bugs. - Synchronization will only work one way -- you can create a - read-only copy of the database at one site, and have it - regularly updated at intervals from the main database. + Well, you can synchronize or you can move bugs. Synchronization will + only work one way -- you can create a read-only copy of the database + at one site, and have it regularly updated at intervals from the main + database. </para> <para> - MySQL has some synchronization features builtin to the - latest releases. It would be great if someone looked into - the possibilities there and provided a report to the - newsgroup on how to effectively synchronize two Bugzilla - installations. + MySQL has some synchronization features builtin to the latest releases. + It would be great if someone looked into the possibilities there + and provided a report to the newsgroup on how to effectively + synchronize two Bugzilla installations. </para> <para> - If you simply need to transfer bugs from one Bugzilla to - another, checkout the "move.pl" script in the Bugzilla - distribution. + If you simply need to transfer bugs from one Bugzilla to another, + checkout the "move.pl" script in the Bugzilla distribution. </para> </answer> </qandaentry> @@ -1566,16 +1406,15 @@ <qandaentry> <question> <para> - Why do I get bizarre errors when trying to submit data, - particularly problems with "groupset"? + Why do I get bizarre errors when trying to submit data, particularly problems + with "groupset"? </para> </question> <answer> <para> - If you're sure your MySQL parameters are correct, you - might want turn "strictvaluechecks" OFF in editparams.cgi. - If you have "usebugsentry" set "On", you also cannot - submit a bug as readable by more than one group with + If you're sure your MySQL parameters are correct, you might want turn + "strictvaluechecks" OFF in editparams.cgi. If you have "usebugsentry" set + "On", you also cannot submit a bug as readable by more than one group with "strictvaluechecks" ON. </para> </answer> @@ -1584,17 +1423,15 @@ <qandaentry> <question> <para> - How come even after I delete bugs, the long descriptions - show up? + How come even after I delete bugs, the long descriptions show up? </para> </question> <answer> <para> - Delete everything from $BUZILLA_HOME/shadow. Bugzilla - creates shadow files there, with each filename - corresponding to a bug number. Also be sure to run - syncshadowdb to make sure, if you are using a shadow - database, that the shadow database is current. + Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow + files there, with each filename corresponding to a + bug number. Also be sure to run syncshadowdb to make sure, if you are using + a shadow database, that the shadow database is current. </para> </answer> </qandaentry> @@ -1607,14 +1444,13 @@ <qandaentry> <question> <para> - What is the easiest way to run Bugzilla on Win32 - (Win98+/NT/2K)? + What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)? </para> </question> <answer> <para> - Remove Windows. Install Linux. Install Bugzilla. The boss - will never know the difference. + Remove Windows. Install Linux. Install Bugzilla. + The boss will never know the difference. </para> </answer> </qandaentry> @@ -1627,10 +1463,9 @@ </question> <answer> <para> - Not currently. Bundle::Bugzilla enormously simplifies - Bugzilla installation on UNIX systems. If someone can - volunteer to create a suitable PPM bundle for Win32, it - would be appreciated. + Not currently. Bundle::Bugzilla enormously simplifies Bugzilla + installation on UNIX systems. If someone can volunteer to + create a suitable PPM bundle for Win32, it would be appreciated. </para> </answer> </qandaentry> @@ -1638,34 +1473,29 @@ <qandaentry> <question> <para> - CGI's are failing with a "something.cgi is not a valid - Windows NT application" error. Why? + CGI's are failing with a "something.cgi is not a valid Windows NT + application" error. Why? </para> </question> <answer> <para> - Depending on what Web server you are using, you will have - to configure the Web server to treat *.cgi files as CGI - scripts. In IIS, you do this by adding *.cgi to the App - Mappings with the <path>\perl.exe %s %s as the + Depending on what Web server you are using, you will have to configure + the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by + adding *.cgi to the App Mappings with the <path>\perl.exe %s %s as the executable. </para> <para> Microsoft has some advice on this matter, as well: <blockquote> <para> - "Set application mappings. In the ISM, map the - extension for the script file(s) to the executable for - the script interpreter. For example, you might map the - extension .py to Python.exe, the executable for the - Python script interpreter. Note For the ActiveState - Perl script interpreter, the extension .pl is - associated with PerlIS.dll by default. If you want to - change the association of .pl to perl.exe, you need to - change the application mapping. In the mapping, you - must add two percent (%) characters to the end of the - pathname for perl.exe, as shown in this example: - c:\perl\bin\perl.exe %s %s" + "Set application mappings. In the ISM, map the extension for the script + file(s) to the executable for the script interpreter. For example, you might + map the extension .py to Python.exe, the executable for the Python script + interpreter. Note For the ActiveState Perl script interpreter, the extension + .pl is associated with PerlIS.dll by default. If you want to change the + association of .pl to perl.exe, you need to change the application mapping. + In the mapping, you must add two percent (%) characters to the end of the + pathname for perl.exe, as shown in this example: c:\perl\bin\perl.exe %s %s" </para> </blockquote> </para> @@ -1675,69 +1505,108 @@ <qandaentry> <question> <para> - Can I have some general instructions on how to make - Bugzilla on Win32 work? - </para> - </question> + Can I have some general instructions on how to make Bugzilla on Win32 work? + </para> + </question> <answer> <para> - The following couple entries are deprecated in favor of - the Windows installation instructions available in the - "Administration" portion of "The Bugzilla Guide". However, - they are provided here for historical interest and - insight. <literallayout> 1. #!C:/perl/bin/perl had to be - added to every perl file. 2. Converted to Net::SMTP to - handle mail messages instead of /usr/bin/sendmail. 3. - The crypt function isn't available on Windows NT (at - least none that I am aware), so I made encrypted - passwords = plaintext passwords. 4. The system call to - diff had to be changed to the Cygwin diff. 5. This was - just to get a demo running under NT, it seems to be - working good, and I have inserted almost 100 bugs from - another bug tracking system. Since this work was done - just to get an in-house demo, I am NOT planning on - making a patch for submission to Bugzilla. If you would - like a zip file, let me know. Q: Hmm, couldn't figure it - out from the general instructions above. How about - step-by-step? A: Sure! Here ya go! 1. Install IIS 4.0 - from the NT Option Pack #4. 2. Download and install - Active Perl. 3. Install the Windows GNU tools from - Cygwin. Make sure to add the bin directory to your - system path. (Everyone should have these, whether they - decide to use Bugzilla or not. :-) ) 4. Download - relevant packages from ActiveState at - http://www.activestate.com/packages/zips/. + - DBD-Mysql.zip 5. Extract each zip file with WinZip, and - install each ppd file using the notation: ppm install - <module>.ppd 6. Install Mysql. *Note: If you move - the default install from c:\mysql, you must add the - appropriate startup parameters to the NT service. (ex. - -b e:\\programs\\mysql) 7. Download any Mysql client. - http://www.mysql.com/download_win.html 8. Setup MySql. - (These are the commands that I used.) I. Cleanup default - database settings. C:\mysql\bin\mysql -u root mysql - mysql> DELETE FROM user WHERE Host='localhost' AND - User=''; mysql> quit C:\mysql\bin\mysqladmin reload II. - Set password for root. C:\mysql\bin\mysql -u root mysql - mysql> UPDATE user SET Password=PASSWORD('new_password') - WHERE user='root'; mysql> FLUSH PRIVILEGES; mysql> quit - C:\mysql\bin\mysqladmin -u root reload III. Create bugs - user. C:\mysql\bin\mysql -u root -p mysql> insert into - user (host,user,password) values('localhost','bugs',''); - mysql> quit C:\mysql\bin\mysqladmin -u root reload IV. - Create the bugs database. C:\mysql\bin\mysql -u root -p - mysql> create database bugs; V. Give the bugs user - access to the bugs database. mysql> insert into db - (host,db,user,select_priv,insert_priv,update_priv,delete_priv,create_priv,drop_priv) values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N') mysql> quit C:\mysql\bin\mysqladmin -u root reload 9. Run the table scripts to setup the bugs database. 10. Change CGI.pm to use the following regular expression because of differing backslashes in NT versus UNIX. o $0 =~ m:[^\\]*$:; 11. Had to make the crypt password = plain text password in the database. (Thanks to Andrew Lahser" <andrew_lahser@merck.com>" on this one.) The files that I changed were: o globals.pl o CGI.pl o alternately, you can try commenting all references to 'crypt' string and replace them with similar lines but without encrypt() or crypr() functions insida all files. 12. Replaced sendmail with Windmail. Basically, you have to come up with a sendmail substitute for NT. Someone said that they used a Perl module (Net::SMTP), but I was trying to save time and do as little Perl coding as possible. 13. Added "perl" to the beginning of all Perl system calls that use a perl script as an argument and renamed processmail to processmail.pl. 14. In processmail.pl, I added binmode(HANDLE) before all read() calls. I'm not sure about this one, but the read() under NT wasn't counting the EOLs without the binary read." </literallayout> + The following couple entries are deprecated in favor of the Windows installation + instructions available in the "Administration" portion of "The Bugzilla Guide". + However, they are provided here for historical interest and insight. + <literallayout> + 1. #!C:/perl/bin/perl had to be added to every perl file. + 2. Converted to Net::SMTP to handle mail messages instead of + /usr/bin/sendmail. + 3. The crypt function isn't available on Windows NT (at least none that I + am aware), so I made encrypted passwords = plaintext passwords. + 4. The system call to diff had to be changed to the Cygwin diff. + 5. This was just to get a demo running under NT, it seems to be working + good, and I have inserted almost 100 bugs from another bug tracking + system. Since this work was done just to get an in-house demo, I am NOT + planning on making a patch for submission to Bugzilla. If you would + like a zip file, let me know. + +Q: Hmm, couldn't figure it out from the general instructions above. How +about step-by-step? +A: Sure! Here ya go! + + 1. Install IIS 4.0 from the NT Option Pack #4. + 2. Download and install Active Perl. + 3. Install the Windows GNU tools from Cygwin. Make sure to add the bin + directory to your system path. (Everyone should have these, whether + they decide to use Bugzilla or not. :-) ) + 4. Download relevant packages from ActiveState at + http://www.activestate.com/packages/zips/. + DBD-Mysql.zip + 5. Extract each zip file with WinZip, and install each ppd file using the + notation: ppm install <module>.ppd + 6. Install Mysql. *Note: If you move the default install from c:\mysql, + you must add the appropriate startup parameters to the NT service. (ex. + -b e:\\programs\\mysql) + 7. Download any Mysql client. http://www.mysql.com/download_win.html + 8. Setup MySql. (These are the commands that I used.) + + I. Cleanup default database settings. + C:\mysql\bin\mysql -u root mysql + mysql> DELETE FROM user WHERE Host='localhost' AND User=''; + mysql> quit + C:\mysql\bin\mysqladmin reload + + II. Set password for root. + C:\mysql\bin\mysql -u root mysql + mysql> UPDATE user SET Password=PASSWORD('new_password') + WHERE user='root'; + mysql> FLUSH PRIVILEGES; + mysql> quit + C:\mysql\bin\mysqladmin -u root reload + + III. Create bugs user. + C:\mysql\bin\mysql -u root -p + mysql> insert into user (host,user,password) + values('localhost','bugs',''); + mysql> quit + C:\mysql\bin\mysqladmin -u root reload + + IV. Create the bugs database. + C:\mysql\bin\mysql -u root -p + mysql> create database bugs; + + V. Give the bugs user access to the bugs database. + mysql> insert into db + (host,db,user,select_priv,insert_priv,update_priv,delete_priv,create_priv,drop_priv) + values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N') + mysql> quit + C:\mysql\bin\mysqladmin -u root reload + 9. Run the table scripts to setup the bugs database. + 10. Change CGI.pm to use the following regular expression because of + differing backslashes in NT versus UNIX. + o $0 =~ m:[^\\]*$:; + 11. Had to make the crypt password = plain text password in the database. + (Thanks to Andrew Lahser" <andrew_lahser@merck.com>" on this one.) The + files that I changed were: + o globals.pl + o CGI.pl + o alternately, you can try commenting all references to 'crypt' + string and replace them with similar lines but without encrypt() + or crypr() functions insida all files. + 12. Replaced sendmail with Windmail. Basically, you have to come up with a + sendmail substitute for NT. Someone said that they used a Perl module + (Net::SMTP), but I was trying to save time and do as little Perl coding + as possible. + 13. Added "perl" to the beginning of all Perl system calls that use a perl + script as an argument and renamed processmail to processmail.pl. + 14. In processmail.pl, I added binmode(HANDLE) before all read() calls. I'm + not sure about this one, but the read() under NT wasn't counting the + EOLs without the binary read." + </literallayout> </para> </answer> </qandaentry> - - <qandaentry> - <question> - <para> - I'm having trouble with the perl modules for NT not being - able to talk to to the database. + + <qandaentry> + <question> + <para> + I'm having trouble with the perl modules for NT not being able to talk to + to the database. </para> </question> <answer> @@ -1766,14 +1635,14 @@ </listitem> <listitem> <para> - <prompt>PPM></prompt> <command>install DBI DBD-mysql - GD</command> + <prompt>PPM></prompt> <command>install DBI DBD-mysql GD</command> </para> </listitem> - </orderedlist> I reckon TimeDate and Data::Dumper come - with the activeperl. You can check the ActiveState site - for packages for installation through PPM. <ulink url=" - http://www.activestate.com/Packages/"> http://www.activestate.com/Packages/</ulink> + </orderedlist> + I reckon TimeDate and Data::Dumper come with the activeperl. You can check + the ActiveState site for packages for installation through PPM. + <ulink url=" http://www.activestate.com/Packages/"> + http://www.activestate.com/Packages/</ulink> </para> </answer> </qandaentry> @@ -1786,15 +1655,15 @@ <qandaentry> <question> <para> - The query page is very confusing. Isn't there a simpler - way to query? + The query page is very confusing. Isn't there a simpler way to query? </para> </question> <answer> <para> - We are developing in that direction. You can follow - progress on this at <ulink - url="http://bugzilla.mozilla.org/show_bug.cgi?id=16775"> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</ulink>. Some functionality is available in Bugzilla 2.12, and is available as "quicksearch.html" + We are developing in that direction. You can follow progress on this + at <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=16775"> + http://bugzilla.mozilla.org/show_bug.cgi?id=16775</ulink>. Some functionality + is available in Bugzilla 2.12, and is available as "quicksearch.html" </para> </answer> </qandaentry> @@ -1802,24 +1671,23 @@ <qandaentry> <question> <para> - I'm confused by the behavior of the "accept" button in the - Show Bug form. Why doesn't it assign the bug to me when I - accept it? + I'm confused by the behavior of the "accept" button in the Show Bug form. + Why doesn't it assign the bug to me when I accept it? </para> </question> <answer> <para> - The current behavior is acceptable to bugzilla.mozilla.org - and most users. I personally don't like it. You have - your choice of patches to change this behavior, however. + The current behavior is acceptable to bugzilla.mozilla.org and most + users. I personally don't like it. You have your choice of patches + to change this behavior, however. <simplelist> - <member><ulink - url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"> Add a "and accept bug" radio button</ulink></member> - <member><ulink - url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"> "Accept" button automatically assigns to you</ulink></member> - </simplelist> Note that these patches are somewhat dated. - You will need to do the find and replace manually to apply - them. They are very small, though. It is easy. + <member><ulink url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"> + Add a "and accept bug" radio button</ulink></member> + <member><ulink url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"> + "Accept" button automatically assigns to you</ulink></member> + </simplelist> + Note that these patches are somewhat dated. You will need to do the find + and replace manually to apply them. They are very small, though. It is easy. </para> </answer> </qandaentry> @@ -1827,16 +1695,15 @@ <qandaentry> <question> <para> - I can't upload anything into the database via the "Create - Attachment" link. What am I doing wrong? + I can't upload anything into the database via the "Create Attachment" + link. What am I doing wrong? </para> </question> <answer> <para> - The most likely cause is a very old browser or a browser - that is incompatible with file upload via POST. Download - the latest Netscape, Microsoft, or Mozilla browser to - handle uploads correctly. + The most likely cause is a very old browser or a browser that is + incompatible with file upload via POST. Download the latest Netscape, + Microsoft, or Mozilla browser to handle uploads correctly. </para> </answer> </qandaentry> @@ -1844,16 +1711,15 @@ <qandaentry> <question> <para> - Email submissions to Bugzilla that have attachments end up - asking me to save it as a "cgi" file. + Email submissions to Bugzilla that have attachments end up asking me to + save it as a "cgi" file. </para> </question> <answer> <para> - Yup. Just rename it once you download it, or save it - under a different filename. This will not be fixed - anytime too soon, because it would cripple some other - functionality. + Yup. Just rename it once you download it, or save it under a different + filename. This will not be fixed anytime too soon, because it would + cripple some other functionality. </para> </answer> </qandaentry> @@ -1861,16 +1727,14 @@ <qandaentry> <question> <para> - How do I change a keyword in Bugzilla, once some bugs are - using it? + How do I change a keyword in Bugzilla, once some bugs are using it? </para> </question> <answer> <para> - In the Bugzilla administrator UI, edit the keyword and it - will let you replace the old keyword name with a new one. - This will cause a problem with the keyword cache. Run - sanitycheck.cgi to fix it. + In the Bugzilla administrator UI, edit the keyword and it will let you + replace the old keyword name with a new one. This will cause a problem + with the keyword cache. Run sanitycheck.cgi to fix it. </para> </answer> </qandaentry> @@ -1888,12 +1752,19 @@ </question> <answer> <para> - Try <ulink - url="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Webtools&component=Bugzilla"> this link</ulink> to view current bugs or requests for enhancement for Bugzilla. + Try <ulink url="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Webtools&component=Bugzilla"> + this link</ulink> to view current bugs or requests for + enhancement for Bugzilla. </para> <para> - You can view bugs marked for 2.14 release <ulink - url="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bugzilla&target_milestone=Bugzilla+2.14">here</ulink>. This list includes bugs for the 2.14 release that have already been fixed and checked into CVS. Please consult the <ulink url="http://www.mozilla.org/projects/bugzilla/"> Bugzilla Project Page</ulink> for details on how to check current sources out of CVS so you can have these bug fixes early! + You can view bugs marked for 2.14 release + <ulink url="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bugzilla&target_milestone=Bugzilla+2.14">here</ulink>. + This list includes bugs for the 2.14 release that have already + been fixed and checked into CVS. Please consult the + <ulink url="http://www.mozilla.org/projects/bugzilla/"> + Bugzilla Project Page</ulink> for details on how to + check current sources out of CVS so you can have these + bug fixes early! </para> </answer> </qandaentry> @@ -1901,15 +1772,19 @@ <qandaentry> <question> <para> - How can I change the default priority to a null value? - For instance, have the default priority be "---" instead - of "P2"? + 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... + 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> @@ -1917,8 +1792,7 @@ <qandaentry> <question> <para> - What's the best way to submit patches? What guidelines - should I follow? + What's the best way to submit patches? What guidelines should I follow? </para> </question> <answer> @@ -1926,47 +1800,42 @@ <orderedlist> <listitem> <para> - Enter a bug into bugzilla.mozilla.org for the - "Webtools" product, "Bugzilla" component. + Enter a bug into bugzilla.mozilla.org for the "Webtools" product, + "Bugzilla" component. </para> </listitem> <listitem> <para> - Upload your patch as a unified DIFF (having used - "diff -u" against the <emphasis>current - sources</emphasis> checked out of CVS), or new - source file by clicking "Create a new attachment" - link on the bug page you've just created, and - include any descriptions of database changes you may - make, into the bug ID you submitted in step #1. Be - sure and click the "Patch" radio button to indicate - the text you are sending is a patch! + Upload your patch as a unified DIFF (having used "diff -u" against + the <emphasis>current sources</emphasis> checked out of CVS), + or new source file by clicking + "Create a new attachment" link on the bug page you've just created, and + include any descriptions of database changes you may make, into the bug + ID you submitted in step #1. Be sure and click the "Patch" radio + button to indicate the text you are sending is a patch! </para> </listitem> <listitem> <para> Announce your patch and the associated URL - (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) - for discussion in the newsgroup - (netscape.public.mozilla.webtools). You'll get a - really good, fairly immediate reaction to the - implications of your patch, which will also give us - an idea how well-received the change would be. + (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) for discussion in + the newsgroup (netscape.public.mozilla.webtools). You'll get a really + good, fairly immediate reaction to the implications of your patch, + which will also give us an idea how well-received the change would + be. </para> </listitem> <listitem> <para> - If it passes muster with minimal modification, the - person to whom the bug is assigned in Bugzilla is - responsible for seeing the patch is checked into - CVS. + If it passes muster with minimal modification, the person to whom + the bug is assigned in Bugzilla is responsible for seeing the patch + is checked into CVS. </para> </listitem> <listitem> <para> - Bask in the glory of the fact that you helped write - the most successful open-source bug-tracking - software on the planet :) + Bask in the glory of the fact that you helped write the most successful + open-source bug-tracking software on the planet :) </para> </listitem> </orderedlist> diff --git a/docs/sgml/future.sgml b/docs/sgml/future.sgml index 2e048dc5e..1f4681a31 100644 --- a/docs/sgml/future.sgml +++ b/docs/sgml/future.sgml @@ -3,11 +3,13 @@ <chapter id="future"> <title>The Future of Bugzilla</title> <synopsis>Bugzilla's Future. Much of this is the present, now.</synopsis> - <para>The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do + <para> + The future of Bugzilla is Bugzilla 3.0. Unfortunately, I do not have more information about it right now, and most of what went into the "future" section is now present. That stuff was blue-sky a year ago; MattyT should have me a new document - sometime...</para> + sometime... + </para> </chapter> <!-- Keep this comment at the end of the file diff --git a/docs/sgml/glossary.sgml b/docs/sgml/glossary.sgml index 71ba2dd36..faa4d1781 100644 --- a/docs/sgml/glossary.sgml +++ b/docs/sgml/glossary.sgml @@ -26,9 +26,16 @@ <glossdiv id="gloss_a"> <title>A</title> <glossentry> - <glossterm>There are no entries for A</glossterm> + <glossterm>Apache</glossterm> <glossdef> - <para></para> + <para>In this context, Apache is the web server most + commonly used for serving up + <glossterm>Bugzilla</glossterm> pages. Contrary to + popular belief, the apache web server has nothing to do + with the ancient and noble Native American tribe, but + instead derived its name from the fact that it was + <quote>a patchy</quote> version of the original + <acronym>NCSA</acronym> world-wide-web server.</para> </glossdef> </glossentry> </glossdiv> @@ -70,8 +77,77 @@ the needs of the organization using it, though.</para> </glossdef> </glossentry> + + <glossentry> + <glossterm>Bugzilla</glossterm> + <glossdef> + <para> + Bugzilla is the industry-standard bug tracking system. It + is quite popular among Open Source enthusiasts. + </para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv id="gloss_c"> + <title></title> + <glossentry id="gloss_component"> + <glossterm>Component</glossterm> + <glossdef> + <para> + A Component is a subsection of a Product. It should be a + narrow category, tailored to your organization. All + Products must contain at least one Component (and, as a + matter of fact, creating a Product with no Components will + create an error in Bugzilla). + </para> + </glossdef> + </glossentry> + <glossentry id="gloss_cpan"> + <glossterm><acronym>CPAN</acronym></glossterm> + <glossdef> + <para><acronym>CPAN</acronym> stands for the + <quote>Comprehensive Perl Archive Network</quote>. CPAN + maintains a large number of extremely useful + <glossterm>Perl</glossterm> modules. By themselves, Perl + modules generally do nothing, but when used as part of a + larger program, they provide much-needed algorithms and + functionality.</para> + </glossdef> + </glossentry> </glossdiv> + <glossdiv id="gloss_d"> + <title>D</title> + <glossentry> + <glossterm>daemon</glossterm> + <glossdef> + <para>A daemon is a computer program which runs in the + background. In general, most daemons are started at boot + time via System V init scripts, or through RC scripts on + BSD-based systems. <glossterm>mysqld</glossterm>, the + MySQL server, and <glossterm>apache</glossterm>, a web + server, are generally run as daemons.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv id="gloss_g"> + <title></title> + <glossentry> + <glossterm>Groups</glossterm> + <glossdef> + <para>The word <quote>Groups</quote> has a very special + meaning to Bugzilla. Bugzilla's main security mechanism + comes by lumping users into groups, and assigning those + groups certain privileges to + <glossterm>Products</glossterm> and + <glossterm>Components</glossterm> in the + <glossterm>Bugzilla</glossterm> database.</para> + </glossdef> + </glossentry> + </glossdiv> + <glossdiv id="gloss_i"> <title>I</title> <glossentry id="gloss_infiniteloop"> @@ -81,7 +157,22 @@ </glossdef> </glossentry> </glossdiv> - + + <glossdiv id="gloss_m"> + <title>M</title> + <glossentry> + <glossterm>mysqld</glossterm> + <glossdef> + <para>mysqld is the name of the + <glossterm>daemon</glossterm> for the MySQL database. In + general, it is invoked automatically through the use of + the System V init scripts on GNU/Linux and AT&T System + V-based systems, such as Solaris and HP/UX, or through the + RC scripts on BSD-based systems.</para> + </glossdef> + </glossentry> + </glossdiv> + <glossdiv id="gloss_p"> <title>P</title> <glossentry> @@ -108,6 +199,17 @@ </example> </glossdef> </glossentry> + <glossentry> + <glossterm>Perl</glossterm> + <glossdef> + <para>First written by Larry Wall, Perl is a remarkable + program language. It has the benefits of the flexibility + of an interpreted scripting language (such as shell + script), combined with the speed and power of a compiled + language, such as C. <glossterm>Bugzilla</glossterm> is + maintained in Perl.</para> + </glossdef> + </glossentry> </glossdiv> <glossdiv id="gloss_q"> @@ -129,8 +231,8 @@ <glossdiv id="gloss_r"> <title>R</title> - <glossentry> - <glossterm id="gloss_recursion">Recursion</glossterm> + <glossentry id="gloss_recursion" xreflabel="Recursion"> + <glossterm>Recursion</glossterm> <glossdef> <para>The property of a function looking back at itself for something. <quote>GNU</quote>, for instance, stands for @@ -140,10 +242,52 @@ </glossdef> </glossentry> </glossdiv> + + <glossdiv id="gloss_s"> + <title>S</title> + <glossentry> + <glossterm><acronym>SGML</acronym></glossterm> + <glossdef> + <para><acronym>SGML</acronym> stands for <quote>Standard + Generalized Markup Language</quote>. Created in the + 1980's to provide an extensible means to maintain + documentation based upon content instead of presentation, + <acronym>SGML</acronym> has withstood the test of time as + a robust, powerful language. + <glossterm><acronym>XML</acronym></glossterm> is the + <quote>baby brother</quote> of SGML; any valid + <acronym>XML</acronym> document it, by definition, a valid + <acronym>SGML</acronym> document. The document you are + reading is written and maintained in + <acronym>SGML</acronym>, and is also valid + <acronym>XML</acronym> if you modify the Document Type + Definition.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv id="gloss_t"> + <title>T</title> + <glossentry id="gloss_target_milestone" xreflabel="Target Milestone"> + <glossterm>Target Milestone</glossterm> + <glossdef> + <para> + Target Milestones are Product goals. They are + configurable on a per-Product basis. Most software + development houses have a concept of + <quote>milestones</quote> where the people funding a + project expect certain functionality on certain dates. + Bugzilla facilitates meeting these milestones by giving + you the ability to declare by which milestone a bug will be + fixed, or an enhancement will be implemented. + </para> + </glossdef> + </glossentry> + </glossdiv> <glossdiv id="gloss_z"> <title>Z</title> - <glossentry> + <glossentry id="zarro-boogs-found" xreflabel="Zarro Boogs Found"> <glossterm>Zarro Boogs Found</glossterm> <glossdef> <para>This is the cryptic response sent by Bugzilla when a diff --git a/docs/sgml/installation.sgml b/docs/sgml/installation.sgml index dfbc35071..547d466ba 100644 --- a/docs/sgml/installation.sgml +++ b/docs/sgml/installation.sgml @@ -1,6 +1,6 @@ <!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> --> - <chapter id="installation"> + <chapter id="installation" xreflabel="Bugzilla Installation"> <title>Installation</title> <para> These installation instructions are presented assuming you are @@ -50,6 +50,7 @@ refer to these documents when installing, configuring, and maintaining your Bugzilla installation. </member> + </simplelist> <warning> @@ -108,8 +109,7 @@ the CPAN dependencies listed below, and are running the very most recent version of Perl and MySQL (both the executables and development libraries) on your system, check out - Bundle::Bugzilla in <xref - linkend="bundlebugzilla"></para> + Bundle::Bugzilla in <xref linkend="bundlebugzilla"></para> </note> <para> The software packages necessary for the proper running of bugzilla are: @@ -185,39 +185,64 @@ attack. </para> </warning> + <note> + <para>Linux-Mandrake 8.0, the author's test system, includes + every required and optional library for Bugzilla. The + easiest way to install them is by using the + <filename>urpmi</filename> utility. If you follow these + commands, you should have everything you need for + Bugzilla, and <filename>checksetup.pl</filename> should + not complain about any missing libraries. You may already + have some of these installed.</para> + <simplelist> + <member><prompt>bash#</prompt><command> urpmi + perl-mysql</command></member> + <member><prompt>bash#</prompt><command> urpmi + perl-chart</command></member> + <member><prompt>bash#</prompt><command> urpmi + perl-gd</command></member> + <member><prompt>bash#</prompt><command> urpmi + perl-MailTools</command> (for Bugzilla email + integration)</member> + <member><prompt>bash#</prompt><command> urpmi + apache-modules</command></member> + </simplelist> + </note> </para> </section> <section id="install-mysql"> <title>Installing MySQL Database</title> <para> - Visit MySQL homepage at http://www.mysql.com/ and grab the - latest stable release of the server. Both binaries and source - are available and which you get shouldn't matter. Be aware - that many of the binary versions of MySQL store their data - files in /var which on many installations (particularly common - with linux installations) is part of a smaller root partition. - If you decide to build from sources you can easily set the - dataDir as an option to configure. + Visit MySQL homepage at <ulink + url="http://www.mysql.com">www.mysql.com</ulink> and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <filename>/var</filename> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <filename>configure</filename>. </para> <para> - If you've installed from source or non-package (RPM, deb, - etc.) binaries you'll want to make sure to add mysqld to your + If you install from source or non-package (RPM, deb, etc.) + binaries you need to add + <firstterm>mysqld</firstterm> to your init scripts so the server daemon will come back up whenever - your machine reboots. You also may want to edit those init - scripts, to make sure that mysqld will accept large packets. - By default, mysqld is set up to only accept packets up to 64K - long. This limits the size of attachments you may put on - bugs. If you add something like "-O max_allowed_packet=1M" to - the command that starts mysqld (or safe_mysqld), then you will - be able to have attachments up to about 1 megabyte. + your machine reboots. Further discussion of UNIX init + sequences are beyond the scope of this guide. + <note> + <para>You should have your init script start + <glossterm>mysqld</glossterm> with the ability to accept + large packets. By default, <filename>mysqld</filename> + only accepts packets up to 64K long. This limits the size + of attachments you may put on bugs. If you add <option>-O + max_allowed_packet=1M</option> to the command that starts + <filename>mysqld</filename> (or + <filename>safe_mysqld</filename>), then you will be able + to have attachments up to about 1 megabyte.</para> + </note> + </para> <note> <para> If you plan on running Bugzilla and MySQL on the same - machine, consider using the "--skip-networking" option in - the init script. This enhances security by preventing - network access to MySQL. + machine, consider using the <option>--skip-networking</option> + option in the init script. This enhances security by + preventing network access to MySQL. </para> </note> </section> @@ -260,9 +285,10 @@ <tip id="bundlebugzilla" xreflabel="Using Bundle::Bugzilla instead of manually installing Perl modules"> <para> You can skip the following Perl module installation steps by - installing "Bundle::Bugzilla" from CPAN, which includes - them. All Perl module installation steps require you have an - active Internet connection. If you wish to use + installing <productname>Bundle::Bugzilla</productname> from + <glossterm linkend="gloss_cpan">CPAN</glossterm>, which + includes them. All Perl module installation steps require + you have an active Internet connection. If you wish to use Bundle::Bugzilla, however, you must be using the latest version of Perl (at this writing, version &perl-ver;) </para> @@ -293,7 +319,7 @@ Like almost all Perl modules DBI can be found on the Comprehensive Perl Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a real tendency to bog down, so please use mirrors. The current location - at the time of this writing (02/17/99) can be found in Appendix A. + at the time of this writing can be found in <xref linkend="downloadlinks">. </para> <para> Quality, general Perl module installation instructions can be found on @@ -370,9 +396,11 @@ hurt anything. </para> <para> - Data::Dumper is used by the MySQL-related Perl modules. It can be - found on CPAN (link in Appendix A) and can be installed by following - the same four step make sequence used for the DBI module. + Data::Dumper is used by the MySQL-related Perl modules. It + can be found on CPAN (see <xref linkend="downloadlinks">) and + can be + installed by following the same four step make sequence used + for the DBI module. </para> </section> @@ -414,37 +442,42 @@ <section> <title>TimeDate Perl Module Collection</title> <para> - Many of the more common date/time/calendar related Perl modules have - been grouped into a bundle similar to the MySQL modules bundle. This - bundle is stored on the CPAN under the name TimeDate. A link - link may be found in Appendix B, Software Download Links. - The component module we're - most interested in is the Date::Format module, but installing all of them - is probably a good idea anyway. The standard Perl module installation - instructions should work perfectly for this simple package. + Many of the more common date/time/calendar related Perl + modules have been grouped into a bundle similar to the MySQL + modules bundle. This bundle is stored on the CPAN under the + name TimeDate (see link: <xref linkend="downloadlinks">). The + component module we're most interested in is the Date::Format + module, but installing all of them is probably a good idea + anyway. The standard Perl module installation instructions + should work perfectly for this simple package. </para> </section> <section> <title>GD Perl Module (1.8.3)</title> <para> - The GD library was written by Thomas Boutell a long while ago to - programatically generate images in C. Since then it's become almost a - defacto standard for programatic image construction. The Perl bindings - to it found in the GD library are used on a million web pages to generate - graphs on the fly. That's what bugzilla will be using it for so you'd - better install it if you want any of the graphing to work. + The GD library was written by Thomas Boutell a long while + ago to programatically generate images in C. Since then it's + become the defacto standard for programatic image + construction. The Perl bindings to it found in the GD library + are used on millions of web pages to generate graphs on the + fly. That's what bugzilla will be using it for so you must + install it if you want any of the graphing to work. </para> <para> - Actually bugzilla uses the Graph module which relies on GD itself, - but isn't that always the way with OOP. At any rate, you can find the - GD library on CPAN (link in Appendix B, Software Download Links). + Actually bugzilla uses the Graph module which relies on GD + itself. Isn't that always the way with object-oriented + programming? At any rate, you can find the GD library on CPAN + in <xref linkend="downloadlinks">. </para> <note> <para> - The Perl GD library requires some other libraries that may or may not be - installed on your system, including "libpng" and "libgd". The full requirements - are listed in the Perl GD library README. Just realize that if compiling GD fails, - it's probably because you're missing a required library. + The Perl GD library requires some other libraries that may + or may not be installed on your system, including + <classname>libpng</classname> and + <classname>libgd</classname>. The full requirements are + listed in the Perl GD library README. Just realize that if + compiling GD fails, it's probably because you're missing a + required library. </para> </note> </section> @@ -453,62 +486,78 @@ <title>Chart::Base Perl Module (0.99c)</title> <para> The Chart module provides bugzilla with on-the-fly charting - abilities. It can be installed in the usual fashion after it has been - fetched from CPAN where it is found as the Chart-x.x... tarball in a - directory to be listed in Appendix B, "Software Download Links". - Note that as with the GD perl - module, only the version listed above, or newer, will work. - Earlier - versions used GIF's, which are no longer supported by the latest - versions of GD. + abilities. It can be installed in the usual fashion after it + has been fetched from CPAN where it is found as the + Chart-x.x... tarball, linked in <xref linkend="downloadlinks">. Note that + as with the GD perl module, only the version listed above, or + newer, will work. Earlier versions used GIF's, which are no + longer supported by the latest versions of GD. </para> </section> <section> <title>DB_File Perl Module</title> <para> - DB_File is a module which allows Perl programs to make use of the facilities provided by - Berkeley DB version 1.x. This module is required by collectstats.pl which is used for - bug charting. If you plan to make use of bug charting, you must install this module. + DB_File is a module which allows Perl programs to make use + of the facilities provided by Berkeley DB version 1.x. This + module is required by collectstats.pl which is used for bug + charting. If you plan to make use of bug charting, you must + install this module. </para> </section> <section> <title>HTTP Server</title> <para> - You have a freedom of choice here - Apache, Netscape or any other - server on UNIX would do. You can easily run the web server on a different - machine than MySQL, but need to adjust the MySQL "bugs" user permissions - accordingly. + You have a freedom of choice here - Apache, Netscape or any + other server on UNIX would do. You can easily run the web + server on a different machine than MySQL, but need to adjust + the MySQL <quote>bugs</quote> user permissions accordingly. + <note> + <para>I strongly recommend Apache as the web server to use. + The Bugzilla Guide installation instructions, in general, + assume you are using Apache. As more users use different + webservers and send me information on the peculiarities of + installing using their favorite webserver, I will provide + notes for them.</para> + </note> </para> <para> - You'll want to make sure that your web server will run any file - with the .cgi extension as a cgi and not just display it. If you're using - apache that means uncommenting the following line in the srm.conf file: - <computeroutput>AddHandler cgi-script .cgi</computeroutput> + You'll want to make sure that your web server will run any + file with the .cgi extension as a cgi and not just display it. + If you're using apache that means uncommenting the following + line in the srm.conf file: + <programlisting> +AddHandler cgi-script .cgi + </programlisting> </para> <para> - With apache you'll also want to make sure that within the access.conf - file the line: - <computeroutput> - Options ExecCGI - </computeroutput> - is in the stanza that covers the directories you intend to put the bugzilla - .html and .cgi files into. + With apache you'll also want to make sure that within the + access.conf file the line: + <programlisting> +Options ExecCGI +</programlisting> + is in the stanza that covers the directories into which + you intend to put the bugzilla .html and .cgi files. </para> + <note> <para> - If you are using a newer version of Apache, both of the above lines will be - (or will need to be) in the httpd.conf file, rather than srm.conf or - access.conf. + Users of newer versions of Apache will generally find both + of the above lines will be in the httpd.conf file, rather + than srm.conf or access.conf. </para> + </note> <warning> <para> - There are two critical directories and a file that should not be a served by - the HTTP server. These are the <quote>data</quote> and <quote>shadow</quote> - directories and the - <quote>localconfig</quote> file. You should configure your HTTP server to not serve - content from these files. Failure to do so will expose critical passwords - and other data. Please see <xref linkend="htaccess"> for details. + There are important files and directories that should not + be a served by the HTTP server. These are most files in the + <quote>data</quote> and <quote>shadow</quote> directories + and the <quote>localconfig</quote> file. You should + configure your HTTP server to not serve content from these + files. Failure to do so will expose critical passwords and + other data. Please see <xref linkend="htaccess"> for details + on how to do this for Apache. I appreciate notes on how to + get this same functionality using other webservers. </para> </warning> </section> @@ -516,59 +565,65 @@ <section> <title>Installing the Bugzilla Files</title> <para> - You should untar the Bugzilla files into a directory that you're - willing to make writable by the default web server user (probably - <quote>nobody</quote>). You may decide to put the files off of the main web space - for your web server or perhaps off of /usr/local with a symbolic link - in the web space that points to the bugzilla directory. At any rate, - just dump all the files in the same place (optionally omitting the CVS - directories if they were accidentally tarred up with the rest of Bugzilla) - and make sure you can access the files in that directory through your - web server. + You should untar the Bugzilla files into a directory that + you're willing to make writable by the default web server user + (probably <quote>nobody</quote>). You may decide to put the + files off of the main web space for your web server or perhaps + off of <filename>/usr/local</filename> with a symbolic link in + the web space that points to the Bugzilla directory. At any + rate, just dump all the files in the same place, and make sure + you can access the files in that directory through your web + server. </para> <tip> <para> If you symlink the bugzilla directory into your Apache's - HTML heirarchy, you may receive "Forbidden" errors unless you - add the "FollowSymLinks" directive to the <Directory> entry - for the HTML root. + HTML heirarchy, you may receive + <errorname>Forbidden</errorname> errors unless you add the + <quote>FollowSymLinks</quote> directive to the + <Directory> entry for the HTML root. </para> </tip> <para> - Once all the files are in a web accessible directory, make that - directory writable by your webserver's user (which may require just - making it world writable). This is a temporary step until you run - the post-install <quote>checksetup.pl</quote> script, which locks down your - installation. - </para> - <para> - Lastly, you'll need to set up a symbolic link to /usr/bonsaitools/bin/perl - for the correct location of your perl executable (probably /usr/bin/perl). - Otherwise you must hack all the .cgi files to change where they look - for perl. To make future upgrades easier, you should use the symlink - approach. - <example> - <title>Setting up bonsaitools symlink</title> - <para> - Here's how you set up the Perl symlink on Linux to make Bugzilla work. - Your mileage may vary; if you are running on Solaris, you probably need to subsitute - <quote>/usr/local/bin/perl</quote> for <quote>/usr/bin/perl</quote> - below; if on certain other UNIX systems, - Perl may live in weird places like <quote>/opt/perl</quote>. As root, run these commands: - <programlisting> -bash# mkdir /usr/bonsaitools -bash# mkdir /usr/bonsaitools/bin + Once all the files are in a web accessible directory, make + that directory writable by your webserver's user. This is a + temporary step until you run the post-install + <filename>checksetup.pl</filename> script, which locks down your + installation. + </para> + <para> + Lastly, you'll need to set up a symbolic link to + <filename>/usr/bonsaitools/bin/perl</filename> for the correct + location of your perl executable (probably + <filename>/usr/bin/perl</filename>). Otherwise you must hack + all the .cgi files to change where they look for perl, or use + <xref linkend="setperl">, found in + <xref linkend="patches">. I suggest using the symlink + approach for future release compatability. + <example> + <title>Setting up bonsaitools symlink</title> + <para> + Here's how you set up the Perl symlink on Linux to make + Bugzilla work. Your mileage may vary. For some UNIX + operating systems, you probably need to subsitute + <quote>/usr/local/bin/perl</quote> for + <quote>/usr/bin/perl</quote> below; if on certain other + UNIX systems, Perl may live in weird places like + <quote>/opt/perl</quote>. As root, run these commands: + <programlisting> +bash# mkdir /usr/bonsaitools +bash# mkdir /usr/bonsaitools/bin bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl - </programlisting> - </para> - </example> - <tip> - <para> - If you don't have root access to set this symlink up, + </programlisting> + </para> + </example> + <tip> + <para> + If you don't have root access to set this symlink up, check out the - <xref linkend="setperl">, listed in <xref linkend="patches">. - It will change the path to perl in all your Bugzilla files for you. - </para> + <xref linkend="setperl">, listed in <xref + linkend="patches">. It will change the path to perl in all your Bugzilla files for you. + </para> </tip> </para> </section> @@ -581,10 +636,11 @@ bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl quality bug tracker. </para> <para> - First, you'll want to fix MySQL permissions to allow access from - Bugzilla. For the purpose of this Installation section, the Bugzilla username - will be "bugs", and will have minimal permissions. - + First, you'll want to fix MySQL permissions to allow access + from Bugzilla. For the purpose of this Installation section, + the Bugzilla username will be <quote>bugs</quote>, and will + have minimal permissions. + <warning> <para> Bugzilla has not undergone a thorough security audit. It @@ -594,199 +650,190 @@ bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl </para> <para>That would be bad.</para> </warning> - </para> - - <para> - Give the MySQL root user a password. MySQL passwords are - limited to 16 characters. - <simplelist> - <member> - <computeroutput> - <prompt>bash#</prompt> - <command>mysql -u root mysql</command> - </computeroutput> - </member> - <member> - <computeroutput> - <prompt>mysql></prompt> - <command> - UPDATE user SET Password=PASSWORD ('new_password') - WHERE user='root'; - </command> - </computeroutput> - </member> - <member> - <computeroutput> - <prompt>mysql></prompt> - <command>FLUSH PRIVILEGES;</command> - </computeroutput> - </member> - </simplelist> - From this point on, if you need to access MySQL as the - MySQL root user, you will need to use "mysql -u root -p" and - enter your new_password. Remember that MySQL user names have - nothing to do with Unix user names (login names). - </para> - <para> - Next, we create the "bugs" user, and grant sufficient - permissions for checksetup.pl, which we'll use later, to work - its magic. This also restricts the "bugs" user to operations - within a database called "bugs", and only allows the account - to connect from "localhost". Modify it to reflect your setup - if you will be connecting from another machine or as a different - user. - </para> - <para> - Remember to set bugs_password to some unique password. - <simplelist> - <member> - <computeroutput> - <prompt>mysql></prompt> - <command>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, - ALTER,CREATE,DROP,REFERENCES - ON bugs.* TO bugs@localhost - IDENTIFIED BY 'bugs_password';</command> - </computeroutput> - </member> - <member> - <computeroutput> - <prompt> - mysql> - </prompt> - <command> - FLUSH PRIVILEGES; - </command> - </computeroutput> - </member> - </simplelist> - </para> - <para> - Next, run the magic checksetup.pl script. (Many thanks to Holger - Schurig <holgerschurig@nikocity.de> for writing this script!) - It will make sure Bugzilla files and directories have reasonable - permissions, set up the "data" directory, and create all the MySQL - tables. - <simplelist> - <member> - <computeroutput> - <prompt>bash#</prompt> - <command>./checksetup.pl</command> - </computeroutput> - </member> - </simplelist> - The first time you run it, it will create a file called "localconfig". - </para> - </section> - - <section> - <title>Tweaking "localconfig"</title> - <para> - This file contains a variety of settings you may need to tweak including - how Bugzilla should connect to the MySQL database. - </para> - <para> - The connection settings include: - <orderedlist> - <listitem> - <para> - server's host: just use "localhost" if the MySQL server is - local - </para> - </listitem> - <listitem> - <para> - database name: "bugs" if you're following these directions - </para> - </listitem> - <listitem> - <para> - MySQL username: "bugs" if you're following these directions - </para> - </listitem> - <listitem> - <para> - Password for the "bugs" MySQL account above - </para> - </listitem> - </orderedlist> - </para> - <para> - You may also install .htaccess files that the Apache webserver will use - to restrict access to Bugzilla data files. See <xref linkend="htaccess">. - </para> - <para> - Once you are happy with the settings, re-run checksetup.pl. On this - second run, it will create the database and an administrator account - for which you will be prompted to provide information. - </para> - <para> - When logged into an administrator account once Bugzilla is running, - if you go to the query page (off of the bugzilla main menu), you'll - find an 'edit parameters' option that is filled with editable treats. - </para> - <para> - Should everything work, you should have a nearly empty copy of the bug - tracking setup. - </para> - <para> - The second time around, checksetup.pl will stall if it is on a - filesystem that does not fully support file locking via flock(), such as - NFS mounts. This support is required for Bugzilla to operate safely with - multiple instances. If flock() is not fully supported, it will stall at: - <errorcode>Now regenerating the shadow database for all bugs.</errorcode> - <note> + </para> + + <para> + Give the MySQL root user a password. MySQL passwords are + limited to 16 characters. + <simplelist> + <member> + <computeroutput> <prompt>bash#</prompt> <command>mysql + -u root mysql</command> </computeroutput> + </member> + <member> + <computeroutput> <prompt>mysql></prompt> <command> + UPDATE user SET Password=PASSWORD ('new_password') + WHERE user='root'; </command> </computeroutput> + </member> + <member> + <computeroutput> <prompt>mysql></prompt> <command>FLUSH + PRIVILEGES;</command> </computeroutput> + </member> + </simplelist> From this point on, if you need to access + MySQL as the MySQL root user, you will need to use + <command>mysql -u root -p</command> and enter your + new_password. Remember that MySQL user names have nothing to + do with Unix user names (login names). + </para> + <para> + Next, we create the <quote>bugs</quote> user, and grant + sufficient permissions for checksetup.pl, which we'll use + later, to work its magic. This also restricts the + <quote>bugs</quote> user to operations within a database + called <quote>bugs</quote>, and only allows the account to + connect from <quote>localhost</quote>. Modify it to reflect + your setup if you will be connecting from another machine or + as a different user. + </para> + <para> + Remember to set bugs_password to some unique password. + <simplelist> + <member> + <computeroutput> + <prompt>mysql></prompt> + <command>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, + ALTER,CREATE,DROP,REFERENCES + ON bugs.* TO bugs@localhost + IDENTIFIED BY 'bugs_password';</command> + </computeroutput> + </member> + <member> + <computeroutput> + <prompt> + mysql> + </prompt> + <command> + FLUSH PRIVILEGES; + </command> + </computeroutput> + </member> + </simplelist> + </para> + <para> + Next, run the magic checksetup.pl script. (Many thanks to + Holger Schurig <holgerschurig@nikocity.de> for writing + this script!) It will make sure Bugzilla files and directories + have reasonable permissions, set up the + <filename>data</filename> directory, and create all the MySQL + tables. + <simplelist> + <member> + <computeroutput> <prompt>bash#</prompt> + <command>./checksetup.pl</command> </computeroutput> + </member> + </simplelist> The first time you run it, it will create a + file called <filename>localconfig</filename>. + </para> + </section> + + <section> + <title>Tweaking <filename>localconfig</filename></title> + <para> + This file contains a variety of settings you may need to tweak including + how Bugzilla should connect to the MySQL database. + </para> + <para> + The connection settings include: + <orderedlist> + <listitem> <para> - The second time you run checksetup.pl, you should become the - user your web server runs as, and that you ensure that you set the - "webservergroup" parameter in localconfig to match the web - server's group - name, if any. I believe, for the next release of Bugzilla, - this will - be fixed so that Bugzilla supports a "webserveruser" parameter - in localconfig - as well. - <example> - <title>Running checksetup.pl as the web user</title> - <para> - Assuming your web server runs as user "apache", - and Bugzilla is installed in - "/usr/local/bugzilla", here's one way to run checksetup.pl - as the web server user. - As root, for the <emphasis>second run</emphasis> - of checksetup.pl, do this: - <programlisting> -bash# chown -R apache:apache /usr/local/bugzilla -bash# su - apache -bash# cd /usr/local/bugzilla -bash# ./checksetup.pl - </programlisting> - </para> - </example> + server's host: just use <quote>localhost</quote> if the + MySQL server is local </para> - </note> - </para> + </listitem> + <listitem> + <para> + database name: <quote>bugs</quote> if you're following + these directions + </para> + </listitem> + <listitem> + <para> + MySQL username: <quote>bugs</quote> if you're following + these directions + </para> + </listitem> + <listitem> + <para> + Password for the <quote>bugs</quote> MySQL account above + </para> + </listitem> + </orderedlist> + </para> + <para> + You should also install .htaccess files that the Apache + webserver will use to restrict access to Bugzilla data files. + See <xref + linkend="htaccess">. + </para> + <para> + Once you are happy with the settings, re-run + <filename>checksetup.pl</filename>. On this second run, it will + create the database and an administrator account for which + you will be prompted to provide information. + </para> + <para> + When logged into an administrator account once Bugzilla is + running, if you go to the query page (off of the Bugzilla main + menu), you'll find an <quote>edit parameters</quote> option + that is filled with editable treats. + </para> + <para> + Should everything work, you will have a nearly empty Bugzilla + database and a newly-created <filename>localconfig</filename> + file in your Bugzilla root directory. + </para> + <para> <note> <para> - The checksetup.pl script is designed so that you can run - it at any time without causing harm. You should run it - after any upgrade to Bugzilla. + The second time you run checksetup.pl, you should become + the user your web server runs as, and that you ensure that + you set the <quote>webservergroup</quote> parameter in localconfig to + match the web server's group name, if any. I believe, + for the next release of Bugzilla, this will be fixed so + that Bugzilla supports a <quote>webserveruser</quote> parameter in + localconfig as well. + <example> + <title>Running checksetup.pl as the web user</title> + <para> + Assuming your web server runs as user "apache", and + Bugzilla is installed in "/usr/local/bugzilla", here's + one way to run checksetup.pl as the web server user. + As root, for the <emphasis>second run</emphasis> of + checksetup.pl, do this: + <programlisting> +bash# chown -R apache:apache /usr/local/bugzilla +bash# su - apache +bash# cd /usr/local/bugzilla +bash# ./checksetup.pl + </programlisting> + </para> + </example> </para> </note> - </section> - - <section> - <title>Setting Up Maintainers Manually (Optional)</title> + </para> + <note> <para> - If you want to add someone else to every group by hand, you + The checksetup.pl script is designed so that you can run + it at any time without causing harm. You should run it + after any upgrade to Bugzilla. + </para> + </note> + </section> + + <section> + <title>Setting Up Maintainers Manually (Optional)</title> + <para> + If you want to add someone else to every group by hand, you can do it by typing the appropriate MySQL commands. Run - '<computeroutput> mysql -u root -p bugs</computeroutput>' You + <command> mysql -u root -p bugs</command> You may need different parameters, depending on your security settings. Then: <simplelist> <member> <computeroutput> <prompt>mysql></prompt> <command>update profiles set groupset=0x7fffffffffffffff where - login_name = 'XXX';</command> </computeroutput> + login_name = 'XXX';</command> </computeroutput> (yes, that's <emphasis>fifteen</emphasis><quote>f</quote>'s. </member> </simplelist> replacing XXX with the Bugzilla email address. </para> @@ -1156,33 +1203,74 @@ bash# ./checksetup.pl <parameter>0</parameter>. </para> </section> + + <section id="mod_throttle" xreflabel="Using mod_throttle to prevent Denial of Service attacks"> + <title><filename>mod_throttle</filename> and Security</title> + <para> + It is possible for a user, by mistake or on purpose, to access + the database many times in a row which can result in very slow + access speeds for other users. If your Bugzilla installation + is experiencing this problem , you may install the Apache + module <filename>mod_throttle</filename> which can limit + connections by ip-address. You may download this module at + <ulink + url="http://www.snert.com/Software/Throttle/">http://www.snert.com/Software/Throttle/</ulink>. Follow the instructions to install into your Apache install. <emphasis>This module only functions with the Apache web server!</emphasis>. You may use the <command>ThrottleClientIP</command> command provided by this module to accomplish this goal. See the <ulink url="http://www.snert.com/Software/Throttle/">Module Instructions</ulink> for more information. </para> + </section> + + <section id="content_type" xreflabel="Preventing untrusted Bugzilla contentfrom executing malicious Javascript code"> + <title>Preventing untrusted Bugzilla content from executing malicious Javascript code</title> + <para>It is possible for a Bugzilla to execute malicious + Javascript code. Due to internationalization concerns, we are + unable to incorporate the code changes necessary to fulfill + the CERT advisory requirements mentioned in <ulink + url="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3">http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</ulink>. Executing the following code snippet from a UNIX command shell will rectify the problem if your Bugzilla installation is intended for an English-speaking audience. As always, be sure your Bugzilla installation has a good backup before making changes, and I recommend you understand what the script is doing before executing it. </para> + <para><programlisting> +bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ + do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' >$i.tmp; \ + mv $i.tmp $i; done + </programlisting></para> + <para> + All this one-liner command does is search for all instances of + <quote>Content-type: text/html</quote> and replaces it with + <quote>Content-Type: text/html; charset=ISO-8859-1</quote>. + This specification prevents possible Javascript attacks on the + browser, and is suggested for all English-speaking sites. For + non-english-speaking Bugzilla sites, I suggest changing + <quote>ISO-8859-1</quote>, above, to <quote>UTF-8</quote>. + </para> + </section> + <section> <title>UNIX Installation Instructions History</title> <para> - This document was originally adapted from the Bonsai installation - instructions by Terry Weissman <terry@mozilla.org>. + This document was originally adapted from the Bonsai + installation instructions by Terry Weissman + <terry@mozilla.org>. </para> <para> - The February 25, 1999 re-write of this page was done by Ry4an Brase - <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt, - Martin Pool, & Dan Mosedale (But don't send bug reports to them; - report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi , - project Webtools, component Bugzilla). + The February 25, 1999 re-write of this page was done by Ry4an + Brase <ry4an@ry4an.org>, with some edits by Terry + Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But + don't send bug reports to them; report them using bugzilla, at + http://bugzilla.mozilla.org/enter_bug.cgi , project Webtools, + component Bugzilla). </para> <para> - This document was heavily modified again Wednesday, March 07 2001 to - reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The - securing MySQL section should be changed to become standard procedure - for Bugzilla installations. + This document was heavily modified again Wednesday, March 07 + 2001 to reflect changes for Bugzilla 2.12 release by Matthew + P. Barnson. The securing MySQL section should be changed to + become standard procedure for Bugzilla installations. </para> <para> - Finally, the README in its entirety was marked up in SGML and included into - the Guide on April 24, 2001 by Matt Barnson. Since that time, it's undergone - extensive modification as Bugzilla grew. + Finally, the README in its entirety was marked up in SGML and + included into the Guide on April 24, 2001 by Matt Barnson. + Since that time, it's undergone extensive modification as + Bugzilla grew. </para> <para> - Comments from people using this Guide for the first time are particularly welcome. + Comments from people using this Guide for the first time are + particularly welcome. </para> </section> </section> @@ -1217,27 +1305,33 @@ bash# ./checksetup.pl picnic. Support for Win32 has improved dramatically in the last few releases, but, if you choose to proceed, you should be a <emphasis>very</emphasis> skilled Windows Systems - Administrator with both strong troubleshooting abilities and - a high tolerance for pain. Bugzilla on NT requires hacking - source code and implementing some advanced utilities. What - follows is the recommended installation procedure for Win32; - additional suggestions are provided in <xref linkend="faq">. + Administrator with strong troubleshooting abilities, a high + tolerance for pain, and moderate perl skills. Bugzilla on NT + requires hacking source code and implementing some advanced + utilities. What follows is the recommended installation + procedure for Win32; additional suggestions are provided in + <xref linkend="faq">. </para> </note> <procedure> <step> <para> - Install <ulink url="http://www.apache.org/">Apache Web Server</ulink> - for Windows. + Install <ulink url="http://www.apache.org/">Apache Web + Server</ulink> for Windows, and copy the Bugzilla files + somewhere Apache can serve them. Please follow all the + instructions referenced in <xref linkend="installation"> + regarding your Apache configuration, particularly + instructions regarding the <quote>AddHandler</quote> + parameter and <quote>ExecCGI</quote>. </para> <note> <para> - You may also use Internet Information Server or Personal Web - Server for this purpose. However, setup is slightly more - difficult. If ActivePerl doesn't seem to handle your file - associations correctly (for .cgi and .pl files), please - consult <xref linkend="faq">. + You may also use Internet Information Server or Personal + Web Server for this purpose. However, setup is quite + different. If ActivePerl doesn't seem to handle your + file associations correctly (for .cgi and .pl files), + please consult <xref linkend="faq">. </para> <para> If you are going to use IIS, if on Windows NT you must @@ -1299,8 +1393,7 @@ bash# ./checksetup.pl Install MySQL for NT. <note> <para> - You can download MySQL for Windows NT from <ulink - url="http://www.mysql.com/">MySQL.com</ulink>. Some find it helpful to use the WinMySqlAdmin utility, included with the download, to set up the database. + You can download MySQL for Windows NT from <ulink url="http://www.mysql.com/">MySQL.com</ulink>. Some find it helpful to use the WinMySqlAdmin utility, included with the download, to set up the database. </para> </note> </para> @@ -1393,13 +1486,21 @@ bash# ./checksetup.pl this line: </para> <para> - "my $webservergid = getgrnam($my_webservergroup); " + <programlisting> +my $webservergid = getgrnam($my_webservergroup); + </programlisting> </para> <para> to </para> <para> - "my $webservergid = $my_webservergroup; " + <programlisting> +my $webservergid = $my_webservergroup; + </programlisting> +or the name of the group you wish to own the files explicitly: + <programlisting> +my $webservergid = 'Administrators' + </programlisting> </para> </step> @@ -1412,8 +1513,7 @@ bash# ./checksetup.pl <step> <para>Edit <filename>localconfig</filename> to suit your requirements. Set <varname>$db_pass</varname> to your - <quote>bugs_password</quote> from <xref - linkend="ntbugs-password">, and <varname>$webservergroup</varname> to <quote>8</quote>.</para> + <quote>bugs_password</quote> from <xref linkend="ntbugs-password">, and <varname>$webservergroup</varname> to <quote>8</quote>.</para> <note> <para>Not sure on the <quote>8</quote> for <varname>$webservergroup</varname> above. If it's @@ -1455,8 +1555,7 @@ bash# ./checksetup.pl <procedure> <step> <para> - Download NTsendmail, available from<ulink - url="http://www.ntsendmail.com/"> www.ntsendmail.com</ulink>. You must have a "real" mail server which allows you to relay off it in your $ENV{"NTsendmail"} (which you should probably place in globals.pl) + Download NTsendmail, available from<ulink url="http://www.ntsendmail.com/"> www.ntsendmail.com</ulink>. You must have a "real" mail server which allows you to relay off it in your $ENV{"NTsendmail"} (which you should probably place in globals.pl) </para> </step> @@ -1503,7 +1602,15 @@ $mail->send($from,$to,$subject,$msg); </programlisting> </para> <note> - <para>The code above needs testing as well to make sure it is correct.</para> + <para> + Some have found success using the commercial product, + <productname>Windmail</productname>. + You could try replacing your sendmail calls with: + <programlisting> +open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log"; + </programlisting> + or something to that effect. + </para> </note> </step> </procedure> @@ -1568,9 +1675,9 @@ exit; <step> <note> <para> - This step is completely optional if you are using IIS or - another web server which only decides on an interpreter - based upon the file extension (.pl), rather than the + This step is optional if you are using IIS or another + web server which only decides on an interpreter based + upon the file extension (.pl), rather than the <quote>shebang</quote> line (#/usr/bonsaitools/bin/perl) </para> </note> @@ -1583,8 +1690,7 @@ exit; utility to speed part of this procedure, available in the <xref linkend="patches"> section of The Bugzilla Guide. However, it requires the Cygwin GNU-compatible environment - for Win32 be set up in order to work. See <ulink - url="http://www.cygwin.com/">http://www.cygwin.com/</ulink> for details on obtaining Cygwin. + for Win32 be set up in order to work. See <ulink url="http://www.cygwin.com/">http://www.cygwin.com/</ulink> for details on obtaining Cygwin. </para> </step> @@ -1604,10 +1710,11 @@ system ("perl processmail.pl",@ARGLIST); <tip> <para> - If you are using IIS 5.0 or higher, you must add cgi + If you are using IIS or Personal Web Server, you must add cgi relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), - such as: <programlisting> + such as: + <programlisting> .cgi to: <perl install directory>\perl.exe %s %s .pl to: <perl install directory>\perl.exe %s %s GET,HEAD,POST @@ -1625,11 +1732,10 @@ GET,HEAD,POST From Andrew Pearson: <blockquote> <para> - "You can make Bugzilla work with Personal Web Server for - Windows 98 and higher, as well as for IIS 4.0. Microsoft has - information available at - <ulink url=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"> - http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</ulink> + You can make Bugzilla work with Personal Web Server for + Windows 98 and higher, as well as for IIS 4.0. + Microsoft has information available at <ulink url=" + http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</ulink> </para> <para> Basically you need to add two String Keys in the @@ -1651,119 +1757,28 @@ GET,HEAD,POST </para> </tip> <tip> - <para>"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</para> - <blockquote> - <para> - 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). - </para> - <para> - In checksetup.pl, I did the following... - </para> - <procedure> - <step> - <programlisting> -my $webservergid = getgrnam($my_webservergroup); + <para> + If attempting to run Bugzilla 2.12 or older, you will need + to remove encrypt() calls from the Perl source. This is + <emphasis>not necessary</emphasis> for Bugzilla 2.13 and + later. + <example> + <title>Removing encrypt() for Windows NT Bugzilla version + 2.12 or earlier</title> + <para> + Replace this: + <programlisting> +SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); +my $enteredcryptpwd = FetchOneColumn(); </programlisting> - <para>to</para> - <programlisting> -my $webservergid = 'Administrators' + with this: + <programlisting> +my $enteredcryptpwd = $enteredpwd </programlisting> - </step> - <step> - <para> - I then ran checksetup.pl - </para> - </step> - <step> - <para> - I removed all the encrypt() - <example> - <title>Removing encrypt() for Windows NT installations</title> - <para> - Replace this: - <programlisting> -SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . - SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); -my $enteredcryptpwd = FetchOneColumn(); - </programlisting> - with this: - <programlisting> -my $enteredcryptpwd = $enteredpwd - </programlisting> - in cgi.pl. - </para> - </example> - </para> - </step> - <step> - <para> - I renamed processmail to processmail.pl - </para> - </step> - <step> - <para> - I altered the sendmail statements to windmail: - <programlisting> -open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log"; - </programlisting> - </para> - <para> - The quotes around the dir is for the spaces. mail.log is for the output - </para> - </step> - </procedure> - </blockquote> - </tip> - <tip> - <para> - This was some late breaking information from Jan Evert. Sorry for the lack of formatting. + in cgi.pl. + </para> + </example> </para> - <literallayout> -I'm busy installing bugzilla on a WinNT machine and I thought I'd notify you -at this moment of the commments I have to section 2.2.1 of the bugzilla -guide (at http://www.trilobyte.net/barnsons/html/). - -Step 1: -I've used apache, installation is really straightforward. -After reading the Unix installation instructions, I found that it is -necessary to add the ExecCGI option to the bugzilla directory. Also the -'AddHandler' line for .cgi is by default commented out. - -Step 3: although just a detail, 'ppm install <module%gt;' will also work -(without .ppd). And, it can also download these automatically from -ActiveState. - -Step 4: although I have cygwin installed, it seems that it is not necessary. -On my machine cygwin is not in the PATH and everything seems to work as -expected. -However, I've not used everything yet. - -Step 6: the 'bugs_password' given in SQL command d needs to be edited into -localconfig later on (Step 7) if the password is not empty. I've also edited -it into globals.pl, but I'm not sure that is needed. In both places, the -variable is named db_pass. - -Step 8: all the sendmail replacements mentioned are not as simple as -described there. Since I am not familiar (yet) with perl, I don't have any -mail working yet. - -Step 9: in globals.pl the encrypt() call can be replaced by just the -unencrypted password. In CGI.pl, the complete SQL command can be removed. - -Step 11: I've only changed the #! lines in *.cgi. I haven't noticed problems -with the system() call yet. -There seem to be only four system() called programs: processmail.pl (handled -by step 10), syncshadowdb (which should probably get the same treatment as -processmail.pl), diff and mysqldump. The last one is only needed with the -shadowdb feature (which I don't use). - -There seems to be one step missing: copying the bugzilla files somehwere -that apache can serve them. - -Just noticed the updated guide... Brian's comment is new. His first comment -will work, but opens up a huge security hole. - </literallayout> </tip> </section> </section> diff --git a/docs/sgml/integration.sgml b/docs/sgml/integration.sgml index c7aa78f82..e0547c365 100644 --- a/docs/sgml/integration.sgml +++ b/docs/sgml/integration.sgml @@ -5,49 +5,59 @@ <chapter id="integration"> <title>Integrating Bugzilla with Third-Party Tools</title> - <section id="bonsai"> + <section id="bonsai" xreflabel="Bonsai, the Mozilla automated CVS management system"> <title>Bonsai</title> - <para>We need Bonsai integration information.</para> + <para>Bonsai is a web-based tool for managing <xref + linkend="cvs"> + . Using Bonsai, administrators can control open/closed status + of trees, query a fast relational database back-end for change, + branch, and comment information, and view changes made since the + last time the tree was closed. These kinds of changes cause the + engineer responsible to be <quote>on the hook</quote> (include + cool URL link here for Hook policies at mozilla.org). Bonsai + also includes gateways to <xref + linkend="tinderbox"> and Bugzilla </para> </section> - <section id="cvs"> + <section id="cvs" xreflabel="CVS, the Concurrent Versioning System"> <title>CVS</title> - <para>CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</para> + <para>CVS integration is best accomplished, at this point, using + the Bugzilla Email Gateway. There have been some files + submitted to allow greater CVS integration, but we need to make + certain that Bugzilla is not tied into one particular software + management package.</para> + <para> + Follow the instructions in the FAQ for enabling Bugzilla e-mail + integration. Ensure that your check-in script sends an email to + your Bugzilla e-mail gateway with the subject of <quote>[Bug + XXXX]</quote>, and you can have CVS check-in comments append + to your Bugzilla bug. If you have your check-in script include + an @resolution field, you can even change the Bugzilla bug + state. + </para> </section> - <section id="scm"> + <section id="scm" xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS"> <title>Perforce SCM</title> <para> - You can find the project page for Bugzilla and Teamtrack Perforce integration 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. + You can find the project page for Bugzilla and Teamtrack + Perforce integration (p4dti) at: <ulink + url="http://www.ravenbrook.com/project/p4dti/"> http://www.ravenbrook.com/project/p4dti</ulink> . <quote>p4dti</quote> is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html"> http://public.perforce.com/public/perforce/p4dti/index.html</ulink>. </para> <para> - 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. + Integration of Perforce with Bugzilla, once patches are applied, + is seamless. Perforce replication information will appear below + the comments of each bug. Be certain you have a matching set of + patches for the Bugzilla version you are installing. p4dti is + designed to support multiple defect trackers, and maintains its + own documentation for it. Please consult the pages linked above + for further information. </para> </section> - <section id="tinderbox"> - <title>Tinderbox</title> - <para>We need Tinderbox integration information</para> + <section id="tinderbox" xreflabel="Tinderbox, the Mozilla automated build management system"> + <title>Tinderbox/Tinderbox2</title> + <para>We need Tinderbox integration information.</para> </section> </chapter> diff --git a/docs/sgml/patches.sgml b/docs/sgml/patches.sgml index 8ebfdee15..3a1ce90d2 100644 --- a/docs/sgml/patches.sgml +++ b/docs/sgml/patches.sgml @@ -3,6 +3,40 @@ <appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla"> <title>Useful Patches and Utilities for Bugzilla</title> + <para>Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</para> + + <section id="rewrite" xreflabel="Apache mod_rewrite magic"> + <title>Apache <filename>mod_rewrite</filename> magic</title> + <para>Apache's <filename>mod_rewrite</filename> module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</para> + <orderedlist> + <listitem> + <para> + Make it so if someone types + <computeroutput>http://www.foo.com/12345</computeroutput>, + Bugzilla spits back + http://www.foo.com/show_bug.cgi?id=12345. Try setting up + your VirtualHost section for Bugzilla with a rule like + this:</para> + <programlisting> +<![CDATA[ +<VirtualHost 12.34.56.78> +RewriteEngine On +RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R] +</VirtualHost> +]]> + </programlisting> + + </listitem> + <listitem> + <para>There are many, many more things you can do with + mod_rewrite. As time goes on, I will include many more in + the Guide. For now, though, please refer to the mod_rewrite + documentation at <ulink + url="http://www.apache.org">http://www.apache.org</ulink></para> + </listitem> + </orderedlist> + </section> + <section id="setperl" xreflabel="The setperl.csh Utility"> <title>The setperl.csh Utility</title> <para> You can use the "setperl.csh" utility to quickly and diff --git a/docs/sgml/using.sgml b/docs/sgml/using.sgml index fd5901196..91a7658cd 100644 --- a/docs/sgml/using.sgml +++ b/docs/sgml/using.sgml @@ -31,7 +31,7 @@ Chapter: Using Bugzilla <title>Using Bugzilla</title> <epigraph> <para> - What, Why, How, & What's in it for me? + What, Why, How, & Where? </para> </epigraph> @@ -92,8 +92,10 @@ system against which all others are measured. </listitem> <listitem> <para> - available integration with automated software configuration management systems, including - Perforce and CVS + available integration with automated software + configuration management systems, including Perforce and + CVS (through the Bugzilla email interface and + checkin/checkout scripts) </para> </listitem> <listitem> @@ -104,23 +106,28 @@ system against which all others are measured. </itemizedlist> </para> <para> - Despite its current robustness and popularity, however, Bugzilla - faces some near-term challenges, such as reliance on a single database, a lack of - abstraction of the user interface and program logic, verbose email bug - notifications, a powerful but daunting query interface, little reporting configurability, - problems with extremely large queries, some unsupportable bug resolution options, - no internationalization, and dependence on some nonstandard libraries. + Despite its current robustness and popularity, Bugzilla faces + some near-term challenges, such as reliance on a single + database, a lack of abstraction of the user interface and + program logic, verbose email bug notifications, a powerful but + daunting query interface, little reporting configurability, + problems with extremely large queries, some unsupportable bug + resolution options, little internationalization (although non-US + character sets are accepted for comments), 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". + Some recent headway has been made on the query front, however. + If you are using the latest version of Bugzilla, you should see + a <quote>simple search</quote> 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. + Despite these small problems, Bugzilla is very hard to beat. It + is under <emphasis>very</emphasis> active development to address + the current issues, and continually gains new features. </para> </section> @@ -132,50 +139,57 @@ system against which all others are measured. </para> </epigraph> <para> - For many years, defect-tracking software has remained principally the domain - of large software development houses. Even then, most shops never bothered - with bug-tracking software, and instead simply relied on shared lists and - email to monitor the status of defects. This procedure is error-prone and - tends to cause those bugs judged least significant by developers to be + For many years, defect-tracking software has remained + principally the domain of large software development houses. + Even then, most shops never bothered with bug-tracking software, + and instead simply relied on shared lists and email to monitor + the status of defects. This procedure is error-prone and tends + to cause those bugs judged least significant by developers to be dropped or ignored. </para> <para> - These days, many companies are finding that integrated defect-tracking - systems reduce downtime, increase productivity, and raise customer - satisfaction with their systems. Along with full disclosure, an open - bug-tracker allows manufacturers to keep in touch with their clients - and resellers, to communicate about problems effectively throughout - the data management chain. Many corporations have also discovered that - defect-tracking helps reduce costs by providing IT support accountability, - telephone support knowledge bases, and a common, well-understood system - for accounting for unusual system or software issues. + These days, many companies are finding that integrated + defect-tracking systems reduce downtime, increase productivity, + and raise customer satisfaction with their systems. Along with + full disclosure, an open bug-tracker allows manufacturers to + keep in touch with their clients and resellers, to communicate + about problems effectively throughout the data management chain. + Many corporations have also discovered that defect-tracking + helps reduce costs by providing IT support accountability, + telephone support knowledge bases, and a common, well-understood + system for accounting for unusual system or software issues. </para> <para> But why should <emphasis>you</emphasis> use Bugzilla? </para> <para> - 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 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 + 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 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 </para> <para> - Bugzilla can dramatically increase the productivity and accountability - of individual employees by providing a documented workflow and positive - feedback for good performance. How many times do you wake up in the - morning, remembering that you were supposed to do *something* today, - but you just can't quite remember? Put it in Bugzilla, and you have a record - of it from which you can extrapolate milestones, predict product versions - for integration, and by using Bugzilla's e-mail integration features - be able to follow the discussion trail that led to critical decisions. + Bugzilla can dramatically increase the productivity and + accountability of individual employees by providing a documented + workflow and positive feedback for good performance. How many + times do you wake up in the morning, remembering that you were + supposed to do <emphasis>something</emphasis> today, but you + just can't quite remember? Put it in Bugzilla, and you have a + record of it from which you can extrapolate milestones, predict + product versions for integration, and by using Bugzilla's e-mail + integration features be able to follow the discussion trail that + led to critical decisions. </para> <para> - Ultimately, Bugzilla puts the power in your hands to improve your value - to your employer or business while providing a usable framework for your natural - attention to detail and knowledge store to flourish. + Ultimately, Bugzilla puts the power in your hands to improve + your value to your employer or business while providing a usable + framework for your natural attention to detail and knowledge + store to flourish. </para> </section> @@ -189,46 +203,45 @@ system against which all others are measured. <para> 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 - developing end-user mastery of Bugzilla, so you may fully enjoy the benefits - afforded by using this reliable open-source bug-tracking software. + 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 developing end-user + mastery of Bugzilla, so you may fully enjoy the benefits + afforded by using this reliable open-source bug-tracking + software. </para> <para> - Throughout this portion of the Guide, we will refer to user account - options available at the Bugzilla test installation, + Throughout this portion of the Guide, we will refer to user + account options available at the Bugzilla test installation, <ulink url="http://landfill.tequilarista.org/"> - landfill.tequilarista.org</ulink>. + 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> + 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. Additionally, - Landfill often runs cutting-edge versions of Bugzilla for testing, so some things - may work slightly differently than mentioned here. + </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. 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"> <title>Create a Bugzilla Account</title> <para> - First things first! If you want to use Bugzilla, first you need to create - an account. Consult with the administrator responsible for your installation - of Bugzilla for the URL you should use to access it. - If you're test-driving the end-user Bugzilla experience, use this URL: - <ulink url="http://landfill.tequilarista.org/bugzilla-tip/"> - http://landfill.tequilarista.org/bugzilla-tip/</ulink> + First things first! If you want to use Bugzilla, first you + need to create an account. Consult with the administrator + responsible for your installation of Bugzilla for the URL you + should use to access it. If you're test-driving the end-user + Bugzilla experience, use this URL: <ulink + url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink> </para> <orderedlist> <listitem> @@ -238,64 +251,81 @@ system against which all others are measured. </listitem> <listitem> <para> - Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself) - in the spaces provided, then select the "Create Account" button. + Enter your "E-mail address" and "Real Name" (or whatever + name you want to call yourself) in the spaces provided, + then select the "Create Account" button. </para> </listitem> <listitem> <para> - Within 5-10 minutes, you should receive an email to the address you provided above, - which contains your login name (generally the same as the email address), and - a password you can use to access your account. This password is randomly generated, - and should be changed at your nearest opportunity (we'll go into how to do it later). + Within moments, you should receive an email to the address + you provided above, which contains your login name + (generally the same as the email address), and a password + you can use to access your account. This password is + randomly generated, and should be changed at your nearest + opportunity (we'll go into how to do it later). </para> </listitem> <listitem> <para> - Click the "Log In" link in the yellow area at the bottom of the page in your browser, - then enter your "E-mail address" and "Password" you just received into the spaces provided, - and select "Login". + Click the <quote>Log In</quote> link in the yellow area at + the bottom of the page in your browser, then enter your + <quote>E-mail address</quote> and <quote>Password</quote> + you just received into the spaces provided, and select + <quote>Login</quote>. <note> <para> - If you ever forget your password, you can come back to this page, enter your - "E-mail address", then select the "E-mail me a password" button to have your password - mailed to you again so that you can login. + If you ever forget your password, you can come back to + this page, enter your <quote>E-mail address</quote>, + then select the <quote>E-mail me a password</quote> + button to have your password mailed to you again so + that you can login. </para> </note> <caution> <para> - Many modern browsers include an "Auto-Complete" or "Form Fill" feature to - remember the user names and passwords you type in at many sites. Unfortunately, - sometimes they attempt to "guess" what you will put in as your password, and guess - wrong. If you notice a text box is already filled out, please overwrite the contents - of the text box so you can be sure to input the correct information. + Many modern browsers include an + <quote>Auto-Complete</quote> or <quote>Form + Fill</quote> feature to remember the user names and + passwords you type in at many sites. Unfortunately, + sometimes they attempt to guess what you will put in + as your password, and guess wrong. If you notice a + text box is already filled out, please overwrite the + contents of the text box so you can be sure to input + the correct information. </para> </caution> </para> </listitem> </orderedlist> <para> - Congratulations! If you followed these directions, you now are the - proud owner of a user account on landfill.tequilarista.org (Landfill) or - your local Bugzilla install. You should now see in your browser a - page called the "Bugzilla Query Page". It may look daunting, but - with this Guide to walk you through it, you will master it in no time. + Congratulations! If you followed these directions, you now + are the proud owner of a user account on + landfill.tequilarista.org (Landfill) or your local Bugzilla + install. You should now see in your browser a page called the + <quote>Bugzilla Query Page</quote>. It may look daunting, but with this + Guide to walk you through it, you will master it in no time. </para> </section> <section id="query"> <title>The Bugzilla Query Page</title> <para> - The Bugzilla Query Page is the heart and soul of Bugzilla. It is the master - interface where you can find any bug report, comment, or patch currently in the Bugzilla - system. We'll go into how to create your own bug report later on. + The Bugzilla Query Page is the heart and soul of the Bugzilla + user experience. It is the master interface where you can + find any bug report, comment, or patch currently in the + Bugzilla system. We'll go into how to create your own bug + report later on. </para> <para> - There are efforts underway to simplify query usage. If you have a local installation - of Bugzilla 2.12 or higher, you should have "quicksearch.html" available - to use and simplify your searches. There is also, or shortly will be, a helper - for the query interface, called "queryhelp.cgi". Landfill tends to run the latest code, - so these two utilities should be available there for your perusal. + There are efforts underway to simplify query usage. If you + have a local installation of Bugzilla 2.12 or higher, you + should have <filename>quicksearch.html</filename> available to + use and simplify your searches. There is also a helper for + the query interface, called + <filename>queryhelp.cgi</filename>. Landfill tends to run the + latest code, so these two utilities should be available there + for your perusal. </para> <para> At this point, please visit the main Bugzilla site, @@ -303,47 +333,57 @@ system against which all others are measured. bugzilla.mozilla.org</ulink>, to see a more fleshed-out query page. </para> <para> - The first thing you need to notice about the Bugzilla Query Page is that - nearly every box you see on your screen has a hyperlink nearby, explaining what - it is or what it does. Near the upper-left-hand corner of your browser window - you should see the word "Status" underlined. Select it. + The first thing you need to notice about the Bugzilla Query + Page is that nearly every box you see on your screen has a + hyperlink nearby, explaining what it is or what it does. Near + the upper-left-hand corner of your browser window you should + see the word <quote>Status</quote> underlined. Select it. </para> <para> - Notice the page that popped up? Every underlined word you see on your screen - is a hyperlink that will take you to context-sensitive help. - Click around for a while, and learn what everything here does. To return - to the query interface after pulling up a help page, use the "Back" button in - your browser. + Notice the page that popped up? Every underlined word you see + on your screen is a hyperlink that will take you to + context-sensitive help. Click around for a while, and learn + what everything here does. To return to the query interface + after pulling up a help page, use the <quote>Back</quote> + button in your browser. </para> <para> - I'm sure that after checking out the online help, you are now an Expert - on the Bugzilla Query Page. If, however, you feel you haven't mastered it yet, - let me walk you through making a few successful queries to find out what there - are in the Bugzilla bug-tracking system itself. + I'm sure that after checking out the online help, you are now + an expert on the Bugzilla Query Page. If, however, you feel + you haven't mastered it yet, let me walk you through making a + few successful queries to find out what there are in the + Bugzilla bug-tracking system itself. </para> <orderedlist> <listitem> <para> - Ensure you are back on the "Bugzilla Query Page" - Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys", - "Priority", or "Severity". The default query for "Status" is to find all bugs that - are NEW, ASSIGNED, or REOPENED, which is what we want. If you don't select anything - in the other 5 scrollboxes there, then you are saying that "any of these are OK"; - we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95" - OpSys (Operating System). You're smart, I think you have it figured out. + Ensure you are back on the <quote>Bugzilla Query + Page</quote>. Do nothing in the boxes marked "Status", + "Resolution", "Platform", "OpSys", "Priority", or + "Severity". The default query for "Status" is to find all + bugs that are NEW, ASSIGNED, or REOPENED, which is what we + want. If you don't select anything in the other 5 + scrollboxes there, then you are saying that "any of these + are OK"; we're not locking ourselves into only finding + bugs on the "DEC" Platform, or "Windows 95" OpSys + (Operating System). You're smart, I think you have it + figured out. </para> <para> - Basically, selecting <emphasis>anything</emphasis> on the query page narrows your search - down. Leaving stuff unselected, or text boxes unfilled, broadens your search! + Basically, selecting <emphasis>anything</emphasis> on the + query page narrows your search down. Leaving stuff + unselected, or text boxes unfilled, broadens your search. </para> </listitem> <listitem> <para> - You see the box immediately below the top six boxes that contains an "Email" text box, - with the words "matching as", a drop-down selection box, then some checkboxes with - "Assigned To" checked by default? This allows you to filter your search down based upon - email address. Let's put my email address in there, and see what happens. + You see the box immediately below the top six boxes that + contains an "Email" text box, with the words "matching + as", a drop-down selection box, then some checkboxes with + "Assigned To" checked by default? This allows you to + filter your search down based upon email address. Let's + put my email address in there, and see what happens. </para> <para> Type "barnboy@trilobyte.net" in the top Email text box. @@ -352,47 +392,55 @@ system against which all others are measured. <listitem> <para> - Let's narrow the search some more. Scroll down until you find the box with the word - "Program" over the top of it. This is where we can narrow our search down to only - specific products (software programs or product lines) in our Bugzilla database. - Please notice the box is a <emphasis>scrollbox</emphasis>. Using the down arrow on the - scrollbox, scroll down until you can see an entry called "Webtools". Select this entry. + Let's narrow the search some more. Scroll down until you + find the box with the word "Program" over the top of it. + This is where we can narrow our search down to only + specific products (software programs or product lines) in + our Bugzilla database. Please notice the box is a + <emphasis>scrollbox</emphasis>. Using the down arrow on + the scrollbox, scroll down until you can see an entry + called "Webtools". Select this entry. </para> </listitem> <listitem> <para> - Did you notice that some of the boxes to the right changed when you selected "Webtools"? - Every Program (or Product) has different Versions, Components, and Target Milestones associated - with it. A "Version" is the number of a software program. + Did you notice that some of the boxes to the right changed + when you selected "Webtools"? Every Program (or Product) + has different Versions, Components, and Target Milestones + associated with it. A "Version" is the number of a + software program. <example> <title>Some Famous Software Versions</title> <informalexample> <para> - Do you remember the hype in 1995 when Microsoft Windows 95(r) was released? - It may have been several years - ago, but Microsoft(tm) spent over $300 Million advertising this new Version of their - software. Three years later, they released Microsoft Windows 98(r), - another new version, to great fanfare, and then in 2000 quietly - released Microsoft Windows ME(Millenium Edition)(r). + Do you remember the hype in 1995 when Microsoft + Windows 95(r) was released? It may have been several + years ago, but Microsoft(tm) spent over $300 Million + advertising this new Version of their software. + Three years later, they released Microsoft Windows + 98(r), another new version, to great fanfare, and + then in 2000 quietly released Microsoft Windows + ME(Millenium Edition)(r). </para> <para> - Software "Versions" help a manufacturer differentiate - their current product from their - previous products. Most do not identify their products - by the year they were released. - Instead, the "original" version of their software will - often be numbered "1.0", with - small bug-fix releases on subsequent tenths of a digit. In most cases, it's not - a decimal number; for instance, often 1.9 is an <emphasis>older</emphasis> version - of the software than 1.11, - but is a <emphasis>newer</emphasis> version than 1.1.1. + Software "Versions" help a manufacturer + differentiate their current product from their + previous products. Most do not identify their + products by the year they were released. Instead, + the "original" version of their software will often + be numbered "1.0", with small bug-fix releases on + subsequent tenths of a digit. In most cases, it's + not a decimal number; for instance, often 1.9 is an + <emphasis>older</emphasis> version of the software + than 1.11, but is a <emphasis>newer</emphasis> + version than 1.1.1. </para> <para> - In general, a "Version" in Bugzilla should refer to - <emphasis>released</emphasis> - products, not products that have not yet been released - to the public. Forthcoming products - are what the Target Milestone field is for. + In general, a "Version" in Bugzilla should refer to + <emphasis>released</emphasis> products, not products + that have not yet been released to the public. + Forthcoming products are what the Target Milestone + field is for. </para> </informalexample> </example> @@ -438,26 +486,25 @@ system against which all others are measured. </example> </para> <para> - A "Milestone", or "Target Milestone" is a often a planned future "Version" of a - product. In many cases, though, Milestones simply represent significant dates for - a developer. Having certain features in your Product is frequently - tied to revenue (money) - the developer will receive if the features work by the time she - reaches the Target Milestone. - Target Milestones are a great tool to organize your time. - If someone will pay you $100,000 for - incorporating certain features by a certain date, - those features by that Milestone date become - a very high priority. Milestones tend to be highly malleable creatures, - though, that appear - to be in reach but are out of reach by the time the important day arrives. + A "Milestone", or "Target Milestone" is a often a planned + future "Version" of a product. In many cases, though, + Milestones simply represent significant dates for a + developer. Having certain features in your Product is + frequently tied to revenue (money) the developer will + receive if the features work by the time she reaches the + Target Milestone. Target Milestones are a great tool to + organize your time. If someone will pay you $100,000 for + incorporating certain features by a certain date, those + features by that Milestone date become a very high + priority. Milestones tend to be highly malleable + creatures, though, that appear to be in reach but are out + of reach by the time the important day arrives. </para> <para> - The Bugzilla Project has set up Milestones for future - Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, - a Target Milestone can just as easily be a specific date, - code name, or weird alphanumeric - combination, like "M19". + The Bugzilla Project has set up Milestones for future + Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a + Target Milestone can just as easily be a specific date, + code name, or weird alphanumeric combination, like "M19". </para> </listitem> @@ -475,56 +522,54 @@ system against which all others are measured. </listitem> <listitem> <para> - Congratulations! You've completed your first Query, and have before you the Bug List - of the author of this Guide, Matthew P. Barnson (barnboy@trilobyte.net). If I'm - doing well, - you'll have a cryptic "Zarro Boogs Found" message on your screen. It is just - a happy hacker's way of saying "Zero Bugs Found". However, I am fairly certain I will + Congratulations! You've completed your first Query, and + have before you the Bug List of the author of this Guide, + Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing + well, you'll have a cryptic "Zarro Boogs Found" message on + your screen. It is just a happy hacker's way of saying + "Zero Bugs Found". However, I am fairly certain I will always have some bugs assigned to me that aren't done yet, so you won't often see that message! </para> </listitem> </orderedlist> <para> - I encourage you to click the bug numbers in the left-hand column and examine - my bugs. Also notice that if you click the underlined - links near the top of this page, they do - not take you to context-sensitive help here, - but instead sort the columns of bugs on the screen! - When you need to sort your bugs by priority, severity, - or the people they are assigned to, this - is a tremendous timesaver. + I encourage you to click the bug numbers in the left-hand + column and examine my bugs. Also notice that if you click the + underlined links near the top of this page, they do not take + you to context-sensitive help here, but instead sort the + columns of bugs on the screen! When you need to sort your bugs + by priority, severity, or the people they are assigned to, + this is a tremendous timesaver. </para> <para> A couple more interesting things about the Bug List page: <simplelist> - <member><emphasis>Change Columns</emphasis>: - by selecting this link, you can show all kinds - of information in the Bug List</member> - <member><emphasis>Change several bugs at once</emphasis>: - If you have sufficient rights to change all - the bugs shown in the Bug List, you can mass-modify them. - This is a big time-saver.</member> - <member><emphasis>Send mail to bug owners</emphasis>: - If you have many related bugs, you can request - an update from every person who owns the bugs in - the Bug List asking them the status.</member> - <member><emphasis>Edit this query</emphasis>: - If you didn't get exactly the results you were looking for, - you can return to the Query page through this link and make - small revisions to the query you just made so - you get more accurate results.</member> + <member><emphasis>Change Columns</emphasis>: by selecting + this link, you can show all kinds of information in the + Bug List</member> + <member><emphasis>Change several bugs at once</emphasis>: If + you have sufficient rights to change all the bugs shown in + the Bug List, you can mass-modify them. This is a big + time-saver.</member> + <member><emphasis>Send mail to bug owners</emphasis>: If you + have many related bugs, you can request an update from + every person who owns the bugs in the Bug List asking them + the status.</member> + <member><emphasis>Edit this query</emphasis>: If you didn't + get exactly the results you were looking for, you can + return to the Query page through this link and make small + revisions to the query you just made so you get more + accurate results.</member> </simplelist> </para> <note> <para> - There are many more options to the Bugzilla Query Page - and the Bug List than I have shown you. - But this should be enough for you to learn to get around. - I encourage you to check out the - <ulink url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink> - to learn about the Anatomy - and Life Cycle of a Bug before continuing. + There are many more options to the Bugzilla Query Page and + the Bug List than I have shown you. But this should be + enough for you to learn to get around. I encourage you to + check out the <ulink + url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink> to learn about the Anatomy and Life Cycle of a Bug before continuing. </para> </note> </section> @@ -539,37 +584,35 @@ system against which all others are measured. <section id="bug_writing"> <title>Writing a Great Bug Report</title> <para> - Before we plunge into writing your first bug report, I encourage you to read - <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">Mozilla.org's Bug - Writing Guidelines</ulink>. While some of the advice is Mozilla-specific, the basic - principles of reporting Reproducible, Specific bugs, isolating the Product you are - using, the Version of the Product, the Component which failed, the Hardware Platform, and - Operating System you were using at the time of the failure go a long way toward ensuring accurate, - responsible fixes for the bug that bit you. + Before we plunge into writing your first bug report, I + encourage you to read some bug-writing guidelines. If you + are reading this document as part of a Bugzilla CVS checkout + or un-tarred Bugzilla distribution, you should be able to + read them by clicking <ulink + url="../../bugwritinghelp.html">here</ulink>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">http://www.mozilla.org/quality/bug-writing-guidelines.html</ulink>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you. </para> <para> - While you are at it, why not learn how to find previously reported bugs? Mozilla.org - has published a great tutorial on finding duplicate bugs, available at - <ulink url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"> - http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>. + While you are at it, why not learn how to find previously + reported bugs? Mozilla.org has published a great tutorial + on finding duplicate bugs, available at <ulink + url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>. </para> <para> - I realize this was a lot to read. However, understanding the mentality of writing - great bug reports will help us on the next part! + I realize this was a lot to read. However, understanding + the mentality of writing great bug reports will help us on + the next part! </para> <orderedlist> <listitem> <para> - Go back to <ulink url="http://landfill.tequilarista.org/bugzilla-tip/"> - http://landfill.tequilarista.org/bugzilla-tip/</ulink> - in your browser. + Go back to <ulink + url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink> in your browser. </para> </listitem> <listitem> <para> - Select the - <ulink url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> - Enter a new bug report</ulink> link. + Select the <ulink + url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink> link. </para> </listitem> <listitem> @@ -579,11 +622,11 @@ system against which all others are measured. </listitem> <listitem> <para> - Now you should be at the "Enter Bug" form. - The "reporter" should have been automatically filled out - for you (or else Bugzilla prompted you to Log In again - -- you did keep the email with your username - and password, didn't you?). + Now you should be at the "Enter Bug" form. The + "reporter" should have been automatically filled out for + you (or else Bugzilla prompted you to Log In again -- + you did keep the email with your username and password, + didn't you?). </para> </listitem> <listitem> @@ -593,107 +636,97 @@ system against which all others are measured. </listitem> <listitem> <para> - Bugzilla should have made reasonable guesses, based upon your browser, - for the "Platform" and "OS" drop-down - boxes. If those are wrong, change them -- if you're on an SGI box - running IRIX, we want to know! + Bugzilla should have made reasonable guesses, based upon + your browser, for the "Platform" and "OS" drop-down + boxes. If those are wrong, change them -- if you're on + an SGI box running IRIX, we want to know! </para> </listitem> <listitem> <para> - Fill in the "Assigned To" box with the email address you provided earlier. - This way you don't end up sending copies of your bug to lots of other people, - since it's just a test bug. + Fill in the "Assigned To" box with the email address you + provided earlier. This way you don't end up sending + copies of your bug to lots of other people, since it's + just a test bug. </para> </listitem> <listitem> <para> - Leave the "CC" text box blank. - Fill in the "URL" box with "http://www.mozilla.org". + Leave the "CC" text box blank. Fill in the "URL" box + with "http://www.mozilla.org". </para> </listitem> <listitem> <para> - Enter "The Bugzilla Guide" in the Summary text box, - and place any comments you have on this - tutorial, or the Guide in general, into the Description box. + Enter "The Bugzilla Guide" in the Summary text box, and + place any comments you have on this tutorial, or the + Guide in general, into the Description box. </para> </listitem> </orderedlist> <para> - Voila! Select "Commit" and send in your bug report! - Next we'll look at resolving bugs. + Voila! Select "Commit" and send in your bug report! Next + we'll look at resolving bugs. </para> </section> <section id="bug_manage"> <title>Managing your Bug Reports</title> <para> - OK, you should have a link to the bug you just created near the top of your page. - It should say - "Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX". - Select this link. + OK, you should have a link to the bug you just created near + the top of your page. It should say "Bug XXXX posted", with + a link to the right saying "Back to BUG# XXXX". Select this + link. </para> <orderedlist> <listitem> <para> - Scroll down a bit on the subsequent page, - until you see the "Resolve bug, changing resolution to (dropdown box). - Normally, you would - "Accept bug (change status to ASSIGNED)", fix it, and then resolve. - But in this case, we're - going to short-circuit the process because this wasn't a real bug. - Change the dropdown next to - "Resolve Bug" to "INVALID", make sure the radio button is - marked next to "Resolve Bug", then - click "Commit". + Scroll down a bit on the subsequent page, until you see + the "Resolve bug, changing resolution to (dropdown box). + Normally, you would "Accept bug (change status to + ASSIGNED)", fix it, and then resolve. But in this case, + we're going to short-circuit the process because this + wasn't a real bug. Change the dropdown next to "Resolve + Bug" to "INVALID", make sure the radio button is marked + next to "Resolve Bug", then click "Commit". </para> </listitem> <listitem> <para> - Hey! It said it couldn't take the change in a big red box! - That's right, you must specify - a Comment in order to make this change. Select the "Back" - button in your browser, add a - Comment, then try Resolving the bug with INVALID status again. - This time it should work. + Hey! It said it couldn't take the change in a big red + box! That's right, you must specify a Comment in order + to make this change. Select the "Back" button in your + browser, add a Comment, then try Resolving the bug with + INVALID status again. This time it should work. </para> </listitem> </orderedlist> <para> You have now learned the basics of Bugzilla navigation, - entering a bug, and bug maintenance. - I encourage you to explore these features, and see what you can do with them! - We'll spend no more time on individual Bugs or Queries from this point on, so you are - on your own there. + entering a bug, and bug maintenance. I encourage you to + explore these features, and see what you can do with them! + We'll spend no more time on individual Bugs or Queries from + this point on, so you are on your own there. </para> <para> But I'll give a few last hints! </para> <para> - There is a <ulink url="http://bugzilla.mozilla.org/help.html">CLUE</ulink> - on the Query page - that will teach you more how to use the form. + There is a <ulink + url="http://bugzilla.mozilla.org/help.html">CLUE</ulink> on the Query page that will teach you more how to use the form. </para> <para> - If you click the hyperlink on the - <ulink url="http://bugzilla.mozilla.org/describecomponents.cgi">Component</ulink> - box of the Query page, you will be presented a form that will describe what all - the components are. + If you click the hyperlink on the <ulink + url="http://bugzilla.mozilla.org/describecomponents.cgi">Component</ulink> box of the Query page, you will be presented a form that will describe what all the components are. </para> <para> - Possibly the most powerful feature of the Query page is the - <ulink url="http://bugzilla.mozilla.org/booleanchart.html">Boolean Chart</ulink> section. - It's a bit confusing to use the first time, but can provide unparalleled - flexibility in your queries, - allowing you to build extremely powerful requests. + Possibly the most powerful feature of the Query page is the + <ulink + url="http://bugzilla.mozilla.org/booleanchart.html">Boolean Chart</ulink> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests. </para> <para> - Finally, you can build some nifty - <ulink url="http://bugzilla.mozilla.org/reports.cgi">Reports</ulink> - using the "Bug Reports" link near the bottom of the query page, and also - available via the "Reports" link - at the footer of each page. + Finally, you can build some nifty <ulink + url="http://bugzilla.mozilla.org/reports.cgi">Reports</ulink> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page. </para> </section> </section> @@ -701,7 +734,7 @@ system against which all others are measured. </section> <section id="init4me"> - <title>What's in it for me?</title> + <title>Where can I find my user preferences?</title> <epigraph> <para> Indiana, it feels like we walking on fortune cookies! @@ -711,98 +744,95 @@ system against which all others are measured. </para> </epigraph> <para> - Customized User Preferences offer tremendous versatility to - your individual Bugzilla experience. - Let's plunge into what you can do! The first step is to click - the "Edit prefs" link at the footer of each page once you - have logged in to - <ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1"> - Landfill</ulink>. + Customized User Preferences offer tremendous versatility to your + individual Bugzilla experience. Let's plunge into what you can + do! The first step is to click the "Edit prefs" link at the + footer of each page once you have logged in to <ulink + url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1"> Landfill</ulink>. </para> - <section id="accountsettings"> + <section id="accountsettings" xreflabel="Account Settings"> <title>Account Settings</title> <para> On this page, you can change your basic Account Settings, - including your password and full name. - For security reasons, in order to change anything on this page you - must type your <emphasis>current</emphasis> - password into the "Old Password" field. - If you wish to change your password, type the new password you - want into the "New Password" field and again into the "Re-enter - new password" field to ensure - you typed your new password correctly. Select the "Submit" button and you're done! + including your password and full name. For security reasons, + in order to change anything on this page you must type your + <emphasis>current</emphasis> password into the <quote>Old + Password</quote> field. If you wish to change your + password, type the new password you want into the <quote>New + Password</quote> field and again into the <quote>Re-enter + new password</quote> field to ensure you typed your new + password correctly. Select the <quote>Submit</quote> button + and you are done. </para> </section> - <section id="emailsettings"> + <section id="emailsettings" > <title>Email Settings</title> - <section id="notification"> + <section id="notification" xreflabel=""> <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 - <simplelist> - <member><emphasis>All qualifying bugs</emphasis>: sends you every change to every bug - where your name is somewhere on it, regardless of who changed it.</member> - <member><emphasis>Only those bugs which I am listed in the CC line</emphasis>: prevents - you from receiving mail for which you are the reporter,' - owner, or QA contact. If you are on the CC - list, presumably someone had a <emphasis>good</emphasis> - reason for you to get the email.</member> - <member><emphasis>All qulifying bugs except those which I change</emphasis>: - This is the default, and - a sensible setting. If someone else changes your bugs, you will get emailed, - but if you change bugs - yourself you will receive no notification of the change.</member> - </simplelist> + Here you can reduce or increase the amount of email sent you + from Bugzilla. Although this is referred to as + <quote>Advanced Email Filtering Options</quote>, they are, + in fact, the standard email filter set. All of them are + self-explanatory, but you can use the filters in interesting + ways. For instance, some people (notably Quality Assurance + personnel) often only care to receive updates regarding a + bug when the bug changes state, so they can track bugs on + their flow charts and know when it is time to pull the bug + onto a quality assurance platform for inspection. Other + people set up email gateways to + <xref linkend="bonsai"> or <xref linkend="tinderbox">, and + restrict which types of Bugzilla information are fed to + these systems.. </para> </section> <section id="newemailtech"> <title>New Email Technology</title> <note> <para> - This option may not be available in all Bugzilla installations, depending upon - the preferences of the systems administrator responsible for the setup of your Bugzilla. - However, if you really want this functionality, ask her to "enable newemailtech - in Params" - and "make it the default for all new users", referring her to the Administration section - of this Guide. + This option may not be available in all Bugzilla + installations, depending upon the preferences of the + systems administrator responsible for the setup of your + Bugzilla. However, if you really want this functionality, + ask her to "enable newemailtech in Params" and "make it + the default for all new users", referring her to the + Administration section of this Guide. </para> </note> <para> - Disregard the warnings about "experimental and bleeding edge"; the code to handle email - in a cleaner manner than that historically used for Bugzilla is - quite robust and well-tested now. + Disregard the warnings about "experimental and bleeding + edge"; the code to handle email in a cleaner manner than + that historically used for Bugzilla is quite robust and + well-tested now. </para> <para> - I recommend you enable the option, "Click here to sign up (and risk any bugs)". - Your email-box - will thank you for it. The fundamental shift in "newemailtech" is away from standard UNIX - "diff" output, which is quite ugly, to a prettier, better laid-out email. + I recommend you enable the option, "Click here to sign up + (and risk any bugs)". Your email-box will thank you for it. + The fundamental shift in "newemailtech" is away from + standard UNIX "diff" output, which is quite ugly, to a + prettier, better laid-out email. </para> </section> <section id="watchsettings"> <title>"Watching" Users</title> <note> <para> - This option may not be available in all Bugzilla installations, depending upon - the preferences of the systems administrator responsible for the setup of your Bugzilla. - However, if you really want this functionality, ask her to "enable watchers in Params". + This option may not be available in all Bugzilla + installations, depending upon the preferences of the + systems administrator responsible for the setup of your + Bugzilla. However, if you really want this functionality, + ask her to "enable watchers in Params". </para> </note> <para> - By entering user email names into the "Users to watch" text entry box, delineated by commas, - you can watch bugs of other users. This powerful functionality enables seamless transitions - as developers change projects, managers wish to get in touch with the issues faced by their - direct reports, or users go on vacation. If any of these three situations apply - to you, you will undoubtedly find this feature quite convenient. + By entering user email names into the "Users to watch" text + entry box, delineated by commas, you can watch bugs of other + users. This powerful functionality enables seamless + transitions as developers change projects, managers wish to + get in touch with the issues faced by their direct reports, + or users go on vacation. If any of these three situations + apply to you, you will undoubtedly find this feature quite + convenient. </para> </section> </section> @@ -810,36 +840,46 @@ system against which all others are measured. <title>Page Footer</title> <note> <para> - By default, this page is quite barren. However, go explore the Query Page some more; you will - find that you can store numerous queries on the server, so if you regularly run a particular query - it is just a drop-down menu away. On this page of Preferences, if you have many stored - queries you can elect to have them always one-click away! + By default, this page is quite barren. However, go explore + the Query Page some more; you will find that you can store + numerous queries on the server, so if you regularly run a + particular query it is just a drop-down menu away. On this + page of Preferences, if you have many stored queries you can + elect to have them always one-click away! </para> </note> <para> - If you have many stored queries on the server, here you will find individual drop-downs for each - stored query. Each drop-down gives you the option of that query appearing on the footer of every - page in Bugzilla! This gives you powerful one-click access to any complex searches you may set up, - and is an excellent way to impress your boss... + If you have many stored queries on the server, here you will + find individual drop-downs for each stored query. Each + drop-down gives you the option of that query appearing on the + footer of every page in Bugzilla! This gives you powerful + one-click access to any complex searches you may set up, and + is an excellent way to impress your boss... </para> <tip> - <para>By default, the "My Bugs" link appears at the bottom of each page. However, this query - gives you both the bugs you have reported, as well as those you are assigned. One of the most - common uses for this page is to remove the "My Bugs" link, replacing it with two other queries, - commonly called "My Bug Reports" and "My Bugs" (but only referencing bugs assigned to you). This - allows you to distinguish those bugs you have reported from those you are assigned. I commonly - set up complex Boolean queries in the Query page and link them to my footer in this page. When - they are significantly complex, a one-click reference can save hours of work.</para> + <para>By default, the "My Bugs" link appears at the bottom of + each page. However, this query gives you both the bugs you + have reported, as well as those you are assigned. One of + the most common uses for this page is to remove the "My + Bugs" link, replacing it with two other queries, commonly + called "My Bug Reports" and "My Bugs" (but only referencing + bugs assigned to you). This allows you to distinguish those + bugs you have reported from those you are assigned. I + commonly set up complex Boolean queries in the Query page + and link them to my footer in this page. When they are + significantly complex, a one-click reference can save hours + of work.</para> </tip> </section> <section id="permissionsettings"> <title>Permissions</title> <para> - This is a purely informative page which outlines your current permissions on - this installation of Bugzilla. If you have permissions to grant certain permissions to - other users, the "other users" link appears on this page as well as the footer. - For more information regarding user administration, please consult the Administration - section of this Guide. + This is a purely informative page which outlines your current + permissions on this installation of Bugzilla. If you have + permissions to grant certain permissions to other users, the + "other users" link appears on this page as well as the footer. + For more information regarding user administration, please + consult the Administration section of this Guide. </para> </section> </section> @@ -847,12 +887,11 @@ system against which all others are measured. <section id="usingbz-conc"> <title>Using Bugzilla-Conclusion</title> <para> - Thank you for reading through this portion of the Bugzilla Guide. I anticipate - it may not yet meet the needs of all readers. If you have additional comments or - corrections to make, please submit your contributions to the - <ulink url="mailto://mozilla-webtools@mozilla.org">mozilla-webtools</ulink> - mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools - newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org + Thank you for reading through this portion of the Bugzilla + Guide. I anticipate it may not yet meet the needs of all + readers. If you have additional comments or corrections to + make, please submit your contributions to the <ulink + url="mailto://mozilla-webtools@mozilla.org">mozilla-webtools</ulink> mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org </para> </section> </chapter> diff --git a/docs/sgml/variants.sgml b/docs/sgml/variants.sgml index fec867946..a5b346023 100644 --- a/docs/sgml/variants.sgml +++ b/docs/sgml/variants.sgml @@ -1,72 +1,77 @@ <!-- <!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> +<chapter id="variants" xreflabel="Bugzilla Variants and Competitors"> + <title>Bugzilla Variants and Competitors</title> + <para>I created this section to answer questions about Bugzilla + competitors and variants, then found a wonderful site which covers + an awful lot of what I wanted to discuss. Rather than quote it in + its entirety, I'll simply refer you here: <ulink + url="http://linas.org/linux/pm.html">http://linas.org/linux/pm.html</ulink></para> - <section id="rhbugzilla"> + <section id="rhbugzilla" xreflabel="Red Hat Bugzilla"> <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. - + Red Hat Bugzilla is probably the most popular Bugzilla variant + on the planet. One of the major benefits of Red Hat Bugzilla is + the ability to work with Oracle, MySQL, and PostGreSQL databases + serving as the back-end, instead of just MySQL. Dave Lawrence + has worked very hard to keep Red Hat Bugzilla up-to-date, and + many people prefer the snappier-looking page layout of Red Hat + Bugzilla to the default Mozilla-standard formatting. + </para> + <para>URL: <ulink + url="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</ulink></para> + </section> -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. + <section id="variant_fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris"> + <title>Loki Bugzilla (Fenris)</title> + <para>Fenris can be found at <ulink + url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para> + </section> -Also number 6 contradicts number 8 where number 6 would be the most up to date status -on the Oracle port. + <section id="variant_issuezilla" xreflabel="Issuezilla"> + <title>Issuezilla</title> + <para>Issuezilla is another fork from Bugzilla, and seems nearly + as popular as the Red Hat Bugzilla fork. Some Issuezilla team + members are regular contributors to the Bugzilla mailing + list/newsgroup. Issuezilla is not the primary focus of + bug-tracking at tigris.org, however. Their Java-based + bug-tracker, <xref linkend="variant_scarab">, is under heavy development + and looks promising!</para> + <para>URL: <ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">http://issuezilla.tigris.org/servlets/ProjectHome</ulink></para> + </section> -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. + <section id="variant_scarab" xreflabel="Scarab, a newfangled Java-based issue tracker"> + <title>Scarab</title> + <para>Scarab is a promising new bug-tracking system built using + Java Serlet technology. As of this writing, no source code has + been released as a package, but you can obtain the code from + CVS. + </para> + <para>URL: <ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink></para> + </section> -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. + <section id="variant_perforce" xreflabel="Using Perforce to track bugs"> + <title>Perforce SCM</title> + <para>Although Perforce isn't really a bug tracker, it can be used + as such through the <quote>jobs</quote> functionality.</para> + <para><ulink + url="http://www.perforce.com/perforce/technotes/note052.html"></ulink>http://www.perforce.com/perforce/technotes/note052.html</para> + </section> -3. Of course even more cosmetic changes. It is difficult to keep up with the ever -changing faces of www.redhat.com. + <section id="variant_sourceforge" xreflabel="SourceForge"> + <title>SourceForge</title> + <para>SourceForge is more of a way of coordinating geographically + distributed free software and open source projects over the + Internet than strictly a bug tracker, but if you're hunting for + bug-tracking for your open project, it may be just what the + software engineer ordered!</para> + <para>URL: <ulink + url="http://www.sourceforge.net">http://www.sourceforge.net</ulink></para> + </section> -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 diff --git a/docs/txt/Bugzilla-Guide.txt b/docs/txt/Bugzilla-Guide.txt index a5fd79fcb..46972a7d8 100644 --- a/docs/txt/Bugzilla-Guide.txt +++ b/docs/txt/Bugzilla-Guide.txt @@ -7,11 +7,6 @@ Matthew P. Barnson Zach Lipton zach@NOSPAM.zachlipton.com - -Edited by - -I. P. Freely - Revision History Revision v2.11 20 December 2000 Revised by: MPB Converted the README, FAQ, and DATABASE information into SGML docbook @@ -52,6 +47,11 @@ I. P. Freely responsible for installing and maintaining this software is a qualified professional on operating system upon which you install Bugzilla. + + THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT. IF YOU + WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN TEXT OR SGML DIFFS + AGAINST THE SOURCE. I CANNOT ACCEPT ADDITIONS TO THE GUIDE WRITTEN IN + HTML! _________________________________________________________________ Table of Contents @@ -80,7 +80,7 @@ I. P. Freely 2.3.3.1. Writing a Great Bug Report 2.3.3.2. Managing your Bug Reports - 2.4. What's in it for me? + 2.4. Where can I find my user preferences? 2.4.1. Account Settings 2.4.2. Email Settings @@ -113,7 +113,7 @@ I. P. Freely 3.2.12. HTTP Server 3.2.13. Installing the Bugzilla Files 3.2.14. Setting Up the MySQL Database - 3.2.15. Tweaking "localconfig" + 3.2.15. Tweaking localconfig 3.2.16. Setting Up Maintainers Manually (Optional) 3.2.17. The Whining Cron (Optional) 3.2.18. Bug Graphs (Optional) @@ -126,7 +126,11 @@ I. P. Freely 3.5.1. Modifying Your Running System 3.5.2. Upgrading From Previous Versions 3.5.3. .htaccess files and security - 3.5.4. UNIX Installation Instructions History + 3.5.4. mod_throttle and Security + 3.5.5. Preventing untrusted Bugzilla content from executing + malicious Javascript code + + 3.5.6. UNIX Installation Instructions History 3.6. Win32 Installation Notes @@ -162,7 +166,7 @@ I. P. Freely 5.1. Bonsai 5.2. CVS 5.3. Perforce SCM - 5.4. Tinderbox + 5.4. Tinderbox/Tinderbox2 6. The Future of Bugzilla A. The Bugzilla FAQ @@ -178,15 +182,21 @@ I. P. Freely C.3. MySQL Permissions & Grant Tables - 7. Bugzilla Variants + 7. Bugzilla Variants and Competitors 7.1. Red Hat Bugzilla + 7.2. Loki Bugzilla (Fenris) + 7.3. Issuezilla + 7.4. Scarab + 7.5. Perforce SCM + 7.6. SourceForge D. Useful Patches and Utilities for Bugzilla - D.1. The setperl.csh Utility - D.2. Command-line Bugzilla Queries - D.3. The Quicksearch Utility + D.1. Apache mod_rewrite magic + D.2. The setperl.csh Utility + D.3. Command-line Bugzilla Queries + D.4. The Quicksearch Utility E. GNU Free Documentation License @@ -211,7 +221,9 @@ I. P. Freely 3-1. Setting up bonsaitools symlink 3-2. Running checksetup.pl as the web user 3-3. Installing ActivePerl ppd Modules on Microsoft Windows - 3-4. Removing encrypt() for Windows NT installations + 3-4. Removing encrypt() for Windows NT Bugzilla version 2.12 or + earlier + 4-1. Creating some Components 4-2. Common Use of Versions 4-3. A Different Use of Versions @@ -231,14 +243,13 @@ Chapter 1. About This Guide I left untouched for nearly half a year. After numerous complete rewrites and reformatting, it is the document you see today. - Despite the lack of updates, Bugzilla is simply the best piece of - bug-tracking software the world has ever seen. This document is - intended to be the comprehensive guide to the installation, - administration, maintenance, and use of the Bugzilla bug-tracking - system. + Bugzilla is simply the best piece of bug-tracking software the world + has ever seen. This document is intended to be the comprehensive guide + to the installation, administration, maintenance, and use of the + Bugzilla bug-tracking system. - This release of the Bugzilla Guide is the 2.14.0 release. It is so - named that it may match the current version of Bugzilla. The numbering + This release of the Bugzilla Guide is the 2.14 release. It is so named + that it may match the current version of Bugzilla. The numbering tradition stems from that used for many free software projects, in which even-numbered point releases (1.2, 1.14, etc.) are considered "stable releases", intended for public consumption; on the other hand, @@ -253,7 +264,7 @@ Chapter 1. About This Guide of Bugzilla, as of this writing (August 10, 2001) is 2.14; if something were seriously wrong with that edition of the Guide, subsequent releases would receive an additional dotted-decimal digit - to indicate the update (2.14.0.1, 2.14.0.2, etc.). Got it? Good. + to indicate the update (2.14.1, 2.14.2, etc.). Got it? Good. I wrote this in response to the enormous demand for decent Bugzilla documentation. I have incorporated instructions from the Bugzilla @@ -322,7 +333,7 @@ Chapter 1. About This Guide 1.4. New Versions - This is the 2.14.0 version of The Bugzilla Guide. If you are reading + This is the 2.14 version of The Bugzilla Guide. If you are reading this from any source other than those below, please check one of these mirrors to make sure you are reading an up-to-date version of the Guide. @@ -431,7 +442,7 @@ Chapter 2. Using Bugzilla - What, Why, How, & What's in it for me? + What, Why, How, & Where? _________________________________________________________________ 2.1. What is Bugzilla? @@ -461,16 +472,18 @@ Chapter 2. Using Bugzilla protocol * email, XML, console, and HTTP APIs * available integration with automated software configuration - management systems, including Perforce and CVS + management systems, including Perforce and CVS (through the + Bugzilla email interface and checkin/checkout scripts) * too many more features to list - Despite its current robustness and popularity, however, Bugzilla faces - some near-term challenges, such as reliance on a single database, a - lack of abstraction of the user interface and program logic, verbose - email bug notifications, a powerful but daunting query interface, - little reporting configurability, problems with extremely large - queries, some unsupportable bug resolution options, no - internationalization, and dependence on some nonstandard libraries. + Despite its current robustness and popularity, Bugzilla faces some + near-term challenges, such as reliance on a single database, a lack of + abstraction of the user interface and program logic, verbose email bug + notifications, a powerful but daunting query interface, little + reporting configurability, problems with extremely large queries, some + unsupportable bug resolution options, little internationalization + (although non-US character sets are accepted for comments), and + dependence on some nonstandard libraries. 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 @@ -479,9 +492,8 @@ Chapter 2. Using Bugzilla information. This is also available as "queryhelp.cgi". Despite these small problems, Bugzilla is very hard to beat. It is - under very 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. + under very active development to address the current issues, and + continually gains new features. _________________________________________________________________ 2.2. Why Should We Use Bugzilla? @@ -522,7 +534,7 @@ Chapter 2. Using Bugzilla Bugzilla can dramatically increase the productivity and accountability of individual employees by providing a documented workflow and positive feedback for good performance. How many times do you wake up - in the morning, remembering that you were supposed to do *something* + in the morning, remembering that you were supposed to do something today, but you just can't quite remember? Put it in Bugzilla, and you have a record of it from which you can extrapolate milestones, predict product versions for integration, and by using Bugzilla's e-mail @@ -555,7 +567,7 @@ Chapter 2. Using Bugzilla Note Some people have run into difficulties completing this tutorial. If - you run into problems, please check the updated, online documentation + you run into problems, please check the updated online documentation available at http://www.trilobyte.net/barnsons. 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 @@ -581,10 +593,10 @@ Chapter 2. Using Bugzilla 2. Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself) in the spaces provided, then select the "Create Account" button. - 3. Within 5-10 minutes, you should receive an email to the address - you provided above, which contains your login name (generally the - same as the email address), and a password you can use to access - your account. This password is randomly generated, and should be + 3. Within moments, you should receive an email to the address you + provided above, which contains your login name (generally the same + as the email address), and a password you can use to access your + account. This password is randomly generated, and should be changed at your nearest opportunity (we'll go into how to do it later). 4. Click the "Log In" link in the yellow area at the bottom of the @@ -603,8 +615,8 @@ Chapter 2. Using Bugzilla Many modern browsers include an "Auto-Complete" or "Form Fill" feature to remember the user names and passwords you type in at many sites. - Unfortunately, sometimes they attempt to "guess" what you will put in - as your password, and guess wrong. If you notice a text box is already + Unfortunately, sometimes they attempt to guess what you will put in as + your password, and guess wrong. If you notice a text box is already filled out, please overwrite the contents of the text box so you can be sure to input the correct information. @@ -617,17 +629,17 @@ Chapter 2. Using Bugzilla 2.3.2. The Bugzilla Query Page - The Bugzilla Query Page is the heart and soul of Bugzilla. It is the - master interface where you can find any bug report, comment, or patch - currently in the Bugzilla system. We'll go into how to create your own - bug report later on. + The Bugzilla Query Page is the heart and soul of the Bugzilla user + experience. It is the master interface where you can find any bug + report, comment, or patch currently in the Bugzilla system. We'll go + into how to create your own bug report later on. There are efforts underway to simplify query usage. If you have a local installation of Bugzilla 2.12 or higher, you should have - "quicksearch.html" available to use and simplify your searches. There - is also, or shortly will be, a helper for the query interface, called - "queryhelp.cgi". Landfill tends to run the latest code, so these two - utilities should be available there for your perusal. + quicksearch.html available to use and simplify your searches. There is + also a helper for the query interface, called queryhelp.cgi. Landfill + tends to run the latest code, so these two utilities should be + available there for your perusal. At this point, please visit the main Bugzilla site, bugzilla.mozilla.org, to see a more fleshed-out query page. @@ -645,13 +657,13 @@ Chapter 2. Using Bugzilla "Back" button in your browser. I'm sure that after checking out the online help, you are now an - Expert on the Bugzilla Query Page. If, however, you feel you haven't + expert on the Bugzilla Query Page. If, however, you feel you haven't mastered it yet, let me walk you through making a few successful queries to find out what there are in the Bugzilla bug-tracking system itself. - 1. Ensure you are back on the "Bugzilla Query Page" Do nothing in the - boxes marked "Status", "Resolution", "Platform", "OpSys", + 1. Ensure you are back on the "Bugzilla Query Page". Do nothing in + the boxes marked "Status", "Resolution", "Platform", "OpSys", "Priority", or "Severity". The default query for "Status" is to find all bugs that are NEW, ASSIGNED, or REOPENED, which is what we want. If you don't select anything in the other 5 scrollboxes @@ -661,7 +673,7 @@ Chapter 2. Using Bugzilla have it figured out. Basically, selecting anything on the query page narrows your search down. Leaving stuff unselected, or text boxes unfilled, - broadens your search! + broadens your search. 2. You see the box immediately below the top six boxes that contains an "Email" text box, with the words "matching as", a drop-down selection box, then some checkboxes with "Assigned To" checked by @@ -786,13 +798,17 @@ Chapter 2. Using Bugzilla 2.3.3.1. Writing a Great Bug Report Before we plunge into writing your first bug report, I encourage you - to read Mozilla.org's Bug Writing Guidelines. While some of the advice - is Mozilla-specific, the basic principles of reporting Reproducible, - Specific bugs, isolating the Product you are using, the Version of the - Product, the Component which failed, the Hardware Platform, and - Operating System you were using at the time of the failure go a long - way toward ensuring accurate, responsible fixes for the bug that bit - you. + to read some bug-writing guidelines. If you are reading this document + as part of a Bugzilla CVS checkout or un-tarred Bugzilla distribution, + you should be able to read them by clicking here. If you are reading + this online, check out the Mozilla.org bug-writing guidelines at + http://www.mozilla.org/quality/bug-writing-guidelines.html. While some + of the advice is Mozilla-specific, the basic principles of reporting + Reproducible, Specific bugs, isolating the Product you are using, the + Version of the Product, the Component which failed, the Hardware + Platform, and Operating System you were using at the time of the + failure go a long way toward ensuring accurate, responsible fixes for + the bug that bit you. While you are at it, why not learn how to find previously reported bugs? Mozilla.org has published a great tutorial on finding duplicate @@ -872,7 +888,7 @@ Chapter 2. Using Bugzilla "Reports" link at the footer of each page. _________________________________________________________________ -2.4. What's in it for me? +2.4. Where can I find my user preferences? @@ -894,34 +910,25 @@ Chapter 2. Using Bugzilla "Old Password" field. If you wish to change your password, type the new password you want into the "New Password" field and again into the "Re-enter new password" field to ensure you typed your new password - correctly. Select the "Submit" button and you're done! + correctly. Select the "Submit" button and you are done. _________________________________________________________________ 2.4.2. Email Settings 2.4.2.1. Email Notification - Note - - 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. - - 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 - - All qualifying bugs: sends you every change to every bug where your - name is somewhere on it, regardless of who changed it. - Only those bugs which I am listed in the CC line: prevents you from - receiving mail for which you are the reporter,' owner, or QA contact. - If you are on the CC list, presumably someone had a good reason for - you to get the email. - All qulifying bugs except those which I change: This is the default, - and a sensible setting. If someone else changes your bugs, you will - get emailed, but if you change bugs yourself you will receive no - notification of the change. + Here you can reduce or increase the amount of email sent you from + Bugzilla. Although this is referred to as "Advanced Email Filtering + Options", they are, in fact, the standard email filter set. All of + them are self-explanatory, but you can use the filters in interesting + ways. For instance, some people (notably Quality Assurance personnel) + often only care to receive updates regarding a bug when the bug + changes state, so they can track bugs on their flow charts and know + when it is time to pull the bug onto a quality assurance platform for + inspection. Other people set up email gateways to Bonsai, the Mozilla + automated CVS management system or Tinderbox, the Mozilla automated + build management system, and restrict which types of Bugzilla + information are fed to these systems.. _________________________________________________________________ 2.4.2.2. New Email Technology @@ -1126,32 +1133,49 @@ Chapter 3. Installation Internet. Many installation steps require an active Internet connection to complete, but you must take care to ensure that at no point is your machine vulnerable to an attack. + + Note + + Linux-Mandrake 8.0, the author's test system, includes every required + and optional library for Bugzilla. The easiest way to install them is + by using the urpmi utility. If you follow these commands, you should + have everything you need for Bugzilla, and checksetup.pl should not + complain about any missing libraries. You may already have some of + these installed. + + bash# urpmi perl-mysql + bash# urpmi perl-chart + bash# urpmi perl-gd + bash# urpmi perl-MailTools (for Bugzilla email integration) + bash# urpmi apache-modules _________________________________________________________________ 3.2.3. Installing MySQL Database - Visit MySQL homepage at http://www.mysql.com/ and grab the latest - stable release of the server. Both binaries and source are available - and which you get shouldn't matter. Be aware that many of the binary - versions of MySQL store their data files in /var which on many - installations (particularly common with linux installations) is part - of a smaller root partition. If you decide to build from sources you - can easily set the dataDir as an option to configure. - - If you've installed from source or non-package (RPM, deb, etc.) - binaries you'll want to make sure to add mysqld to your init scripts - so the server daemon will come back up whenever your machine reboots. - You also may want to edit those init scripts, to make sure that mysqld - will accept large packets. By default, mysqld is set up to only accept - packets up to 64K long. This limits the size of attachments you may - put on bugs. If you add something like "-O max_allowed_packet=1M" to - the command that starts mysqld (or safe_mysqld), then you will be able - to have attachments up to about 1 megabyte. + Visit MySQL homepage at www.mysql.com and grab the latest stable + release of the server. Many of the binary versions of MySQL store + their data files in /var which is often part of a smaller root + partition. If you decide to build from sources you can easily set the + dataDir as an option to configure. + + If you install from source or non-package (RPM, deb, etc.) binaries + you need to add mysqld to your init scripts so the server daemon will + come back up whenever your machine reboots. Further discussion of UNIX + init sequences are beyond the scope of this guide. + + Note + + You should have your init script start mysqld with the ability to + accept large packets. By default, mysqld only accepts packets up to + 64K long. This limits the size of attachments you may put on bugs. If + you add -O max_allowed_packet=1M to the command that starts mysqld (or + safe_mysqld), then you will be able to have attachments up to about 1 + megabyte. Note If you plan on running Bugzilla and MySQL on the same machine, - consider using the "--skip-networking" option in the init script. This + consider using the --skip-networking option in the init script. This enhances security by preventing network access to MySQL. _________________________________________________________________ @@ -1188,7 +1212,7 @@ Chapter 3. Installation Tip You can skip the following Perl module installation steps by - installing "Bundle::Bugzilla" from CPAN, which includes them. All Perl + installing Bundle::Bugzilla from CPAN, which includes them. All Perl module installation steps require you have an active Internet connection. If you wish to use Bundle::Bugzilla, however, you must be using the latest version of Perl (at this writing, version 5.6.1) @@ -1212,8 +1236,7 @@ Chapter 3. Installation Like almost all Perl modules DBI can be found on the Comprehensive Perl Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a real tendency to bog down, so please use mirrors. The current - location at the time of this writing (02/17/99) can be found in - Appendix A. + location at the time of this writing can be found in Appendix B. Quality, general Perl module installation instructions can be found on the CPAN website, but the easy thing to do is to just use the CPAN @@ -1251,8 +1274,8 @@ Chapter 3. Installation hurt anything. Data::Dumper is used by the MySQL-related Perl modules. It can be - found on CPAN (link in Appendix A) and can be installed by following - the same four step make sequence used for the DBI module. + found on CPAN (see Appendix B) and can be installed by following the + same four step make sequence used for the DBI module. _________________________________________________________________ 3.2.7. MySQL related Perl Module Collection @@ -1285,31 +1308,30 @@ Chapter 3. Installation Many of the more common date/time/calendar related Perl modules have been grouped into a bundle similar to the MySQL modules bundle. This - bundle is stored on the CPAN under the name TimeDate. A link link may - be found in Appendix B, Software Download Links. The component module - we're most interested in is the Date::Format module, but installing - all of them is probably a good idea anyway. The standard Perl module - installation instructions should work perfectly for this simple - package. + bundle is stored on the CPAN under the name TimeDate (see link: + Appendix B). The component module we're most interested in is the + Date::Format module, but installing all of them is probably a good + idea anyway. The standard Perl module installation instructions should + work perfectly for this simple package. _________________________________________________________________ 3.2.9. GD Perl Module (1.8.3) The GD library was written by Thomas Boutell a long while ago to - programatically generate images in C. Since then it's become almost a + programatically generate images in C. Since then it's become the defacto standard for programatic image construction. The Perl bindings - to it found in the GD library are used on a million web pages to + to it found in the GD library are used on millions of web pages to generate graphs on the fly. That's what bugzilla will be using it for - so you'd better install it if you want any of the graphing to work. + so you must install it if you want any of the graphing to work. - Actually bugzilla uses the Graph module which relies on GD itself, but - isn't that always the way with OOP. At any rate, you can find the GD - library on CPAN (link in Appendix B, Software Download Links). + Actually bugzilla uses the Graph module which relies on GD itself. + Isn't that always the way with object-oriented programming? At any + rate, you can find the GD library on CPAN in Appendix B. Note The Perl GD library requires some other libraries that may or may not - be installed on your system, including "libpng" and "libgd". The full + be installed on your system, including libpng and libgd. The full requirements are listed in the Perl GD library README. Just realize that if compiling GD fails, it's probably because you're missing a required library. @@ -1319,11 +1341,10 @@ Chapter 3. Installation The Chart module provides bugzilla with on-the-fly charting abilities. It can be installed in the usual fashion after it has been fetched - from CPAN where it is found as the Chart-x.x... tarball in a directory - to be listed in Appendix B, "Software Download Links". Note that as - with the GD perl module, only the version listed above, or newer, will - work. Earlier versions used GIF's, which are no longer supported by - the latest versions of GD. + from CPAN where it is found as the Chart-x.x... tarball, linked in + Appendix B. Note that as with the GD perl module, only the version + listed above, or newer, will work. Earlier versions used GIF's, which + are no longer supported by the latest versions of GD. _________________________________________________________________ 3.2.11. DB_File Perl Module @@ -1341,27 +1362,42 @@ Chapter 3. Installation different machine than MySQL, but need to adjust the MySQL "bugs" user permissions accordingly. + Note + + I strongly recommend Apache as the web server to use. The Bugzilla + Guide installation instructions, in general, assume you are using + Apache. As more users use different webservers and send me information + on the peculiarities of installing using their favorite webserver, I + will provide notes for them. + You'll want to make sure that your web server will run any file with the .cgi extension as a cgi and not just display it. If you're using apache that means uncommenting the following line in the srm.conf - file: AddHandler cgi-script .cgi + file: + AddHandler cgi-script .cgi With apache you'll also want to make sure that within the access.conf - file the line: Options ExecCGI is in the stanza that covers the - directories you intend to put the bugzilla .html and .cgi files into. + file the line: + Options ExecCGI - If you are using a newer version of Apache, both of the above lines - will be (or will need to be) in the httpd.conf file, rather than - srm.conf or access.conf. + is in the stanza that covers the directories into which you intend to + put the bugzilla .html and .cgi files. + + Note + + Users of newer versions of Apache will generally find both of the + above lines will be in the httpd.conf file, rather than srm.conf or + access.conf. Warning - There are two critical directories and a file that should not be a - served by the HTTP server. These are the "data" and "shadow" + There are important files and directories that should not be a served + by the HTTP server. These are most files in the "data" and "shadow" directories and the "localconfig" file. You should configure your HTTP server to not serve content from these files. Failure to do so will expose critical passwords and other data. Please see .htaccess files - and security for details. + and security for details on how to do this for Apache. I appreciate + notes on how to get this same functionality using other webservers. _________________________________________________________________ 3.2.13. Installing the Bugzilla Files @@ -1370,34 +1406,32 @@ Chapter 3. Installation willing to make writable by the default web server user (probably "nobody"). You may decide to put the files off of the main web space for your web server or perhaps off of /usr/local with a symbolic link - in the web space that points to the bugzilla directory. At any rate, - just dump all the files in the same place (optionally omitting the CVS - directories if they were accidentally tarred up with the rest of - Bugzilla) and make sure you can access the files in that directory - through your web server. + in the web space that points to the Bugzilla directory. At any rate, + just dump all the files in the same place, and make sure you can + access the files in that directory through your web server. Tip If you symlink the bugzilla directory into your Apache's HTML - heirarchy, you may receive "Forbidden" errors unless you add the + heirarchy, you may receive Forbidden errors unless you add the "FollowSymLinks" directive to the <Directory> entry for the HTML root. Once all the files are in a web accessible directory, make that - directory writable by your webserver's user (which may require just - making it world writable). This is a temporary step until you run the - post-install "checksetup.pl" script, which locks down your - installation. + directory writable by your webserver's user. This is a temporary step + until you run the post-install checksetup.pl script, which locks down + your installation. Lastly, you'll need to set up a symbolic link to /usr/bonsaitools/bin/perl for the correct location of your perl executable (probably /usr/bin/perl). Otherwise you must hack all the - .cgi files to change where they look for perl. To make future upgrades - easier, you should use the symlink approach. + .cgi files to change where they look for perl, or use The setperl.csh + Utility, found in Useful Patches and Utilities for Bugzilla. I suggest + using the symlink approach for future release compatability. Example 3-1. Setting up bonsaitools symlink Here's how you set up the Perl symlink on Linux to make Bugzilla work. - Your mileage may vary; if you are running on Solaris, you probably + Your mileage may vary. For some UNIX operating systems, you probably need to subsitute "/usr/local/bin/perl" for "/usr/bin/perl" below; if on certain other UNIX systems, Perl may live in weird places like "/opt/perl". As root, run these commands: @@ -1440,7 +1474,7 @@ bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl mysql> FLUSH PRIVILEGES; From this point on, if you need to access MySQL as the MySQL root - user, you will need to use "mysql -u root -p" and enter your + user, you will need to use mysql -u root -p and enter your new_password. Remember that MySQL user names have nothing to do with Unix user names (login names). @@ -1461,14 +1495,14 @@ bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl Next, run the magic checksetup.pl script. (Many thanks to Holger Schurig <holgerschurig@nikocity.de> for writing this script!) It will make sure Bugzilla files and directories have reasonable permissions, - set up the "data" directory, and create all the MySQL tables. + set up the data directory, and create all the MySQL tables. bash# ./checksetup.pl - The first time you run it, it will create a file called "localconfig". + The first time you run it, it will create a file called localconfig. _________________________________________________________________ -3.2.15. Tweaking "localconfig" +3.2.15. Tweaking localconfig This file contains a variety of settings you may need to tweak including how Bugzilla should connect to the MySQL database. @@ -1480,7 +1514,7 @@ bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl 3. MySQL username: "bugs" if you're following these directions 4. Password for the "bugs" MySQL account above - You may also install .htaccess files that the Apache webserver will + You should also install .htaccess files that the Apache webserver will use to restrict access to Bugzilla data files. See .htaccess files and security. @@ -1489,17 +1523,11 @@ bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl for which you will be prompted to provide information. When logged into an administrator account once Bugzilla is running, if - you go to the query page (off of the bugzilla main menu), you'll find - an 'edit parameters' option that is filled with editable treats. + you go to the query page (off of the Bugzilla main menu), you'll find + an "edit parameters" option that is filled with editable treats. - Should everything work, you should have a nearly empty copy of the bug - tracking setup. - - The second time around, checksetup.pl will stall if it is on a - filesystem that does not fully support file locking via flock(), such - as NFS mounts. This support is required for Bugzilla to operate safely - with multiple instances. If flock() is not fully supported, it will - stall at: Now regenerating the shadow database for all bugs. + Should everything work, you will have a nearly empty Bugzilla database + and a newly-created localconfig file in your Bugzilla root directory. Note @@ -1516,6 +1544,7 @@ bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl installed in "/usr/local/bugzilla", here's one way to run checksetup.pl as the web server user. As root, for the second run of checksetup.pl, do this: + bash# chown -R apache:apache /usr/local/bugzilla bash# su - apache bash# cd /usr/local/bugzilla @@ -1531,12 +1560,12 @@ bash# ./checksetup.pl 3.2.16. Setting Up Maintainers Manually (Optional) If you want to add someone else to every group by hand, you can do it - by typing the appropriate MySQL commands. Run ' mysql -u root -p bugs' + by typing the appropriate MySQL commands. Run mysql -u root -p bugs You may need different parameters, depending on your security settings. Then: mysql> update profiles set groupset=0x7fffffffffffffff where - login_name = 'XXX'; + login_name = 'XXX'; (yes, that's fifteen"f"'s. replacing XXX with the Bugzilla email address. _________________________________________________________________ @@ -1774,7 +1803,48 @@ sr/local/lib); by editing localconfig and setting the $create_htaccess variable to 0. _________________________________________________________________ -3.5.4. UNIX Installation Instructions History +3.5.4. mod_throttle and Security + + It is possible for a user, by mistake or on purpose, to access the + database many times in a row which can result in very slow access + speeds for other users. If your Bugzilla installation is experiencing + this problem , you may install the Apache module mod_throttle which + can limit connections by ip-address. You may download this module at + http://www.snert.com/Software/Throttle/. Follow the instructions to + install into your Apache install. This module only functions with the + Apache web server!. You may use the ThrottleClientIP command provided + by this module to accomplish this goal. See the Module Instructions + for more information. + _________________________________________________________________ + +3.5.5. Preventing untrusted Bugzilla content from executing malicious +Javascript code + + It is possible for a Bugzilla to execute malicious Javascript code. + Due to internationalization concerns, we are unable to incorporate the + code changes necessary to fulfill the CERT advisory requirements + mentioned in + http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3. + Executing the following code snippet from a UNIX command shell will + rectify the problem if your Bugzilla installation is intended for an + English-speaking audience. As always, be sure your Bugzilla + installation has a good backup before making changes, and I recommend + you understand what the script is doing before executing it. + +bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ + do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html +\; charset=ISO-8859-1/' >$i.tmp; \ + mv $i.tmp $i; done + + All this one-liner command does is search for all instances of + "Content-type: text/html" and replaces it with "Content-Type: + text/html; charset=ISO-8859-1". This specification prevents possible + Javascript attacks on the browser, and is suggested for all + English-speaking sites. For non-english-speaking Bugzilla sites, I + suggest changing "ISO-8859-1", above, to "UTF-8". + _________________________________________________________________ + +3.5.6. UNIX Installation Instructions History This document was originally adapted from the Bonsai installation instructions by Terry Weissman <terry@mozilla.org>. @@ -1821,24 +1891,29 @@ sr/local/lib); Note You should be familiar with, and cross-reference, the rest of the - Chapter 3 section while performing your Win32 installation. + Bugzilla Installation section while performing your Win32 + installation. Making Bugzilla work on Microsoft Windows is no picnic. Support for Win32 has improved dramatically in the last few releases, but, if you choose to proceed, you should be a very skilled Windows Systems - Administrator with both strong troubleshooting abilities and a high - tolerance for pain. Bugzilla on NT requires hacking source code and - implementing some advanced utilities. What follows is the recommended - installation procedure for Win32; additional suggestions are provided - in The Bugzilla FAQ. - 1. Install Apache Web Server for Windows. + Administrator with strong troubleshooting abilities, a high tolerance + for pain, and moderate perl skills. Bugzilla on NT requires hacking + source code and implementing some advanced utilities. What follows is + the recommended installation procedure for Win32; additional + suggestions are provided in Appendix A. + 1. Install Apache Web Server for Windows, and copy the Bugzilla files + somewhere Apache can serve them. Please follow all the + instructions referenced in Bugzilla Installation regarding your + Apache configuration, particularly instructions regarding the + "AddHandler" parameter and "ExecCGI". Note You may also use Internet Information Server or Personal Web Server - for this purpose. However, setup is slightly more difficult. If - ActivePerl doesn't seem to handle your file associations correctly - (for .cgi and .pl files), please consult The Bugzilla FAQ. + for this purpose. However, setup is quite different. If ActivePerl + doesn't seem to handle your file associations correctly (for .cgi and + .pl files), please consult Appendix A. If you are going to use IIS, if on Windows NT you must be updated to at least Service Pack 4. Windows 2000 ships with a sufficient version of IIS. @@ -1888,9 +1963,20 @@ sr/local/lib); g. mysql> exit; h. C:> C:\mysql\bin\mysqladmin -u root -p reload 6. Edit checksetup.pl in your Bugzilla directory. Change this line: - "my $webservergid = getgrnam($my_webservergroup); " + +my $webservergid = getgrnam($my_webservergroup); + + to - "my $webservergid = $my_webservergroup; " + +my $webservergid = $my_webservergroup; + + + or the name of the group you wish to own the files explicitly: + +my $webservergid = 'Administrators' + + 7. Run checksetup.pl from the Bugzilla directory. 8. Edit localconfig to suit your requirements. Set $db_pass to your "bugs_password" from step 5.d, and $webservergroup to "8". @@ -1949,9 +2035,15 @@ my $to=$login; my $subject=$urlbase; $mail->send($from,$to,$subject,$msg); - Note + Note - The code above needs testing as well to make sure it is correct. + Some have found success using the commercial product, Windmail. You + could try replacing your sendmail calls with: +open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail. +log"; + + + or something to that effect. 11. Change all references in all files from processmail to processmail.pl, and rename processmail to processmail.pl. @@ -1996,10 +2088,9 @@ exit; Note - This step is completely optional if you are using IIS or another web - server which only decides on an interpreter based upon the file - extension (.pl), rather than the "shebang" line - (#/usr/bonsaitools/bin/perl) + This step is optional if you are using IIS or another web server which + only decides on an interpreter based upon the file extension (.pl), + rather than the "shebang" line (#/usr/bonsaitools/bin/perl) Modify the path to perl on the first line (#!) of all files to point to your Perl installation, and add "perl" to the beginning of all Perl system calls that use a perl script as an argument. @@ -2023,9 +2114,9 @@ system ("perl processmail.pl",@ARGLIST); Tip - If you are using IIS 5.0 or higher, you must add cgi relationships to - Properties -> Home directory (tab) -> Application Settings (section) - -> Configuration (button), such as: + If you are using IIS or Personal Web Server, you must add cgi + relationships to Properties -> Home directory (tab) -> Application + Settings (section) -> Configuration (button), such as: .cgi to: <perl install directory>\perl.exe %s %s .pl to: <perl install directory>\perl.exe %s %s @@ -2040,7 +2131,7 @@ GET,HEAD,POST From Andrew Pearson: - "You can make Bugzilla work with Personal Web Server for Windows 98 + You can make Bugzilla work with Personal Web Server for Windows 98 and higher, as well as for IIS 4.0. Microsoft has information available at http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP @@ -2059,106 +2150,24 @@ GET,HEAD,POST Tip - "Brian" had this to add, about upgrading to Bugzilla 2.12 from - previous versions: - - 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). - - In checksetup.pl, I did the following... - - 1. - -my $webservergid = getgrnam($my_webservergroup); - - - to + If attempting to run Bugzilla 2.12 or older, you will need to remove + encrypt() calls from the Perl source. This is not necessary for + Bugzilla 2.13 and later. -my $webservergid = 'Administrators' + Example 3-4. Removing encrypt() for Windows NT Bugzilla version 2.12 + or earlier + Replace this: - 2. I then ran checksetup.pl - 3. I removed all the encrypt() - Example 3-4. Removing encrypt() for Windows NT installations - Replace this: - -SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . - SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); +SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($rea +lcryptpwd, 0, 2)) . ")"); my $enteredcryptpwd = FetchOneColumn(); - - with this: + with this: my $enteredcryptpwd = $enteredpwd - - in cgi.pl. - 4. I renamed processmail to processmail.pl - 5. I altered the sendmail statements to windmail: - - -open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail. -log"; - - The quotes around the dir is for the spaces. mail.log is for the - output - - Tip - - This was some late breaking information from Jan Evert. Sorry for the - lack of formatting. - - I'm busy installing bugzilla on a WinNT machine and I thought I'd noti - fy you - at this moment of the commments I have to section 2.2.1 of the bugzill - a - guide (at http://www.trilobyte.net/barnsons/html/). - Step 1: - I've used apache, installation is really straightforward. - After reading the Unix installation instructions, I found that it is - necessary to add the ExecCGI option to the bugzilla directory. Also th - e - 'AddHandler' line for .cgi is by default commented out. - Step 3: although just a detail, 'ppm install <module%gt;' will also wo - rk - (without .ppd). And, it can also download these automatically from - ActiveState. - Step 4: although I have cygwin installed, it seems that it is not nece - ssary. - On my machine cygwin is not in the PATH and everything seems to work a - s - expected. - However, I've not used everything yet. - Step 6: the 'bugs_password' given in SQL command d needs to be edited - into - localconfig later on (Step 7) if the password is not empty. I've also - edited - it into globals.pl, but I'm not sure that is needed. In both places, t - he - variable is named db_pass. - Step 8: all the sendmail replacements mentioned are not as simple as - described there. Since I am not familiar (yet) with perl, I don't have - any - mail working yet. - Step 9: in globals.pl the encrypt() call can be replaced by just the - unencrypted password. In CGI.pl, the complete SQL command can be remov - ed. - Step 11: I've only changed the #! lines in *.cgi. I haven't noticed pr - oblems - with the system() call yet. - There seem to be only four system() called programs: processmail.pl (h - andled - by step 10), syncshadowdb (which should probably get the same treatmen - t as - processmail.pl), diff and mysqldump. The last one is only needed with - the - shadowdb feature (which I don't use). - There seems to be one step missing: copying the bugzilla files somehwe - re - that apache can serve them. - Just noticed the updated guide... Brian's comment is new. His first co - mment - will work, but opens up a huge security hole. + in cgi.pl. _________________________________________________________________ Chapter 4. Administering Bugzilla @@ -2166,38 +2175,66 @@ Chapter 4. Administering Bugzilla Or, I just got this cool thing installed. Now what the heck do I do with it? - So you followed the installation instructions 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 business needs to be to setup the operating parameters - for bugzilla. + So you followed "Bugzilla Installation" to the letter, and logged into + Bugzilla for the very first time with your super-duper god account. + You sit, contentedly staring at the Bugzilla Query Screen, the worst + of the whole mad business of installing this terrific program behind + you. It seems, though, you have nothing yet to query! Your first act + of business should be to setup the operating parameters for Bugzilla + so you can get busy getting data into your bug tracker. _________________________________________________________________ 4.1. Post-Installation Checklist - After installation, follow the checklist below to ensure that you have - a successful installation. If you do not see a recommended setting for - a parameter, consider leaving it at the default while you perform your - initial tests on your Bugzilla setup. - 1. Bring up "editparams.cgi" in your web browser. For instance, to - edit parameters at mozilla.org, the URL would be - http://bugzilla.mozilla.org/editparams.cgi, also available under - the "edit parameters" link on your query page. - 2. Set "maintainer" to your email address. This allows Bugzilla's + After installation, follow the checklist below to help ensure that you + have a successful installation. If you do not see a recommended + setting for a parameter, consider leaving it at the default while you + perform your initial tests on your Bugzilla setup. + 1. Bring up editparams.cgi in your web browser. This should be + available as the "edit parameters" link from any Bugzilla screen + once you have logged in. + 2. The "maintainer" is the email address of the person responsible + for maintaining this Bugzilla installation. The maintainer need + not be a valid Bugzilla user. Error pages, error emails, and + administrative mail will be sent with the maintainer as the return + email address. + Set "maintainer" to your email address. This allows Bugzilla's error messages to display your email address and allow people to contact you for help. - 3. Set "urlbase" to the URL reference for your Bugzilla installation. - If your bugzilla query page is at - http://www.foo.com/bugzilla/query.cgi, your url base is - http://www.foo.com/bugzilla/ - 4. Set "usebuggroups" to "on" only if you need to restrict access to - products. I suggest leaving this parameter off while initially + 3. The "urlbase" parameter defines the fully qualified domain name + and web server path to your Bugzilla installation. + For example, if your bugzilla query page is + http://www.foo.com/bugzilla/query.cgi, set your "urlbase" is + http://www.foo.com/bugzilla/. + 4. "usebuggroups" dictates whether or not to implement group-based + security for Bugzilla. If set, Bugzilla bugs can have an + associated groupmask defining which groups of users are allowed to + see and edit the bug. + Set "usebuggroups" to "on" only if you may wish to restrict access + to products. I suggest leaving this parameter off while initially testing your Bugzilla. - 5. Set "usebuggroupsentry" to "on" 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. - 6. Set "shadowdb" to "bug_shadowdb" if you will be running a *very* + 5. "usebuggroupsentry", when set to "on", requires that all bugs have + an associated groupmask when submitted. This parameter is made for + those installations where product isolation is a necessity. + Set "usebuggroupsentry" to "on" if you absolutely need to restrict + access to bugs from the moment they are submitted through + resolution. 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. + 6. You run into an interesting problem when Bugzilla reaches a high + level of continuous activity. MySQL supports only table-level + write locking. What this means is that if someone needs to make a + change to a bug, they will lock the entire table until the + operation is complete. Locking for write also blocks reads until + the write is complete. The "shadowdb" parameter was designed to + get around this limitation. While only a single user is allowed to + write to a table at a time, reads can continue unimpeded on a + read-only shadow copy of the database. Although your database size + will double, a shadow database can cause an enormous performance + improvement when implemented on extremely high-traffic Bugzilla + databases. + Set "shadowdb" to "bug_shadowdb" if you will be running a *very* large installation of Bugzilla. The shadow database enables many simultaneous users to read and write to the database without interfering with one another. @@ -2205,17 +2242,30 @@ Chapter 4. Administering Bugzilla Note Enabling "shadowdb" can adversely affect the stability of your - installation of Bugzilla. You may frequently need to manually - synchronize your databases, or schedule nightly syncs via "cron" + installation of Bugzilla. You should regularly check that your + database is in sync. It is often advisable to force a shadow database + sync nightly via "cron". Once again, in testing you should avoid this option -- use it if or when you need to use it, and have repeatedly run into the problem it was designed to solve -- very long wait times while - attempting to commit a change to the database. + attempting to commit a change to the database. Mozilla.org began + needing "shadowdb" when they reached around 40,000 Bugzilla users + with several hundred Bugzilla bug changes and comments per day. 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! - 7. If you have custom logos or HTML you must put in place to fit + 7. "headerhtml", "footerhtml", "errorhtml", "bannerhtml", and + "blurbhtml" are all templates which control display of headers, + footers, errors, banners, and additional data. We could go into + some detail regarding the usage of these, but it is really best + just to monkey around with them a bit to see what they do. I + strongly recommend you copy your data/params file somewhere safe + before playing with these values, though. If they are changed + dramatically, it may make it impossible for you to display + Bugzilla pages to fix the problem until you have restored your + data/params file. + 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. @@ -2223,28 +2273,52 @@ Chapter 4. Administering Bugzilla Note The "headerhtml" text box is the HTML printed out before any other - code on the page. If you have a special banner, put the code for it in + code on the page, except the CONTENT-TYPE header sent by the Bugzilla + engine. If you have a special banner, put the code for it in "bannerhtml". You may want to leave these settings at the defaults initially. - 8. Add any text you wish to the "passwordmail" parameter box. For + 8. "passwordmail" is rather simple. Every time a user creates an + account, the text of this parameter is read as the text to send to + the new user along with their password message. + Add any text you wish to the "passwordmail" parameter box. For instance, many people choose to use this box to give a quick training blurb about how to use Bugzilla at your site. - 9. 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. - 10. Do you want to use the QA Contact ("useqacontact") and status + 9. "useqacontact" allows you to define an email address for each + component, in addition to that of the default owner, who will be + sent carbon copies of incoming bugs. The critical difference + between a QA Contact and an Owner is that the QA Contact follows + the component. If you reassign a bug from component A to component + B, the QA Contact for that bug will change with the reassignment, + regardless of owner. + "usestatuswhiteboard" defines whether you wish to have a + free-form, overwritable field associated with each bug. The + advantage of the Status Whiteboard is that it can be deleted or + modified with ease, and provides an easily-searchable field for + indexing some bugs that have some trait in common. Many people + will put "help wanted", "stalled", or "waiting on reply from + somebody" messages into the Status Whiteboard field so those who + peruse the bugs are aware of their status even more than that + which can be indicated by the Resolution fields. + 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. - 11. Set "whinedays" to the amount of days you want to let bugs go in + team, but they may not be needed for many smaller installations. + 10. 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 installation - instructions, or set this value to "0". - 12. Set the "commenton" options according to your site policy. It is a + instructions, or set this value to "0" (never whine). + 11. "commenton" fields allow you to dictate what changes can pass + without comment, and which must have a comment from the person who + changed them. Often, administrators will allow users to add + themselves to the CC list, accept bugs, or change the Status + Whiteboard without adding a comment as to their reasons for the + change, yet require that most other changes come with an + explanation. + Set the "commenton" options according to your site policy. It is a wise idea to require comments when users resolve, reassign, or - reopen bugs. + reopen bugs at the very least. Note @@ -2252,11 +2326,22 @@ Chapter 4. Administering Bugzilla resolving bugs than not. Few things are more annoying to bug database users than having a developer mark a bug "fixed" without any comment as to what the fix was (or even that it was truly fixed!) - 13. Set "supportwatchers" to "On". This feature is helpful for team - leads to monitor progress in their respective areas, and can offer - many other benefits, such as allowing a developer to pick up a - former engineer's bugs without requiring her to change all the - information in the bug. + 12. The "supportwatchers" option can be an exceptionally powerful tool + in the hands of a power Bugzilla user. By enabling this option, + you allow users to receive email updates whenever other users + receive email updates. This is, of course, subject to the groupset + restrictions on the bug; if the "watcher" would not normally be + allowed to view a bug, the watcher cannot get around the system by + setting herself up to watch the bugs of someone with bugs outside + her priveleges. She would still only receive email updates for + those bugs she could normally view. + For Bugzilla sites which require strong inter-Product security to + prevent snooping, watchers are not a good idea. + However, for most sites you should set "supportwatchers" to "On". + This feature is helpful for team leads to monitor progress in + their respective areas, and can offer many other benefits, such as + allowing a developer to pick up a former engineer's bugs without + requiring her to change all the information in the bug. _________________________________________________________________ 4.2. User Administration @@ -2280,6 +2365,9 @@ Chapter 4. Administering Bugzilla ("mysql>" denotes the mysql prompt, not something you should type in): mysql> use bugs; mysql> update profiles set groupset=0x7ffffffffffffff where login_name = "(user's login name)"; + + Yes, that is fourteen "f"'s. A whole lot of f-ing going on if you want + to create a new administator. _________________________________________________________________ 4.2.2. Managing Other Users @@ -2314,10 +2402,10 @@ Chapter 4. Administering Bugzilla More functionality is available via the list on the right-hand side of the text entry box. You can match what you type as a case-insensitive substring (the default) of all users on your system, a case-sensitive - regular expression (please see the "man regexp" manual page for - details on regular expression syntax), or a reverse regular expression - match, where every user name which does NOT match the regular - expression is selected. + regular expression (please see the man regexp manual page for details + on regular expression syntax), or a reverse regular expression match, + where every user name which does NOT match the regular expression is + selected. 3. Click the "Add New User" link at the bottom of the user list 4. Fill out the form presented. This page is self-explanatory. When done, click "submit". @@ -2325,10 +2413,12 @@ Chapter 4. Administering Bugzilla Note Adding a user this way will not send an email informing them of their - username and password. In general, it is preferable to log out and use - the "New Account" button to create users, as it will pre-populate all - the required fields and also notify the user of her account name and - password. + username and password. While useful for creating dummy accounts + (watchers which shuttle mail to another system, for instance, or email + addresses which are a mailing list), in general it is preferable to + log out and use the "New Account" button to create users, as it will + pre-populate all the required fields and also notify the user of her + account name and password. _________________________________________________________________ 4.2.2.3. Disabling Users @@ -2343,6 +2433,11 @@ Chapter 4. Administering Bugzilla Warning Don't disable your own administrative account, or you will hate life! + + At this time, "Disabled Text" does not prevent a user from using the + email interface. If you have the email interface enabled, they can + still continue to submit bugs and comments that way. We need a patch + to fix this. _________________________________________________________________ 4.2.2.4. Modifying Users @@ -2359,9 +2454,8 @@ Chapter 4. Administering Bugzilla For compatability reasons, you should probably stick with email addresses as user login names. It will make your life easier. * Real Name: Duh! - * Password: You will only see asterisks in versions of Bugzilla - newer than 2.10 or early 2.11. You can change the user password - here. + * Password: You can change the user password here. It is normal to + only see asterisks. * Email Notification: You may choose from one of three options: 1. All qualifying bugs except those which I change: The user will be notified of any change to any bug for which she is @@ -2895,45 +2989,50 @@ Chapter 5. Integrating Bugzilla with Third-Party Tools 5.1. Bonsai - We need Bonsai integration information. + Bonsai is a web-based tool for managing CVS, the Concurrent Versioning + System . Using Bonsai, administrators can control open/closed status + of trees, query a fast relational database back-end for change, + branch, and comment information, and view changes made since the last + time the tree was closed. These kinds of changes cause the engineer + responsible to be "on the hook" (include cool URL link here for Hook + policies at mozilla.org). Bonsai also includes gateways to Tinderbox, + the Mozilla automated build management system and Bugzilla _________________________________________________________________ 5.2. CVS CVS integration is best accomplished, at this point, using the - Bugzilla Email Gateway. + Bugzilla Email Gateway. There have been some files submitted to allow + greater CVS integration, but we need to make certain that Bugzilla is + not tied into one particular software management package. + + Follow the instructions in the FAQ for enabling Bugzilla e-mail + integration. Ensure that your check-in script sends an email to your + Bugzilla e-mail gateway with the subject of "[Bug XXXX]", and you can + have CVS check-in comments append to your Bugzilla bug. If you have + your check-in script include an @resolution field, you can even change + the Bugzilla bug state. _________________________________________________________________ 5.3. Perforce SCM You can find the project page for Bugzilla and Teamtrack Perforce - integration at: http://www.ravenbrook.com/project/p4dti. "p4dti" is - now an officially supported product from Perforce, and you can find - the "Perforce Public Depot" p4dti page at + integration (p4dti) at: http://www.ravenbrook.com/project/p4dti . + "p4dti" is now an officially supported product from Perforce, and you + can find the "Perforce Public Depot" p4dti page at http://public.perforce.com/public/perforce/p4dti/index.html. 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 + seamless. Perforce replication information will appear below the + comments of each bug. Be certain you have a matching set of patches + for the Bugzilla version you are installing. p4dti is designed to support multiple defect trackers, and maintains its own documentation for it. Please consult the pages linked above for further information. - - 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. _________________________________________________________________ -5.4. Tinderbox +5.4. Tinderbox/Tinderbox2 - We need Tinderbox integration information + We need Tinderbox integration information. _________________________________________________________________ Chapter 6. The Future of Bugzilla @@ -2978,9 +3077,7 @@ Appendix A. The Bugzilla FAQ 3. Loki Bugzilla (AKA Fenris) - A.3.1. What about Loki Bugzilla? - A.3.2. Who maintains Fenris (Loki Bugzilla) now? - A.3.3. + A.3.1. What is Loki Bugzilla (Fenris)? 4. Pointy-Haired-Boss Questions @@ -3242,14 +3339,8 @@ Appendix A. The Bugzilla FAQ A.1.5. Who maintains Bugzilla? - There are many, many contributors from around the world maintaining - Bugzilla. The designated "Maintainer" is Tara Hernandez, with QA - support by Matthew Tuck. Dan Mosedale and Dawn Endico are employees of - Mozilla.org responsible for the installation of Bugzilla there, and - are very frequent code contributors. Terry Weissman originally ported - Bugzilla, but "these days, Terry just hangs around and heckles." The - rest of us are mostly transient developers; Bugzilla suits our needs, - and we contribute code as we have needs for updates. + Bugzilla maintenance has been in a state of flux recently. Please + check the Bugzilla Project Page for the latest details. A.1.6. How does Bugzilla stack up against other bug-tracking databases? @@ -3262,10 +3353,10 @@ Appendix A. The Bugzilla FAQ email integration, and platform independence), improved scalability, open source code, greater flexibility, and superior ease-of-use. - If you happen to be a commercial Bugzilla vendor, please step forward - with a rebuttal so I can include it in the FAQ. We're not in pursuit - of Bugzilla ueber alles; we simply love having a powerful, open-source - tool to get our jobs done. + If you happen to be a commercial bug-tracker vendor, please step + forward with a rebuttal so I can include it in the FAQ. We're not in + pursuit of Bugzilla ueber alles; we simply love having a powerful, + open-source tool to get our jobs done. A.1.7. How do I change my user name in Bugzilla? @@ -3492,42 +3583,16 @@ Appendix A. The Bugzilla FAQ 3. Loki Bugzilla (AKA Fenris) - Note - - 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. - - A.3.1. What about Loki Bugzilla? + A.3.1. What is Loki Bugzilla (Fenris)? Loki Games has a customized version of Bugzilla available at - http://fenris.lokigames.com. From that page, - - You may have noticed that Fenris is a fork from Bugzilla-- our - patches weren't suitable for integration --and a few people have - expressed interest in the code. Fenris has one major improvement - over Bugzilla, and that is individual comments are not appended - onto a string blob, they are stored as a record in a separate - table. This allows you to, for instance, separate comments out - according to privilege levels in case your bug database could - contain sensitive information not for public eyes. We also provide - things like email hiding to protect user's privacy, additional - fields such as 'user_affected' in case someone enters someone - else's bug, comment editing and deletion, and more conditional - system variables than Bugzilla does (turn off attachments, - qacontact, etc.). - - A.3.2. Who maintains Fenris (Loki Bugzilla) now? - - Raphael Barrerro <raistlin@lokigames.com>. Michael Vance created the - initial fork, but no longer maintains the project. - - A.3.3. + http://fenris.lokigames.com. There are some advantages to using + Fenris, chief being separation of comments based upon user privacy + level, data hiding, forced login for any data retrieval, and some + additional fields. Loki has mainted their code, originally a fork from + the Bugzilla 2.8 code base, and it is quite a bit different than stock + Bugzilla at this point. I recommend you stick with official Bugzilla + version 2.14 rather than using a fork, but it's up to you. 4. Pointy-Haired-Boss Questions @@ -3547,10 +3612,7 @@ Appendix A. The Bugzilla FAQ with Perforce (SCM software)? Yes! You can find more information elsewhere in "The Bugzilla Guide" - in the "Integration with Third-Party Products" section. The section on - Perforce isn't very large, but as the maintainer of the Guide is - charged with Perforce/Bugzilla integration by his company, you can - expect this section to grow. + in the "Integration with Third-Party Products" section. A.4.3. Does Bugzilla allow the user to track multiple projects? @@ -3590,27 +3652,44 @@ Appendix A. The Bugzilla FAQ This was a late-breaking question for the Guide, so I just have to quote the relevant newsgroup thread on it. - > AFAIK, most sites (even if they have SSI enabled) won't have #exec - cmd > enabled. Perhaps what would be better is a #include - virtual and a > footer.cgi the basically has the "require - 'CGI.pl' and PutFooter command. > > Please note that under - most configurations, this also requires naming > the file - from index.html to index.shtml (and making sure that it - will > still be reconized as an index). Personally, I - think this is better on > a per-installation basis - (perhaps add something to the FAQ that says how > to do - this). Good point. Yeah, easy enough to do, that it - shouldn't be a big deal for someone to take it on if they - want it. FAQ is a good place for it. > Dave Miller wrote: - > >> I did a little experimenting with getting the command - menu and footer on >> the end of the index page while - leaving it as an HTML file... >> >> I was successful. :) - >> >> I added this line: >> >> >> >> Just before the - </BODY> </HTML> at the end of the file. And - it worked. >> >> Thought I'd toss that out there. Should - I check this in? For those that >> have SSI disabled, - it'll act like a comment, so I wouldn't think it would >> - break anything. + > AFAIK, most sites (even if they have SSI enabled) won't have #exec c + md + > enabled. Perhaps what would be better is a #include virtual and a + > footer.cgi the basically has the "require 'CGI.pl' and PutFooter com + mand. + > + > Please note that under most configurations, this also requires namin + g + > the file from index.html to index.shtml (and making sure that it wil + l + > still be reconized as an index). Personally, I think this is better + on + > a per-installation basis (perhaps add something to the FAQ that says + how + > to do this). + Good point. Yeah, easy enough to do, that it shouldn't be a big deal + for + someone to take it on if they want it. FAQ is a good place for it. + > Dave Miller wrote: + > + >> I did a little experimenting with getting the command menu and foot + er on + >> the end of the index page while leaving it as an HTML file... + >> + >> I was successful. :) + >> + >> I added this line: + >> + >> + >> + >> Just before the </BODY> </HTML> at the end of the file. And it wor + ked. + >> + >> Thought I'd toss that out there. Should I check this in? For thos + e that + >> have SSI disabled, it'll act like a comment, so I wouldn't think it + would + >> break anything. A.4.8. Does Bugzilla provide any reporting features, metrics, graphs, etc? You know, the type of stuff that management likes to see. :) @@ -4034,68 +4113,104 @@ Appendix A. The Bugzilla FAQ "The Bugzilla Guide". However, they are provided here for historical interest and insight. - 1. #!C:/perl/bin/perl had to be - added to every perl file. 2. Converted to Net::SMTP to - handle mail messages instead of /usr/bin/sendmail. 3. - The crypt function isn't available on Windows NT (at - least none that I am aware), so I made encrypted - passwords = plaintext passwords. 4. The system call to - diff had to be changed to the Cygwin diff. 5. This was - just to get a demo running under NT, it seems to be - working good, and I have inserted almost 100 bugs from - another bug tracking system. Since this work was done - just to get an in-house demo, I am NOT planning on - making a patch for submission to Bugzilla. If you would - like a zip file, let me know. Q: Hmm, couldn't figure it - out from the general instructions above. How about - step-by-step? A: Sure! Here ya go! 1. Install IIS 4.0 - from the NT Option Pack #4. 2. Download and install - Active Perl. 3. Install the Windows GNU tools from - Cygwin. Make sure to add the bin directory to your - system path. (Everyone should have these, whether they - decide to use Bugzilla or not. :-) ) 4. Download - relevant packages from ActiveState at - http://www.activestate.com/packages/zips/. + - DBD-Mysql.zip 5. Extract each zip file with WinZip, and - install each ppd file using the notation: ppm install - <module>.ppd 6. Install Mysql. *Note: If you move - the default install from c:\mysql, you must add the - appropriate startup parameters to the NT service. (ex. - -b e:\\programs\\mysql) 7. Download any Mysql client. - http://www.mysql.com/download_win.html 8. Setup MySql. - (These are the commands that I used.) I. Cleanup default - database settings. C:\mysql\bin\mysql -u root mysql - mysql> DELETE FROM user WHERE Host='localhost' AND - User=''; mysql> quit C:\mysql\bin\mysqladmin reload II. - Set password for root. C:\mysql\bin\mysql -u root mysql - mysql> UPDATE user SET Password=PASSWORD('new_password') - WHERE user='root'; mysql> FLUSH PRIVILEGES; mysql> quit - C:\mysql\bin\mysqladmin -u root reload III. Create bugs - user. C:\mysql\bin\mysql -u root -p mysql> insert into - user (host,user,password) values('localhost','bugs',''); - mysql> quit C:\mysql\bin\mysqladmin -u root reload IV. - Create the bugs database. C:\mysql\bin\mysql -u root -p - mysql> create database bugs; V. Give the bugs user - access to the bugs database. mysql> insert into db - (host,db,user,select_priv,insert_priv,update_priv,delete_priv,cr - eate_priv,drop_priv) values('localhost','bugs','bugs','Y','Y','Y','Y', - 'Y','N') mysql> quit C:\mysql\bin\mysqladmin -u root reload 9. Run the - table scripts to setup the bugs database. 10. Change CGI.pm to use th - e following regular expression because of differing backslashes in NT - versus UNIX. o $0 =~ m:[^\\]*$:; 11. Had to make the crypt password = - plain text password in the database. (Thanks to Andrew Lahser" <andrew - _lahser@merck.com>" on this one.) The files that I changed were: o glo - bals.pl o CGI.pl o alternately, you can try commenting all references - to 'crypt' string and replace them with similar lines but without encr - ypt() or crypr() functions insida all files. 12. Replaced sendmail wit - h Windmail. Basically, you have to come up with a sendmail substitute - for NT. Someone said that they used a Perl module (Net::SMTP), but I w - as trying to save time and do as little Perl coding as possible. 13. A - dded "perl" to the beginning of all Perl system calls that use a perl - script as an argument and renamed processmail to processmail.pl. 14. I - n processmail.pl, I added binmode(HANDLE) before all read() calls. I'm - not sure about this one, but the read() under NT wasn't counting the - EOLs without the binary read." + 1. #!C:/perl/bin/perl had to be added to every perl file. + 2. Converted to Net::SMTP to handle mail messages instead of + /usr/bin/sendmail. + 3. The crypt function isn't available on Windows NT (at least none t + hat I + am aware), so I made encrypted passwords = plaintext passwords. + 4. The system call to diff had to be changed to the Cygwin diff. + 5. This was just to get a demo running under NT, it seems to be work + ing + good, and I have inserted almost 100 bugs from another bug tracki + ng + system. Since this work was done just to get an in-house demo, I + am NOT + planning on making a patch for submission to Bugzilla. If you wou + ld + like a zip file, let me know. + Q: Hmm, couldn't figure it out from the general instructions above. H + ow + about step-by-step? + A: Sure! Here ya go! + 1. Install IIS 4.0 from the NT Option Pack #4. + 2. Download and install Active Perl. + 3. Install the Windows GNU tools from Cygwin. Make sure to add the b + in + directory to your system path. (Everyone should have these, wheth + er + they decide to use Bugzilla or not. :-) ) + 4. Download relevant packages from ActiveState at + http://www.activestate.com/packages/zips/. + DBD-Mysql.zip + 5. Extract each zip file with WinZip, and install each ppd file usin + g the + notation: ppm install <module>.ppd + 6. Install Mysql. *Note: If you move the default install from c:\my + sql, + you must add the appropriate startup parameters to the NT service + . (ex. + -b e:\\programs\\mysql) + 7. Download any Mysql client. http://www.mysql.com/download_win.html + 8. Setup MySql. (These are the commands that I used.) + I. Cleanup default database settings. + C:\mysql\bin\mysql -u root mysql + mysql> DELETE FROM user WHERE Host='localhost' AND User=''; + mysql> quit + C:\mysql\bin\mysqladmin reload + II. Set password for root. + C:\mysql\bin\mysql -u root mysql + mysql> UPDATE user SET Password=PASSWORD('new_password') + WHERE user='root'; + mysql> FLUSH PRIVILEGES; + mysql> quit + C:\mysql\bin\mysqladmin -u root reload + III. Create bugs user. + C:\mysql\bin\mysql -u root -p + mysql> insert into user (host,user,password) + values('localhost','bugs',''); + mysql> quit + C:\mysql\bin\mysqladmin -u root reload + IV. Create the bugs database. + C:\mysql\bin\mysql -u root -p + mysql> create database bugs; + V. Give the bugs user access to the bugs database. + mysql> insert into db + (host,db,user,select_priv,insert_priv,update_priv,delete_pri + v,create_priv,drop_priv) + values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N') + mysql> quit + C:\mysql\bin\mysqladmin -u root reload + 9. Run the table scripts to setup the bugs database. + 10. Change CGI.pm to use the following regular expression because of + differing backslashes in NT versus UNIX. + o $0 =~ m:[^\\]*$:; + 11. Had to make the crypt password = plain text password in the datab + ase. + (Thanks to Andrew Lahser" <andrew_lahser@merck.com>" on this one. + ) The + files that I changed were: + o globals.pl + o CGI.pl + o alternately, you can try commenting all references to 'crypt + ' + string and replace them with similar lines but without encry + pt() + or crypr() functions insida all files. + 12. Replaced sendmail with Windmail. Basically, you have to come up w + ith a + sendmail substitute for NT. Someone said that they used a Perl mo + dule + (Net::SMTP), but I was trying to save time and do as little Perl + coding + as possible. + 13. Added "perl" to the beginning of all Perl system calls that use a + perl + script as an argument and renamed processmail to processmail.pl. + 14. In processmail.pl, I added binmode(HANDLE) before all read() call + s. I'm + not sure about this one, but the read() under NT wasn't counting + the + EOLs without the binary read." A.9.5. I'm having trouble with the perl modules for NT not being able to talk to to the database. @@ -4789,84 +4904,101 @@ C.3. MySQL Permissions & Grant Tables http://www.mysql.com/Manual/manual.html. _________________________________________________________________ -Chapter 7. Bugzilla Variants +Chapter 7. Bugzilla Variants and Competitors - Note - - I know 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. + I created this section to answer questions about Bugzilla competitors + and variants, then found a wonderful site which covers an awful lot of + what I wanted to discuss. Rather than quote it in its entirety, I'll + simply refer you here: http://linas.org/linux/pm.html _________________________________________________________________ 7.1. Red Hat Bugzilla - 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, - - 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 docum - entation 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 its - elf. 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 number - ed 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 tha - t 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 syst - em. 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 t - he 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. A - nd more integration - with other internal/external Red Hat web sites. - I hope this information may prove helpful for your documentation. P - lease contact - me if you have any more question or I can do anything else. - Regards + Red Hat Bugzilla is probably the most popular Bugzilla variant on the + planet. One of the major benefits of Red Hat Bugzilla is the ability + to work with Oracle, MySQL, and PostGreSQL databases serving as the + back-end, instead of just MySQL. Dave Lawrence has worked very hard to + keep Red Hat Bugzilla up-to-date, and many people prefer the + snappier-looking page layout of Red Hat Bugzilla to the default + Mozilla-standard formatting. + + URL: http://bugzilla.redhat.com/bugzilla/ + _________________________________________________________________ + +7.2. Loki Bugzilla (Fenris) + + Fenris can be found at http://fenris.lokigames.com. It is a fork from + Bugzilla. + _________________________________________________________________ + +7.3. Issuezilla + + Issuezilla is another fork from Bugzilla, and seems nearly as popular + as the Red Hat Bugzilla fork. Some Issuezilla team members are regular + contributors to the Bugzilla mailing list/newsgroup. Issuezilla is not + the primary focus of bug-tracking at tigris.org, however. Their + Java-based bug-tracker, Scarab, a newfangled Java-based issue tracker, + is under heavy development and looks promising! + + URL: http://issuezilla.tigris.org/servlets/ProjectHome + _________________________________________________________________ + +7.4. Scarab + + Scarab is a promising new bug-tracking system built using Java Serlet + technology. As of this writing, no source code has been released as a + package, but you can obtain the code from CVS. + + URL: http://scarab.tigris.org + _________________________________________________________________ + +7.5. Perforce SCM + + Although Perforce isn't really a bug tracker, it can be used as such + through the "jobs" functionality. + + http://www.perforce.com/perforce/technotes/note052.htmlhttp://www.perf + orce.com/perforce/technotes/note052.html + _________________________________________________________________ + +7.6. SourceForge + + SourceForge is more of a way of coordinating geographically + distributed free software and open source projects over the Internet + than strictly a bug tracker, but if you're hunting for bug-tracking + for your open project, it may be just what the software engineer + ordered! + + URL: http://www.sourceforge.net _________________________________________________________________ Appendix D. Useful Patches and Utilities for Bugzilla -D.1. The setperl.csh Utility + Are you looking for a way to put your Bugzilla into overdrive? Catch + some of the niftiest tricks here in this section. + _________________________________________________________________ + +D.1. Apache mod_rewrite magic + + Apache's mod_rewrite module lets you do some truly amazing things with + URL rewriting. Here are a couple of examples of what you can do. + + 1. Make it so if someone types http://www.foo.com/12345, Bugzilla + spits back http://www.foo.com/show_bug.cgi?id=12345. Try setting + up your VirtualHost section for Bugzilla with a rule like this: + +<VirtualHost 12.34.56.78> +RewriteEngine On +RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R] +</VirtualHost> + + 2. There are many, many more things you can do with mod_rewrite. As + time goes on, I will include many more in the Guide. For now, + though, please refer to the mod_rewrite documentation at + http://www.apache.org + _________________________________________________________________ + +D.2. The setperl.csh Utility 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 @@ -4889,7 +5021,7 @@ D.1. The setperl.csh Utility bash# ./setperl.csh /usr/bin/perl _________________________________________________________________ -D.2. Command-line Bugzilla Queries +D.3. Command-line Bugzilla Queries Users can query Bugzilla from the command line using this suite of utilities. @@ -4932,7 +5064,7 @@ D.2. Command-line Bugzilla Queries 2. Make your utilities executable: bash$ chmod u+x buglist bugs _________________________________________________________________ -D.3. The Quicksearch Utility +D.4. The Quicksearch Utility Quicksearch is a new, experimental feature of the 2.12 release. It consist of two Javascript files, "quicksearch.js" and @@ -5342,7 +5474,13 @@ Glossary A - There are no entries for A + Apache + In this context, Apache is the web server most commonly used + for serving up Bugzilla pages. Contrary to popular belief, the + apache web server has nothing to do with the ancient and noble + Native American tribe, but instead derived its name from the + fact that it was "a patchy" version of the original NCSA + world-wide-web server. B @@ -5364,11 +5502,53 @@ B verification. The "Bug Life Cycle" is moderately flexible according to the needs of the organization using it, though. + Bugzilla + Bugzilla is the industry-standard bug tracking system. It is + quite popular among Open Source enthusiasts. + + Component + A Component is a subsection of a Product. It should be a narrow + category, tailored to your organization. All Products must + contain at least one Component (and, as a matter of fact, + creating a Product with no Components will create an error in + Bugzilla). + + CPAN + CPAN stands for the "Comprehensive Perl Archive Network". CPAN + maintains a large number of extremely useful Perl modules. By + themselves, Perl modules generally do nothing, but when used as + part of a larger program, they provide much-needed algorithms + and functionality. + +D + + daemon + A daemon is a computer program which runs in the background. In + general, most daemons are started at boot time via System V + init scripts, or through RC scripts on BSD-based systems. + mysqld, the MySQL server, and apache, a web server, are + generally run as daemons. + + Groups + The word "Groups" has a very special meaning to Bugzilla. + Bugzilla's main security mechanism comes by lumping users into + groups, and assigning those groups certain privileges to + Products and Components in the Bugzilla database. + I Infinite Loop A loop of information that never ends; see recursion. +M + + mysqld + mysqld is the name of the daemon for the MySQL database. In + general, it is invoked automatically through the use of the + System V init scripts on GNU/Linux and AT&T System V-based + systems, such as Solaris and HP/UX, or through the RC scripts + on BSD-based systems. + P Product @@ -5387,6 +5567,13 @@ P permissions so that only those people who are members of Group "Z" can see components and bugs under Product "Z". + Perl + First written by Larry Wall, Perl is a remarkable program + language. It has the benefits of the flexibility of an + interpreted scripting language (such as shell script), combined + with the speed and power of a compiled language, such as C. + Bugzilla is maintained in Perl. + Q QA @@ -5405,6 +5592,29 @@ R thus recursing upon itself for definition. For further clarity, see Infinite Loop. +S + + SGML + SGML stands for "Standard Generalized Markup Language". Created + in the 1980's to provide an extensible means to maintain + documentation based upon content instead of presentation, SGML + has withstood the test of time as a robust, powerful language. + XML is the "baby brother" of SGML; any valid XML document it, + by definition, a valid SGML document. The document you are + reading is written and maintained in SGML, and is also valid + XML if you modify the Document Type Definition. + +T + + Target Milestone + Target Milestones are Product goals. They are configurable on a + per-Product basis. Most software development houses have a + concept of "milestones" where the people funding a project + expect certain functionality on certain dates. Bugzilla + facilitates meeting these milestones by giving you the ability + to declare by which milestone a bug will be fixed, or an + enhancement will be implemented. + Z Zarro Boogs Found diff --git a/docs/xml/Bugzilla-Guide.xml b/docs/xml/Bugzilla-Guide.xml index 30deb5c4a..59befaf0a 100644 --- a/docs/xml/Bugzilla-Guide.xml +++ b/docs/xml/Bugzilla-Guide.xml @@ -23,7 +23,7 @@ <!ENTITY bz-ver "2.14"> <!ENTITY bz-cvs-ver "2.15"> <!ENTITY bzg-date "August 10, 2001"> -<!ENTITY bzg-ver "2.14.0"> +<!ENTITY bzg-ver "2.14"> <!ENTITY bzg-cvs-ver "2.15.0"> <!ENTITY bzg-auth "Matthew P. Barnson"> <!ENTITY bzg-auth-email "<email>barnboy@NOSPAM.trilobyte.net</email>"> @@ -137,15 +137,6 @@ try to avoid clutter and feel free to waste space in the code to make it more re </affiliation> </collab> - <editor> - <firstname>I.</firstname> - <surname>Freely</surname> - <othername>P.</othername> - <affiliation> - <address><email>ipfreely@freely.eye-p.net</email></address> - </affiliation> - </editor> - </authorgroup> <abstract> @@ -165,6 +156,12 @@ try to avoid clutter and feel free to waste space in the code to make it more re professional on operating system upon which you install Bugzilla. </para> + <para> + THIS DOCUMENTATION IS MAINTAINED IN DOCBOOK 4.1 SGML FORMAT. + IF YOU WISH TO MAKE CORRECTIONS, PLEASE MAKE THEM IN PLAIN + TEXT OR SGML DIFFS AGAINST THE SOURCE. I CANNOT ACCEPT + ADDITIONS TO THE GUIDE WRITTEN IN HTML! + </para> </abstract> diff --git a/docs/xml/about.xml b/docs/xml/about.xml index d92fa9b30..89f7bb127 100644 --- a/docs/xml/about.xml +++ b/docs/xml/about.xml @@ -14,11 +14,10 @@ document you see today. </para> <para> - Despite the lack of updates, Bugzilla is simply the best piece - of bug-tracking software the world has ever seen. This document - is intended to be the comprehensive guide to the installation, - administration, maintenance, and use of the Bugzilla - bug-tracking system. + Bugzilla is simply the best piece of bug-tracking software the + world has ever seen. This document is intended to be the + comprehensive guide to the installation, administration, + maintenance, and use of the Bugzilla bug-tracking system. </para> <para> This release of the Bugzilla Guide is the diff --git a/docs/xml/administration.xml b/docs/xml/administration.xml index 0f290da31..54f984fbc 100644 --- a/docs/xml/administration.xml +++ b/docs/xml/administration.xml @@ -8,18 +8,21 @@ </subtitle> <para> - So you followed the installation instructions 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 business needs to be to setup the - operating parameters for bugzilla. + So you followed <quote><xref linkend="installation"></quote> to the + letter, and logged into Bugzilla for the very first time with your + super-duper god account. You sit, contentedly staring at the + Bugzilla Query Screen, the worst of the whole mad business of + installing this terrific program behind you. It seems, though, you + have nothing yet to query! Your first act of business should be to + setup the operating parameters for Bugzilla so you can get busy + getting data into your bug tracker. </para> <section id="postinstall-check"> <title>Post-Installation Checklist</title> <para> - After installation, follow the checklist below to ensure that - you have a successful installation. If you do not see a + After installation, follow the checklist below to help ensure + that you have a successful installation. If you do not see a recommended setting for a parameter, consider leaving it at the default while you perform your initial tests on your Bugzilla setup. @@ -30,47 +33,80 @@ <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. + Bring up <filename>editparams.cgi</filename> in your web + browser. This should be available as the <quote>edit + parameters</quote> link from any Bugzilla screen once you + have logged in. </para> </step> <step> + <para>The <quote>maintainer</quote> is the email address of + the person responsible for maintaining this Bugzilla + installation. The maintainer need not be a valid Bugzilla + user. Error pages, error emails, and administrative mail + will be sent with the maintainer as the return email + address.</para> <para> - Set "maintainer" to <emphasis>your</emphasis> email address. + Set <quote>maintainer</quote> to <emphasis>your</emphasis> email address. This allows Bugzilla's error messages to display your email address and allow people to contact you for help. </para> </step> <step> + <para>The <quote>urlbase</quote> parameter defines the fully + qualified domain name and web server path to your Bugzilla + installation.</para> <para> - Set "urlbase" to the URL reference for your Bugzilla - installation. If your bugzilla query page is at - http://www.foo.com/bugzilla/query.cgi, your url base is - http://www.foo.com/bugzilla/ + For example, if your bugzilla query page is + http://www.foo.com/bugzilla/query.cgi, set your + <quote>urlbase</quote> is http://www.foo.com/bugzilla/. </para> </step> <step> + <para><quote>usebuggroups</quote> dictates whether or not to + implement group-based security for Bugzilla. If set, + Bugzilla bugs can have an associated groupmask defining + which groups of users are allowed to see and edit the + bug.</para> <para> Set "usebuggroups" to "on" <emphasis>only</emphasis> if you - need to restrict access to products. I suggest leaving this - parameter <emphasis>off</emphasis> while initially testing - your Bugzilla. + may wish to restrict access to products. I suggest leaving + this parameter <emphasis>off</emphasis> while initially + testing your Bugzilla. </para> </step> <step> <para> - Set "usebuggroupsentry" to "on" if you want to restrict - access to products. Once again, if you are simply testing + <quote>usebuggroupsentry</quote>, when set to + <quote>on</quote>, requires that all bugs have an associated + groupmask when submitted. This parameter is made for those + installations where product isolation is a necessity. + </para> + <para> + Set "usebuggroupsentry" to "on" if you absolutely need to + restrict access to bugs from the moment they are submitted + through resolution. 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. </para> </step> <step> + <para> + You run into an interesting problem when Bugzilla reaches a + high level of continuous activity. MySQL supports only + table-level write locking. What this means is that if + someone needs to make a change to a bug, they will lock the + entire table until the operation is complete. Locking for + write also blocks reads until the write is complete. The + <quote>shadowdb</quote> parameter was designed to get around + this limitation. While only a single user is allowed to + write to a table at a time, reads can continue unimpeded on + a read-only shadow copy of the database. Although your + database size will double, a shadow database can cause an + enormous performance improvement when implemented on + extremely high-traffic Bugzilla databases. + </para> <para> Set "shadowdb" to "bug_shadowdb" if you will be running a *very* large installation of Bugzilla. The shadow database @@ -79,15 +115,19 @@ <note> <para> Enabling "shadowdb" can adversely affect the stability - of your installation of Bugzilla. You may frequently - need to manually synchronize your databases, or schedule - nightly syncs via "cron" + of your installation of Bugzilla. You should regularly + check that your database is in sync. It is often + advisable to force a shadow database sync nightly via + <quote>cron</quote>. </para> </note> Once again, in testing you should avoid this option -- use it if or when you <emphasis>need</emphasis> to use it, and have repeatedly run into the problem it was designed to solve -- very long wait times while attempting to commit - a change to the database. + a change to the database. Mozilla.org began needing + <quote>shadowdb</quote> when they reached around 40,000 + Bugzilla users with several hundred Bugzilla bug changes and + comments per day. </para> <para> If you use the "shadowdb" option, it is only natural that @@ -97,6 +137,18 @@ </para> </step> <step> + <para><quote>headerhtml</quote>, <quote>footerhtml</quote>, + <quote>errorhtml</quote>, <quote>bannerhtml</quote>, and + <quote>blurbhtml</quote> are all templates which control + display of headers, footers, errors, banners, and additional + data. We could go into some detail regarding the usage of + these, but it is really best just to monkey around with them + a bit to see what they do. I strongly recommend you copy + your <filename>data/params</filename> file somewhere safe + before playing with these values, though. If they are + changed dramatically, it may make it impossible for you to + display Bugzilla pages to fix the problem until you have + restored your <filename>data/params</filename> file.</para> <para> If you have custom logos or HTML you must put in place to fit within your site design guidelines, place the code in @@ -105,15 +157,20 @@ <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 settings at - the defaults initially. + <emphasis>before</emphasis> any other code on the page, + except the CONTENT-TYPE header sent by the Bugzilla + engine. 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> </para> </step> <step> + <para><quote>passwordmail</quote> is rather simple. Every + time a user creates an account, the text of this parameter + is read as the text to send to the new user along with their + password message.</para> <para> Add any text you wish to the "passwordmail" parameter box. For instance, many people choose to use this box to give a @@ -121,20 +178,32 @@ </para> </step> <step> - <para> - 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><quote>useqacontact</quote> allows you to define an + email address for each component, in addition to that of the + default owner, who will be sent carbon copies of incoming + bugs. The critical difference between a QA Contact and an + Owner is that the QA Contact follows the component. If you + reassign a bug from component A to component B, the QA + Contact for that bug will change with the reassignment, + regardless of owner.</para> + <para><quote>usestatuswhiteboard</quote> defines whether you + wish to have a free-form, overwritable field associated with + each bug. The advantage of the Status Whiteboard is that it + can be deleted or modified with ease, and provides an + easily-searchable field for indexing some bugs that have + some trait in common. Many people will put <quote>help + wanted</quote>, <quote>stalled</quote>, or <quote>waiting + on reply from somebody</quote> messages into the Status + Whiteboard field so those who peruse the bugs are aware of + their status even more than that which can be indicated by + the Resolution fields.</para> <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 Quality Assurance and/or Release Engineering team, but they may not be needed - for smaller installations. + for many smaller installations. </para> </step> <step> @@ -144,14 +213,22 @@ 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 installation instructions, or set this - value to "0". + value to "0" (never whine). </para> </step> <step> + <para><quote>commenton</quote> fields allow you to dictate + what changes can pass without comment, and which must have a + comment from the person who changed them. Often, + administrators will allow users to add themselves to the CC + list, accept bugs, or change the Status Whiteboard without + adding a comment as to their reasons for the change, yet + require that most other changes come with an + explanation.</para> <para> Set the "commenton" options according to your site policy. It is a wise idea to require comments when users resolve, - reassign, or reopen bugs. + reassign, or reopen bugs at the very least. <note> <para> It is generally far better to require a developer @@ -164,12 +241,28 @@ </para> </step> <step> + <para>The <quote>supportwatchers</quote> option can be an + exceptionally powerful tool in the hands of a power Bugzilla + user. By enabling this option, you allow users to receive + email updates whenever other users receive email updates. + This is, of course, subject to the groupset restrictions on + the bug; if the <quote>watcher</quote> would not normally be + allowed to view a bug, the watcher cannot get around the + system by setting herself up to watch the bugs of someone + with bugs outside her priveleges. She would still only + receive email updates for those bugs she could normally + view.</para> + <para>For Bugzilla sites which require strong inter-Product + security to prevent snooping, watchers are not a good + idea.</para> <para> - Set "supportwatchers" to "On". This feature is helpful for - team leads to monitor progress in their respective areas, - and can offer many other benefits, such as allowing a - developer to pick up a former engineer's bugs without - requiring her to change all the information in the bug. + However, for most sites you should set + <quote>supportwatchers</quote> to "On". This feature is + helpful for team leads to monitor progress in their + respective areas, and can offer many other benefits, such as + allowing a developer to pick up a former engineer's bugs + without requiring her to change all the information in the + bug. </para> </step> </procedure> @@ -205,6 +298,9 @@ groupset=0x7ffffffffffffff where login_name = "(user's login name)"; </command> </para> + <para>Yes, that is <emphasis>fourteen</emphasis> + <quote>f</quote>'s. A whole lot of f-ing going on if you + want to create a new administator.</para> </tip> </section> @@ -269,11 +365,11 @@ right-hand side of the text entry box. You can match what you type as a case-insensitive substring (the default) of all users on your system, a case-sensitive - regular expression (please see the "man regexp" manual - page for details on regular expression syntax), or a - <emphasis>reverse</emphasis> regular expression match, - where every user name which does NOT match the regular - expression is selected. + regular expression (please see the <command>man + regexp</command> manual page for details on regular + expression syntax), or a <emphasis>reverse</emphasis> + regular expression match, where every user name which + does NOT match the regular expression is selected. </para> </tip> </listitem> @@ -292,10 +388,14 @@ <para> Adding a user this way will <emphasis>not</emphasis> send an email informing them of their username and - password. In general, it is preferable to log out and - use the "New Account" button to create users, as it - will pre-populate all the required fields and also - notify the user of her account name and password. + password. While useful for creating dummy accounts + (watchers which shuttle mail to another system, for + instance, or email addresses which are a mailing + list), in general it is preferable to log out and use + the <quote>New Account</quote> button to create users, + as it will pre-populate all the required fields and + also notify the user of her account name and + password. </para> </note> </listitem> @@ -317,6 +417,11 @@ Don't disable your own administrative account, or you will hate life! </para> + <para>At this time, <quote>Disabled Text</quote> does not + prevent a user from using the email interface. If you + have the email interface enabled, they can still + continue to submit bugs and comments that way. We need + a patch to fix this.</para> </warning> </para> </section> @@ -350,9 +455,8 @@ </listitem> <listitem> <para> - <emphasis>Password</emphasis>: You will only see - asterisks in versions of Bugzilla newer than 2.10 or - early 2.11. You can change the user password here. + <emphasis>Password</emphasis>: You can change the user + password here. It is normal to only see asterisks. </para> </listitem> <listitem> diff --git a/docs/xml/faq.xml b/docs/xml/faq.xml index f01b43053..34b952b01 100644 --- a/docs/xml/faq.xml +++ b/docs/xml/faq.xml @@ -1,6 +1,6 @@ <!-- <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> --> -<appendix id="faq" xreflabel="The Bugzilla FAQ"> +<appendix id="faq"> <title>The Bugzilla FAQ</title> <qandaset> @@ -17,8 +17,8 @@ <answer> <para> You can stay up-to-date with the latest Bugzilla - information at <ulink - url="http://www.mozilla.org/projects/bugzilla/"> http://www.mozilla.org/projects/bugzilla/</ulink> + information at <ulink url="http://www.mozilla.org/projects/bugzilla/"> + http://www.mozilla.org/projects/bugzilla/</ulink> </para> </answer> </qandaentry> @@ -31,9 +31,9 @@ </question> <answer> <para> - Bugzilla is covered by the Mozilla Public License. See - details at <ulink url="http://www.mozilla.org/MPL/"> - http://www.mozilla.org/MPL/</ulink> + Bugzilla is covered by the Mozilla Public License. + See details at <ulink url="http://www.mozilla.org/MPL/"> + http://www.mozilla.org/MPL/</ulink> </para> </answer> </qandaentry> @@ -46,17 +46,16 @@ </question> <answer> <para> - <ulink url="http://www.collab.net/">www.collab.net</ulink> - offers Bugzilla as part of their standard offering to - large projects. They do have some minimum fees that are - pretty hefty, and generally aren't interested in small - projects. + <ulink url="http://www.collab.net/">www.collab.net</ulink> offers + Bugzilla as part of their standard offering to large projects. + They do have some minimum fees that are pretty hefty, and generally + aren't interested in small projects. </para> <para> - There are several experienced Bugzilla hackers on the - mailing list/newsgroup who are willing to whore themselves - out for generous compensation. Try sending a message to - the mailing list asking for a volunteer. + There are several experienced + Bugzilla hackers on the mailing list/newsgroup who are willing + to whore themselves out for generous compensation. + Try sending a message to the mailing list asking for a volunteer. </para> </answer> </qandaentry> @@ -64,15 +63,14 @@ <qandaentry> <question> <para> - What major companies or projects are currently using - Bugzilla for bug-tracking? + What major companies or projects are currently using Bugzilla + for bug-tracking? </para> </question> <answer> <para> - There are <emphasis>dozens</emphasis> of major comapanies - with public Bugzilla sites to track bugs in their - products. A few include: + There are <emphasis>dozens</emphasis> of major comapanies with public + Bugzilla sites to track bugs in their products. A few include: <simplelist> <member>Netscape/AOL</member> <member>Mozilla.org</member> @@ -94,9 +92,8 @@ </simplelist> </para> <para> - Suffice to say, there are more than enough huge projects - using Bugzilla that we can safely say it's extremely - popular. + Suffice to say, there are more than enough huge projects using Bugzilla + that we can safely say it's extremely popular. </para> </answer> </qandaentry> @@ -109,16 +106,9 @@ </question> <answer> <para> - There are many, many contributors from around the world - maintaining Bugzilla. The designated "Maintainer" is Tara - Hernandez, with QA support by Matthew Tuck. Dan Mosedale - and Dawn Endico are employees of Mozilla.org responsible - for the installation of Bugzilla there, and are very - frequent code contributors. Terry Weissman originally - ported Bugzilla, but "these days, Terry just hangs around - and heckles." The rest of us are mostly transient - developers; Bugzilla suits our needs, and we contribute - code as we have needs for updates. + Bugzilla maintenance has been in a state of flux recently. + Please check <ulink + url="http://www.mozilla.org/projects/bugzilla/">the Bugzilla Project Page for the latest details. </ulink> </para> </answer> </qandaentry> @@ -126,8 +116,7 @@ <qandaentry> <question> <para> - How does Bugzilla stack up against other bug-tracking - databases? + How does Bugzilla stack up against other bug-tracking databases? </para> </question> <answer> @@ -143,7 +132,7 @@ flexibility, and superior ease-of-use. </para> <para> - If you happen to be a commercial Bugzilla vendor, please + If you happen to be a commercial bug-tracker vendor, please step forward with a rebuttal so I can include it in the FAQ. We're not in pursuit of Bugzilla ueber alles; we simply love having a powerful, open-source tool to get our @@ -160,9 +149,8 @@ </question> <answer> <para> - You can't. However, the administrative account can, by - simply opening your user account in editusers.cgi and - changing the login name. + You can't. However, the administrative account can, by simply opening + your user account in editusers.cgi and changing the login name. </para> </answer> </qandaentry> @@ -170,26 +158,24 @@ <qandaentry> <question> <para> - Why doesn't Bugzilla offer this or that feature or - compatability with this other tracking software? + Why doesn't Bugzilla offer this or that feature or compatability + with this other tracking software? </para> </question> <answer> <para> - It may be that the support has not been built yet, or that - you have not yet found it. Bugzilla is making tremendous - strides in usability, customizability, scalability, and - user interface. It is widely considered the most complete - and popular open-source bug-tracking software in - existence. + It may be that the support has not been built yet, or that you + have not yet found it. Bugzilla is making tremendous strides in + usability, customizability, scalability, and user interface. It + is widely considered the most complete and popular open-source + bug-tracking software in existence. </para> <para> - That doesn't mean it can't use improvement! You can help - the project along by either hacking a patch yourself that - supports the functionality you require, or else submitting - a "Request for Enhancement" (RFE) using the bug submission - interface at <ulink - url="http://bugzilla.mozilla.org/">bugzilla.mozilla.org</ulink>. + That doesn't mean it can't use improvement! + You can help the project along by either hacking a patch yourself + that supports the functionality you require, or else submitting a + "Request for Enhancement" (RFE) using the bug submission interface + at <ulink url="http://bugzilla.mozilla.org/">bugzilla.mozilla.org</ulink>. </para> </answer> </qandaentry> @@ -205,40 +191,37 @@ <para>Terry Weissman answers, <blockquote> <para> - You're not the only one. But <emphasis>I</emphasis> am - not very interested. I'm not a real SQL or database - person. I just wanted to make a useful tool, and build - it on top of free software. So, I picked MySQL, and - learned SQL by staring at the MySQL manual and some - code lying around here, and wrote Bugzilla. I didn't - know that Enum's were non-standard SQL. I'm not sure - if I would have cared, but I didn't even know. So, to - me, things are "portable" because it uses MySQL, and - MySQL is portable enough. I fully understand (now) - that people want to be portable to other databases, - but that's never been a real concern of mine. + You're not the only one. But <emphasis>I</emphasis> am not very interested. I'm not + a real SQL or database person. I just wanted to make a useful tool, + and build it on top of free software. So, I picked MySQL, and + learned SQL by staring at the MySQL manual and some code lying + around here, and + wrote Bugzilla. I didn't know that Enum's were non-standard SQL. + I'm not sure if I would have cared, but I didn't even know. So, to + me, things are "portable" because it uses MySQL, and MySQL is + portable enough. I fully understand (now) that people want to be + portable to other databases, but that's never been a real concern + of mine. </para> </blockquote> </para> <para> - Things aren't quite that grim these days, however. Terry - pretty much sums up much of the thinking many of us have - for Bugzilla, but there is light on the horizon for - database-independence! Here are some options: + Things aren't quite that grim these days, however. Terry pretty much + sums up much of the thinking many of us have for Bugzilla, but there + is light on the horizon for database-independence! Here are some options: </para> <simplelist> <member> - <emphasis><ulink url="http://bugzilla.redhat.com/">Red - Hat Bugzilla</ulink></emphasis>: Runs a modified - Bugzilla 2.8 atop an Oracle database. + <emphasis><ulink url="http://bugzilla.redhat.com/">Red Hat Bugzilla</ulink></emphasis>: + Runs a modified Bugzilla 2.8 atop an Oracle database. </member> <member> - <emphasis><ulink - url="http://sourceforge.net/projects/interzilla">Interzilla</ulink></emphasis>: A project to run Bugzilla on Interbase. No code released yet, however. + <emphasis><ulink url="http://sourceforge.net/projects/interzilla">Interzilla</ulink></emphasis>: + A project to run Bugzilla on Interbase. No code released yet, however. </member> <member> - <emphasis>Bugzilla 3.0</emphasis>: One of the primary - stated goals is multiple database support. + <emphasis>Bugzilla 3.0</emphasis>: One of the primary stated goals + is multiple database support. </member> </simplelist> </answer> @@ -247,40 +230,36 @@ <qandaentry> <question> <para> - Why do the scripts say "/usr/bonsaitools/bin/perl" instead - of "/usr/bin/perl" or something else? + Why do the scripts say "/usr/bonsaitools/bin/perl" instead of + "/usr/bin/perl" or something else? </para> </question> <answer> <para> - Mozilla.org uses /usr/bonsaitools/bin/perl. The prime - rule in making submissions is "don't break - bugzilla.mozilla.org". If it breaks it, your patch will be - reverted faster than you can do a diff. + Mozilla.org uses /usr/bonsaitools/bin/perl. The prime rule in making + submissions is "don't break bugzilla.mozilla.org". If it breaks it, your + patch will be reverted faster than you can do a diff. </para> <para> - Here's Terry Weissman's comment, for some historical - context: + Here's Terry Weissman's comment, for some historical context: <blockquote> <para> - [This was] purely my own convention. I wanted a place - to put a version of Perl and other tools that was - strictly under my control for the various webtools, - and not subject to anyone else. Edit it to point to - whatever you like. + [This was] purely my own convention. I wanted a place to put a version of + Perl and other tools that was strictly under my control for the + various webtools, and not subject to anyone else. Edit it to point + to whatever you like. </para> <note> <para> - We always recommend that, if possible, you keep the - path as /usr/bonsaitools/bin/perl, and simply add a - /usr/bonsaitools and /usr/bonsaitools/bin directory, - then symlink your version of perl to - /usr/bonsaitools/bin/perl. This will make upgrading + We always recommend that, if possible, you keep the path + as /usr/bonsaitools/bin/perl, and simply add a /usr/bonsaitools + and /usr/bonsaitools/bin directory, then symlink your version + of perl to /usr/bonsaitools/bin/perl. This will make upgrading your Bugzilla much easier in the future. </para> <para> - Obviously, if you do not have root access to your - Bugzilla box, our suggestion is irrelevant. + Obviously, if you do not have root access to your Bugzilla + box, our suggestion is irrelevant. </para> </note> </blockquote> @@ -297,8 +276,7 @@ <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. + Please see the section on "Red Hat Bugzilla" under "Variants" in The Bugzilla Guide. </para> </note> </para> @@ -310,29 +288,27 @@ </question> <answer> <para> - Red Hat Bugzilla is arguably more user-friendly, - customizable, and scalable than stock Bugzilla. Check it - out at http://bugzilla.redhat.com and the sources at - ftp://people.redhat.com/dkl/. They've set their Bugzilla - up to work with Oracle out of the box. Note that Redhat - Bugzilla is based upon the 2.8 Bugzilla tree; Bugzilla has - made some tremendous advances since the 2.8 release. Why - not download both Bugzillas to check out the differences - for yourself? + Red Hat Bugzilla is arguably more user-friendly, customizable, and scalable + than stock Bugzilla. Check it out at + http://bugzilla.redhat.com and the sources at ftp://people.redhat.com/dkl/. + They've set their Bugzilla up to work with Oracle out of the box. + Note that Redhat Bugzilla is based upon the 2.8 Bugzilla tree; + Bugzilla has made some tremendous advances since the 2.8 release. + Why not download both Bugzillas to check out the differences for + yourself? </para> <para> - Dave Lawrence, the original Red Hat Bugzilla maintainer, - mentions: + Dave Lawrence, the original Red Hat Bugzilla maintainer, mentions: <blockquote> <para> - Somebody needs to take the ball and run with it. I'm - the only maintainer and am very pressed for time. + Somebody needs to take the ball and run with it. I'm the only + maintainer and am very pressed for time. </para> - </blockquote> If you, or someone you know, has the time - and expertise to do the integration work so main-tree - Bugzilla 2.12 and higher integrates the Red Hat Bugzilla - Oracle modifications, please donate your time to - supporting the Bugzilla project. + </blockquote> + If you, or someone you know, has the time and expertise to do the integration + work so main-tree Bugzilla 2.12 and higher integrates the Red + Hat Bugzilla Oracle modifications, please donate your + time to supporting the Bugzilla project. </para> </answer> </qandaentry> @@ -348,123 +324,102 @@ <emphasis>Dave Lawrence</emphasis>: <blockquote> <para> - 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. + 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. </para> <para> - I do want to land the changes that I have made to - Bugzilla but I may have to back out a good deal and - make a different version of Red Hat's Bugzilla for - checking in to CVS. Especially the cosmetic changes - because it seems they may not fit the general public. - I will do that as soon as I can. I also still do my - regular QA responsibilities along with Bugzilla so - time is difficult sometimes to come by. + I do want to land the changes that I have made to Bugzilla but I may + have to back out a good deal and make a different version of Red Hat's + Bugzilla for checking in to CVS. Especially the cosmetic changes because it + seems they may not fit the general public. I will do that as soon as I can. + I also still do my regular QA responsibilities along with Bugzilla so time + is difficult sometimes to come by. </para> <para> - There are also a good deal of other changes that were - requested by management for things like support - contracts and different permission groups for making - bugs private. Here is a short list of the major + There are also a good deal of other changes that were requested by + management for things like support contracts and different permission + groups for making bugs private. Here is a short list of the major changes that have been made: </para> <orderedlist> <listitem> <para> - No enum types. All old enum types are now separate - smaller tables. + No enum types. All old enum types are now separate smaller tables. </para> </listitem> <listitem> <para> - No bit wise operations. Not all databases support - this so they were changed to a more generic way of - doing this task + No bit wise operations. Not all databases support this so they were + changed to a more generic way of doing this task </para> </listitem> <listitem> <para> - Bug reports can only be altered by the reporter, - assignee, or a privileged bugzilla user. The rest - of the world can see the bug but in a - non-changeable format (unless the bug has been - marked private). They can however add comments, - add and remove themselves from the CC list + Bug reports can only be altered by the reporter, assignee, or a + privileged bugzilla user. The rest of the world can see the bug but in + a non-changeable format (unless the bug has been marked private). They + can however add comments, add and remove themselves from the CC list </para> </listitem> <listitem> <para> - Different group scheme. Each group has an id - number related to it. There is a user_group table - which contains userid to groupid mappings to - determine which groups each user belongs to. - Additionally there is a bug_group table that has - bugid to groupid mappings to show which groups can - see a particular bug. If there are no entries for - a bug in this table then the bug is public. + Different group scheme. Each group has an id number related to it. + There is a user_group table which contains userid to groupid mappings + to determine which groups each user belongs to. Additionally there is + a bug_group table that has bugid to groupid mappings to show which + groups can see a particular bug. If there are no entries for a bug in + this table then the bug is public. </para> </listitem> <listitem> <para> - Product groups. product_table created to only - allow certain products to be visible for certain - groups in both bug entry and query. This was + Product groups. product_table created to only allow certain products to + be visible for certain groups in both bug entry and query. This was particulary helpful for support contracts. </para> </listitem> <listitem> <para> - Of course many (too many) changes to Bugzilla code - itself to allow use with Oracle and still allow - operation with Mysql if so desired. Currently if - you use Mysql it is set to use Mysql's old - permission scheme to keep breakage to a minimum. - Hopefully one day this will standardize on one - style which may of course be something completely + Of course many (too many) changes to Bugzilla code itself to allow use + with Oracle and still allow operation with Mysql if so desired. + Currently if you use Mysql it is set to use Mysql's old permission + scheme to keep breakage to a minimum. Hopefully one day this will + standardize on one style which may of course be something completely different. </para> </listitem> <listitem> <para> - Uses Text::Template perl module for rendering of - the dynamic HTML pages such as enter_bug.cgi, - query.cgi, bug_form.pl, and for the header and - footer parts of the page. This allows the html to - be separate from the perl code for customizing the - look and feel of the page to one's preference. + Uses Text::Template perl module for rendering of the dynamic HTML pages + such as enter_bug.cgi, query.cgi, bug_form.pl, and for the header and + footer parts of the page. This allows the html to be separate from the + perl code for customizing the look and feel of the page to one's + preference. </para> </listitem> <listitem> <para> - There are many other smaller changes. There is - also a port to Oracle that I have been working on - as time permits but is not completely finished but - somewhat usable. I will merge it into our standard - code base when it becomes production quality. - Unfortunately there will have to be some - conditionals in the code to make it work with - other than Oracle due to some differences between - Oracle and Mysql. + There are many other smaller changes. There is also a port to Oracle + that I have been working on as time permits but is not completely + finished but somewhat usable. I will merge it into our standard code + base when it becomes production quality. Unfortunately there will have + to be some conditionals in the code to make it work with other than + Oracle due to some differences between Oracle and Mysql. </para> </listitem> </orderedlist> <para> - Both the Mysql and Oracle versions of our current code - base are available from ftp://people.redhat.com/dkl. - If Terry/Tara wants I can submit patch files for all - of the changes I have made and he can determine what - is suitable for addition to the main bugzilla cade - base. But for me to commit changes to the actual CVS I - will need to back out alot of things that are not - suitable for the rest of the Bugzilla community. I am - open to suggestions. + Both the Mysql and Oracle versions of our current code base are + available from ftp://people.redhat.com/dkl. If Terry/Tara wants I can submit + patch files for all of the changes I have made and he can determine what is + suitable for addition to the main bugzilla cade base. But for me to commit + changes to the actual CVS I will need to back out alot of things that are + not suitable for the rest of the Bugzilla community. I am open to + suggestions. </para> </blockquote> </para> @@ -482,66 +437,57 @@ <note> <para> This information is somewhat dated; I last updated it - 7 June 2000. Please see the "Variants" section of - "The Bugzilla Guide" for more up-to-date information - regarding Red Hat Bugzilla. + 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>: + </note> + <emphasis>Dave Lawrence</emphasis>: <blockquote> <para> - I suppose the current thread warrants an update - on the status of Oracle and bugzilla ;) We have now - been running Bugzilla 2.8 on Oracle for the last two - days in our production environment. I tried to do as - much testing as possible with it before going live - which is some of the reason for the long delay. I did - not get enough feedback as I would have liked from - internal developers to help weed out any bugs still - left so I said "Fine, i will take it live and then I - will get the feedback I want :)" So it is now starting - to stabilize and it running quite well after working - feverishly the last two days fixing problems as soon - as they came in from the outside world. The current - branch in cvs is up2date if anyone would like to grab - it and try it out. The oracle _setup.pl is broken - right now due to some last minute changes but I will - update that soon. Therefore you would probably need to - create the database tables the old fashioned way using - the supplied sql creation scripts located in the - ./oracle directory. We have heavy optimizations in the - database it self thanks to the in-house DBA here at - Red Hat so it is running quite fast. The database - itself is located on a dual PII450 with 1GB ram and 14 - high voltage differential raided scsi drives. The - tables and indexes are partitioned in 4 chuncks across - the raided drive which is nice because when ever you - need to do a full table scan, it is actually starting - in 4 different locations on 4 different drives - simultaneously. And the indexes of course are on - separate drives from the data so that speeds things up - tremendously. When I can find the time I will - document all that we have done to get this thing going - to help others that may need it. + I suppose the current thread warrants an update on the status of + Oracle and bugzilla ;) We have now been running Bugzilla 2.8 on + Oracle for the last two days in our production environment. I + tried to do as much testing as possible with it before going live + which is some of the reason for the long delay. I did not get + enough feedback as I would have liked from internal developers to + help weed out any bugs still left so I said "Fine, i will take it + live and then I will get the feedback I want :)" So it is now + starting to stabilize and it running quite well after working + feverishly the last two days fixing problems as soon as they came + in from the outside world. The current branch in cvs is up2date if + anyone would like to grab it and try it out. The oracle _setup.pl + is broken right now due to some last minute changes but I will + update that soon. Therefore you would probably need to create the + database tables the old fashioned way using the supplied sql + creation scripts located in the ./oracle directory. We have heavy + optimizations in the database it self thanks to the in-house DBA + here at Red Hat so it is running quite fast. The database itself + is located on a dual PII450 with 1GB ram and 14 high voltage + differential raided scsi drives. The tables and indexes are + partitioned in 4 chuncks across the raided drive which is nice + because when ever you need to do a full table scan, it is actually + starting in 4 different locations on 4 different drives + simultaneously. And the indexes of course are on separate drives + from the data so that speeds things up tremendously. When I can + find the time I will document all that we have done to get this + 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 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 appreciated. What - we are using now is what I call a best first effort. - It definitely can be improved on and may even need - complete rewrites in a lot of areas. A lot of changes - may have to be made in the way Bugzilla does things - currently to make this transition to a more generic - database interface. Fortunately when making the - Oracle changes I made sure I didn't do anything that - I would consider Oracle specific and could not be - easily done with other databases. Alot of the sql - statements need to be broken up into smaller utilities - that themselves would need to make decisions on what - database they are using but the majority of the code - can be made database neutral. + 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 + appreciated. What we are using now is what I call a best first + effort. It definitely can be improved on and may even need + complete rewrites in a lot of areas. A lot of changes may have to + be made in the way Bugzilla does things currently to make this + transition to a more generic database interface. Fortunately when + making the Oracle changes I made sure I didn't do anything that I + would consider Oracle specific and could not be easily done with + other databases. Alot of the sql statements need to be broken up + into smaller utilities that themselves would need to make + decisions on what database they are using but the majority of the + code can be made database neutral. </para> </blockquote> </para> @@ -552,78 +498,21 @@ <qandadiv id="faq_loki"> <title>Loki Bugzilla (AKA Fenris)</title> - <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> - <para> - What about Loki Bugzilla? - </para> - </question> - <answer> - <para> - Loki Games has a customized version of Bugzilla available - at http://fenris.lokigames.com. From that page, - <blockquote> - <para> - You may have noticed that Fenris is a fork from - Bugzilla-- our patches weren't suitable for - integration --and a few people have expressed interest - in the code. Fenris has one major improvement over - Bugzilla, and that is individual comments are not - appended onto a string blob, they are stored as a - record in a separate table. This allows you to, for - instance, separate comments out according to privilege - levels in case your bug database could contain - sensitive information not for public eyes. We also - provide things like email hiding to protect user's - privacy, additional fields such as 'user_affected' in - case someone enters someone else's bug, comment - editing and deletion, and more conditional system - variables than Bugzilla does (turn off attachments, - qacontact, etc.). - </para> - </blockquote> - </para> - </answer> - </qandaentry> <qandaentry> <question> <para> - Who maintains Fenris (Loki Bugzilla) now? + What is Loki Bugzilla (Fenris)? </para> </question> <answer> <para> - Raphael Barrerro <raistlin@lokigames.com>. Michael - Vance created the initial fork, but no longer maintains - the project. + Loki Games has a customized version of Bugzilla available at + <ulink url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. There are some advantages to using Fenris, chief being separation of comments based upon user privacy level, data hiding, forced login for any data retrieval, and some additional fields. Loki has mainted their code, originally a fork from the Bugzilla 2.8 code base, and it is quite a bit different than stock Bugzilla at this point. I recommend you stick with official Bugzilla version &bz-ver; rather than using a fork, but it's up to you. </para> </answer> </qandaentry> - <qandaentry> - <question> - <para> - - </para> - </question> - </qandaentry> </qandadiv> <qandadiv id="faq_phb"> @@ -631,9 +520,8 @@ <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 - :) + 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> @@ -641,15 +529,14 @@ <qandaentry> <question> <para> - Is Bugzilla web-based or do you have to have specific - software or specific operating system on your machine? + Is Bugzilla web-based or do you have to have specific software or + specific operating system on your machine? </para> </question> <answer> <para> - It is web and e-mail based. You can edit bugs by sending - specially formatted email to a properly configured - Bugzilla, or control via the web. + It is web and e-mail based. You can edit bugs by sending specially + formatted email to a properly configured Bugzilla, or control via the web. </para> </answer> </qandaentry> @@ -657,18 +544,14 @@ <qandaentry> <question> <para> - Has anyone you know of already done any Bugzilla - integration with Perforce (SCM software)? + Has anyone you know of already done any Bugzilla integration with + Perforce (SCM software)? </para> </question> <answer> <para> - Yes! You can find more information elsewhere in "The - Bugzilla Guide" in the "Integration with Third-Party - Products" section. The section on Perforce isn't very - large, but as the maintainer of the Guide is charged with - Perforce/Bugzilla integration by his company, you can - expect this section to grow. + Yes! You can find more information elsewhere in "The Bugzilla + Guide" in the "Integration with Third-Party Products" section. </para> </answer> </qandaentry> @@ -684,8 +567,8 @@ Absolutely! You can track up to a "soft-limit" of around 64 individual "Products", that can each be composed of as many "Components" as you want. Check the Administration - section of the Bugzilla Guide for more information - regarding setting up Products and Components. + section of the Bugzilla Guide for more information regarding + setting up Products and Components. </para> </answer> </qandaentry> @@ -693,9 +576,8 @@ <qandaentry> <question> <para> - If I am on many projects, and search for all bugs assigned - to me, will Bugzilla list them for me and allow me to sort - by project, severity etc? + If I am on many projects, and search for all bugs assigned to me, will + Bugzilla list them for me and allow me to sort by project, severity etc? </para> </question> <answer> @@ -708,20 +590,18 @@ <qandaentry> <question> <para> - Does Bugzilla allow attachments (text, screenshots, urls - etc)? If yes, are there any that are NOT allowed? + Does Bugzilla allow attachments (text, screenshots, urls etc)? If yes, + are there any that are NOT allowed? </para> </question> <answer> <para> - Yes. There are many specific MIME-types that are - pre-defined by Bugzilla, but you may specify any arbitrary - MIME-type you need when you upload the file. Since all - attachments are stored in the database, however, I - recommend storing large binary attachments elsewhere in - the web server's file system and providing a hyperlink as - a comment, or in the provided "URL" field in the bug - report. + Yes. There are many specific MIME-types that are pre-defined by Bugzilla, + but you may specify any arbitrary MIME-type you need when you + upload the file. Since all attachments are stored in the database, + however, I recommend storing large binary attachments elsewhere + in the web server's file system and providing a hyperlink + as a comment, or in the provided "URL" field in the bug report. </para> </answer> </qandaentry> @@ -729,17 +609,16 @@ <qandaentry> <question> <para> - Does Bugzilla allow us to define our own priorities and - levels? Do we have complete freedom to change the labels - of fields and format of them, and the choice of acceptable - values? + Does Bugzilla allow us to define our own priorities and levels? Do we + have complete freedom to change the labels of fields and format of them, and + the choice of acceptable values? </para> </question> <answer> <para> - Yes. However, modifying some fields, notably those - related to bug progression states, also require adjusting - the program logic to compensate for the change. + Yes. However, modifying some fields, notably those related to bug + progression states, also require adjusting the program logic to + compensate for the change. </para> </answer> </qandaentry> @@ -748,65 +627,70 @@ <qandaentry> <question> <para> - The index.html page doesn't show the footer. It's really - annoying to have to go to the querypage just to check my - "my bugs" link. How do I get a footer on static HTML - pages? + The index.html page doesn't show the footer. It's really annoying to have + to go to the querypage just to check my "my bugs" link. How do I get a footer + on static HTML pages? </para> </question> <answer> <para> - This was a late-breaking question for the Guide, so I just - have to quote the relevant newsgroup thread on it. + This was a late-breaking question for the Guide, so I just have to + quote the relevant newsgroup thread on it. </para> <literallayout> -> AFAIK, most sites (even if they have SSI enabled) won't have #exec - cmd > enabled. Perhaps what would be better is a #include - virtual and a > footer.cgi the basically has the "require - 'CGI.pl' and PutFooter command. > > Please note that under - most configurations, this also requires naming > the file - from index.html to index.shtml (and making sure that it - will > still be reconized as an index). Personally, I - think this is better on > a per-installation basis - (perhaps add something to the FAQ that says how > to do - this). Good point. Yeah, easy enough to do, that it - shouldn't be a big deal for someone to take it on if they - want it. FAQ is a good place for it. > Dave Miller wrote: - > >> I did a little experimenting with getting the command - menu and footer on >> the end of the index page while - leaving it as an HTML file... >> >> I was successful. :) - >> >> I added this line: >> >> <!--#exec - cmd="/usr/bin/perl -e "require 'CGI.pl'; - >>PutFooter();"" --> >> >> Just before the - </BODY> </HTML> at the end of the file. And - it worked. >> >> Thought I'd toss that out there. Should - I check this in? For those that >> have SSI disabled, - it'll act like a comment, so I wouldn't think it would >> - break anything. +> AFAIK, most sites (even if they have SSI enabled) won't have #exec cmd +> enabled. Perhaps what would be better is a #include virtual and a +> footer.cgi the basically has the "require 'CGI.pl' and PutFooter command. +> +> Please note that under most configurations, this also requires naming +> the file from index.html to index.shtml (and making sure that it will +> still be reconized as an index). Personally, I think this is better on +> a per-installation basis (perhaps add something to the FAQ that says how +> to do this). + +Good point. Yeah, easy enough to do, that it shouldn't be a big deal for +someone to take it on if they want it. FAQ is a good place for it. + +> Dave Miller wrote: +> +>> I did a little experimenting with getting the command menu and footer on +>> the end of the index page while leaving it as an HTML file... +>> +>> I was successful. :) +>> +>> I added this line: +>> +>> <!--#exec cmd="/usr/bin/perl -e "require 'CGI.pl'; +>>PutFooter();"" --> +>> +>> Just before the </BODY> </HTML> at the end of the file. And it worked. +>> +>> Thought I'd toss that out there. Should I check this in? For those that +>> have SSI disabled, it'll act like a comment, so I wouldn't think it would +>> break anything. </literallayout> </answer> </qandaentry> <qandaentry> <question> <para> - Does Bugzilla provide any reporting features, metrics, - graphs, etc? You know, the type of stuff that management - likes to see. :) + Does Bugzilla provide any reporting features, metrics, graphs, etc? You + know, the type of stuff that management likes to see. :) </para> </question> <answer> <para> - Yes. Look at <ulink - url="http://bugzilla.mozilla.org/reports.cgi"> http://bugzilla.mozilla.org/reports.cgi</ulink> for basic reporting facilities. + Yes. Look at <ulink url="http://bugzilla.mozilla.org/reports.cgi"> + http://bugzilla.mozilla.org/reports.cgi</ulink> for basic reporting + facilities. </para> <para> - For more advanced reporting, I recommend hooking up a - professional reporting package, such as Crystal Reports, - and use ODBC to access the MySQL database. You can do a - lot through the Query page of Bugzilla as well, but right - now Advanced Reporting is much better accomplished through - third-party utilities that can interface with the database - directly. + For more advanced reporting, I recommend hooking up a professional + reporting package, such as Crystal Reports, and use ODBC to access + the MySQL database. You can do a lot through the Query page of + Bugzilla as well, but right now Advanced Reporting is much + better accomplished through third-party utilities that can + interface with the database directly. </para> <para> Advanced Reporting is a Bugzilla 3.X proposed feature. @@ -817,16 +701,15 @@ <qandaentry> <question> <para> - Is there email notification and if so, what do you see - when you get an email? Do you see bug number and title or - is it only the number? + Is there email notification and if so, what do you see when you get an + email? Do you see bug number and title or is it only the number? </para> </question> <answer> <para> - Email notification is user-configurable. The bug id and - Topic of the bug report accompany each email notification, - along with a list of the changes made. + Email notification is user-configurable. The bug id and Topic + of the bug report accompany each email notification, along with + a list of the changes made. </para> </answer> </qandaentry> @@ -848,24 +731,22 @@ <qandaentry> <question> <para> - If there is email notification, do users have to have any - particular type of email application? + If there is email notification, do users have to have any particular + type of email application? </para> </question> <answer> <para> - Bugzilla email is sent in plain text, the most compatible - mail format on the planet. + Bugzilla email is sent in plain text, the most compatible mail format + on the planet. <note> <para> - If you decide to use the bugzilla_email integration - features to allow Bugzilla to record responses to mail - with the associated bug, you may need to caution your - users to set their mailer to "respond to messages in - the format in which they were sent". For security - reasons Bugzilla ignores HTML tags in comments, and if - a user sends HTML-based email into Bugzilla the - resulting comment looks downright awful. + If you decide to use the bugzilla_email integration features + to allow Bugzilla to record responses to mail with the associated bug, + you may need to caution your users to set their mailer to "respond + to messages in the format in which they were sent". For security reasons + Bugzilla ignores HTML tags in comments, and if a user sends HTML-based + email into Bugzilla the resulting comment looks downright awful. </para> </note> </para> @@ -875,19 +756,17 @@ <qandaentry> <question> <para> - If I just wanted to track certain bugs, as they go - through life, can I set it up to alert me via email - whenever that bug changes, whether it be owner, status or - description etc.? + If I just wanted to track certain bugs, as they go through life, can I + set it up to alert me via email whenever that bug changes, whether it be + owner, status or description etc.? </para> </question> <answer> <para> - Yes. Place yourself in the "cc" field of the bug you wish - to monitor. Then change your "Notify me of changes to" - field in the Email Settings tab of the User Preferences - screen in Bugzilla to the "Only those bugs which I am - listed on the CC line" option. + Yes. Place yourself in the "cc" field of the bug you wish to monitor. + Then change your "Notify me of changes to" field in the Email Settings + tab of the User Preferences screen in Bugzilla to the "Only those + bugs which I am listed on the CC line" option. </para> </answer> </qandaentry> @@ -895,34 +774,32 @@ <qandaentry> <question> <para> - Does Bugzilla allow data to be imported and exported? If I - had outsiders write up a bug report using a MS Word bug - template, could that template be imported into "matching" - fields? If I wanted to take the results of a query and - export that data to MS Excel, could I do that? + Does Bugzilla allow data to be imported and exported? If I had outsiders + write up a bug report using a MS Word bug template, could that template be + imported into "matching" fields? If I wanted to take the results of a query + and export that data to MS Excel, could I do that? </para> </question> <answer> <para> - Mozilla allows data export through a custom DTD in XML - format. It does not, however, export to specific formats - other than the XML Mozilla DTD. Importing the data into - Excel or any other application is left as an exercise for - the reader. + Mozilla allows data export through a custom DTD in XML format. + It does not, however, export to specific formats other than the + XML Mozilla DTD. Importing the data into Excel or any other application + is left as an exercise for the reader. </para> <para> - If you create import filters to other applications from - Mozilla's XML, please submit your modifications for - inclusion in future Bugzilla distributions. + If you create import filters to other applications from Mozilla's XML, + please submit your modifications for inclusion in future Bugzilla + distributions. </para> <para> - As for data import, any application can send data to - Bugzilla through the HTTP protocol, or through Mozilla's - XML API. However, it seems kind of silly to put another - front-end in front of Bugzilla; it makes more sense to - create a simplified bug submission form in HTML. You can - find an excellent example at <ulink - url="http://www.mozilla.org/quality/help/bugzilla-helper.html"> http://www.mozilla.org/quality/help/bugzilla-helper.html</ulink> + As for data import, any application can send data to Bugzilla through + the HTTP protocol, or through Mozilla's XML API. However, it seems + kind of silly to put another front-end in front of Bugzilla; + it makes more sense to create a simplified bug submission form in + HTML. You can find an excellent example at + <ulink url="http://www.mozilla.org/quality/help/bugzilla-helper.html"> + http://www.mozilla.org/quality/help/bugzilla-helper.html</ulink> </para> </answer> </qandaentry> @@ -930,9 +807,9 @@ <qandaentry> <question> <para> - Does Bugzilla allow fields to be added, changed or - deleted? If I want to customize the bug submission form to - meet our needs, can I do that using our terminology? + Does Bugzilla allow fields to be added, changed or deleted? If I want to + customize the bug submission form to meet our needs, can I do that using our + terminology? </para> </question> <answer> @@ -945,16 +822,16 @@ <qandaentry> <question> <para> - Has anyone converted Bugzilla to another language to be - used in other countries? Is it localizable? + Has anyone converted Bugzilla to another language to be used in other + countries? Is it localizable? </para> </question> <answer> <para> - Currently, no. Internationalization support for Perl did - not exist in a robust fashion until the recent release of - version 5.6.0; Bugzilla is, and likely will remain (until - 3.X) completely non-localized. + Currently, no. Internationalization support for Perl did not + exist in a robust fashion until the recent release of version 5.6.0; + Bugzilla is, and likely will remain (until 3.X) completely + non-localized. </para> </answer> </qandaentry> @@ -962,8 +839,8 @@ <qandaentry> <question> <para> - Can a user create and save reports? Can they do this in - Word format? Excel format? + Can a user create and save reports? Can they do this in Word format? + Excel format? </para> </question> <answer> @@ -989,15 +866,13 @@ <qandaentry> <question> <para> - Can a user modify an existing report and then save it into - another name? + Can a user modify an existing report and then save it into another name? </para> </question> <answer> <para> - You can save an unlimited number of queries in Bugzilla. - You are free to modify them and rename them to your - heart's desire. + You can save an unlimited number of queries in Bugzilla. You are free + to modify them and rename them to your heart's desire. </para> </answer> </qandaentry> @@ -1005,15 +880,14 @@ <qandaentry> <question> <para> - Does Bugzilla have the ability to search by word, phrase, - compound search? + Does Bugzilla have the ability to search by word, phrase, compound + search? </para> </question> <answer> <para> - You have no idea. Bugzilla's query interface, - particularly with the advanced Boolean operators, is - incredibly versatile. + You have no idea. Bugzilla's query interface, particularly with the + advanced Boolean operators, is incredibly versatile. </para> </answer> </qandaentry> @@ -1021,8 +895,8 @@ <qandaentry> <question> <para> - Can the admin person establish separate group and - individual user privileges? + Can the admin person establish separate group and individual user + privileges? </para> </question> <answer> @@ -1035,17 +909,15 @@ <qandaentry> <question> <para> - Does Bugzilla provide record locking when there is - simultaneous access to the same bug? Does the second - person get a notice that the bug is in use or how are they - notified? + Does Bugzilla provide record locking when there is simultaneous access + to the same bug? Does the second person get a notice that the bug is in use + or how are they notified? </para> </question> <answer> <para> - Bugzilla does not lock records. It provides mid-air - collision detection, and offers the offending user a - choice of options to deal with the conflict. + Bugzilla does not lock records. It provides mid-air collision detection, + and offers the offending user a choice of options to deal with the conflict. </para> </answer> </qandaentry> @@ -1058,10 +930,10 @@ </question> <answer> <para> - MySQL, the database back-end for Bugzilla, allows - hot-backup of data. You can find strategies for dealing - with backup considerations at <ulink - url="http://www.mysql.com/doc/B/a/Backup.html"> http://www.mysql.com/doc/B/a/Backup.html</ulink> + MySQL, the database back-end for Bugzilla, allows hot-backup of data. + You can find strategies for dealing with backup considerations + at <ulink url="http://www.mysql.com/doc/B/a/Backup.html"> + http://www.mysql.com/doc/B/a/Backup.html</ulink> </para> </answer> </qandaentry> @@ -1074,8 +946,8 @@ </question> <answer> <para> - Yes. However, commits to the database must wait until the - tables are unlocked. Bugzilla databases are typically + Yes. However, commits to the database must wait + until the tables are unlocked. Bugzilla databases are typically very small, and backups routinely take less than a minute. </para> </answer> @@ -1084,33 +956,29 @@ <qandaentry> <question> <para> - What type of human resources are needed to be on staff to - install and maintain Bugzilla? Specifically, what type of - skills does the person need to have? I need to find out if - we were to go with Bugzilla, what types of individuals - would we need to hire and how much would that cost vs - buying an "Out-of-the-Box" solution. + What type of human resources are needed to be on staff to install and + maintain Bugzilla? Specifically, what type of skills does the person need to + have? I need to find out if we were to go with Bugzilla, what types of + individuals would we need to hire and how much would that cost vs buying an + "Out-of-the-Box" solution. </para> </question> <answer> <para> - If Bugzilla is set up correctly from the start, continuing - maintenance needs are minimal and can be completed by - unskilled labor. Things like rotate backup tapes and - check log files for the word "error". + If Bugzilla is set up correctly from the start, continuing maintenance needs + are minimal and can be completed by unskilled labor. Things like rotate + backup tapes and check log files for the word "error". </para> <para> - Commercial Bug-tracking software typically costs somewhere - upwards of $20,000 or more for 5-10 floating licenses. - Bugzilla consultation is available from skilled members of - the newsgroup. + Commercial Bug-tracking software typically costs somewhere upwards + of $20,000 or more for 5-10 floating licenses. Bugzilla consultation + is available from skilled members of the newsgroup. </para> <para> - As an example, as of this writing I typically charge $115 - for the first hour, and $89 each hour thereafter for - consulting work. It takes me three to five hours to make - Bugzilla happy on a Development installation of - Linux-Mandrake. + As an example, as of this writing I typically charge + $115 for the first hour, and $89 each hour thereafter + for consulting work. It takes me three to five hours to make Bugzilla + happy on a Development installation of Linux-Mandrake. </para> </answer> </qandaentry> @@ -1118,22 +986,20 @@ <qandaentry> <question> <para> - What time frame are we looking at if we decide to hire - people to install and maintain the Bugzilla? Is this - something that takes hours or weeks to install and a - couple of hours per week to maintain and customize or is - this a multi-week install process, plus a full time job - for 1 person, 2 people, etc? + What time frame are we looking at if we decide to hire people to install + and maintain the Bugzilla? Is this something that takes hours or weeks to + install and a couple of hours per week to maintain and customize or is this + a multi-week install process, plus a full time job for 1 person, 2 people, + etc? </para> </question> <answer> <para> - It all depends on your level of commitment. Someone with - much Bugzilla experience can get you up and running in - less than a day, and your Bugzilla install can run - untended for years. If your Bugzilla strategy is critical - to your business workflow, hire somebody with reasonable - UNIX or Perl skills to handle your process management and + It all depends on your level of commitment. Someone with much Bugzilla + experience can get you up and running in less than a day, and + your Bugzilla install can run untended for years. If your + Bugzilla strategy is critical to your business workflow, hire somebody + with reasonable UNIX or Perl skills to handle your process management and bug-tracking maintenance & customization. </para> </answer> @@ -1142,16 +1008,14 @@ <qandaentry> <question> <para> - Is there any licensing fee or other fees for using - Bugzilla? Any out-of-pocket cost other than the bodies - needed as identified above? + Is there any licensing fee or other fees for using Bugzilla? Any + out-of-pocket cost other than the bodies needed as identified above? </para> </question> <answer> <para> - No. MySQL asks, if you find their product valuable, that - you purchase a support contract from them that suits your - needs. + No. MySQL asks, if you find their product valuable, that you purchase + a support contract from them that suits your needs. </para> </answer> </qandaentry> @@ -1167,8 +1031,9 @@ </question> <answer> <para> - Check <ulink - url="http://www.mozilla.org/projects/bugzilla/"> http://www.mozilla.org/projects/bugzilla/</ulink> for details. Once you download it, untar it, read the Bugzilla Guide. + Check <ulink url="http://www.mozilla.org/projects/bugzilla/"> + http://www.mozilla.org/projects/bugzilla/</ulink> for details. + Once you download it, untar it, read the Bugzilla Guide. </para> </answer> </qandaentry> @@ -1181,8 +1046,8 @@ </question> <answer> <para> - Installation on Windows NT has its own section in "The - Bugzilla Guide". + Installation on Windows NT has its own section in + "The Bugzilla Guide". </para> </answer> </qandaentry> @@ -1208,19 +1073,16 @@ <qandaentry> <question> <para> - How do I completely disable MySQL security if it's giving - me problems (I've followed the instructions in the - installation section of this guide!)? + How do I completely disable MySQL security if it's giving me problems + (I've followed the instructions in the installation section of this guide!)? </para> </question> <answer> <para> - Run mysql like this: "mysqld --skip-grant-tables". Please - remember <emphasis>this makes mysql as secure as taping a - $100 to the floor of a football stadium bathroom for - safekeeping.</emphasis> Please read the Security - section of the Administration chapter of "The Bugzilla - Guide" before proceeding. + Run mysql like this: "mysqld --skip-grant-tables". Please remember <emphasis>this + makes mysql as secure as taping a $100 to the floor of a football stadium + bathroom for safekeeping.</emphasis> Please read the Security section of the + Administration chapter of "The Bugzilla Guide" before proceeding. </para> </answer> </qandaentry> @@ -1233,11 +1095,10 @@ </question> <answer> <para> - The Bugzilla code has not undergone a complete security - audit. It is recommended that you closely examine - permissions on your Bugzilla installation, and follow the - recommended security guidelines found in The Bugzilla - Guide. + The Bugzilla code has not undergone a complete security audit. + It is recommended that you closely examine permissions on your Bugzilla + installation, and follow the recommended security guidelines found + in The Bugzilla Guide. </para> </answer> </qandaentry> @@ -1246,17 +1107,16 @@ <qandaentry> <question> <para> - I've implemented the security fixes mentioned in Chris - Yeh's security advisory of 5/10/2000 advising not to run - MySQL as root, and am running into problems with MySQL no - longer working correctly. + I've implemented the security fixes mentioned in Chris Yeh's security + advisory of 5/10/2000 advising not to run MySQL as root, and am running into + problems with MySQL no longer working correctly. </para> </question> <answer> <para> - This is a common problem, related to running out of file - descriptors. Simply add "ulimit -n unlimited" to the - script which starts mysqld. + This is a common problem, related to running out of file descriptors. + Simply add "ulimit -n unlimited" to the script which starts + mysqld. </para> </answer> </qandaentry> @@ -1268,14 +1128,14 @@ <qandaentry> <question> <para> - I have a user who doesn't want to receive any more email - from Bugzilla. How do I stop it entirely for this user? + I have a user who doesn't want to receive any more email from Bugzilla. + How do I stop it entirely for this user? </para> </question> <answer> <para> - With the email changes to 2.12, the user should be able to - set this in user email preferences. + With the email changes to 2.12, the user should be able to set + this in user email preferences. </para> </answer> </qandaentry> @@ -1283,15 +1143,14 @@ <qandaentry> <question> <para> - I'm evaluating/testing Bugzilla, and don't want it to send - email to anyone but me. How do I do it? + I'm evaluating/testing Bugzilla, and don't want it to send email to + anyone but me. How do I do it? </para> </question> <answer> <para> - Edit the param for the mail text. Replace "To:" with - "X-Real-To:", replace "Cc:" with "X-Real-CC:", and add a - "To: (myemailaddress)". + Edit the param for the mail text. Replace "To:" with "X-Real-To:", + replace "Cc:" with "X-Real-CC:", and add a "To: (myemailaddress)". </para> </answer> </qandaentry> @@ -1299,15 +1158,17 @@ <qandaentry> <question> <para> - I want whineatnews.pl to whine at something more, or other - than, only new bugs. How do I do it? + I want whineatnews.pl to whine at something more, or other than, only new + bugs. How do I do it? </para> </question> <answer> <para> - Try Klaas Freitag's excellent patch for "whineatassigned" - functionality. You can find it at<ulink url=" - http://bugzilla.mozilla.org/show_bug.cgi?id=6679"> http://bugzilla.mozilla.org/show_bug.cgi?id=6679</ulink>. This patch is against an older version of Bugzilla, so you must apply the diffs manually. + Try Klaas Freitag's excellent patch for "whineatassigned" functionality. + You can find it at<ulink url=" http://bugzilla.mozilla.org/show_bug.cgi?id=6679"> + http://bugzilla.mozilla.org/show_bug.cgi?id=6679</ulink>. This + patch is against an older version of Bugzilla, so you must apply + the diffs manually. </para> </answer> </qandaentry> @@ -1315,23 +1176,22 @@ <qandaentry> <question> <para> - I don't like/want to use Procmail to hand mail off to - bug_email.pl. What alternatives do I have? + I don't like/want to use Procmail to hand mail off to bug_email.pl. + What alternatives do I have? </para> </question> <answer> <para> - You can call bug_email.pl directly from your aliases file, - with an entry like this: + You can call bug_email.pl directly from your aliases file, with + an entry like this: <blockquote> <para> - bugzilla-daemon: - "|/usr/local/bin/bugzilla/contrib/bug_email.pl" + bugzilla-daemon: "|/usr/local/bin/bugzilla/contrib/bug_email.pl" </para> - </blockquote> However, this is fairly nasty and subject to - problems; you also need to set up your smrsh (sendmail - restricted shell) to allow it. In a pinch, though, it can - work. + </blockquote> + However, this is fairly nasty and subject to problems; you also + need to set up your smrsh (sendmail restricted shell) to allow + it. In a pinch, though, it can work. </para> </answer> </qandaentry> @@ -1339,15 +1199,13 @@ <qandaentry> <question> <para> - How do I set up the email interface to submit/change bugs - via email? + How do I set up the email interface to submit/change bugs via email? </para> </question> <answer> <para> - You can find an updated README.mailif file in the contrib/ - directory of your Bugzilla distribution that walks you - through the setup. + You can find an updated README.mailif file in the contrib/ directory + of your Bugzilla distribution that walks you through the setup. </para> </answer> </qandaentry> @@ -1355,29 +1213,28 @@ <qandaentry> <question> <para> - Email takes FOREVER to reach me from bugzilla -- it's - extremely slow. What gives? + Email takes FOREVER to reach me from bugzilla -- it's extremely slow. + What gives? </para> </question> <answer> <para> - If you are using an alternate Mail Transport Agent (MTA - other than sendmail), make sure the options given in the - "processmail" script for all instances of "sendmail" are - correct for your MTA. If you are using Sendmail, you may - wish to delete the "-ODeliveryMode=deferred" option in the - "processmail" script for every invocation of "sendmail". - (Be sure and leave the "-t" option, though!) + If you are using an alternate Mail Transport Agent (MTA other than + sendmail), make sure the options given in the "processmail" script for all + instances of "sendmail" are correct for your MTA. If you are using Sendmail, + you may wish to delete the "-ODeliveryMode=deferred" option in the + "processmail" script for every invocation of "sendmail". (Be sure and leave + the "-t" option, though!) </para> <para> A better alternative is to change the "-O" option to - "-ODeliveryMode=background". This prevents Sendmail from - hanging your Bugzilla Perl processes if the domain to - which it must send mail is unavailable. + "-ODeliveryMode=background". This prevents Sendmail from hanging your + Bugzilla Perl processes if the domain to which it must send mail + is unavailable. </para> <para> - This is now a configurable parameter called "sendmailnow", - available from editparams.cgi. + This is now a configurable parameter called "sendmailnow", available + from editparams.cgi. </para> </answer> </qandaentry> @@ -1390,16 +1247,15 @@ </question> <answer> <para> - Double-check that you have not turned off email in your - user preferences. Confirm that Bugzilla is able to send - email by visiting the "Log In" link of your Bugzilla - installation and clicking the "Email me a password" button - after entering your email address. + Double-check that you have not turned off email in your user preferences. + Confirm that Bugzilla is able to send email by visiting the "Log In" + link of your Bugzilla installation and clicking the "Email me a password" + button after entering your email address. </para> <para> - If you never receive mail from Bugzilla, chances you do - not have sendmail in "/usr/lib/sendmail". Ensure sendmail - lives in, or is symlinked to, "/usr/lib/sendmail". + If you never receive mail from Bugzilla, chances you do not have + sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked + to, "/usr/lib/sendmail". </para> </answer> </qandaentry> @@ -1416,11 +1272,10 @@ </question> <answer> <para> - Red Hat Bugzilla, mentioned above, works with Oracle. The - current version from Mozilla.org does not have this - capability. Unfortunately, though you will sacrifice a - lot of the really great features available in Bugzilla - 2.10 and 2.12 if you go with the 2.8-based Redhat version. + Red Hat Bugzilla, mentioned above, works with Oracle. The current version + from Mozilla.org does not have this capability. Unfortunately, though + you will sacrifice a lot of the really great features available in + Bugzilla 2.10 and 2.12 if you go with the 2.8-based Redhat version. </para> </answer> </qandaentry> @@ -1428,30 +1283,25 @@ <qandaentry> <question> <para> - Bugs are missing from queries, but exist in the database - (and I can pull them up by specifying the bug ID). What's - wrong? + Bugs are missing from queries, but exist in the database (and I can pull + them up by specifying the bug ID). What's wrong? </para> </question> <answer> <para> - You've almost certainly enabled the "shadow database", - but for some reason it hasn't been updated for all your - bugs. This is the database against which queries are run, - so that really complex or slow queries won't lock up - portions of the database for other users. You can turn off - the shadow database in editparams.cgi. If you wish to - continue using the shadow database, then as your "bugs" - user run "./syncshadowdb -syncall" from the command line - in the bugzilla installation directory to recreate your - shadow database. After it finishes, be sure to check the - params and make sure that "queryagainstshadowdb" is still - turned on. The syncshadowdb program turns it off if it was - on, and is supposed to turn it back on when completed; - that way, if it crashes in the middle of recreating the - database, it will stay off forever until someone turns it - back on by hand. Apparently, it doesn't always do that - yet. + You've almost certainly enabled the "shadow database", but for some + reason it hasn't been updated for all your bugs. This is the database + against which queries are run, so that really complex or slow queries won't + lock up portions of the database for other users. You can turn off the + shadow database in editparams.cgi. If you wish to continue using the shadow + database, then as your "bugs" user run "./syncshadowdb -syncall" from the + command line in the bugzilla installation directory to recreate your shadow + database. After it finishes, be sure to check the params and make sure that + "queryagainstshadowdb" is still turned on. The syncshadowdb program turns it + off if it was on, and is supposed to turn it back on when completed; that + way, if it crashes in the middle of recreating the database, it will stay + off forever until someone turns it back on by hand. Apparently, it doesn't + always do that yet. </para> </answer> </qandaentry> @@ -1459,20 +1309,18 @@ <qandaentry> <question> <para> - I think my database might be corrupted, or contain invalid - entries. What do I do? + I think my database might be corrupted, or contain invalid entries. What + do I do? </para> </question> <answer> <para> - Run the "sanity check" utility (./sanitycheck.cgi in the - bugzilla_home directory) to see! If it all comes back, - you're OK. If it doesn't come back OK (i.e. any red - letters), there are certain things Bugzilla can recover - from and certain things it can't. If it can't - auto-recover, I hope you're familiar with mysqladmin - commands or have installed another way to manage your - database... + Run the "sanity check" utility (./sanitycheck.cgi in the bugzilla_home + directory) to see! If it all comes back, you're OK. If it doesn't come back + OK (i.e. any red letters), there are certain things Bugzilla can recover + from and certain things it can't. If it can't auto-recover, I hope you're + familiar with mysqladmin commands or have installed another way to manage + your database... </para> </answer> </qandaentry> @@ -1485,14 +1333,12 @@ </question> <answer> <para> - There is no facility in Bugzilla itself to do this. It's - also generally not a smart thing to do if you don't know - exactly what you're doing. However, if you understand SQL - you can use the mysqladmin utility to manually insert, - delete, and modify table information. Personally, I use - "phpMyAdmin". You have to compile a PHP module with MySQL - support to make it work, but it's very clean and easy to - use. + There is no facility in Bugzilla itself to do this. It's also generally + not a smart thing to do if you don't know exactly what you're doing. + However, if you understand SQL you can use the mysqladmin utility to + manually insert, delete, and modify table information. Personally, I + use "phpMyAdmin". You have to compile a PHP module with MySQL + support to make it work, but it's very clean and easy to use. </para> </answer> </qandaentry> @@ -1500,17 +1346,14 @@ <qandaentry> <question> <para> - I try to add myself as a user, but Bugzilla always tells - me my password is wrong. + I try to add myself as a user, but Bugzilla always tells me my password is wrong. </para> </question> <answer> <para> - Certain version of MySQL (notably, 3.23.29 and 3.23.30) - accidentally disabled the "crypt()" function. This - prevented MySQL from storing encrypted passwords. Upgrade - to the "3.23 stable" version of MySQL and you should be - good to go. + Certain version of MySQL (notably, 3.23.29 and 3.23.30) accidentally disabled + the "crypt()" function. This prevented MySQL from storing encrypted passwords. + Upgrade to the "3.23 stable" version of MySQL and you should be good to go. </para> </answer> </qandaentry> @@ -1518,18 +1361,17 @@ <qandaentry> <question> <para> - I think I've set up MySQL permissions correctly, but - bugzilla still can't connect. + I think I've set up MySQL permissions correctly, but bugzilla still can't + connect. </para> </question> <answer> <para> - Try running MySQL from its binary: "mysqld - --skip-grant-tables". This will allow you to completely - rule out grant tables as the cause of your frustration. - However, I do not recommend you run it this way on a - regular basis, unless you really want your web site - defaced and your machine cracked. + Try running MySQL from its binary: "mysqld --skip-grant-tables". This + will allow you to completely rule out grant tables as the cause of your + frustration. However, I do not recommend you run it this way on a regular + basis, unless you really want your web site defaced and your machine + cracked. </para> </answer> </qandaentry> @@ -1537,28 +1379,26 @@ <qandaentry> <question> <para> - How do I synchronize bug information among multiple - different Bugzilla databases? + How do I synchronize bug information among multiple different Bugzilla + databases? </para> </question> <answer> <para> - Well, you can synchronize or you can move bugs. - Synchronization will only work one way -- you can create a - read-only copy of the database at one site, and have it - regularly updated at intervals from the main database. + Well, you can synchronize or you can move bugs. Synchronization will + only work one way -- you can create a read-only copy of the database + at one site, and have it regularly updated at intervals from the main + database. </para> <para> - MySQL has some synchronization features builtin to the - latest releases. It would be great if someone looked into - the possibilities there and provided a report to the - newsgroup on how to effectively synchronize two Bugzilla - installations. + MySQL has some synchronization features builtin to the latest releases. + It would be great if someone looked into the possibilities there + and provided a report to the newsgroup on how to effectively + synchronize two Bugzilla installations. </para> <para> - If you simply need to transfer bugs from one Bugzilla to - another, checkout the "move.pl" script in the Bugzilla - distribution. + If you simply need to transfer bugs from one Bugzilla to another, + checkout the "move.pl" script in the Bugzilla distribution. </para> </answer> </qandaentry> @@ -1566,16 +1406,15 @@ <qandaentry> <question> <para> - Why do I get bizarre errors when trying to submit data, - particularly problems with "groupset"? + Why do I get bizarre errors when trying to submit data, particularly problems + with "groupset"? </para> </question> <answer> <para> - If you're sure your MySQL parameters are correct, you - might want turn "strictvaluechecks" OFF in editparams.cgi. - If you have "usebugsentry" set "On", you also cannot - submit a bug as readable by more than one group with + If you're sure your MySQL parameters are correct, you might want turn + "strictvaluechecks" OFF in editparams.cgi. If you have "usebugsentry" set + "On", you also cannot submit a bug as readable by more than one group with "strictvaluechecks" ON. </para> </answer> @@ -1584,17 +1423,15 @@ <qandaentry> <question> <para> - How come even after I delete bugs, the long descriptions - show up? + How come even after I delete bugs, the long descriptions show up? </para> </question> <answer> <para> - Delete everything from $BUZILLA_HOME/shadow. Bugzilla - creates shadow files there, with each filename - corresponding to a bug number. Also be sure to run - syncshadowdb to make sure, if you are using a shadow - database, that the shadow database is current. + Delete everything from $BUZILLA_HOME/shadow. Bugzilla creates shadow + files there, with each filename corresponding to a + bug number. Also be sure to run syncshadowdb to make sure, if you are using + a shadow database, that the shadow database is current. </para> </answer> </qandaentry> @@ -1607,14 +1444,13 @@ <qandaentry> <question> <para> - What is the easiest way to run Bugzilla on Win32 - (Win98+/NT/2K)? + What is the easiest way to run Bugzilla on Win32 (Win98+/NT/2K)? </para> </question> <answer> <para> - Remove Windows. Install Linux. Install Bugzilla. The boss - will never know the difference. + Remove Windows. Install Linux. Install Bugzilla. + The boss will never know the difference. </para> </answer> </qandaentry> @@ -1627,10 +1463,9 @@ </question> <answer> <para> - Not currently. Bundle::Bugzilla enormously simplifies - Bugzilla installation on UNIX systems. If someone can - volunteer to create a suitable PPM bundle for Win32, it - would be appreciated. + Not currently. Bundle::Bugzilla enormously simplifies Bugzilla + installation on UNIX systems. If someone can volunteer to + create a suitable PPM bundle for Win32, it would be appreciated. </para> </answer> </qandaentry> @@ -1638,34 +1473,29 @@ <qandaentry> <question> <para> - CGI's are failing with a "something.cgi is not a valid - Windows NT application" error. Why? + CGI's are failing with a "something.cgi is not a valid Windows NT + application" error. Why? </para> </question> <answer> <para> - Depending on what Web server you are using, you will have - to configure the Web server to treat *.cgi files as CGI - scripts. In IIS, you do this by adding *.cgi to the App - Mappings with the <path>\perl.exe %s %s as the + Depending on what Web server you are using, you will have to configure + the Web server to treat *.cgi files as CGI scripts. In IIS, you do this by + adding *.cgi to the App Mappings with the <path>\perl.exe %s %s as the executable. </para> <para> Microsoft has some advice on this matter, as well: <blockquote> <para> - "Set application mappings. In the ISM, map the - extension for the script file(s) to the executable for - the script interpreter. For example, you might map the - extension .py to Python.exe, the executable for the - Python script interpreter. Note For the ActiveState - Perl script interpreter, the extension .pl is - associated with PerlIS.dll by default. If you want to - change the association of .pl to perl.exe, you need to - change the application mapping. In the mapping, you - must add two percent (%) characters to the end of the - pathname for perl.exe, as shown in this example: - c:\perl\bin\perl.exe %s %s" + "Set application mappings. In the ISM, map the extension for the script + file(s) to the executable for the script interpreter. For example, you might + map the extension .py to Python.exe, the executable for the Python script + interpreter. Note For the ActiveState Perl script interpreter, the extension + .pl is associated with PerlIS.dll by default. If you want to change the + association of .pl to perl.exe, you need to change the application mapping. + In the mapping, you must add two percent (%) characters to the end of the + pathname for perl.exe, as shown in this example: c:\perl\bin\perl.exe %s %s" </para> </blockquote> </para> @@ -1675,69 +1505,108 @@ <qandaentry> <question> <para> - Can I have some general instructions on how to make - Bugzilla on Win32 work? - </para> - </question> + Can I have some general instructions on how to make Bugzilla on Win32 work? + </para> + </question> <answer> <para> - The following couple entries are deprecated in favor of - the Windows installation instructions available in the - "Administration" portion of "The Bugzilla Guide". However, - they are provided here for historical interest and - insight. <literallayout> 1. #!C:/perl/bin/perl had to be - added to every perl file. 2. Converted to Net::SMTP to - handle mail messages instead of /usr/bin/sendmail. 3. - The crypt function isn't available on Windows NT (at - least none that I am aware), so I made encrypted - passwords = plaintext passwords. 4. The system call to - diff had to be changed to the Cygwin diff. 5. This was - just to get a demo running under NT, it seems to be - working good, and I have inserted almost 100 bugs from - another bug tracking system. Since this work was done - just to get an in-house demo, I am NOT planning on - making a patch for submission to Bugzilla. If you would - like a zip file, let me know. Q: Hmm, couldn't figure it - out from the general instructions above. How about - step-by-step? A: Sure! Here ya go! 1. Install IIS 4.0 - from the NT Option Pack #4. 2. Download and install - Active Perl. 3. Install the Windows GNU tools from - Cygwin. Make sure to add the bin directory to your - system path. (Everyone should have these, whether they - decide to use Bugzilla or not. :-) ) 4. Download - relevant packages from ActiveState at - http://www.activestate.com/packages/zips/. + - DBD-Mysql.zip 5. Extract each zip file with WinZip, and - install each ppd file using the notation: ppm install - <module>.ppd 6. Install Mysql. *Note: If you move - the default install from c:\mysql, you must add the - appropriate startup parameters to the NT service. (ex. - -b e:\\programs\\mysql) 7. Download any Mysql client. - http://www.mysql.com/download_win.html 8. Setup MySql. - (These are the commands that I used.) I. Cleanup default - database settings. C:\mysql\bin\mysql -u root mysql - mysql> DELETE FROM user WHERE Host='localhost' AND - User=''; mysql> quit C:\mysql\bin\mysqladmin reload II. - Set password for root. C:\mysql\bin\mysql -u root mysql - mysql> UPDATE user SET Password=PASSWORD('new_password') - WHERE user='root'; mysql> FLUSH PRIVILEGES; mysql> quit - C:\mysql\bin\mysqladmin -u root reload III. Create bugs - user. C:\mysql\bin\mysql -u root -p mysql> insert into - user (host,user,password) values('localhost','bugs',''); - mysql> quit C:\mysql\bin\mysqladmin -u root reload IV. - Create the bugs database. C:\mysql\bin\mysql -u root -p - mysql> create database bugs; V. Give the bugs user - access to the bugs database. mysql> insert into db - (host,db,user,select_priv,insert_priv,update_priv,delete_priv,create_priv,drop_priv) values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N') mysql> quit C:\mysql\bin\mysqladmin -u root reload 9. Run the table scripts to setup the bugs database. 10. Change CGI.pm to use the following regular expression because of differing backslashes in NT versus UNIX. o $0 =~ m:[^\\]*$:; 11. Had to make the crypt password = plain text password in the database. (Thanks to Andrew Lahser" <andrew_lahser@merck.com>" on this one.) The files that I changed were: o globals.pl o CGI.pl o alternately, you can try commenting all references to 'crypt' string and replace them with similar lines but without encrypt() or crypr() functions insida all files. 12. Replaced sendmail with Windmail. Basically, you have to come up with a sendmail substitute for NT. Someone said that they used a Perl module (Net::SMTP), but I was trying to save time and do as little Perl coding as possible. 13. Added "perl" to the beginning of all Perl system calls that use a perl script as an argument and renamed processmail to processmail.pl. 14. In processmail.pl, I added binmode(HANDLE) before all read() calls. I'm not sure about this one, but the read() under NT wasn't counting the EOLs without the binary read." </literallayout> + The following couple entries are deprecated in favor of the Windows installation + instructions available in the "Administration" portion of "The Bugzilla Guide". + However, they are provided here for historical interest and insight. + <literallayout> + 1. #!C:/perl/bin/perl had to be added to every perl file. + 2. Converted to Net::SMTP to handle mail messages instead of + /usr/bin/sendmail. + 3. The crypt function isn't available on Windows NT (at least none that I + am aware), so I made encrypted passwords = plaintext passwords. + 4. The system call to diff had to be changed to the Cygwin diff. + 5. This was just to get a demo running under NT, it seems to be working + good, and I have inserted almost 100 bugs from another bug tracking + system. Since this work was done just to get an in-house demo, I am NOT + planning on making a patch for submission to Bugzilla. If you would + like a zip file, let me know. + +Q: Hmm, couldn't figure it out from the general instructions above. How +about step-by-step? +A: Sure! Here ya go! + + 1. Install IIS 4.0 from the NT Option Pack #4. + 2. Download and install Active Perl. + 3. Install the Windows GNU tools from Cygwin. Make sure to add the bin + directory to your system path. (Everyone should have these, whether + they decide to use Bugzilla or not. :-) ) + 4. Download relevant packages from ActiveState at + http://www.activestate.com/packages/zips/. + DBD-Mysql.zip + 5. Extract each zip file with WinZip, and install each ppd file using the + notation: ppm install <module>.ppd + 6. Install Mysql. *Note: If you move the default install from c:\mysql, + you must add the appropriate startup parameters to the NT service. (ex. + -b e:\\programs\\mysql) + 7. Download any Mysql client. http://www.mysql.com/download_win.html + 8. Setup MySql. (These are the commands that I used.) + + I. Cleanup default database settings. + C:\mysql\bin\mysql -u root mysql + mysql> DELETE FROM user WHERE Host='localhost' AND User=''; + mysql> quit + C:\mysql\bin\mysqladmin reload + + II. Set password for root. + C:\mysql\bin\mysql -u root mysql + mysql> UPDATE user SET Password=PASSWORD('new_password') + WHERE user='root'; + mysql> FLUSH PRIVILEGES; + mysql> quit + C:\mysql\bin\mysqladmin -u root reload + + III. Create bugs user. + C:\mysql\bin\mysql -u root -p + mysql> insert into user (host,user,password) + values('localhost','bugs',''); + mysql> quit + C:\mysql\bin\mysqladmin -u root reload + + IV. Create the bugs database. + C:\mysql\bin\mysql -u root -p + mysql> create database bugs; + + V. Give the bugs user access to the bugs database. + mysql> insert into db + (host,db,user,select_priv,insert_priv,update_priv,delete_priv,create_priv,drop_priv) + values('localhost','bugs','bugs','Y','Y','Y','Y','Y','N') + mysql> quit + C:\mysql\bin\mysqladmin -u root reload + 9. Run the table scripts to setup the bugs database. + 10. Change CGI.pm to use the following regular expression because of + differing backslashes in NT versus UNIX. + o $0 =~ m:[^\\]*$:; + 11. Had to make the crypt password = plain text password in the database. + (Thanks to Andrew Lahser" <andrew_lahser@merck.com>" on this one.) The + files that I changed were: + o globals.pl + o CGI.pl + o alternately, you can try commenting all references to 'crypt' + string and replace them with similar lines but without encrypt() + or crypr() functions insida all files. + 12. Replaced sendmail with Windmail. Basically, you have to come up with a + sendmail substitute for NT. Someone said that they used a Perl module + (Net::SMTP), but I was trying to save time and do as little Perl coding + as possible. + 13. Added "perl" to the beginning of all Perl system calls that use a perl + script as an argument and renamed processmail to processmail.pl. + 14. In processmail.pl, I added binmode(HANDLE) before all read() calls. I'm + not sure about this one, but the read() under NT wasn't counting the + EOLs without the binary read." + </literallayout> </para> </answer> </qandaentry> - - <qandaentry> - <question> - <para> - I'm having trouble with the perl modules for NT not being - able to talk to to the database. + + <qandaentry> + <question> + <para> + I'm having trouble with the perl modules for NT not being able to talk to + to the database. </para> </question> <answer> @@ -1766,14 +1635,14 @@ </listitem> <listitem> <para> - <prompt>PPM></prompt> <command>install DBI DBD-mysql - GD</command> + <prompt>PPM></prompt> <command>install DBI DBD-mysql GD</command> </para> </listitem> - </orderedlist> I reckon TimeDate and Data::Dumper come - with the activeperl. You can check the ActiveState site - for packages for installation through PPM. <ulink url=" - http://www.activestate.com/Packages/"> http://www.activestate.com/Packages/</ulink> + </orderedlist> + I reckon TimeDate and Data::Dumper come with the activeperl. You can check + the ActiveState site for packages for installation through PPM. + <ulink url=" http://www.activestate.com/Packages/"> + http://www.activestate.com/Packages/</ulink> </para> </answer> </qandaentry> @@ -1786,15 +1655,15 @@ <qandaentry> <question> <para> - The query page is very confusing. Isn't there a simpler - way to query? + The query page is very confusing. Isn't there a simpler way to query? </para> </question> <answer> <para> - We are developing in that direction. You can follow - progress on this at <ulink - url="http://bugzilla.mozilla.org/show_bug.cgi?id=16775"> http://bugzilla.mozilla.org/show_bug.cgi?id=16775</ulink>. Some functionality is available in Bugzilla 2.12, and is available as "quicksearch.html" + We are developing in that direction. You can follow progress on this + at <ulink url="http://bugzilla.mozilla.org/show_bug.cgi?id=16775"> + http://bugzilla.mozilla.org/show_bug.cgi?id=16775</ulink>. Some functionality + is available in Bugzilla 2.12, and is available as "quicksearch.html" </para> </answer> </qandaentry> @@ -1802,24 +1671,23 @@ <qandaentry> <question> <para> - I'm confused by the behavior of the "accept" button in the - Show Bug form. Why doesn't it assign the bug to me when I - accept it? + I'm confused by the behavior of the "accept" button in the Show Bug form. + Why doesn't it assign the bug to me when I accept it? </para> </question> <answer> <para> - The current behavior is acceptable to bugzilla.mozilla.org - and most users. I personally don't like it. You have - your choice of patches to change this behavior, however. + The current behavior is acceptable to bugzilla.mozilla.org and most + users. I personally don't like it. You have your choice of patches + to change this behavior, however. <simplelist> - <member><ulink - url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"> Add a "and accept bug" radio button</ulink></member> - <member><ulink - url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"> "Accept" button automatically assigns to you</ulink></member> - </simplelist> Note that these patches are somewhat dated. - You will need to do the find and replace manually to apply - them. They are very small, though. It is easy. + <member><ulink url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8029"> + Add a "and accept bug" radio button</ulink></member> + <member><ulink url="http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8153"> + "Accept" button automatically assigns to you</ulink></member> + </simplelist> + Note that these patches are somewhat dated. You will need to do the find + and replace manually to apply them. They are very small, though. It is easy. </para> </answer> </qandaentry> @@ -1827,16 +1695,15 @@ <qandaentry> <question> <para> - I can't upload anything into the database via the "Create - Attachment" link. What am I doing wrong? + I can't upload anything into the database via the "Create Attachment" + link. What am I doing wrong? </para> </question> <answer> <para> - The most likely cause is a very old browser or a browser - that is incompatible with file upload via POST. Download - the latest Netscape, Microsoft, or Mozilla browser to - handle uploads correctly. + The most likely cause is a very old browser or a browser that is + incompatible with file upload via POST. Download the latest Netscape, + Microsoft, or Mozilla browser to handle uploads correctly. </para> </answer> </qandaentry> @@ -1844,16 +1711,15 @@ <qandaentry> <question> <para> - Email submissions to Bugzilla that have attachments end up - asking me to save it as a "cgi" file. + Email submissions to Bugzilla that have attachments end up asking me to + save it as a "cgi" file. </para> </question> <answer> <para> - Yup. Just rename it once you download it, or save it - under a different filename. This will not be fixed - anytime too soon, because it would cripple some other - functionality. + Yup. Just rename it once you download it, or save it under a different + filename. This will not be fixed anytime too soon, because it would + cripple some other functionality. </para> </answer> </qandaentry> @@ -1861,16 +1727,14 @@ <qandaentry> <question> <para> - How do I change a keyword in Bugzilla, once some bugs are - using it? + How do I change a keyword in Bugzilla, once some bugs are using it? </para> </question> <answer> <para> - In the Bugzilla administrator UI, edit the keyword and it - will let you replace the old keyword name with a new one. - This will cause a problem with the keyword cache. Run - sanitycheck.cgi to fix it. + In the Bugzilla administrator UI, edit the keyword and it will let you + replace the old keyword name with a new one. This will cause a problem + with the keyword cache. Run sanitycheck.cgi to fix it. </para> </answer> </qandaentry> @@ -1888,12 +1752,19 @@ </question> <answer> <para> - Try <ulink - url="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Webtools&component=Bugzilla"> this link</ulink> to view current bugs or requests for enhancement for Bugzilla. + Try <ulink url="http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Webtools&component=Bugzilla"> + this link</ulink> to view current bugs or requests for + enhancement for Bugzilla. </para> <para> - You can view bugs marked for 2.14 release <ulink - url="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bugzilla&target_milestone=Bugzilla+2.14">here</ulink>. This list includes bugs for the 2.14 release that have already been fixed and checked into CVS. Please consult the <ulink url="http://www.mozilla.org/projects/bugzilla/"> Bugzilla Project Page</ulink> for details on how to check current sources out of CVS so you can have these bug fixes early! + You can view bugs marked for 2.14 release + <ulink url="http://bugzilla.mozilla.org/buglist.cgi?product=Webtools&component=Bugzilla&target_milestone=Bugzilla+2.14">here</ulink>. + This list includes bugs for the 2.14 release that have already + been fixed and checked into CVS. Please consult the + <ulink url="http://www.mozilla.org/projects/bugzilla/"> + Bugzilla Project Page</ulink> for details on how to + check current sources out of CVS so you can have these + bug fixes early! </para> </answer> </qandaentry> @@ -1901,15 +1772,19 @@ <qandaentry> <question> <para> - How can I change the default priority to a null value? - For instance, have the default priority be "---" instead - of "P2"? + 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... + 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> @@ -1917,8 +1792,7 @@ <qandaentry> <question> <para> - What's the best way to submit patches? What guidelines - should I follow? + What's the best way to submit patches? What guidelines should I follow? </para> </question> <answer> @@ -1926,47 +1800,42 @@ <orderedlist> <listitem> <para> - Enter a bug into bugzilla.mozilla.org for the - "Webtools" product, "Bugzilla" component. + Enter a bug into bugzilla.mozilla.org for the "Webtools" product, + "Bugzilla" component. </para> </listitem> <listitem> <para> - Upload your patch as a unified DIFF (having used - "diff -u" against the <emphasis>current - sources</emphasis> checked out of CVS), or new - source file by clicking "Create a new attachment" - link on the bug page you've just created, and - include any descriptions of database changes you may - make, into the bug ID you submitted in step #1. Be - sure and click the "Patch" radio button to indicate - the text you are sending is a patch! + Upload your patch as a unified DIFF (having used "diff -u" against + the <emphasis>current sources</emphasis> checked out of CVS), + or new source file by clicking + "Create a new attachment" link on the bug page you've just created, and + include any descriptions of database changes you may make, into the bug + ID you submitted in step #1. Be sure and click the "Patch" radio + button to indicate the text you are sending is a patch! </para> </listitem> <listitem> <para> Announce your patch and the associated URL - (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) - for discussion in the newsgroup - (netscape.public.mozilla.webtools). You'll get a - really good, fairly immediate reaction to the - implications of your patch, which will also give us - an idea how well-received the change would be. + (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXX) for discussion in + the newsgroup (netscape.public.mozilla.webtools). You'll get a really + good, fairly immediate reaction to the implications of your patch, + which will also give us an idea how well-received the change would + be. </para> </listitem> <listitem> <para> - If it passes muster with minimal modification, the - person to whom the bug is assigned in Bugzilla is - responsible for seeing the patch is checked into - CVS. + If it passes muster with minimal modification, the person to whom + the bug is assigned in Bugzilla is responsible for seeing the patch + is checked into CVS. </para> </listitem> <listitem> <para> - Bask in the glory of the fact that you helped write - the most successful open-source bug-tracking - software on the planet :) + Bask in the glory of the fact that you helped write the most successful + open-source bug-tracking software on the planet :) </para> </listitem> </orderedlist> diff --git a/docs/xml/glossary.xml b/docs/xml/glossary.xml index 71ba2dd36..faa4d1781 100644 --- a/docs/xml/glossary.xml +++ b/docs/xml/glossary.xml @@ -26,9 +26,16 @@ <glossdiv id="gloss_a"> <title>A</title> <glossentry> - <glossterm>There are no entries for A</glossterm> + <glossterm>Apache</glossterm> <glossdef> - <para></para> + <para>In this context, Apache is the web server most + commonly used for serving up + <glossterm>Bugzilla</glossterm> pages. Contrary to + popular belief, the apache web server has nothing to do + with the ancient and noble Native American tribe, but + instead derived its name from the fact that it was + <quote>a patchy</quote> version of the original + <acronym>NCSA</acronym> world-wide-web server.</para> </glossdef> </glossentry> </glossdiv> @@ -70,8 +77,77 @@ the needs of the organization using it, though.</para> </glossdef> </glossentry> + + <glossentry> + <glossterm>Bugzilla</glossterm> + <glossdef> + <para> + Bugzilla is the industry-standard bug tracking system. It + is quite popular among Open Source enthusiasts. + </para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv id="gloss_c"> + <title></title> + <glossentry id="gloss_component"> + <glossterm>Component</glossterm> + <glossdef> + <para> + A Component is a subsection of a Product. It should be a + narrow category, tailored to your organization. All + Products must contain at least one Component (and, as a + matter of fact, creating a Product with no Components will + create an error in Bugzilla). + </para> + </glossdef> + </glossentry> + <glossentry id="gloss_cpan"> + <glossterm><acronym>CPAN</acronym></glossterm> + <glossdef> + <para><acronym>CPAN</acronym> stands for the + <quote>Comprehensive Perl Archive Network</quote>. CPAN + maintains a large number of extremely useful + <glossterm>Perl</glossterm> modules. By themselves, Perl + modules generally do nothing, but when used as part of a + larger program, they provide much-needed algorithms and + functionality.</para> + </glossdef> + </glossentry> </glossdiv> + <glossdiv id="gloss_d"> + <title>D</title> + <glossentry> + <glossterm>daemon</glossterm> + <glossdef> + <para>A daemon is a computer program which runs in the + background. In general, most daemons are started at boot + time via System V init scripts, or through RC scripts on + BSD-based systems. <glossterm>mysqld</glossterm>, the + MySQL server, and <glossterm>apache</glossterm>, a web + server, are generally run as daemons.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv id="gloss_g"> + <title></title> + <glossentry> + <glossterm>Groups</glossterm> + <glossdef> + <para>The word <quote>Groups</quote> has a very special + meaning to Bugzilla. Bugzilla's main security mechanism + comes by lumping users into groups, and assigning those + groups certain privileges to + <glossterm>Products</glossterm> and + <glossterm>Components</glossterm> in the + <glossterm>Bugzilla</glossterm> database.</para> + </glossdef> + </glossentry> + </glossdiv> + <glossdiv id="gloss_i"> <title>I</title> <glossentry id="gloss_infiniteloop"> @@ -81,7 +157,22 @@ </glossdef> </glossentry> </glossdiv> - + + <glossdiv id="gloss_m"> + <title>M</title> + <glossentry> + <glossterm>mysqld</glossterm> + <glossdef> + <para>mysqld is the name of the + <glossterm>daemon</glossterm> for the MySQL database. In + general, it is invoked automatically through the use of + the System V init scripts on GNU/Linux and AT&T System + V-based systems, such as Solaris and HP/UX, or through the + RC scripts on BSD-based systems.</para> + </glossdef> + </glossentry> + </glossdiv> + <glossdiv id="gloss_p"> <title>P</title> <glossentry> @@ -108,6 +199,17 @@ </example> </glossdef> </glossentry> + <glossentry> + <glossterm>Perl</glossterm> + <glossdef> + <para>First written by Larry Wall, Perl is a remarkable + program language. It has the benefits of the flexibility + of an interpreted scripting language (such as shell + script), combined with the speed and power of a compiled + language, such as C. <glossterm>Bugzilla</glossterm> is + maintained in Perl.</para> + </glossdef> + </glossentry> </glossdiv> <glossdiv id="gloss_q"> @@ -129,8 +231,8 @@ <glossdiv id="gloss_r"> <title>R</title> - <glossentry> - <glossterm id="gloss_recursion">Recursion</glossterm> + <glossentry id="gloss_recursion" xreflabel="Recursion"> + <glossterm>Recursion</glossterm> <glossdef> <para>The property of a function looking back at itself for something. <quote>GNU</quote>, for instance, stands for @@ -140,10 +242,52 @@ </glossdef> </glossentry> </glossdiv> + + <glossdiv id="gloss_s"> + <title>S</title> + <glossentry> + <glossterm><acronym>SGML</acronym></glossterm> + <glossdef> + <para><acronym>SGML</acronym> stands for <quote>Standard + Generalized Markup Language</quote>. Created in the + 1980's to provide an extensible means to maintain + documentation based upon content instead of presentation, + <acronym>SGML</acronym> has withstood the test of time as + a robust, powerful language. + <glossterm><acronym>XML</acronym></glossterm> is the + <quote>baby brother</quote> of SGML; any valid + <acronym>XML</acronym> document it, by definition, a valid + <acronym>SGML</acronym> document. The document you are + reading is written and maintained in + <acronym>SGML</acronym>, and is also valid + <acronym>XML</acronym> if you modify the Document Type + Definition.</para> + </glossdef> + </glossentry> + </glossdiv> + + <glossdiv id="gloss_t"> + <title>T</title> + <glossentry id="gloss_target_milestone" xreflabel="Target Milestone"> + <glossterm>Target Milestone</glossterm> + <glossdef> + <para> + Target Milestones are Product goals. They are + configurable on a per-Product basis. Most software + development houses have a concept of + <quote>milestones</quote> where the people funding a + project expect certain functionality on certain dates. + Bugzilla facilitates meeting these milestones by giving + you the ability to declare by which milestone a bug will be + fixed, or an enhancement will be implemented. + </para> + </glossdef> + </glossentry> + </glossdiv> <glossdiv id="gloss_z"> <title>Z</title> - <glossentry> + <glossentry id="zarro-boogs-found" xreflabel="Zarro Boogs Found"> <glossterm>Zarro Boogs Found</glossterm> <glossdef> <para>This is the cryptic response sent by Bugzilla when a diff --git a/docs/xml/installation.xml b/docs/xml/installation.xml index dfbc35071..547d466ba 100644 --- a/docs/xml/installation.xml +++ b/docs/xml/installation.xml @@ -1,6 +1,6 @@ <!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN"> --> - <chapter id="installation"> + <chapter id="installation" xreflabel="Bugzilla Installation"> <title>Installation</title> <para> These installation instructions are presented assuming you are @@ -50,6 +50,7 @@ refer to these documents when installing, configuring, and maintaining your Bugzilla installation. </member> + </simplelist> <warning> @@ -108,8 +109,7 @@ the CPAN dependencies listed below, and are running the very most recent version of Perl and MySQL (both the executables and development libraries) on your system, check out - Bundle::Bugzilla in <xref - linkend="bundlebugzilla"></para> + Bundle::Bugzilla in <xref linkend="bundlebugzilla"></para> </note> <para> The software packages necessary for the proper running of bugzilla are: @@ -185,39 +185,64 @@ attack. </para> </warning> + <note> + <para>Linux-Mandrake 8.0, the author's test system, includes + every required and optional library for Bugzilla. The + easiest way to install them is by using the + <filename>urpmi</filename> utility. If you follow these + commands, you should have everything you need for + Bugzilla, and <filename>checksetup.pl</filename> should + not complain about any missing libraries. You may already + have some of these installed.</para> + <simplelist> + <member><prompt>bash#</prompt><command> urpmi + perl-mysql</command></member> + <member><prompt>bash#</prompt><command> urpmi + perl-chart</command></member> + <member><prompt>bash#</prompt><command> urpmi + perl-gd</command></member> + <member><prompt>bash#</prompt><command> urpmi + perl-MailTools</command> (for Bugzilla email + integration)</member> + <member><prompt>bash#</prompt><command> urpmi + apache-modules</command></member> + </simplelist> + </note> </para> </section> <section id="install-mysql"> <title>Installing MySQL Database</title> <para> - Visit MySQL homepage at http://www.mysql.com/ and grab the - latest stable release of the server. Both binaries and source - are available and which you get shouldn't matter. Be aware - that many of the binary versions of MySQL store their data - files in /var which on many installations (particularly common - with linux installations) is part of a smaller root partition. - If you decide to build from sources you can easily set the - dataDir as an option to configure. + Visit MySQL homepage at <ulink + url="http://www.mysql.com">www.mysql.com</ulink> and grab the latest stable release of the server. Many of the binary versions of MySQL store their data files in <filename>/var</filename> which is often part of a smaller root partition. If you decide to build from sources you can easily set the dataDir as an option to <filename>configure</filename>. </para> <para> - If you've installed from source or non-package (RPM, deb, - etc.) binaries you'll want to make sure to add mysqld to your + If you install from source or non-package (RPM, deb, etc.) + binaries you need to add + <firstterm>mysqld</firstterm> to your init scripts so the server daemon will come back up whenever - your machine reboots. You also may want to edit those init - scripts, to make sure that mysqld will accept large packets. - By default, mysqld is set up to only accept packets up to 64K - long. This limits the size of attachments you may put on - bugs. If you add something like "-O max_allowed_packet=1M" to - the command that starts mysqld (or safe_mysqld), then you will - be able to have attachments up to about 1 megabyte. + your machine reboots. Further discussion of UNIX init + sequences are beyond the scope of this guide. + <note> + <para>You should have your init script start + <glossterm>mysqld</glossterm> with the ability to accept + large packets. By default, <filename>mysqld</filename> + only accepts packets up to 64K long. This limits the size + of attachments you may put on bugs. If you add <option>-O + max_allowed_packet=1M</option> to the command that starts + <filename>mysqld</filename> (or + <filename>safe_mysqld</filename>), then you will be able + to have attachments up to about 1 megabyte.</para> + </note> + </para> <note> <para> If you plan on running Bugzilla and MySQL on the same - machine, consider using the "--skip-networking" option in - the init script. This enhances security by preventing - network access to MySQL. + machine, consider using the <option>--skip-networking</option> + option in the init script. This enhances security by + preventing network access to MySQL. </para> </note> </section> @@ -260,9 +285,10 @@ <tip id="bundlebugzilla" xreflabel="Using Bundle::Bugzilla instead of manually installing Perl modules"> <para> You can skip the following Perl module installation steps by - installing "Bundle::Bugzilla" from CPAN, which includes - them. All Perl module installation steps require you have an - active Internet connection. If you wish to use + installing <productname>Bundle::Bugzilla</productname> from + <glossterm linkend="gloss_cpan">CPAN</glossterm>, which + includes them. All Perl module installation steps require + you have an active Internet connection. If you wish to use Bundle::Bugzilla, however, you must be using the latest version of Perl (at this writing, version &perl-ver;) </para> @@ -293,7 +319,7 @@ Like almost all Perl modules DBI can be found on the Comprehensive Perl Archive Network (CPAN) at http://www.cpan.org. The CPAN servers have a real tendency to bog down, so please use mirrors. The current location - at the time of this writing (02/17/99) can be found in Appendix A. + at the time of this writing can be found in <xref linkend="downloadlinks">. </para> <para> Quality, general Perl module installation instructions can be found on @@ -370,9 +396,11 @@ hurt anything. </para> <para> - Data::Dumper is used by the MySQL-related Perl modules. It can be - found on CPAN (link in Appendix A) and can be installed by following - the same four step make sequence used for the DBI module. + Data::Dumper is used by the MySQL-related Perl modules. It + can be found on CPAN (see <xref linkend="downloadlinks">) and + can be + installed by following the same four step make sequence used + for the DBI module. </para> </section> @@ -414,37 +442,42 @@ <section> <title>TimeDate Perl Module Collection</title> <para> - Many of the more common date/time/calendar related Perl modules have - been grouped into a bundle similar to the MySQL modules bundle. This - bundle is stored on the CPAN under the name TimeDate. A link - link may be found in Appendix B, Software Download Links. - The component module we're - most interested in is the Date::Format module, but installing all of them - is probably a good idea anyway. The standard Perl module installation - instructions should work perfectly for this simple package. + Many of the more common date/time/calendar related Perl + modules have been grouped into a bundle similar to the MySQL + modules bundle. This bundle is stored on the CPAN under the + name TimeDate (see link: <xref linkend="downloadlinks">). The + component module we're most interested in is the Date::Format + module, but installing all of them is probably a good idea + anyway. The standard Perl module installation instructions + should work perfectly for this simple package. </para> </section> <section> <title>GD Perl Module (1.8.3)</title> <para> - The GD library was written by Thomas Boutell a long while ago to - programatically generate images in C. Since then it's become almost a - defacto standard for programatic image construction. The Perl bindings - to it found in the GD library are used on a million web pages to generate - graphs on the fly. That's what bugzilla will be using it for so you'd - better install it if you want any of the graphing to work. + The GD library was written by Thomas Boutell a long while + ago to programatically generate images in C. Since then it's + become the defacto standard for programatic image + construction. The Perl bindings to it found in the GD library + are used on millions of web pages to generate graphs on the + fly. That's what bugzilla will be using it for so you must + install it if you want any of the graphing to work. </para> <para> - Actually bugzilla uses the Graph module which relies on GD itself, - but isn't that always the way with OOP. At any rate, you can find the - GD library on CPAN (link in Appendix B, Software Download Links). + Actually bugzilla uses the Graph module which relies on GD + itself. Isn't that always the way with object-oriented + programming? At any rate, you can find the GD library on CPAN + in <xref linkend="downloadlinks">. </para> <note> <para> - The Perl GD library requires some other libraries that may or may not be - installed on your system, including "libpng" and "libgd". The full requirements - are listed in the Perl GD library README. Just realize that if compiling GD fails, - it's probably because you're missing a required library. + The Perl GD library requires some other libraries that may + or may not be installed on your system, including + <classname>libpng</classname> and + <classname>libgd</classname>. The full requirements are + listed in the Perl GD library README. Just realize that if + compiling GD fails, it's probably because you're missing a + required library. </para> </note> </section> @@ -453,62 +486,78 @@ <title>Chart::Base Perl Module (0.99c)</title> <para> The Chart module provides bugzilla with on-the-fly charting - abilities. It can be installed in the usual fashion after it has been - fetched from CPAN where it is found as the Chart-x.x... tarball in a - directory to be listed in Appendix B, "Software Download Links". - Note that as with the GD perl - module, only the version listed above, or newer, will work. - Earlier - versions used GIF's, which are no longer supported by the latest - versions of GD. + abilities. It can be installed in the usual fashion after it + has been fetched from CPAN where it is found as the + Chart-x.x... tarball, linked in <xref linkend="downloadlinks">. Note that + as with the GD perl module, only the version listed above, or + newer, will work. Earlier versions used GIF's, which are no + longer supported by the latest versions of GD. </para> </section> <section> <title>DB_File Perl Module</title> <para> - DB_File is a module which allows Perl programs to make use of the facilities provided by - Berkeley DB version 1.x. This module is required by collectstats.pl which is used for - bug charting. If you plan to make use of bug charting, you must install this module. + DB_File is a module which allows Perl programs to make use + of the facilities provided by Berkeley DB version 1.x. This + module is required by collectstats.pl which is used for bug + charting. If you plan to make use of bug charting, you must + install this module. </para> </section> <section> <title>HTTP Server</title> <para> - You have a freedom of choice here - Apache, Netscape or any other - server on UNIX would do. You can easily run the web server on a different - machine than MySQL, but need to adjust the MySQL "bugs" user permissions - accordingly. + You have a freedom of choice here - Apache, Netscape or any + other server on UNIX would do. You can easily run the web + server on a different machine than MySQL, but need to adjust + the MySQL <quote>bugs</quote> user permissions accordingly. + <note> + <para>I strongly recommend Apache as the web server to use. + The Bugzilla Guide installation instructions, in general, + assume you are using Apache. As more users use different + webservers and send me information on the peculiarities of + installing using their favorite webserver, I will provide + notes for them.</para> + </note> </para> <para> - You'll want to make sure that your web server will run any file - with the .cgi extension as a cgi and not just display it. If you're using - apache that means uncommenting the following line in the srm.conf file: - <computeroutput>AddHandler cgi-script .cgi</computeroutput> + You'll want to make sure that your web server will run any + file with the .cgi extension as a cgi and not just display it. + If you're using apache that means uncommenting the following + line in the srm.conf file: + <programlisting> +AddHandler cgi-script .cgi + </programlisting> </para> <para> - With apache you'll also want to make sure that within the access.conf - file the line: - <computeroutput> - Options ExecCGI - </computeroutput> - is in the stanza that covers the directories you intend to put the bugzilla - .html and .cgi files into. + With apache you'll also want to make sure that within the + access.conf file the line: + <programlisting> +Options ExecCGI +</programlisting> + is in the stanza that covers the directories into which + you intend to put the bugzilla .html and .cgi files. </para> + <note> <para> - If you are using a newer version of Apache, both of the above lines will be - (or will need to be) in the httpd.conf file, rather than srm.conf or - access.conf. + Users of newer versions of Apache will generally find both + of the above lines will be in the httpd.conf file, rather + than srm.conf or access.conf. </para> + </note> <warning> <para> - There are two critical directories and a file that should not be a served by - the HTTP server. These are the <quote>data</quote> and <quote>shadow</quote> - directories and the - <quote>localconfig</quote> file. You should configure your HTTP server to not serve - content from these files. Failure to do so will expose critical passwords - and other data. Please see <xref linkend="htaccess"> for details. + There are important files and directories that should not + be a served by the HTTP server. These are most files in the + <quote>data</quote> and <quote>shadow</quote> directories + and the <quote>localconfig</quote> file. You should + configure your HTTP server to not serve content from these + files. Failure to do so will expose critical passwords and + other data. Please see <xref linkend="htaccess"> for details + on how to do this for Apache. I appreciate notes on how to + get this same functionality using other webservers. </para> </warning> </section> @@ -516,59 +565,65 @@ <section> <title>Installing the Bugzilla Files</title> <para> - You should untar the Bugzilla files into a directory that you're - willing to make writable by the default web server user (probably - <quote>nobody</quote>). You may decide to put the files off of the main web space - for your web server or perhaps off of /usr/local with a symbolic link - in the web space that points to the bugzilla directory. At any rate, - just dump all the files in the same place (optionally omitting the CVS - directories if they were accidentally tarred up with the rest of Bugzilla) - and make sure you can access the files in that directory through your - web server. + You should untar the Bugzilla files into a directory that + you're willing to make writable by the default web server user + (probably <quote>nobody</quote>). You may decide to put the + files off of the main web space for your web server or perhaps + off of <filename>/usr/local</filename> with a symbolic link in + the web space that points to the Bugzilla directory. At any + rate, just dump all the files in the same place, and make sure + you can access the files in that directory through your web + server. </para> <tip> <para> If you symlink the bugzilla directory into your Apache's - HTML heirarchy, you may receive "Forbidden" errors unless you - add the "FollowSymLinks" directive to the <Directory> entry - for the HTML root. + HTML heirarchy, you may receive + <errorname>Forbidden</errorname> errors unless you add the + <quote>FollowSymLinks</quote> directive to the + <Directory> entry for the HTML root. </para> </tip> <para> - Once all the files are in a web accessible directory, make that - directory writable by your webserver's user (which may require just - making it world writable). This is a temporary step until you run - the post-install <quote>checksetup.pl</quote> script, which locks down your - installation. - </para> - <para> - Lastly, you'll need to set up a symbolic link to /usr/bonsaitools/bin/perl - for the correct location of your perl executable (probably /usr/bin/perl). - Otherwise you must hack all the .cgi files to change where they look - for perl. To make future upgrades easier, you should use the symlink - approach. - <example> - <title>Setting up bonsaitools symlink</title> - <para> - Here's how you set up the Perl symlink on Linux to make Bugzilla work. - Your mileage may vary; if you are running on Solaris, you probably need to subsitute - <quote>/usr/local/bin/perl</quote> for <quote>/usr/bin/perl</quote> - below; if on certain other UNIX systems, - Perl may live in weird places like <quote>/opt/perl</quote>. As root, run these commands: - <programlisting> -bash# mkdir /usr/bonsaitools -bash# mkdir /usr/bonsaitools/bin + Once all the files are in a web accessible directory, make + that directory writable by your webserver's user. This is a + temporary step until you run the post-install + <filename>checksetup.pl</filename> script, which locks down your + installation. + </para> + <para> + Lastly, you'll need to set up a symbolic link to + <filename>/usr/bonsaitools/bin/perl</filename> for the correct + location of your perl executable (probably + <filename>/usr/bin/perl</filename>). Otherwise you must hack + all the .cgi files to change where they look for perl, or use + <xref linkend="setperl">, found in + <xref linkend="patches">. I suggest using the symlink + approach for future release compatability. + <example> + <title>Setting up bonsaitools symlink</title> + <para> + Here's how you set up the Perl symlink on Linux to make + Bugzilla work. Your mileage may vary. For some UNIX + operating systems, you probably need to subsitute + <quote>/usr/local/bin/perl</quote> for + <quote>/usr/bin/perl</quote> below; if on certain other + UNIX systems, Perl may live in weird places like + <quote>/opt/perl</quote>. As root, run these commands: + <programlisting> +bash# mkdir /usr/bonsaitools +bash# mkdir /usr/bonsaitools/bin bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl - </programlisting> - </para> - </example> - <tip> - <para> - If you don't have root access to set this symlink up, + </programlisting> + </para> + </example> + <tip> + <para> + If you don't have root access to set this symlink up, check out the - <xref linkend="setperl">, listed in <xref linkend="patches">. - It will change the path to perl in all your Bugzilla files for you. - </para> + <xref linkend="setperl">, listed in <xref + linkend="patches">. It will change the path to perl in all your Bugzilla files for you. + </para> </tip> </para> </section> @@ -581,10 +636,11 @@ bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl quality bug tracker. </para> <para> - First, you'll want to fix MySQL permissions to allow access from - Bugzilla. For the purpose of this Installation section, the Bugzilla username - will be "bugs", and will have minimal permissions. - + First, you'll want to fix MySQL permissions to allow access + from Bugzilla. For the purpose of this Installation section, + the Bugzilla username will be <quote>bugs</quote>, and will + have minimal permissions. + <warning> <para> Bugzilla has not undergone a thorough security audit. It @@ -594,199 +650,190 @@ bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl </para> <para>That would be bad.</para> </warning> - </para> - - <para> - Give the MySQL root user a password. MySQL passwords are - limited to 16 characters. - <simplelist> - <member> - <computeroutput> - <prompt>bash#</prompt> - <command>mysql -u root mysql</command> - </computeroutput> - </member> - <member> - <computeroutput> - <prompt>mysql></prompt> - <command> - UPDATE user SET Password=PASSWORD ('new_password') - WHERE user='root'; - </command> - </computeroutput> - </member> - <member> - <computeroutput> - <prompt>mysql></prompt> - <command>FLUSH PRIVILEGES;</command> - </computeroutput> - </member> - </simplelist> - From this point on, if you need to access MySQL as the - MySQL root user, you will need to use "mysql -u root -p" and - enter your new_password. Remember that MySQL user names have - nothing to do with Unix user names (login names). - </para> - <para> - Next, we create the "bugs" user, and grant sufficient - permissions for checksetup.pl, which we'll use later, to work - its magic. This also restricts the "bugs" user to operations - within a database called "bugs", and only allows the account - to connect from "localhost". Modify it to reflect your setup - if you will be connecting from another machine or as a different - user. - </para> - <para> - Remember to set bugs_password to some unique password. - <simplelist> - <member> - <computeroutput> - <prompt>mysql></prompt> - <command>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, - ALTER,CREATE,DROP,REFERENCES - ON bugs.* TO bugs@localhost - IDENTIFIED BY 'bugs_password';</command> - </computeroutput> - </member> - <member> - <computeroutput> - <prompt> - mysql> - </prompt> - <command> - FLUSH PRIVILEGES; - </command> - </computeroutput> - </member> - </simplelist> - </para> - <para> - Next, run the magic checksetup.pl script. (Many thanks to Holger - Schurig <holgerschurig@nikocity.de> for writing this script!) - It will make sure Bugzilla files and directories have reasonable - permissions, set up the "data" directory, and create all the MySQL - tables. - <simplelist> - <member> - <computeroutput> - <prompt>bash#</prompt> - <command>./checksetup.pl</command> - </computeroutput> - </member> - </simplelist> - The first time you run it, it will create a file called "localconfig". - </para> - </section> - - <section> - <title>Tweaking "localconfig"</title> - <para> - This file contains a variety of settings you may need to tweak including - how Bugzilla should connect to the MySQL database. - </para> - <para> - The connection settings include: - <orderedlist> - <listitem> - <para> - server's host: just use "localhost" if the MySQL server is - local - </para> - </listitem> - <listitem> - <para> - database name: "bugs" if you're following these directions - </para> - </listitem> - <listitem> - <para> - MySQL username: "bugs" if you're following these directions - </para> - </listitem> - <listitem> - <para> - Password for the "bugs" MySQL account above - </para> - </listitem> - </orderedlist> - </para> - <para> - You may also install .htaccess files that the Apache webserver will use - to restrict access to Bugzilla data files. See <xref linkend="htaccess">. - </para> - <para> - Once you are happy with the settings, re-run checksetup.pl. On this - second run, it will create the database and an administrator account - for which you will be prompted to provide information. - </para> - <para> - When logged into an administrator account once Bugzilla is running, - if you go to the query page (off of the bugzilla main menu), you'll - find an 'edit parameters' option that is filled with editable treats. - </para> - <para> - Should everything work, you should have a nearly empty copy of the bug - tracking setup. - </para> - <para> - The second time around, checksetup.pl will stall if it is on a - filesystem that does not fully support file locking via flock(), such as - NFS mounts. This support is required for Bugzilla to operate safely with - multiple instances. If flock() is not fully supported, it will stall at: - <errorcode>Now regenerating the shadow database for all bugs.</errorcode> - <note> + </para> + + <para> + Give the MySQL root user a password. MySQL passwords are + limited to 16 characters. + <simplelist> + <member> + <computeroutput> <prompt>bash#</prompt> <command>mysql + -u root mysql</command> </computeroutput> + </member> + <member> + <computeroutput> <prompt>mysql></prompt> <command> + UPDATE user SET Password=PASSWORD ('new_password') + WHERE user='root'; </command> </computeroutput> + </member> + <member> + <computeroutput> <prompt>mysql></prompt> <command>FLUSH + PRIVILEGES;</command> </computeroutput> + </member> + </simplelist> From this point on, if you need to access + MySQL as the MySQL root user, you will need to use + <command>mysql -u root -p</command> and enter your + new_password. Remember that MySQL user names have nothing to + do with Unix user names (login names). + </para> + <para> + Next, we create the <quote>bugs</quote> user, and grant + sufficient permissions for checksetup.pl, which we'll use + later, to work its magic. This also restricts the + <quote>bugs</quote> user to operations within a database + called <quote>bugs</quote>, and only allows the account to + connect from <quote>localhost</quote>. Modify it to reflect + your setup if you will be connecting from another machine or + as a different user. + </para> + <para> + Remember to set bugs_password to some unique password. + <simplelist> + <member> + <computeroutput> + <prompt>mysql></prompt> + <command>GRANT SELECT,INSERT,UPDATE,DELETE,INDEX, + ALTER,CREATE,DROP,REFERENCES + ON bugs.* TO bugs@localhost + IDENTIFIED BY 'bugs_password';</command> + </computeroutput> + </member> + <member> + <computeroutput> + <prompt> + mysql> + </prompt> + <command> + FLUSH PRIVILEGES; + </command> + </computeroutput> + </member> + </simplelist> + </para> + <para> + Next, run the magic checksetup.pl script. (Many thanks to + Holger Schurig <holgerschurig@nikocity.de> for writing + this script!) It will make sure Bugzilla files and directories + have reasonable permissions, set up the + <filename>data</filename> directory, and create all the MySQL + tables. + <simplelist> + <member> + <computeroutput> <prompt>bash#</prompt> + <command>./checksetup.pl</command> </computeroutput> + </member> + </simplelist> The first time you run it, it will create a + file called <filename>localconfig</filename>. + </para> + </section> + + <section> + <title>Tweaking <filename>localconfig</filename></title> + <para> + This file contains a variety of settings you may need to tweak including + how Bugzilla should connect to the MySQL database. + </para> + <para> + The connection settings include: + <orderedlist> + <listitem> <para> - The second time you run checksetup.pl, you should become the - user your web server runs as, and that you ensure that you set the - "webservergroup" parameter in localconfig to match the web - server's group - name, if any. I believe, for the next release of Bugzilla, - this will - be fixed so that Bugzilla supports a "webserveruser" parameter - in localconfig - as well. - <example> - <title>Running checksetup.pl as the web user</title> - <para> - Assuming your web server runs as user "apache", - and Bugzilla is installed in - "/usr/local/bugzilla", here's one way to run checksetup.pl - as the web server user. - As root, for the <emphasis>second run</emphasis> - of checksetup.pl, do this: - <programlisting> -bash# chown -R apache:apache /usr/local/bugzilla -bash# su - apache -bash# cd /usr/local/bugzilla -bash# ./checksetup.pl - </programlisting> - </para> - </example> + server's host: just use <quote>localhost</quote> if the + MySQL server is local </para> - </note> - </para> + </listitem> + <listitem> + <para> + database name: <quote>bugs</quote> if you're following + these directions + </para> + </listitem> + <listitem> + <para> + MySQL username: <quote>bugs</quote> if you're following + these directions + </para> + </listitem> + <listitem> + <para> + Password for the <quote>bugs</quote> MySQL account above + </para> + </listitem> + </orderedlist> + </para> + <para> + You should also install .htaccess files that the Apache + webserver will use to restrict access to Bugzilla data files. + See <xref + linkend="htaccess">. + </para> + <para> + Once you are happy with the settings, re-run + <filename>checksetup.pl</filename>. On this second run, it will + create the database and an administrator account for which + you will be prompted to provide information. + </para> + <para> + When logged into an administrator account once Bugzilla is + running, if you go to the query page (off of the Bugzilla main + menu), you'll find an <quote>edit parameters</quote> option + that is filled with editable treats. + </para> + <para> + Should everything work, you will have a nearly empty Bugzilla + database and a newly-created <filename>localconfig</filename> + file in your Bugzilla root directory. + </para> + <para> <note> <para> - The checksetup.pl script is designed so that you can run - it at any time without causing harm. You should run it - after any upgrade to Bugzilla. + The second time you run checksetup.pl, you should become + the user your web server runs as, and that you ensure that + you set the <quote>webservergroup</quote> parameter in localconfig to + match the web server's group name, if any. I believe, + for the next release of Bugzilla, this will be fixed so + that Bugzilla supports a <quote>webserveruser</quote> parameter in + localconfig as well. + <example> + <title>Running checksetup.pl as the web user</title> + <para> + Assuming your web server runs as user "apache", and + Bugzilla is installed in "/usr/local/bugzilla", here's + one way to run checksetup.pl as the web server user. + As root, for the <emphasis>second run</emphasis> of + checksetup.pl, do this: + <programlisting> +bash# chown -R apache:apache /usr/local/bugzilla +bash# su - apache +bash# cd /usr/local/bugzilla +bash# ./checksetup.pl + </programlisting> + </para> + </example> </para> </note> - </section> - - <section> - <title>Setting Up Maintainers Manually (Optional)</title> + </para> + <note> <para> - If you want to add someone else to every group by hand, you + The checksetup.pl script is designed so that you can run + it at any time without causing harm. You should run it + after any upgrade to Bugzilla. + </para> + </note> + </section> + + <section> + <title>Setting Up Maintainers Manually (Optional)</title> + <para> + If you want to add someone else to every group by hand, you can do it by typing the appropriate MySQL commands. Run - '<computeroutput> mysql -u root -p bugs</computeroutput>' You + <command> mysql -u root -p bugs</command> You may need different parameters, depending on your security settings. Then: <simplelist> <member> <computeroutput> <prompt>mysql></prompt> <command>update profiles set groupset=0x7fffffffffffffff where - login_name = 'XXX';</command> </computeroutput> + login_name = 'XXX';</command> </computeroutput> (yes, that's <emphasis>fifteen</emphasis><quote>f</quote>'s. </member> </simplelist> replacing XXX with the Bugzilla email address. </para> @@ -1156,33 +1203,74 @@ bash# ./checksetup.pl <parameter>0</parameter>. </para> </section> + + <section id="mod_throttle" xreflabel="Using mod_throttle to prevent Denial of Service attacks"> + <title><filename>mod_throttle</filename> and Security</title> + <para> + It is possible for a user, by mistake or on purpose, to access + the database many times in a row which can result in very slow + access speeds for other users. If your Bugzilla installation + is experiencing this problem , you may install the Apache + module <filename>mod_throttle</filename> which can limit + connections by ip-address. You may download this module at + <ulink + url="http://www.snert.com/Software/Throttle/">http://www.snert.com/Software/Throttle/</ulink>. Follow the instructions to install into your Apache install. <emphasis>This module only functions with the Apache web server!</emphasis>. You may use the <command>ThrottleClientIP</command> command provided by this module to accomplish this goal. See the <ulink url="http://www.snert.com/Software/Throttle/">Module Instructions</ulink> for more information. </para> + </section> + + <section id="content_type" xreflabel="Preventing untrusted Bugzilla contentfrom executing malicious Javascript code"> + <title>Preventing untrusted Bugzilla content from executing malicious Javascript code</title> + <para>It is possible for a Bugzilla to execute malicious + Javascript code. Due to internationalization concerns, we are + unable to incorporate the code changes necessary to fulfill + the CERT advisory requirements mentioned in <ulink + url="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3">http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</ulink>. Executing the following code snippet from a UNIX command shell will rectify the problem if your Bugzilla installation is intended for an English-speaking audience. As always, be sure your Bugzilla installation has a good backup before making changes, and I recommend you understand what the script is doing before executing it. </para> + <para><programlisting> +bash# cd $BUGZILLA_HOME; for i in `ls *.cgi`; \ + do cat $i | sed 's/Content-type\: text\/html/Content-Type: text\/html\; charset=ISO-8859-1/' >$i.tmp; \ + mv $i.tmp $i; done + </programlisting></para> + <para> + All this one-liner command does is search for all instances of + <quote>Content-type: text/html</quote> and replaces it with + <quote>Content-Type: text/html; charset=ISO-8859-1</quote>. + This specification prevents possible Javascript attacks on the + browser, and is suggested for all English-speaking sites. For + non-english-speaking Bugzilla sites, I suggest changing + <quote>ISO-8859-1</quote>, above, to <quote>UTF-8</quote>. + </para> + </section> + <section> <title>UNIX Installation Instructions History</title> <para> - This document was originally adapted from the Bonsai installation - instructions by Terry Weissman <terry@mozilla.org>. + This document was originally adapted from the Bonsai + installation instructions by Terry Weissman + <terry@mozilla.org>. </para> <para> - The February 25, 1999 re-write of this page was done by Ry4an Brase - <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt, - Martin Pool, & Dan Mosedale (But don't send bug reports to them; - report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi , - project Webtools, component Bugzilla). + The February 25, 1999 re-write of this page was done by Ry4an + Brase <ry4an@ry4an.org>, with some edits by Terry + Weissman, Bryce Nesbitt, Martin Pool, & Dan Mosedale (But + don't send bug reports to them; report them using bugzilla, at + http://bugzilla.mozilla.org/enter_bug.cgi , project Webtools, + component Bugzilla). </para> <para> - This document was heavily modified again Wednesday, March 07 2001 to - reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The - securing MySQL section should be changed to become standard procedure - for Bugzilla installations. + This document was heavily modified again Wednesday, March 07 + 2001 to reflect changes for Bugzilla 2.12 release by Matthew + P. Barnson. The securing MySQL section should be changed to + become standard procedure for Bugzilla installations. </para> <para> - Finally, the README in its entirety was marked up in SGML and included into - the Guide on April 24, 2001 by Matt Barnson. Since that time, it's undergone - extensive modification as Bugzilla grew. + Finally, the README in its entirety was marked up in SGML and + included into the Guide on April 24, 2001 by Matt Barnson. + Since that time, it's undergone extensive modification as + Bugzilla grew. </para> <para> - Comments from people using this Guide for the first time are particularly welcome. + Comments from people using this Guide for the first time are + particularly welcome. </para> </section> </section> @@ -1217,27 +1305,33 @@ bash# ./checksetup.pl picnic. Support for Win32 has improved dramatically in the last few releases, but, if you choose to proceed, you should be a <emphasis>very</emphasis> skilled Windows Systems - Administrator with both strong troubleshooting abilities and - a high tolerance for pain. Bugzilla on NT requires hacking - source code and implementing some advanced utilities. What - follows is the recommended installation procedure for Win32; - additional suggestions are provided in <xref linkend="faq">. + Administrator with strong troubleshooting abilities, a high + tolerance for pain, and moderate perl skills. Bugzilla on NT + requires hacking source code and implementing some advanced + utilities. What follows is the recommended installation + procedure for Win32; additional suggestions are provided in + <xref linkend="faq">. </para> </note> <procedure> <step> <para> - Install <ulink url="http://www.apache.org/">Apache Web Server</ulink> - for Windows. + Install <ulink url="http://www.apache.org/">Apache Web + Server</ulink> for Windows, and copy the Bugzilla files + somewhere Apache can serve them. Please follow all the + instructions referenced in <xref linkend="installation"> + regarding your Apache configuration, particularly + instructions regarding the <quote>AddHandler</quote> + parameter and <quote>ExecCGI</quote>. </para> <note> <para> - You may also use Internet Information Server or Personal Web - Server for this purpose. However, setup is slightly more - difficult. If ActivePerl doesn't seem to handle your file - associations correctly (for .cgi and .pl files), please - consult <xref linkend="faq">. + You may also use Internet Information Server or Personal + Web Server for this purpose. However, setup is quite + different. If ActivePerl doesn't seem to handle your + file associations correctly (for .cgi and .pl files), + please consult <xref linkend="faq">. </para> <para> If you are going to use IIS, if on Windows NT you must @@ -1299,8 +1393,7 @@ bash# ./checksetup.pl Install MySQL for NT. <note> <para> - You can download MySQL for Windows NT from <ulink - url="http://www.mysql.com/">MySQL.com</ulink>. Some find it helpful to use the WinMySqlAdmin utility, included with the download, to set up the database. + You can download MySQL for Windows NT from <ulink url="http://www.mysql.com/">MySQL.com</ulink>. Some find it helpful to use the WinMySqlAdmin utility, included with the download, to set up the database. </para> </note> </para> @@ -1393,13 +1486,21 @@ bash# ./checksetup.pl this line: </para> <para> - "my $webservergid = getgrnam($my_webservergroup); " + <programlisting> +my $webservergid = getgrnam($my_webservergroup); + </programlisting> </para> <para> to </para> <para> - "my $webservergid = $my_webservergroup; " + <programlisting> +my $webservergid = $my_webservergroup; + </programlisting> +or the name of the group you wish to own the files explicitly: + <programlisting> +my $webservergid = 'Administrators' + </programlisting> </para> </step> @@ -1412,8 +1513,7 @@ bash# ./checksetup.pl <step> <para>Edit <filename>localconfig</filename> to suit your requirements. Set <varname>$db_pass</varname> to your - <quote>bugs_password</quote> from <xref - linkend="ntbugs-password">, and <varname>$webservergroup</varname> to <quote>8</quote>.</para> + <quote>bugs_password</quote> from <xref linkend="ntbugs-password">, and <varname>$webservergroup</varname> to <quote>8</quote>.</para> <note> <para>Not sure on the <quote>8</quote> for <varname>$webservergroup</varname> above. If it's @@ -1455,8 +1555,7 @@ bash# ./checksetup.pl <procedure> <step> <para> - Download NTsendmail, available from<ulink - url="http://www.ntsendmail.com/"> www.ntsendmail.com</ulink>. You must have a "real" mail server which allows you to relay off it in your $ENV{"NTsendmail"} (which you should probably place in globals.pl) + Download NTsendmail, available from<ulink url="http://www.ntsendmail.com/"> www.ntsendmail.com</ulink>. You must have a "real" mail server which allows you to relay off it in your $ENV{"NTsendmail"} (which you should probably place in globals.pl) </para> </step> @@ -1503,7 +1602,15 @@ $mail->send($from,$to,$subject,$msg); </programlisting> </para> <note> - <para>The code above needs testing as well to make sure it is correct.</para> + <para> + Some have found success using the commercial product, + <productname>Windmail</productname>. + You could try replacing your sendmail calls with: + <programlisting> +open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log"; + </programlisting> + or something to that effect. + </para> </note> </step> </procedure> @@ -1568,9 +1675,9 @@ exit; <step> <note> <para> - This step is completely optional if you are using IIS or - another web server which only decides on an interpreter - based upon the file extension (.pl), rather than the + This step is optional if you are using IIS or another + web server which only decides on an interpreter based + upon the file extension (.pl), rather than the <quote>shebang</quote> line (#/usr/bonsaitools/bin/perl) </para> </note> @@ -1583,8 +1690,7 @@ exit; utility to speed part of this procedure, available in the <xref linkend="patches"> section of The Bugzilla Guide. However, it requires the Cygwin GNU-compatible environment - for Win32 be set up in order to work. See <ulink - url="http://www.cygwin.com/">http://www.cygwin.com/</ulink> for details on obtaining Cygwin. + for Win32 be set up in order to work. See <ulink url="http://www.cygwin.com/">http://www.cygwin.com/</ulink> for details on obtaining Cygwin. </para> </step> @@ -1604,10 +1710,11 @@ system ("perl processmail.pl",@ARGLIST); <tip> <para> - If you are using IIS 5.0 or higher, you must add cgi + If you are using IIS or Personal Web Server, you must add cgi relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), - such as: <programlisting> + such as: + <programlisting> .cgi to: <perl install directory>\perl.exe %s %s .pl to: <perl install directory>\perl.exe %s %s GET,HEAD,POST @@ -1625,11 +1732,10 @@ GET,HEAD,POST From Andrew Pearson: <blockquote> <para> - "You can make Bugzilla work with Personal Web Server for - Windows 98 and higher, as well as for IIS 4.0. Microsoft has - information available at - <ulink url=" http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"> - http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</ulink> + You can make Bugzilla work with Personal Web Server for + Windows 98 and higher, as well as for IIS 4.0. + Microsoft has information available at <ulink url=" + http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP"> http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP</ulink> </para> <para> Basically you need to add two String Keys in the @@ -1651,119 +1757,28 @@ GET,HEAD,POST </para> </tip> <tip> - <para>"Brian" had this to add, about upgrading to Bugzilla 2.12 from previous versions:</para> - <blockquote> - <para> - 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). - </para> - <para> - In checksetup.pl, I did the following... - </para> - <procedure> - <step> - <programlisting> -my $webservergid = getgrnam($my_webservergroup); + <para> + If attempting to run Bugzilla 2.12 or older, you will need + to remove encrypt() calls from the Perl source. This is + <emphasis>not necessary</emphasis> for Bugzilla 2.13 and + later. + <example> + <title>Removing encrypt() for Windows NT Bugzilla version + 2.12 or earlier</title> + <para> + Replace this: + <programlisting> +SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); +my $enteredcryptpwd = FetchOneColumn(); </programlisting> - <para>to</para> - <programlisting> -my $webservergid = 'Administrators' + with this: + <programlisting> +my $enteredcryptpwd = $enteredpwd </programlisting> - </step> - <step> - <para> - I then ran checksetup.pl - </para> - </step> - <step> - <para> - I removed all the encrypt() - <example> - <title>Removing encrypt() for Windows NT installations</title> - <para> - Replace this: - <programlisting> -SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . - SqlQuote(substr($realcryptpwd, 0, 2)) . ")"); -my $enteredcryptpwd = FetchOneColumn(); - </programlisting> - with this: - <programlisting> -my $enteredcryptpwd = $enteredpwd - </programlisting> - in cgi.pl. - </para> - </example> - </para> - </step> - <step> - <para> - I renamed processmail to processmail.pl - </para> - </step> - <step> - <para> - I altered the sendmail statements to windmail: - <programlisting> -open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log"; - </programlisting> - </para> - <para> - The quotes around the dir is for the spaces. mail.log is for the output - </para> - </step> - </procedure> - </blockquote> - </tip> - <tip> - <para> - This was some late breaking information from Jan Evert. Sorry for the lack of formatting. + in cgi.pl. + </para> + </example> </para> - <literallayout> -I'm busy installing bugzilla on a WinNT machine and I thought I'd notify you -at this moment of the commments I have to section 2.2.1 of the bugzilla -guide (at http://www.trilobyte.net/barnsons/html/). - -Step 1: -I've used apache, installation is really straightforward. -After reading the Unix installation instructions, I found that it is -necessary to add the ExecCGI option to the bugzilla directory. Also the -'AddHandler' line for .cgi is by default commented out. - -Step 3: although just a detail, 'ppm install <module%gt;' will also work -(without .ppd). And, it can also download these automatically from -ActiveState. - -Step 4: although I have cygwin installed, it seems that it is not necessary. -On my machine cygwin is not in the PATH and everything seems to work as -expected. -However, I've not used everything yet. - -Step 6: the 'bugs_password' given in SQL command d needs to be edited into -localconfig later on (Step 7) if the password is not empty. I've also edited -it into globals.pl, but I'm not sure that is needed. In both places, the -variable is named db_pass. - -Step 8: all the sendmail replacements mentioned are not as simple as -described there. Since I am not familiar (yet) with perl, I don't have any -mail working yet. - -Step 9: in globals.pl the encrypt() call can be replaced by just the -unencrypted password. In CGI.pl, the complete SQL command can be removed. - -Step 11: I've only changed the #! lines in *.cgi. I haven't noticed problems -with the system() call yet. -There seem to be only four system() called programs: processmail.pl (handled -by step 10), syncshadowdb (which should probably get the same treatment as -processmail.pl), diff and mysqldump. The last one is only needed with the -shadowdb feature (which I don't use). - -There seems to be one step missing: copying the bugzilla files somehwere -that apache can serve them. - -Just noticed the updated guide... Brian's comment is new. His first comment -will work, but opens up a huge security hole. - </literallayout> </tip> </section> </section> diff --git a/docs/xml/integration.xml b/docs/xml/integration.xml index c7aa78f82..e0547c365 100644 --- a/docs/xml/integration.xml +++ b/docs/xml/integration.xml @@ -5,49 +5,59 @@ <chapter id="integration"> <title>Integrating Bugzilla with Third-Party Tools</title> - <section id="bonsai"> + <section id="bonsai" xreflabel="Bonsai, the Mozilla automated CVS management system"> <title>Bonsai</title> - <para>We need Bonsai integration information.</para> + <para>Bonsai is a web-based tool for managing <xref + linkend="cvs"> + . Using Bonsai, administrators can control open/closed status + of trees, query a fast relational database back-end for change, + branch, and comment information, and view changes made since the + last time the tree was closed. These kinds of changes cause the + engineer responsible to be <quote>on the hook</quote> (include + cool URL link here for Hook policies at mozilla.org). Bonsai + also includes gateways to <xref + linkend="tinderbox"> and Bugzilla </para> </section> - <section id="cvs"> + <section id="cvs" xreflabel="CVS, the Concurrent Versioning System"> <title>CVS</title> - <para>CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</para> + <para>CVS integration is best accomplished, at this point, using + the Bugzilla Email Gateway. There have been some files + submitted to allow greater CVS integration, but we need to make + certain that Bugzilla is not tied into one particular software + management package.</para> + <para> + Follow the instructions in the FAQ for enabling Bugzilla e-mail + integration. Ensure that your check-in script sends an email to + your Bugzilla e-mail gateway with the subject of <quote>[Bug + XXXX]</quote>, and you can have CVS check-in comments append + to your Bugzilla bug. If you have your check-in script include + an @resolution field, you can even change the Bugzilla bug + state. + </para> </section> - <section id="scm"> + <section id="scm" xreflabel="Perforce SCM (Fast Software Configuration Management System, a powerful commercial alternative to CVS"> <title>Perforce SCM</title> <para> - You can find the project page for Bugzilla and Teamtrack Perforce integration 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. + You can find the project page for Bugzilla and Teamtrack + Perforce integration (p4dti) at: <ulink + url="http://www.ravenbrook.com/project/p4dti/"> http://www.ravenbrook.com/project/p4dti</ulink> . <quote>p4dti</quote> is now an officially supported product from Perforce, and you can find the "Perforce Public Depot" p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html"> http://public.perforce.com/public/perforce/p4dti/index.html</ulink>. </para> <para> - 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. + Integration of Perforce with Bugzilla, once patches are applied, + is seamless. Perforce replication information will appear below + the comments of each bug. Be certain you have a matching set of + patches for the Bugzilla version you are installing. p4dti is + designed to support multiple defect trackers, and maintains its + own documentation for it. Please consult the pages linked above + for further information. </para> </section> - <section id="tinderbox"> - <title>Tinderbox</title> - <para>We need Tinderbox integration information</para> + <section id="tinderbox" xreflabel="Tinderbox, the Mozilla automated build management system"> + <title>Tinderbox/Tinderbox2</title> + <para>We need Tinderbox integration information.</para> </section> </chapter> diff --git a/docs/xml/patches.xml b/docs/xml/patches.xml index 8ebfdee15..3a1ce90d2 100644 --- a/docs/xml/patches.xml +++ b/docs/xml/patches.xml @@ -3,6 +3,40 @@ <appendix id="patches" xreflabel="Useful Patches and Utilities for Bugzilla"> <title>Useful Patches and Utilities for Bugzilla</title> + <para>Are you looking for a way to put your Bugzilla into overdrive? Catch some of the niftiest tricks here in this section.</para> + + <section id="rewrite" xreflabel="Apache mod_rewrite magic"> + <title>Apache <filename>mod_rewrite</filename> magic</title> + <para>Apache's <filename>mod_rewrite</filename> module lets you do some truly amazing things with URL rewriting. Here are a couple of examples of what you can do.</para> + <orderedlist> + <listitem> + <para> + Make it so if someone types + <computeroutput>http://www.foo.com/12345</computeroutput>, + Bugzilla spits back + http://www.foo.com/show_bug.cgi?id=12345. Try setting up + your VirtualHost section for Bugzilla with a rule like + this:</para> + <programlisting> +<![CDATA[ +<VirtualHost 12.34.56.78> +RewriteEngine On +RewriteRule ^/([0-9]+)$ http://foo.bar.com/show_bug.cgi?id=$1 [L,R] +</VirtualHost> +]]> + </programlisting> + + </listitem> + <listitem> + <para>There are many, many more things you can do with + mod_rewrite. As time goes on, I will include many more in + the Guide. For now, though, please refer to the mod_rewrite + documentation at <ulink + url="http://www.apache.org">http://www.apache.org</ulink></para> + </listitem> + </orderedlist> + </section> + <section id="setperl" xreflabel="The setperl.csh Utility"> <title>The setperl.csh Utility</title> <para> You can use the "setperl.csh" utility to quickly and diff --git a/docs/xml/using.xml b/docs/xml/using.xml index fd5901196..91a7658cd 100644 --- a/docs/xml/using.xml +++ b/docs/xml/using.xml @@ -31,7 +31,7 @@ Chapter: Using Bugzilla <title>Using Bugzilla</title> <epigraph> <para> - What, Why, How, & What's in it for me? + What, Why, How, & Where? </para> </epigraph> @@ -92,8 +92,10 @@ system against which all others are measured. </listitem> <listitem> <para> - available integration with automated software configuration management systems, including - Perforce and CVS + available integration with automated software + configuration management systems, including Perforce and + CVS (through the Bugzilla email interface and + checkin/checkout scripts) </para> </listitem> <listitem> @@ -104,23 +106,28 @@ system against which all others are measured. </itemizedlist> </para> <para> - Despite its current robustness and popularity, however, Bugzilla - faces some near-term challenges, such as reliance on a single database, a lack of - abstraction of the user interface and program logic, verbose email bug - notifications, a powerful but daunting query interface, little reporting configurability, - problems with extremely large queries, some unsupportable bug resolution options, - no internationalization, and dependence on some nonstandard libraries. + Despite its current robustness and popularity, Bugzilla faces + some near-term challenges, such as reliance on a single + database, a lack of abstraction of the user interface and + program logic, verbose email bug notifications, a powerful but + daunting query interface, little reporting configurability, + problems with extremely large queries, some unsupportable bug + resolution options, little internationalization (although non-US + character sets are accepted for comments), 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". + Some recent headway has been made on the query front, however. + If you are using the latest version of Bugzilla, you should see + a <quote>simple search</quote> 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. + Despite these small problems, Bugzilla is very hard to beat. It + is under <emphasis>very</emphasis> active development to address + the current issues, and continually gains new features. </para> </section> @@ -132,50 +139,57 @@ system against which all others are measured. </para> </epigraph> <para> - For many years, defect-tracking software has remained principally the domain - of large software development houses. Even then, most shops never bothered - with bug-tracking software, and instead simply relied on shared lists and - email to monitor the status of defects. This procedure is error-prone and - tends to cause those bugs judged least significant by developers to be + For many years, defect-tracking software has remained + principally the domain of large software development houses. + Even then, most shops never bothered with bug-tracking software, + and instead simply relied on shared lists and email to monitor + the status of defects. This procedure is error-prone and tends + to cause those bugs judged least significant by developers to be dropped or ignored. </para> <para> - These days, many companies are finding that integrated defect-tracking - systems reduce downtime, increase productivity, and raise customer - satisfaction with their systems. Along with full disclosure, an open - bug-tracker allows manufacturers to keep in touch with their clients - and resellers, to communicate about problems effectively throughout - the data management chain. Many corporations have also discovered that - defect-tracking helps reduce costs by providing IT support accountability, - telephone support knowledge bases, and a common, well-understood system - for accounting for unusual system or software issues. + These days, many companies are finding that integrated + defect-tracking systems reduce downtime, increase productivity, + and raise customer satisfaction with their systems. Along with + full disclosure, an open bug-tracker allows manufacturers to + keep in touch with their clients and resellers, to communicate + about problems effectively throughout the data management chain. + Many corporations have also discovered that defect-tracking + helps reduce costs by providing IT support accountability, + telephone support knowledge bases, and a common, well-understood + system for accounting for unusual system or software issues. </para> <para> But why should <emphasis>you</emphasis> use Bugzilla? </para> <para> - 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 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 + 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 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 </para> <para> - Bugzilla can dramatically increase the productivity and accountability - of individual employees by providing a documented workflow and positive - feedback for good performance. How many times do you wake up in the - morning, remembering that you were supposed to do *something* today, - but you just can't quite remember? Put it in Bugzilla, and you have a record - of it from which you can extrapolate milestones, predict product versions - for integration, and by using Bugzilla's e-mail integration features - be able to follow the discussion trail that led to critical decisions. + Bugzilla can dramatically increase the productivity and + accountability of individual employees by providing a documented + workflow and positive feedback for good performance. How many + times do you wake up in the morning, remembering that you were + supposed to do <emphasis>something</emphasis> today, but you + just can't quite remember? Put it in Bugzilla, and you have a + record of it from which you can extrapolate milestones, predict + product versions for integration, and by using Bugzilla's e-mail + integration features be able to follow the discussion trail that + led to critical decisions. </para> <para> - Ultimately, Bugzilla puts the power in your hands to improve your value - to your employer or business while providing a usable framework for your natural - attention to detail and knowledge store to flourish. + Ultimately, Bugzilla puts the power in your hands to improve + your value to your employer or business while providing a usable + framework for your natural attention to detail and knowledge + store to flourish. </para> </section> @@ -189,46 +203,45 @@ system against which all others are measured. <para> 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 - developing end-user mastery of Bugzilla, so you may fully enjoy the benefits - afforded by using this reliable open-source bug-tracking software. + 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 developing end-user + mastery of Bugzilla, so you may fully enjoy the benefits + afforded by using this reliable open-source bug-tracking + software. </para> <para> - Throughout this portion of the Guide, we will refer to user account - options available at the Bugzilla test installation, + Throughout this portion of the Guide, we will refer to user + account options available at the Bugzilla test installation, <ulink url="http://landfill.tequilarista.org/"> - landfill.tequilarista.org</ulink>. + 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> + 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. Additionally, - Landfill often runs cutting-edge versions of Bugzilla for testing, so some things - may work slightly differently than mentioned here. + </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. 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"> <title>Create a Bugzilla Account</title> <para> - First things first! If you want to use Bugzilla, first you need to create - an account. Consult with the administrator responsible for your installation - of Bugzilla for the URL you should use to access it. - If you're test-driving the end-user Bugzilla experience, use this URL: - <ulink url="http://landfill.tequilarista.org/bugzilla-tip/"> - http://landfill.tequilarista.org/bugzilla-tip/</ulink> + First things first! If you want to use Bugzilla, first you + need to create an account. Consult with the administrator + responsible for your installation of Bugzilla for the URL you + should use to access it. If you're test-driving the end-user + Bugzilla experience, use this URL: <ulink + url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink> </para> <orderedlist> <listitem> @@ -238,64 +251,81 @@ system against which all others are measured. </listitem> <listitem> <para> - Enter your "E-mail address" and "Real Name" (or whatever name you want to call yourself) - in the spaces provided, then select the "Create Account" button. + Enter your "E-mail address" and "Real Name" (or whatever + name you want to call yourself) in the spaces provided, + then select the "Create Account" button. </para> </listitem> <listitem> <para> - Within 5-10 minutes, you should receive an email to the address you provided above, - which contains your login name (generally the same as the email address), and - a password you can use to access your account. This password is randomly generated, - and should be changed at your nearest opportunity (we'll go into how to do it later). + Within moments, you should receive an email to the address + you provided above, which contains your login name + (generally the same as the email address), and a password + you can use to access your account. This password is + randomly generated, and should be changed at your nearest + opportunity (we'll go into how to do it later). </para> </listitem> <listitem> <para> - Click the "Log In" link in the yellow area at the bottom of the page in your browser, - then enter your "E-mail address" and "Password" you just received into the spaces provided, - and select "Login". + Click the <quote>Log In</quote> link in the yellow area at + the bottom of the page in your browser, then enter your + <quote>E-mail address</quote> and <quote>Password</quote> + you just received into the spaces provided, and select + <quote>Login</quote>. <note> <para> - If you ever forget your password, you can come back to this page, enter your - "E-mail address", then select the "E-mail me a password" button to have your password - mailed to you again so that you can login. + If you ever forget your password, you can come back to + this page, enter your <quote>E-mail address</quote>, + then select the <quote>E-mail me a password</quote> + button to have your password mailed to you again so + that you can login. </para> </note> <caution> <para> - Many modern browsers include an "Auto-Complete" or "Form Fill" feature to - remember the user names and passwords you type in at many sites. Unfortunately, - sometimes they attempt to "guess" what you will put in as your password, and guess - wrong. If you notice a text box is already filled out, please overwrite the contents - of the text box so you can be sure to input the correct information. + Many modern browsers include an + <quote>Auto-Complete</quote> or <quote>Form + Fill</quote> feature to remember the user names and + passwords you type in at many sites. Unfortunately, + sometimes they attempt to guess what you will put in + as your password, and guess wrong. If you notice a + text box is already filled out, please overwrite the + contents of the text box so you can be sure to input + the correct information. </para> </caution> </para> </listitem> </orderedlist> <para> - Congratulations! If you followed these directions, you now are the - proud owner of a user account on landfill.tequilarista.org (Landfill) or - your local Bugzilla install. You should now see in your browser a - page called the "Bugzilla Query Page". It may look daunting, but - with this Guide to walk you through it, you will master it in no time. + Congratulations! If you followed these directions, you now + are the proud owner of a user account on + landfill.tequilarista.org (Landfill) or your local Bugzilla + install. You should now see in your browser a page called the + <quote>Bugzilla Query Page</quote>. It may look daunting, but with this + Guide to walk you through it, you will master it in no time. </para> </section> <section id="query"> <title>The Bugzilla Query Page</title> <para> - The Bugzilla Query Page is the heart and soul of Bugzilla. It is the master - interface where you can find any bug report, comment, or patch currently in the Bugzilla - system. We'll go into how to create your own bug report later on. + The Bugzilla Query Page is the heart and soul of the Bugzilla + user experience. It is the master interface where you can + find any bug report, comment, or patch currently in the + Bugzilla system. We'll go into how to create your own bug + report later on. </para> <para> - There are efforts underway to simplify query usage. If you have a local installation - of Bugzilla 2.12 or higher, you should have "quicksearch.html" available - to use and simplify your searches. There is also, or shortly will be, a helper - for the query interface, called "queryhelp.cgi". Landfill tends to run the latest code, - so these two utilities should be available there for your perusal. + There are efforts underway to simplify query usage. If you + have a local installation of Bugzilla 2.12 or higher, you + should have <filename>quicksearch.html</filename> available to + use and simplify your searches. There is also a helper for + the query interface, called + <filename>queryhelp.cgi</filename>. Landfill tends to run the + latest code, so these two utilities should be available there + for your perusal. </para> <para> At this point, please visit the main Bugzilla site, @@ -303,47 +333,57 @@ system against which all others are measured. bugzilla.mozilla.org</ulink>, to see a more fleshed-out query page. </para> <para> - The first thing you need to notice about the Bugzilla Query Page is that - nearly every box you see on your screen has a hyperlink nearby, explaining what - it is or what it does. Near the upper-left-hand corner of your browser window - you should see the word "Status" underlined. Select it. + The first thing you need to notice about the Bugzilla Query + Page is that nearly every box you see on your screen has a + hyperlink nearby, explaining what it is or what it does. Near + the upper-left-hand corner of your browser window you should + see the word <quote>Status</quote> underlined. Select it. </para> <para> - Notice the page that popped up? Every underlined word you see on your screen - is a hyperlink that will take you to context-sensitive help. - Click around for a while, and learn what everything here does. To return - to the query interface after pulling up a help page, use the "Back" button in - your browser. + Notice the page that popped up? Every underlined word you see + on your screen is a hyperlink that will take you to + context-sensitive help. Click around for a while, and learn + what everything here does. To return to the query interface + after pulling up a help page, use the <quote>Back</quote> + button in your browser. </para> <para> - I'm sure that after checking out the online help, you are now an Expert - on the Bugzilla Query Page. If, however, you feel you haven't mastered it yet, - let me walk you through making a few successful queries to find out what there - are in the Bugzilla bug-tracking system itself. + I'm sure that after checking out the online help, you are now + an expert on the Bugzilla Query Page. If, however, you feel + you haven't mastered it yet, let me walk you through making a + few successful queries to find out what there are in the + Bugzilla bug-tracking system itself. </para> <orderedlist> <listitem> <para> - Ensure you are back on the "Bugzilla Query Page" - Do nothing in the boxes marked "Status", "Resolution", "Platform", "OpSys", - "Priority", or "Severity". The default query for "Status" is to find all bugs that - are NEW, ASSIGNED, or REOPENED, which is what we want. If you don't select anything - in the other 5 scrollboxes there, then you are saying that "any of these are OK"; - we're not locking ourselves into only finding bugs on the "DEC" Platform, or "Windows 95" - OpSys (Operating System). You're smart, I think you have it figured out. + Ensure you are back on the <quote>Bugzilla Query + Page</quote>. Do nothing in the boxes marked "Status", + "Resolution", "Platform", "OpSys", "Priority", or + "Severity". The default query for "Status" is to find all + bugs that are NEW, ASSIGNED, or REOPENED, which is what we + want. If you don't select anything in the other 5 + scrollboxes there, then you are saying that "any of these + are OK"; we're not locking ourselves into only finding + bugs on the "DEC" Platform, or "Windows 95" OpSys + (Operating System). You're smart, I think you have it + figured out. </para> <para> - Basically, selecting <emphasis>anything</emphasis> on the query page narrows your search - down. Leaving stuff unselected, or text boxes unfilled, broadens your search! + Basically, selecting <emphasis>anything</emphasis> on the + query page narrows your search down. Leaving stuff + unselected, or text boxes unfilled, broadens your search. </para> </listitem> <listitem> <para> - You see the box immediately below the top six boxes that contains an "Email" text box, - with the words "matching as", a drop-down selection box, then some checkboxes with - "Assigned To" checked by default? This allows you to filter your search down based upon - email address. Let's put my email address in there, and see what happens. + You see the box immediately below the top six boxes that + contains an "Email" text box, with the words "matching + as", a drop-down selection box, then some checkboxes with + "Assigned To" checked by default? This allows you to + filter your search down based upon email address. Let's + put my email address in there, and see what happens. </para> <para> Type "barnboy@trilobyte.net" in the top Email text box. @@ -352,47 +392,55 @@ system against which all others are measured. <listitem> <para> - Let's narrow the search some more. Scroll down until you find the box with the word - "Program" over the top of it. This is where we can narrow our search down to only - specific products (software programs or product lines) in our Bugzilla database. - Please notice the box is a <emphasis>scrollbox</emphasis>. Using the down arrow on the - scrollbox, scroll down until you can see an entry called "Webtools". Select this entry. + Let's narrow the search some more. Scroll down until you + find the box with the word "Program" over the top of it. + This is where we can narrow our search down to only + specific products (software programs or product lines) in + our Bugzilla database. Please notice the box is a + <emphasis>scrollbox</emphasis>. Using the down arrow on + the scrollbox, scroll down until you can see an entry + called "Webtools". Select this entry. </para> </listitem> <listitem> <para> - Did you notice that some of the boxes to the right changed when you selected "Webtools"? - Every Program (or Product) has different Versions, Components, and Target Milestones associated - with it. A "Version" is the number of a software program. + Did you notice that some of the boxes to the right changed + when you selected "Webtools"? Every Program (or Product) + has different Versions, Components, and Target Milestones + associated with it. A "Version" is the number of a + software program. <example> <title>Some Famous Software Versions</title> <informalexample> <para> - Do you remember the hype in 1995 when Microsoft Windows 95(r) was released? - It may have been several years - ago, but Microsoft(tm) spent over $300 Million advertising this new Version of their - software. Three years later, they released Microsoft Windows 98(r), - another new version, to great fanfare, and then in 2000 quietly - released Microsoft Windows ME(Millenium Edition)(r). + Do you remember the hype in 1995 when Microsoft + Windows 95(r) was released? It may have been several + years ago, but Microsoft(tm) spent over $300 Million + advertising this new Version of their software. + Three years later, they released Microsoft Windows + 98(r), another new version, to great fanfare, and + then in 2000 quietly released Microsoft Windows + ME(Millenium Edition)(r). </para> <para> - Software "Versions" help a manufacturer differentiate - their current product from their - previous products. Most do not identify their products - by the year they were released. - Instead, the "original" version of their software will - often be numbered "1.0", with - small bug-fix releases on subsequent tenths of a digit. In most cases, it's not - a decimal number; for instance, often 1.9 is an <emphasis>older</emphasis> version - of the software than 1.11, - but is a <emphasis>newer</emphasis> version than 1.1.1. + Software "Versions" help a manufacturer + differentiate their current product from their + previous products. Most do not identify their + products by the year they were released. Instead, + the "original" version of their software will often + be numbered "1.0", with small bug-fix releases on + subsequent tenths of a digit. In most cases, it's + not a decimal number; for instance, often 1.9 is an + <emphasis>older</emphasis> version of the software + than 1.11, but is a <emphasis>newer</emphasis> + version than 1.1.1. </para> <para> - In general, a "Version" in Bugzilla should refer to - <emphasis>released</emphasis> - products, not products that have not yet been released - to the public. Forthcoming products - are what the Target Milestone field is for. + In general, a "Version" in Bugzilla should refer to + <emphasis>released</emphasis> products, not products + that have not yet been released to the public. + Forthcoming products are what the Target Milestone + field is for. </para> </informalexample> </example> @@ -438,26 +486,25 @@ system against which all others are measured. </example> </para> <para> - A "Milestone", or "Target Milestone" is a often a planned future "Version" of a - product. In many cases, though, Milestones simply represent significant dates for - a developer. Having certain features in your Product is frequently - tied to revenue (money) - the developer will receive if the features work by the time she - reaches the Target Milestone. - Target Milestones are a great tool to organize your time. - If someone will pay you $100,000 for - incorporating certain features by a certain date, - those features by that Milestone date become - a very high priority. Milestones tend to be highly malleable creatures, - though, that appear - to be in reach but are out of reach by the time the important day arrives. + A "Milestone", or "Target Milestone" is a often a planned + future "Version" of a product. In many cases, though, + Milestones simply represent significant dates for a + developer. Having certain features in your Product is + frequently tied to revenue (money) the developer will + receive if the features work by the time she reaches the + Target Milestone. Target Milestones are a great tool to + organize your time. If someone will pay you $100,000 for + incorporating certain features by a certain date, those + features by that Milestone date become a very high + priority. Milestones tend to be highly malleable + creatures, though, that appear to be in reach but are out + of reach by the time the important day arrives. </para> <para> - The Bugzilla Project has set up Milestones for future - Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, - a Target Milestone can just as easily be a specific date, - code name, or weird alphanumeric - combination, like "M19". + The Bugzilla Project has set up Milestones for future + Bugzilla versions 2.14, 2.16, 2.18, 3.0, etc. However, a + Target Milestone can just as easily be a specific date, + code name, or weird alphanumeric combination, like "M19". </para> </listitem> @@ -475,56 +522,54 @@ system against which all others are measured. </listitem> <listitem> <para> - Congratulations! You've completed your first Query, and have before you the Bug List - of the author of this Guide, Matthew P. Barnson (barnboy@trilobyte.net). If I'm - doing well, - you'll have a cryptic "Zarro Boogs Found" message on your screen. It is just - a happy hacker's way of saying "Zero Bugs Found". However, I am fairly certain I will + Congratulations! You've completed your first Query, and + have before you the Bug List of the author of this Guide, + Matthew P. Barnson (barnboy@trilobyte.net). If I'm doing + well, you'll have a cryptic "Zarro Boogs Found" message on + your screen. It is just a happy hacker's way of saying + "Zero Bugs Found". However, I am fairly certain I will always have some bugs assigned to me that aren't done yet, so you won't often see that message! </para> </listitem> </orderedlist> <para> - I encourage you to click the bug numbers in the left-hand column and examine - my bugs. Also notice that if you click the underlined - links near the top of this page, they do - not take you to context-sensitive help here, - but instead sort the columns of bugs on the screen! - When you need to sort your bugs by priority, severity, - or the people they are assigned to, this - is a tremendous timesaver. + I encourage you to click the bug numbers in the left-hand + column and examine my bugs. Also notice that if you click the + underlined links near the top of this page, they do not take + you to context-sensitive help here, but instead sort the + columns of bugs on the screen! When you need to sort your bugs + by priority, severity, or the people they are assigned to, + this is a tremendous timesaver. </para> <para> A couple more interesting things about the Bug List page: <simplelist> - <member><emphasis>Change Columns</emphasis>: - by selecting this link, you can show all kinds - of information in the Bug List</member> - <member><emphasis>Change several bugs at once</emphasis>: - If you have sufficient rights to change all - the bugs shown in the Bug List, you can mass-modify them. - This is a big time-saver.</member> - <member><emphasis>Send mail to bug owners</emphasis>: - If you have many related bugs, you can request - an update from every person who owns the bugs in - the Bug List asking them the status.</member> - <member><emphasis>Edit this query</emphasis>: - If you didn't get exactly the results you were looking for, - you can return to the Query page through this link and make - small revisions to the query you just made so - you get more accurate results.</member> + <member><emphasis>Change Columns</emphasis>: by selecting + this link, you can show all kinds of information in the + Bug List</member> + <member><emphasis>Change several bugs at once</emphasis>: If + you have sufficient rights to change all the bugs shown in + the Bug List, you can mass-modify them. This is a big + time-saver.</member> + <member><emphasis>Send mail to bug owners</emphasis>: If you + have many related bugs, you can request an update from + every person who owns the bugs in the Bug List asking them + the status.</member> + <member><emphasis>Edit this query</emphasis>: If you didn't + get exactly the results you were looking for, you can + return to the Query page through this link and make small + revisions to the query you just made so you get more + accurate results.</member> </simplelist> </para> <note> <para> - There are many more options to the Bugzilla Query Page - and the Bug List than I have shown you. - But this should be enough for you to learn to get around. - I encourage you to check out the - <ulink url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink> - to learn about the Anatomy - and Life Cycle of a Bug before continuing. + There are many more options to the Bugzilla Query Page and + the Bug List than I have shown you. But this should be + enough for you to learn to get around. I encourage you to + check out the <ulink + url="http://www.mozilla.org/bugs/">Bugzilla Home Page</ulink> to learn about the Anatomy and Life Cycle of a Bug before continuing. </para> </note> </section> @@ -539,37 +584,35 @@ system against which all others are measured. <section id="bug_writing"> <title>Writing a Great Bug Report</title> <para> - Before we plunge into writing your first bug report, I encourage you to read - <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">Mozilla.org's Bug - Writing Guidelines</ulink>. While some of the advice is Mozilla-specific, the basic - principles of reporting Reproducible, Specific bugs, isolating the Product you are - using, the Version of the Product, the Component which failed, the Hardware Platform, and - Operating System you were using at the time of the failure go a long way toward ensuring accurate, - responsible fixes for the bug that bit you. + Before we plunge into writing your first bug report, I + encourage you to read some bug-writing guidelines. If you + are reading this document as part of a Bugzilla CVS checkout + or un-tarred Bugzilla distribution, you should be able to + read them by clicking <ulink + url="../../bugwritinghelp.html">here</ulink>. If you are reading this online, check out the Mozilla.org bug-writing guidelines at <ulink url="http://www.mozilla.org/quality/bug-writing-guidelines.html">http://www.mozilla.org/quality/bug-writing-guidelines.html</ulink>. While some of the advice is Mozilla-specific, the basic principles of reporting Reproducible, Specific bugs, isolating the Product you are using, the Version of the Product, the Component which failed, the Hardware Platform, and Operating System you were using at the time of the failure go a long way toward ensuring accurate, responsible fixes for the bug that bit you. </para> <para> - While you are at it, why not learn how to find previously reported bugs? Mozilla.org - has published a great tutorial on finding duplicate bugs, available at - <ulink url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"> - http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>. + While you are at it, why not learn how to find previously + reported bugs? Mozilla.org has published a great tutorial + on finding duplicate bugs, available at <ulink + url="http://www.mozilla.org/quality/help/beginning-duplicate-finding.html"> http://www.mozilla.org/quality/help/beginning-duplicate-finding.html</ulink>. </para> <para> - I realize this was a lot to read. However, understanding the mentality of writing - great bug reports will help us on the next part! + I realize this was a lot to read. However, understanding + the mentality of writing great bug reports will help us on + the next part! </para> <orderedlist> <listitem> <para> - Go back to <ulink url="http://landfill.tequilarista.org/bugzilla-tip/"> - http://landfill.tequilarista.org/bugzilla-tip/</ulink> - in your browser. + Go back to <ulink + url="http://landfill.tequilarista.org/bugzilla-tip/"> http://landfill.tequilarista.org/bugzilla-tip/</ulink> in your browser. </para> </listitem> <listitem> <para> - Select the - <ulink url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> - Enter a new bug report</ulink> link. + Select the <ulink + url="http://landfill.tequilarista.org/bugzilla-tip/enter_bug.cgi"> Enter a new bug report</ulink> link. </para> </listitem> <listitem> @@ -579,11 +622,11 @@ system against which all others are measured. </listitem> <listitem> <para> - Now you should be at the "Enter Bug" form. - The "reporter" should have been automatically filled out - for you (or else Bugzilla prompted you to Log In again - -- you did keep the email with your username - and password, didn't you?). + Now you should be at the "Enter Bug" form. The + "reporter" should have been automatically filled out for + you (or else Bugzilla prompted you to Log In again -- + you did keep the email with your username and password, + didn't you?). </para> </listitem> <listitem> @@ -593,107 +636,97 @@ system against which all others are measured. </listitem> <listitem> <para> - Bugzilla should have made reasonable guesses, based upon your browser, - for the "Platform" and "OS" drop-down - boxes. If those are wrong, change them -- if you're on an SGI box - running IRIX, we want to know! + Bugzilla should have made reasonable guesses, based upon + your browser, for the "Platform" and "OS" drop-down + boxes. If those are wrong, change them -- if you're on + an SGI box running IRIX, we want to know! </para> </listitem> <listitem> <para> - Fill in the "Assigned To" box with the email address you provided earlier. - This way you don't end up sending copies of your bug to lots of other people, - since it's just a test bug. + Fill in the "Assigned To" box with the email address you + provided earlier. This way you don't end up sending + copies of your bug to lots of other people, since it's + just a test bug. </para> </listitem> <listitem> <para> - Leave the "CC" text box blank. - Fill in the "URL" box with "http://www.mozilla.org". + Leave the "CC" text box blank. Fill in the "URL" box + with "http://www.mozilla.org". </para> </listitem> <listitem> <para> - Enter "The Bugzilla Guide" in the Summary text box, - and place any comments you have on this - tutorial, or the Guide in general, into the Description box. + Enter "The Bugzilla Guide" in the Summary text box, and + place any comments you have on this tutorial, or the + Guide in general, into the Description box. </para> </listitem> </orderedlist> <para> - Voila! Select "Commit" and send in your bug report! - Next we'll look at resolving bugs. + Voila! Select "Commit" and send in your bug report! Next + we'll look at resolving bugs. </para> </section> <section id="bug_manage"> <title>Managing your Bug Reports</title> <para> - OK, you should have a link to the bug you just created near the top of your page. - It should say - "Bug XXXX posted", with a link to the right saying "Back to BUG# XXXX". - Select this link. + OK, you should have a link to the bug you just created near + the top of your page. It should say "Bug XXXX posted", with + a link to the right saying "Back to BUG# XXXX". Select this + link. </para> <orderedlist> <listitem> <para> - Scroll down a bit on the subsequent page, - until you see the "Resolve bug, changing resolution to (dropdown box). - Normally, you would - "Accept bug (change status to ASSIGNED)", fix it, and then resolve. - But in this case, we're - going to short-circuit the process because this wasn't a real bug. - Change the dropdown next to - "Resolve Bug" to "INVALID", make sure the radio button is - marked next to "Resolve Bug", then - click "Commit". + Scroll down a bit on the subsequent page, until you see + the "Resolve bug, changing resolution to (dropdown box). + Normally, you would "Accept bug (change status to + ASSIGNED)", fix it, and then resolve. But in this case, + we're going to short-circuit the process because this + wasn't a real bug. Change the dropdown next to "Resolve + Bug" to "INVALID", make sure the radio button is marked + next to "Resolve Bug", then click "Commit". </para> </listitem> <listitem> <para> - Hey! It said it couldn't take the change in a big red box! - That's right, you must specify - a Comment in order to make this change. Select the "Back" - button in your browser, add a - Comment, then try Resolving the bug with INVALID status again. - This time it should work. + Hey! It said it couldn't take the change in a big red + box! That's right, you must specify a Comment in order + to make this change. Select the "Back" button in your + browser, add a Comment, then try Resolving the bug with + INVALID status again. This time it should work. </para> </listitem> </orderedlist> <para> You have now learned the basics of Bugzilla navigation, - entering a bug, and bug maintenance. - I encourage you to explore these features, and see what you can do with them! - We'll spend no more time on individual Bugs or Queries from this point on, so you are - on your own there. + entering a bug, and bug maintenance. I encourage you to + explore these features, and see what you can do with them! + We'll spend no more time on individual Bugs or Queries from + this point on, so you are on your own there. </para> <para> But I'll give a few last hints! </para> <para> - There is a <ulink url="http://bugzilla.mozilla.org/help.html">CLUE</ulink> - on the Query page - that will teach you more how to use the form. + There is a <ulink + url="http://bugzilla.mozilla.org/help.html">CLUE</ulink> on the Query page that will teach you more how to use the form. </para> <para> - If you click the hyperlink on the - <ulink url="http://bugzilla.mozilla.org/describecomponents.cgi">Component</ulink> - box of the Query page, you will be presented a form that will describe what all - the components are. + If you click the hyperlink on the <ulink + url="http://bugzilla.mozilla.org/describecomponents.cgi">Component</ulink> box of the Query page, you will be presented a form that will describe what all the components are. </para> <para> - Possibly the most powerful feature of the Query page is the - <ulink url="http://bugzilla.mozilla.org/booleanchart.html">Boolean Chart</ulink> section. - It's a bit confusing to use the first time, but can provide unparalleled - flexibility in your queries, - allowing you to build extremely powerful requests. + Possibly the most powerful feature of the Query page is the + <ulink + url="http://bugzilla.mozilla.org/booleanchart.html">Boolean Chart</ulink> section. It's a bit confusing to use the first time, but can provide unparalleled flexibility in your queries, allowing you to build extremely powerful requests. </para> <para> - Finally, you can build some nifty - <ulink url="http://bugzilla.mozilla.org/reports.cgi">Reports</ulink> - using the "Bug Reports" link near the bottom of the query page, and also - available via the "Reports" link - at the footer of each page. + Finally, you can build some nifty <ulink + url="http://bugzilla.mozilla.org/reports.cgi">Reports</ulink> using the "Bug Reports" link near the bottom of the query page, and also available via the "Reports" link at the footer of each page. </para> </section> </section> @@ -701,7 +734,7 @@ system against which all others are measured. </section> <section id="init4me"> - <title>What's in it for me?</title> + <title>Where can I find my user preferences?</title> <epigraph> <para> Indiana, it feels like we walking on fortune cookies! @@ -711,98 +744,95 @@ system against which all others are measured. </para> </epigraph> <para> - Customized User Preferences offer tremendous versatility to - your individual Bugzilla experience. - Let's plunge into what you can do! The first step is to click - the "Edit prefs" link at the footer of each page once you - have logged in to - <ulink url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1"> - Landfill</ulink>. + Customized User Preferences offer tremendous versatility to your + individual Bugzilla experience. Let's plunge into what you can + do! The first step is to click the "Edit prefs" link at the + footer of each page once you have logged in to <ulink + url="http://landfill.tequilarista.org/bugzilla-tip/query.cgi?GoAheadAndLogIn=1"> Landfill</ulink>. </para> - <section id="accountsettings"> + <section id="accountsettings" xreflabel="Account Settings"> <title>Account Settings</title> <para> On this page, you can change your basic Account Settings, - including your password and full name. - For security reasons, in order to change anything on this page you - must type your <emphasis>current</emphasis> - password into the "Old Password" field. - If you wish to change your password, type the new password you - want into the "New Password" field and again into the "Re-enter - new password" field to ensure - you typed your new password correctly. Select the "Submit" button and you're done! + including your password and full name. For security reasons, + in order to change anything on this page you must type your + <emphasis>current</emphasis> password into the <quote>Old + Password</quote> field. If you wish to change your + password, type the new password you want into the <quote>New + Password</quote> field and again into the <quote>Re-enter + new password</quote> field to ensure you typed your new + password correctly. Select the <quote>Submit</quote> button + and you are done. </para> </section> - <section id="emailsettings"> + <section id="emailsettings" > <title>Email Settings</title> - <section id="notification"> + <section id="notification" xreflabel=""> <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 - <simplelist> - <member><emphasis>All qualifying bugs</emphasis>: sends you every change to every bug - where your name is somewhere on it, regardless of who changed it.</member> - <member><emphasis>Only those bugs which I am listed in the CC line</emphasis>: prevents - you from receiving mail for which you are the reporter,' - owner, or QA contact. If you are on the CC - list, presumably someone had a <emphasis>good</emphasis> - reason for you to get the email.</member> - <member><emphasis>All qulifying bugs except those which I change</emphasis>: - This is the default, and - a sensible setting. If someone else changes your bugs, you will get emailed, - but if you change bugs - yourself you will receive no notification of the change.</member> - </simplelist> + Here you can reduce or increase the amount of email sent you + from Bugzilla. Although this is referred to as + <quote>Advanced Email Filtering Options</quote>, they are, + in fact, the standard email filter set. All of them are + self-explanatory, but you can use the filters in interesting + ways. For instance, some people (notably Quality Assurance + personnel) often only care to receive updates regarding a + bug when the bug changes state, so they can track bugs on + their flow charts and know when it is time to pull the bug + onto a quality assurance platform for inspection. Other + people set up email gateways to + <xref linkend="bonsai"> or <xref linkend="tinderbox">, and + restrict which types of Bugzilla information are fed to + these systems.. </para> </section> <section id="newemailtech"> <title>New Email Technology</title> <note> <para> - This option may not be available in all Bugzilla installations, depending upon - the preferences of the systems administrator responsible for the setup of your Bugzilla. - However, if you really want this functionality, ask her to "enable newemailtech - in Params" - and "make it the default for all new users", referring her to the Administration section - of this Guide. + This option may not be available in all Bugzilla + installations, depending upon the preferences of the + systems administrator responsible for the setup of your + Bugzilla. However, if you really want this functionality, + ask her to "enable newemailtech in Params" and "make it + the default for all new users", referring her to the + Administration section of this Guide. </para> </note> <para> - Disregard the warnings about "experimental and bleeding edge"; the code to handle email - in a cleaner manner than that historically used for Bugzilla is - quite robust and well-tested now. + Disregard the warnings about "experimental and bleeding + edge"; the code to handle email in a cleaner manner than + that historically used for Bugzilla is quite robust and + well-tested now. </para> <para> - I recommend you enable the option, "Click here to sign up (and risk any bugs)". - Your email-box - will thank you for it. The fundamental shift in "newemailtech" is away from standard UNIX - "diff" output, which is quite ugly, to a prettier, better laid-out email. + I recommend you enable the option, "Click here to sign up + (and risk any bugs)". Your email-box will thank you for it. + The fundamental shift in "newemailtech" is away from + standard UNIX "diff" output, which is quite ugly, to a + prettier, better laid-out email. </para> </section> <section id="watchsettings"> <title>"Watching" Users</title> <note> <para> - This option may not be available in all Bugzilla installations, depending upon - the preferences of the systems administrator responsible for the setup of your Bugzilla. - However, if you really want this functionality, ask her to "enable watchers in Params". + This option may not be available in all Bugzilla + installations, depending upon the preferences of the + systems administrator responsible for the setup of your + Bugzilla. However, if you really want this functionality, + ask her to "enable watchers in Params". </para> </note> <para> - By entering user email names into the "Users to watch" text entry box, delineated by commas, - you can watch bugs of other users. This powerful functionality enables seamless transitions - as developers change projects, managers wish to get in touch with the issues faced by their - direct reports, or users go on vacation. If any of these three situations apply - to you, you will undoubtedly find this feature quite convenient. + By entering user email names into the "Users to watch" text + entry box, delineated by commas, you can watch bugs of other + users. This powerful functionality enables seamless + transitions as developers change projects, managers wish to + get in touch with the issues faced by their direct reports, + or users go on vacation. If any of these three situations + apply to you, you will undoubtedly find this feature quite + convenient. </para> </section> </section> @@ -810,36 +840,46 @@ system against which all others are measured. <title>Page Footer</title> <note> <para> - By default, this page is quite barren. However, go explore the Query Page some more; you will - find that you can store numerous queries on the server, so if you regularly run a particular query - it is just a drop-down menu away. On this page of Preferences, if you have many stored - queries you can elect to have them always one-click away! + By default, this page is quite barren. However, go explore + the Query Page some more; you will find that you can store + numerous queries on the server, so if you regularly run a + particular query it is just a drop-down menu away. On this + page of Preferences, if you have many stored queries you can + elect to have them always one-click away! </para> </note> <para> - If you have many stored queries on the server, here you will find individual drop-downs for each - stored query. Each drop-down gives you the option of that query appearing on the footer of every - page in Bugzilla! This gives you powerful one-click access to any complex searches you may set up, - and is an excellent way to impress your boss... + If you have many stored queries on the server, here you will + find individual drop-downs for each stored query. Each + drop-down gives you the option of that query appearing on the + footer of every page in Bugzilla! This gives you powerful + one-click access to any complex searches you may set up, and + is an excellent way to impress your boss... </para> <tip> - <para>By default, the "My Bugs" link appears at the bottom of each page. However, this query - gives you both the bugs you have reported, as well as those you are assigned. One of the most - common uses for this page is to remove the "My Bugs" link, replacing it with two other queries, - commonly called "My Bug Reports" and "My Bugs" (but only referencing bugs assigned to you). This - allows you to distinguish those bugs you have reported from those you are assigned. I commonly - set up complex Boolean queries in the Query page and link them to my footer in this page. When - they are significantly complex, a one-click reference can save hours of work.</para> + <para>By default, the "My Bugs" link appears at the bottom of + each page. However, this query gives you both the bugs you + have reported, as well as those you are assigned. One of + the most common uses for this page is to remove the "My + Bugs" link, replacing it with two other queries, commonly + called "My Bug Reports" and "My Bugs" (but only referencing + bugs assigned to you). This allows you to distinguish those + bugs you have reported from those you are assigned. I + commonly set up complex Boolean queries in the Query page + and link them to my footer in this page. When they are + significantly complex, a one-click reference can save hours + of work.</para> </tip> </section> <section id="permissionsettings"> <title>Permissions</title> <para> - This is a purely informative page which outlines your current permissions on - this installation of Bugzilla. If you have permissions to grant certain permissions to - other users, the "other users" link appears on this page as well as the footer. - For more information regarding user administration, please consult the Administration - section of this Guide. + This is a purely informative page which outlines your current + permissions on this installation of Bugzilla. If you have + permissions to grant certain permissions to other users, the + "other users" link appears on this page as well as the footer. + For more information regarding user administration, please + consult the Administration section of this Guide. </para> </section> </section> @@ -847,12 +887,11 @@ system against which all others are measured. <section id="usingbz-conc"> <title>Using Bugzilla-Conclusion</title> <para> - Thank you for reading through this portion of the Bugzilla Guide. I anticipate - it may not yet meet the needs of all readers. If you have additional comments or - corrections to make, please submit your contributions to the - <ulink url="mailto://mozilla-webtools@mozilla.org">mozilla-webtools</ulink> - mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools - newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org + Thank you for reading through this portion of the Bugzilla + Guide. I anticipate it may not yet meet the needs of all + readers. If you have additional comments or corrections to + make, please submit your contributions to the <ulink + url="mailto://mozilla-webtools@mozilla.org">mozilla-webtools</ulink> mailing list/newsgroup. The mailing list is mirrored to the netscape.public.mozilla.webtools newsgroup, and the newsgroup is mirrored to mozilla-webtools@mozilla.org </para> </section> </chapter> diff --git a/docs/xml/variants.xml b/docs/xml/variants.xml index fec867946..a5b346023 100644 --- a/docs/xml/variants.xml +++ b/docs/xml/variants.xml @@ -1,72 +1,77 @@ <!-- <!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> +<chapter id="variants" xreflabel="Bugzilla Variants and Competitors"> + <title>Bugzilla Variants and Competitors</title> + <para>I created this section to answer questions about Bugzilla + competitors and variants, then found a wonderful site which covers + an awful lot of what I wanted to discuss. Rather than quote it in + its entirety, I'll simply refer you here: <ulink + url="http://linas.org/linux/pm.html">http://linas.org/linux/pm.html</ulink></para> - <section id="rhbugzilla"> + <section id="rhbugzilla" xreflabel="Red Hat Bugzilla"> <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. - + Red Hat Bugzilla is probably the most popular Bugzilla variant + on the planet. One of the major benefits of Red Hat Bugzilla is + the ability to work with Oracle, MySQL, and PostGreSQL databases + serving as the back-end, instead of just MySQL. Dave Lawrence + has worked very hard to keep Red Hat Bugzilla up-to-date, and + many people prefer the snappier-looking page layout of Red Hat + Bugzilla to the default Mozilla-standard formatting. + </para> + <para>URL: <ulink + url="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</ulink></para> + </section> -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. + <section id="variant_fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris"> + <title>Loki Bugzilla (Fenris)</title> + <para>Fenris can be found at <ulink + url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para> + </section> -Also number 6 contradicts number 8 where number 6 would be the most up to date status -on the Oracle port. + <section id="variant_issuezilla" xreflabel="Issuezilla"> + <title>Issuezilla</title> + <para>Issuezilla is another fork from Bugzilla, and seems nearly + as popular as the Red Hat Bugzilla fork. Some Issuezilla team + members are regular contributors to the Bugzilla mailing + list/newsgroup. Issuezilla is not the primary focus of + bug-tracking at tigris.org, however. Their Java-based + bug-tracker, <xref linkend="variant_scarab">, is under heavy development + and looks promising!</para> + <para>URL: <ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">http://issuezilla.tigris.org/servlets/ProjectHome</ulink></para> + </section> -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. + <section id="variant_scarab" xreflabel="Scarab, a newfangled Java-based issue tracker"> + <title>Scarab</title> + <para>Scarab is a promising new bug-tracking system built using + Java Serlet technology. As of this writing, no source code has + been released as a package, but you can obtain the code from + CVS. + </para> + <para>URL: <ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink></para> + </section> -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. + <section id="variant_perforce" xreflabel="Using Perforce to track bugs"> + <title>Perforce SCM</title> + <para>Although Perforce isn't really a bug tracker, it can be used + as such through the <quote>jobs</quote> functionality.</para> + <para><ulink + url="http://www.perforce.com/perforce/technotes/note052.html"></ulink>http://www.perforce.com/perforce/technotes/note052.html</para> + </section> -3. Of course even more cosmetic changes. It is difficult to keep up with the ever -changing faces of www.redhat.com. + <section id="variant_sourceforge" xreflabel="SourceForge"> + <title>SourceForge</title> + <para>SourceForge is more of a way of coordinating geographically + distributed free software and open source projects over the + Internet than strictly a bug tracker, but if you're hunting for + bug-tracking for your open project, it may be just what the + software engineer ordered!</para> + <para>URL: <ulink + url="http://www.sourceforge.net">http://www.sourceforge.net</ulink></para> + </section> -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 |