Another pre-2.17.7 rev.

docs/en/xml/Bugzilla-Guide.xml

@@ -40,11 +40,11 @@
 <!ENTITY bz "http://www.bugzilla.org/">
 <!ENTITY bzg-bugs "<ulink url='http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation'>Bugzilla Documentation</ulink>">
 <!ENTITY mysql "http://www.mysql.com/">
-<!ENTITY newest-perl-ver "5.8">
+<!ENTITY newest-perl-ver "5.8.2">
 
 <!-- For minimum versions -->
 <!ENTITY min-mysql-ver "3.23.41">
-<!ENTITY min-perl-ver "5.6">
+<!ENTITY min-perl-ver "5.6.0">
 <!ENTITY min-template-ver "2.08">
 <!ENTITY min-file-temp-ver "any">
 <!ENTITY min-appconfig-ver "1.52">

docs/en/xml/about.xml

@@ -67,17 +67,15 @@
       ]]>
     </para>
     <para>
-      The newest version of this guide can always be found at <ulink
-      url="http://www.bugzilla.org"/>; however, you should read the version
+      The latest version of this guide can always be found at <ulink
+      url="http://www.bugzilla.org"/>, or checked out via CVS.
+      (Please follow the <ulink url="http://www.mozilla.org/cvs.html">Mozilla 
+      CVS</ulink> instructions and check out the 
+      <filename>mozilla/webtools/bugzilla/docs/</filename>
+      subtree.) However, you should read the version
       which came with the Bugzilla release you are using.
     </para>
     <para>
-      The latest version of this document can always be checked out via CVS.
-      Please follow the <ulink url="http://www.mozilla.org/cvs.html">Mozilla CVS</ulink>
-      instructions and check out the <filename>mozilla/webtools/bugzilla/docs/</filename>
-      subtree.
-    </para>
-    <para>
       The Bugzilla Guide is currently only available in English. 
       If you would like to volunteer to translate it, please contact
       <ulink url="mailto:justdave@syndicomm.com">Dave Miller</ulink>.
@@ -116,7 +114,7 @@
     
     <para>
       Last but not least, all the members of the 
-      <ulink url="news://news.mozilla.org/netscape/public/mozilla/webtools">
+      <ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">
       netscape.public.mozilla.webtools</ulink>
       newsgroup. Without your discussions, insight, suggestions, and patches,
       this could never have happened.

docs/en/xml/conventions.xml

@@ -20,7 +20,7 @@
 
       <tbody>
         <row>
-          <entry>Warnings</entry>
+          <entry>Warning</entry>
 
           <entry>
             <caution>
@@ -40,7 +40,7 @@
         </row>
 
         <row>
-          <entry>Notes</entry>
+          <entry>Note</entry>
 
           <entry>
             <note>
@@ -60,7 +60,7 @@
         </row>
 
         <row>
-          <entry>File and directory names</entry>
+          <entry>File or directory name</entry>
 
           <entry>
             <filename>filename</filename>
@@ -68,7 +68,7 @@
         </row>
 
         <row>
-          <entry>Commands to be typed</entry>
+          <entry>Command to be typed</entry>
 
           <entry>
             <command>command</command>
@@ -76,7 +76,7 @@
         </row>
 
         <row>
-          <entry>Applications names</entry>
+          <entry>Application name</entry>
 
           <entry>
             <application>application</application>
@@ -85,27 +85,21 @@
 
         <row>
           <entry>
-          <foreignphrase>Prompt</foreignphrase>
-
-          of users command under bash shell</entry>
+          Normal user's prompt under bash shell</entry>
 
           <entry>bash$</entry>
         </row>
 
         <row>
           <entry>
-          <foreignphrase>Prompt</foreignphrase>
-
-          of root users command under bash shell</entry>
+          Root user's prompt under bash shell</entry>
 
           <entry>bash#</entry>
         </row>
 
         <row>
           <entry>
-          <foreignphrase>Prompt</foreignphrase>
-
-          of user command under tcsh shell</entry>
+          Normal user's prompt under tcsh shell</entry>
 
           <entry>tcsh$</entry>
         </row>

docs/en/xml/introduction.xml

@@ -17,30 +17,23 @@
   <section id="why-tracking">
     <title>Why use a bug-tracking system?</title>
     
-    <para>For many years, defect-tracking software was principally
-    the domain of large software development houses. Most smaller shops
-    simply relied on
-    shared lists and email to monitor the status of defects. This procedure
-    was error-prone and tended to cause those bugs judged least significant by
-    developers to be dropped or ignored.</para>
-
-    <para>Integrated
-    defect-tracking systems reduce downtime, increase productivity, and raise
-    customer satisfaction with their systems. Along with full disclosure, an
-    open bug-tracker allows you to keep in touch with your 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 method for accounting for unusual system or software
-    issues.</para>
+    <para>Those who do not use a bug-tracking system tend to rely on
+    shared lists, email, spreadsheets and/or Post-It notes to monitor the 
+    status of defects. This procedure
+    is usually error-prone and tends to cause those bugs judged least 
+    significant by developers to be dropped or ignored.</para>
+
+    <para>Integrated defect-tracking systems make sure that nothing gets
+    swept under the carpet; they provide a method of creating, storing,
+    arranging and processing defect reports and enhancement requests.</para>
     
   </section>
     
   <section id="why-bugzilla">
     <title>Why use Bugzilla?</title>
 
