<HTML ><HEAD ><TITLE >Glossary</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ "><LINK REL="HOME" TITLE="The Bugzilla Guide" HREF="index.html"><LINK REL="PREVIOUS" TITLE="How to use this License for your documents" HREF="gfdl-howto.html"></HEAD ><BODY CLASS="glossary" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation 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="gfdl-howto.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" ></TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" > </TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="GLOSSARY" ><H1 ><A NAME="glossary">Glossary</H1 ><DIV CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A NAME="AEN2610">0-9, high ascii</H1 ><DL ><DT ><B >.htaccess</B ></DT ><DD ><P > Apache web server, and other NCSA-compliant web servers, observe the convention of using files in directories called <TT CLASS="filename" >.htaccess</TT > files. These restrict parameters of the web server. In Bugzilla, they are used to restrict access to certain files which would otherwise compromise your installation. For instance, the <TT CLASS="filename" >localconfig</TT > file contains the password to your database. If this information were generally available, and remote access to your database turned on, you risk corruption of your database by computer criminals or the curious. </P ></DD ></DL ></DIV ><DIV CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A NAME="gloss-a">A</H1 ><DL ><DT ><B >Apache</B ></DT ><DD ><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 ><DIV CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A NAME="gloss-b">B</H1 ><DL ><DT ><B >Bug</B ></DT ><DD ><P > A <SPAN CLASS="QUOTE" >"Bug"</SPAN > in Bugzilla refers to an issue entered into the database which has an associated number, assignments, comments, etc. Some also refer to a <SPAN CLASS="QUOTE" >"tickets"</SPAN > or <SPAN CLASS="QUOTE" >"issues"</SPAN >; in the context of Bugzilla, they are synonymous. </P ></DD ><DT ><B >Bug Number</B ></DT ><DD ><P > Each Bugzilla Bug is assigned a number that uniquely identifies that Bug. The Bug associated with a Bug Number can be pulled up via a query, or easily from the very front page by typing the number in the "Find" box. </P ></DD ><DT ><B >Bug Life Cycle</B ></DT ><DD ><P >A Bug has stages through which it must pass before becoming a <SPAN CLASS="QUOTE" >"closed bug"</SPAN >, including acceptance, resolution, and verification. The <SPAN CLASS="QUOTE" >"Bug Life Cycle"</SPAN > 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"></H1 ><DL ><DT ><A NAME="gloss-component"><B >Component</B ></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 ></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</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"></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 CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A NAME="gloss-i">I</H1 ><DL ><DT ><A NAME="gloss-infiniteloop"><B >Infinite Loop</B ></DT ><DD ><P >A loop of information that never ends; see recursion.</P ></DD ></DL ></DIV ><DIV CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A NAME="gloss-m">M</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</H1 ><DL ><DT ><B >Product</B ></DT ><DD ><P >A Product is a broad category of types of bugs. In general, there are several Components to a Product. A Product also defines a default Group (used for Bug Security) for all bugs entered into components beneath it.</P ><DIV CLASS="example" ><A NAME="AEN2701"><P ><B >Example 1. A Sample Product</B ></P ><P >A company sells a software product called <SPAN CLASS="QUOTE" >"X"</SPAN >. They also maintain some older software called <SPAN CLASS="QUOTE" >"Y"</SPAN >, and have a secret project <SPAN CLASS="QUOTE" >"Z"</SPAN >. An effective use of Products might be to create Products <SPAN CLASS="QUOTE" >"X"</SPAN >, <SPAN CLASS="QUOTE" >"Y"</SPAN >, <SPAN CLASS="QUOTE" >"Z"</SPAN >, each with Components of User Interface, Database, and Business Logic. They might also change group permissions so that only those people who are members of Group <SPAN CLASS="QUOTE" >"Z"</SPAN > can see components and bugs under Product <SPAN CLASS="QUOTE" >"Z"</SPAN >.</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 CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A NAME="gloss-q">Q</H1 ><DL ><DT ><B >QA</B ></DT ><DD ><P ><SPAN CLASS="QUOTE" >"QA"</SPAN >, <SPAN CLASS="QUOTE" >"Q/A"</SPAN >, and <SPAN CLASS="QUOTE" >"Q.A."</SPAN > are short for <SPAN CLASS="QUOTE" >"Quality Assurance"</SPAN >. In most large software development organizations, there is a team devoted to ensuring the product meets minimum standards before shipping. This team will also generally want to track the progress of bugs over their life cycle, thus the need for the <SPAN CLASS="QUOTE" >"QA Contact"</SPAN > field in a Bug.</P ></DD ></DL ></DIV ><DIV CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A NAME="gloss-r">R</H1 ><DL ><DT ><A NAME="gloss-recursion"><B >Recursion</B ></DT ><DD ><P >The property of a function looking back at itself for something. <SPAN CLASS="QUOTE" >"GNU"</SPAN >, for instance, stands for <SPAN CLASS="QUOTE" >"GNU's Not UNIX"</SPAN >, thus recursing upon itself for definition. For further clarity, see Infinite Loop.</P ></DD ></DL ></DIV ><DIV CLASS="glossdiv" ><H1 CLASS="glossdiv" ><A NAME="gloss-s">S</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</H1 ><DL ><DT ><A NAME="gloss-target-milestone"><B >Target Milestone</B ></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</H1 ><DL ><DT ><A NAME="zarro-boogs-found"><B >Zarro Boogs Found</B ></DT ><DD ><P >This is the cryptic response sent by Bugzilla when a query returned no results. It is just a goofy way of saying "Zero Bugs Found".</P ></DD ></DL ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="gfdl-howto.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" > </TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >How to use this License for your documents</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" > </TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" > </TD ></TR ></TABLE ></DIV ></BODY ></HTML >