-    <para>Bugzilla boasts many advanced features. These include: 
+    <para>Bugzilla is the leading open-source/free software bug tracking 
+    system. It boasts many advanced features, including: 
     <itemizedlist>
       <listitem>
         <para>Powerful searching</para>
@@ -75,12 +68,12 @@
       </listitem>
 
       <listitem>
-        <para>Web, XML, email and console interfaces</para>
+        <para>Completely customisable and/or localisable web user
+        interface</para>
       </listitem>
 
       <listitem>
-        <para>Completely customisable and/or localisable web user
-        interface</para>
+        <para>Additional XML, email and console interfaces</para>
       </listitem>
 
       <listitem>
@@ -102,8 +95,7 @@
     <ulink url="http://www.cvshome.org">CVS</ulink>, 
     <ulink url="http://www.mozilla.org/bonsai.html">Bonsai</ulink>, or 
     <ulink url="http://www.perforce.com">Perforce SCM</ulink>, Bugzilla
-    provides a powerful, easy-to-use solution to configuration management and
-    replication problems.</para>
+    provides a powerful, easy-to-use configuration management solution.</para>
   </section>
 </chapter>
 

docs/en/xml/using.xml

@@ -3,14 +3,17 @@
 <chapter id="using">
   <title>Using Bugzilla</title>
 
-  <para>This section contains information for end-users of Bugzilla. 
-  There is a Bugzilla test installation, called 
-  <ulink url="http://landfill.bugzilla.org/bugzilla-tip/">Landfill</ulink>, 
-  which you are welcome to play with (if it's up.) 
-  However, it does not necessarily
-  have all Bugzilla features enabled, and runs an up-to-the-minute version, 
-  so some things may not quite work as this document describes.</para>
-    
+  <section id="using-intro">
+    <title>Introduction</title>
+    <para>This section contains information for end-users of Bugzilla. 
+    There is a Bugzilla test installation, called 
+    <ulink url="http://landfill.bugzilla.org/bugzilla-tip/">Landfill</ulink>, 
+    which you are welcome to play with (if it's up.) 
+    However, it does not necessarily
+    have all Bugzilla features enabled, and runs an up-to-the-minute version, 
+    so some things may not quite work as this document describes.</para>
+  </section>
+      
   <section id="myaccount">
     <title>Create a Bugzilla Account</title>
 
@@ -296,6 +299,12 @@
       of each bug.</member>
 
       <member>
+      <emphasis>CSV:</emphasis>
+
+      get the buglist as comma-separated values, for import into e.g.
+      a spreadsheet.</member>
+      
+      <member>
       <emphasis>Change Columns:</emphasis>
 
       change the bug attributes which appear in the list.</member>
@@ -313,11 +322,18 @@
       Sends mail to the owners of all bugs on the list.</member>
 
       <member>
-      <emphasis>Edit this query:</emphasis>
+      <emphasis>Edit Search:</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>Remember Search As:</emphasis>
+
+      You can give a search a name and remember it; a link will appear
+      in your page footer giving you quick access to run it again later.
+      </member>
     </simplelist>
     </para>
   </section>
@@ -365,6 +381,24 @@
         <para>Select "Commit" and send in your bug report.</para>
       </listitem>
     </orderedlist>
+    
+      <para>Try to make sure that everything said in the summary is also 
+      said in the first comment. Summaries are often updated and this will
+      ensure your original information is easily accessible.
+      </para>
+      
+      <para>
+      You do not need to put "any" or similar strings in the URL field.
+      If there is no specific URL associated with the bug, leave this 
+      field blank.
+      </para> 
+
+      <para>If you feel a bug you filed was incorrectly marked as a
+      DUPLICATE of another, please question it in your bug, not      
+      the bug it was duped to. Feel free to CC the person who duped it 
+      if they are not already CCed.
+      </para>
+      
   </section>
 
   <section id="patchviewer">
@@ -552,27 +586,6 @@
       out of the bug.
       </para>     
     </section>
-    
-    <section>
-      <title>Filing Bugs</title>
-      
-      <para>Try to make sure that everything said in the summary is also 
-      said in the first comment. Summaries are often updated and this will
-      ensure your original information is easily accessible.
-      </para>
-      
-      <para>
-      You do not need to put "any" or similar strings in the URL field.
-      If there is no specific URL associated with the bug, leave this 
-      field blank.
-      </para> 
-
-      <para>If you feel a bug you filed was incorrectly marked as a
-      DUPLICATE of another, please question it in your bug, not      
-      the bug it was duped to. Feel free to CC the person who duped it 
-      if they are not already CCed.
-      </para>
-    </section>
   </section>
   
   <section id="userpreferences">