List:Commits« Previous MessageNext Message »
From:paul Date:January 25 2006 9:20pm
Subject:svn commit - mysqldoc@docsrva: r1038 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2006-01-25 22:20:57 +0100 (Wed, 25 Jan 2006)
New Revision: 1038

Log:
 r2535@kite-hub:  paul | 2006-01-25 15:20:49 -0600
 General revisions.


Modified:
   trunk/
   trunk/refman-4.1/installing.xml
   trunk/refman-5.0/installing.xml
   trunk/refman-5.1/installing.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6663
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2529
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6663
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2535

Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml	2006-01-25 20:49:37 UTC (rev 1037)
+++ trunk/refman-4.1/installing.xml	2006-01-25 21:20:57 UTC (rev 1038)
@@ -23,7 +23,12 @@
   </indexterm>
 
   <para>
-    This chapter describes how to obtain and install MySQL:
+    This chapter describes how to obtain and install MySQL. A summary of
+    the procedure follows and later sections provide the details. If you
+    plan to upgrade an existing version of MySQL to a newer version
+    rather than install MySQL for the first time, see
+    <xref linkend="upgrade"/>, for information about upgrade procedures
+    and about issues that you should consider before upgrading.
   </para>
 
   <orderedlist>
@@ -57,9 +62,9 @@
       <para>
         <emphasis role="bold">Download the distribution that you want to
         install.</emphasis> For a list of sites from which you can
-        obtain MySQL, see <xref linkend="getting-mysql"/>. You can
-        verify the integrity of the distribution using the instructions
-        in <xref linkend="verifying-package-integrity"/>.
+        obtain MySQL, see <xref linkend="getting-mysql"/>. To verify the
+        integrity of the distribution, use the instructions in
+        <xref linkend="verifying-package-integrity"/>.
       </para>
     </listitem>
 
@@ -74,15 +79,6 @@
       </para>
 
       <para>
-        <emphasis role="bold">Note</emphasis>: If you plan to upgrade an
-        existing version of MySQL to a newer version rather than
-        installing MySQL for the first time, see
-        <xref linkend="upgrade"/>, for information about upgrade
-        procedures and about issues that you should consider before
-        upgrading.
-      </para>
-
-      <para>
         If you encounter installation difficulties, see
         <xref linkend="operating-system-specific-notes"/>, for
         information on solving problems for particular platforms.
@@ -291,15 +287,16 @@
 
         <listitem>
           <para>
-            Novell NetWare 6.0. See
+            Novell NetWare 6.0 and 6.5. See
             <xref linkend="netware-installation"/>.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            OpenBSD &gt; 2.5 with native threads. OpenBSD &lt; 2.5 with
-            the MIT-pthreads package. See <xref linkend="openbsd"/>.
+            OpenBSD 2.5 and with native threads. OpenBSD earlier than
+            2.5 with the MIT-pthreads package. See
+            <xref linkend="openbsd"/>.
           </para>
         </listitem>
 
@@ -319,13 +316,13 @@
 
         <listitem>
           <para>
-            SCO UnixWare 7.1.x. See <xref linkend="sco-unixware"/>.
+            SCO Openserver 6.0.x. See <xref linkend="sco-openserver"/>.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            SCO Openserver 6.0.x. See <xref linkend="sco-openserver"/>.
+            SCO UnixWare 7.1.x. See <xref linkend="sco-unixware"/>.
           </para>
         </listitem>
 
@@ -358,7 +355,7 @@
 
         <listitem>
           <para>
-            Windows 9x, Me, NT, 2000, XP, and 2003. See
+            Windows 9x, Me, NT, 2000, XP, and Windows Server 2003. See
             <xref linkend="windows-installation"/>.
           </para>
         </listitem>
@@ -414,9 +411,9 @@
 
         <listitem>
           <para>
-            If your tables are big, the ability of the filesystem to
-            deal with large files at all and to deal with them
-            efficiently.
+            If your tables are large, performance is affected by the
+            ability of the filesystem to deal with large files at all
+            and to deal with them efficiently.
           </para>
         </listitem>
 
@@ -438,10 +435,10 @@
 
         <listitem>
           <para>
-            The number of users that have successfully run MySQL on the
+            The number of users that have run MySQL successfully on the
             platform in similar configurations. If this number is high,
-            the chances of encountering platform-specific surprises are
-            much smaller.
+            the likelihood of encountering platform-specific surprises
+            is much smaller.
           </para>
         </listitem>
 
@@ -471,12 +468,12 @@
         to say that one operating system is better or worse than another
         in general. We are talking only about choosing an OS for the
         specific purpose of running MySQL. With this in mind, the result
-        of this comparison would be different if we considered more
-        factors. In some cases, the reason one OS is better than the
-        other could simply be that we have been able to put more effort
-        into testing and optimizing for a particular platform. We are
-        just stating our observations to help you decide which platform
-        to use for running MySQL.
+        of this comparison might be different if other factors were
+        considered. In some cases, the reason one OS is better for MySQL
+        than another might simply be that we have been able to put more
+        effort into testing and optimizing for a particular platform. We
+        are just stating our observations to help you decide which
+        platform to use for running MySQL.
       </para>
 
     </section>
@@ -544,57 +541,63 @@
 
         <itemizedlist>
 
+          <remark role="note">
+            These series numbers cannot be given using the
+            current-series, previous-series, next-series entities.
+          </remark>
+
           <listitem>
             <para>
-              MySQL 5.0 is the newest development release series and is
-              under very active development for new features. Alpha
-              releases have been issued to allow more widespread
-              testing.
+              MySQL 5.1 is the next development release series and is
+              the series in which new features are to be implemented.
+              Alpha releases are available now to allow widespread
+              testing by interested users.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              MySQL 4.1 is the current stable (production-quality)
-              release series. New releases are issued for bugfixes. No
-              new features are added that could diminish the code
+              MySQL 5.0 is the current stable (production-quality)
+              release series. New releases are issued for bugfixes only;
+              no new features are being added that could effect
               stability.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              MySQL 4.0 is the previous stable (production-quality)
-              release series. New releases are issued for bugfixes. No
-              new features are added that could diminish the code
-              stability.
+              MySQL 4.1 is the previous stable (production-quality)
+              release series. New releases are issued for critical
+              bugfixes and security fixes. No significant new features
+              are to be added to this series.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              MySQL 3.23 is the old stable (production-quality) release
-              series. This series is retired, so new releases are issued
-              only to fix critical bugs.
+              MySQL 4.0 and 3.23 are the old stable (production-quality)
+              release series. These versions are now retired, so new
+              releases are issued only to fix extremely critical bugs
+              (primarily security issues).
             </para>
           </listitem>
 
         </itemizedlist>
 
         <para>
-          We do not believe in a complete freeze, as this also leaves
-          out bugfixes and things that <quote>must be done.</quote>
-          <quote>Somewhat frozen</quote> means that we may add small
-          things that <quote>almost surely do not affect anything that's
-          currently working.</quote> Naturally, relevant bugfixes from
-          an earlier series propagate to later series.
+          We do not believe in a complete code freeze because this
+          prevents us from making bugfixes and other fixes that must be
+          done. By <quote>somewhat frozen</quote> we mean that we may
+          add small things that should not affect anything that
+          currently works in a production release. Naturally, relevant
+          bugfixes from an earlier series propagate to later series.
         </para>
 
         <para>
           Normally, if you are beginning to use MySQL for the first time
           or trying to port it to some system for which there is no
           binary distribution, we recommend going with the production
-          release series. Currently this is MySQL 4.1. All MySQL
+          release series. Currently this is MySQL 5.0. All MySQL
           releases, even those from development series, are checked with
           the MySQL benchmarks and an extensive test suite before being
           issued.
@@ -767,7 +770,7 @@
         </indexterm>
 
         <para>
-          All releases have been tested at least with:
+          All releases have been tested at least with these tools:
         </para>
 
         <itemizedlist>
@@ -819,9 +822,9 @@
         </itemizedlist>
 
         <para>
-          Another test is that we use the newest MySQL version in our
-          internal production environment, on at least one machine. We
-          have more than 100GB of data to work with.
+          We also test the newest MySQL version in our internal
+          production environment, on at least one machine. We have more
+          than 100GB of data to work with.
         </para>
 
       </section>

Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml	2006-01-25 20:49:37 UTC (rev 1037)
+++ trunk/refman-5.0/installing.xml	2006-01-25 21:20:57 UTC (rev 1038)
@@ -23,7 +23,12 @@
   </remark>
 
   <para>
-    This chapter describes how to obtain and install MySQL:
+    This chapter describes how to obtain and install MySQL. A summary of
+    the procedure follows and later sections provide the details. If you
+    plan to upgrade an existing version of MySQL to a newer version
+    rather than install MySQL for the first time, see
+    <xref linkend="upgrade"/>, for information about upgrade procedures
+    and about issues that you should consider before upgrading.
   </para>
 
   <orderedlist>
@@ -57,9 +62,9 @@
       <para>
         <emphasis role="bold">Download the distribution that you want to
         install.</emphasis> For a list of sites from which you can
-        obtain MySQL, see <xref linkend="getting-mysql"/>. You can
-        verify the integrity of the distribution using the instructions
-        in <xref linkend="verifying-package-integrity"/>.
+        obtain MySQL, see <xref linkend="getting-mysql"/>. To verify the
+        integrity of the distribution, use the instructions in
+        <xref linkend="verifying-package-integrity"/>.
       </para>
     </listitem>
 
@@ -74,15 +79,6 @@
       </para>
 
       <para>
-        <emphasis role="bold">Note</emphasis>: If you plan to upgrade an
-        existing version of MySQL to a newer version rather than
-        installing MySQL for the first time, see
-        <xref linkend="upgrade"/>, for information about upgrade
-        procedures and about issues that you should consider before
-        upgrading.
-      </para>
-
-      <para>
         If you encounter installation difficulties, see
         <xref linkend="operating-system-specific-notes"/>, for
         information on solving problems for particular platforms.
@@ -291,15 +287,16 @@
 
         <listitem>
           <para>
-            Novell NetWare 6.0. See
+            Novell NetWare 6.0 and 6.5. See
             <xref linkend="netware-installation"/>.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            OpenBSD &gt; 2.5 with native threads. OpenBSD &lt; 2.5 with
-            the MIT-pthreads package. See <xref linkend="openbsd"/>.
+            OpenBSD 2.5 and with native threads. OpenBSD earlier than
+            2.5 with the MIT-pthreads package. See
+            <xref linkend="openbsd"/>.
           </para>
         </listitem>
 
@@ -319,13 +316,13 @@
 
         <listitem>
           <para>
-            SCO UnixWare 7.1.x. See <xref linkend="sco-unixware"/>.
+            SCO Openserver 6.0.x. See <xref linkend="sco-openserver"/>.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            SCO Openserver 6.0.x. See <xref linkend="sco-openserver"/>.
+            SCO UnixWare 7.1.x. See <xref linkend="sco-unixware"/>.
           </para>
         </listitem>
 
@@ -358,7 +355,7 @@
 
         <listitem>
           <para>
-            Windows 9x, Me, NT, 2000, XP, and 2003. See
+            Windows 9x, Me, NT, 2000, XP, and Windows Server 2003. See
             <xref linkend="windows-installation"/>.
           </para>
         </listitem>
@@ -414,9 +411,9 @@
 
         <listitem>
           <para>
-            If your tables are big, the ability of the filesystem to
-            deal with large files at all and to deal with them
-            efficiently.
+            If your tables are large, performance is affected by the
+            ability of the filesystem to deal with large files at all
+            and to deal with them efficiently.
           </para>
         </listitem>
 
@@ -438,10 +435,10 @@
 
         <listitem>
           <para>
-            The number of users that have successfully run MySQL on the
+            The number of users that have run MySQL successfully on the
             platform in similar configurations. If this number is high,
-            the chances of encountering platform-specific surprises are
-            much smaller.
+            the likelihood of encountering platform-specific surprises
+            is much smaller.
           </para>
         </listitem>
 
@@ -471,12 +468,12 @@
         to say that one operating system is better or worse than another
         in general. We are talking only about choosing an OS for the
         specific purpose of running MySQL. With this in mind, the result
-        of this comparison would be different if we considered more
-        factors. In some cases, the reason one OS is better than the
-        other could simply be that we have been able to put more effort
-        into testing and optimizing for a particular platform. We are
-        just stating our observations to help you decide which platform
-        to use for running MySQL.
+        of this comparison might be different if other factors were
+        considered. In some cases, the reason one OS is better for MySQL
+        than another might simply be that we have been able to put more
+        effort into testing and optimizing for a particular platform. We
+        are just stating our observations to help you decide which
+        platform to use for running MySQL.
       </para>
 
     </section>
@@ -544,31 +541,35 @@
 
         <itemizedlist>
 
+          <remark role="note">
+            These series numbers cannot be given using the
+            current-series, previous-series, next-series entities.
+          </remark>
+
           <listitem>
             <para>
-              MySQL &next-series; is the next development release series
-              and is the series in which new features are to be
-              implemented. Alpha releases will be made available in the
-              near future to allow widespread testing by interested
-              users.
+              MySQL 5.1 is the next development release series and is
+              the series in which new features are to be implemented.
+              Alpha releases are available now to allow widespread
+              testing by interested users.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              MySQL &current-series; is the current stable
-              (production-quality) release series. New releases are
-              issued for bugfixes only; no new features are being added
-              that could effect stability.
+              MySQL 5.0 is the current stable (production-quality)
+              release series. New releases are issued for bugfixes only;
+              no new features are being added that could effect
+              stability.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              MySQL &previous-series; is the previous stable
-              (production-quality) release series. New releases are
-              issued for critical bugfixes and security fixes. No
-              significant new features are to be added to this series.
+              MySQL 4.1 is the previous stable (production-quality)
+              release series. New releases are issued for critical
+              bugfixes and security fixes. No significant new features
+              are to be added to this series.
             </para>
           </listitem>
 
@@ -584,22 +585,22 @@
         </itemizedlist>
 
         <para>
-          We do not believe in a complete freeze, as this also leaves
-          out bugfixes and other fixes that must be done. By
-          <quote>somewhat frozen</quote> we mean that we may add small
-          things that should not affect anything that currently works in
-          a production release. Naturally, relevant bugfixes from an
-          earlier series propagate to later series.
+          We do not believe in a complete code freeze because this
+          prevents us from making bugfixes and other fixes that must be
+          done. By <quote>somewhat frozen</quote> we mean that we may
+          add small things that should not affect anything that
+          currently works in a production release. Naturally, relevant
+          bugfixes from an earlier series propagate to later series.
         </para>
 
         <para>
           Normally, if you are beginning to use MySQL for the first time
           or trying to port it to some system for which there is no
           binary distribution, we recommend going with the production
-          release series. Currently this is MySQL &current-series;. All
-          MySQL releases, even those from development series, are
-          checked with the MySQL benchmarks and an extensive test suite
-          before being issued.
+          release series. Currently this is MySQL 5.0. All MySQL
+          releases, even those from development series, are checked with
+          the MySQL benchmarks and an extensive test suite before being
+          issued.
         </para>
 
         <para>
@@ -640,8 +641,8 @@
         <para>
           The MySQL naming scheme uses release names that consist of
           three numbers and a suffix; for example,
-          <emphasis role="bold">mysql-5.0.9-beta</emphasis>. The numbers
-          within the release name are interpreted as follows:
+          <emphasis role="bold">mysql-5.0.12-beta</emphasis>. The
+          numbers within the release name are interpreted as follows:
         </para>
 
         <itemizedlist>
@@ -664,7 +665,7 @@
 
           <listitem>
             <para>
-              The third number (<emphasis role="bold">9</emphasis>) is
+              The third number (<emphasis role="bold">12</emphasis>) is
               the version number within the release series. This is
               incremented for each new release. Usually you want the
               latest version for the series you have chosen.
@@ -771,7 +772,7 @@
         </indexterm>
 
         <para>
-          All releases have been tested at least with:
+          All releases have been tested at least with these tools:
         </para>
 
         <itemizedlist>
@@ -823,9 +824,9 @@
         </itemizedlist>
 
         <para>
-          Another test is that we use the newest MySQL version in our
-          internal production environment, on at least one machine. We
-          have more than 100GB of data to work with.
+          We also test the newest MySQL version in our internal
+          production environment, on at least one machine. We have more
+          than 100GB of data to work with.
         </para>
 
       </section>

Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml	2006-01-25 20:49:37 UTC (rev 1037)
+++ trunk/refman-5.1/installing.xml	2006-01-25 21:20:57 UTC (rev 1038)
@@ -23,7 +23,12 @@
   </remark>
 
   <para>
-    This chapter describes how to obtain and install MySQL:
+    This chapter describes how to obtain and install MySQL. A summary of
+    the procedure follows and later sections provide the details. If you
+    plan to upgrade an existing version of MySQL to a newer version
+    rather than install MySQL for the first time, see
+    <xref linkend="upgrade"/>, for information about upgrade procedures
+    and about issues that you should consider before upgrading.
   </para>
 
   <orderedlist>
@@ -57,9 +62,9 @@
       <para>
         <emphasis role="bold">Download the distribution that you want to
         install.</emphasis> For a list of sites from which you can
-        obtain MySQL, see <xref linkend="getting-mysql"/>. You can
-        verify the integrity of the distribution using the instructions
-        in <xref linkend="verifying-package-integrity"/>.
+        obtain MySQL, see <xref linkend="getting-mysql"/>. To verify the
+        integrity of the distribution, use the instructions in
+        <xref linkend="verifying-package-integrity"/>.
       </para>
     </listitem>
 
@@ -74,15 +79,6 @@
       </para>
 
       <para>
-        <emphasis role="bold">Note</emphasis>: If you plan to upgrade an
-        existing version of MySQL to a newer version rather than
-        installing MySQL for the first time, see
-        <xref linkend="upgrade"/>, for information about upgrade
-        procedures and about issues that you should consider before
-        upgrading.
-      </para>
-
-      <para>
         If you encounter installation difficulties, see
         <xref linkend="operating-system-specific-notes"/>, for
         information on solving problems for particular platforms.
@@ -291,15 +287,16 @@
 
         <listitem>
           <para>
-            Novell NetWare 6.0. See
+            Novell NetWare 6.0 and 6.5. See
             <xref linkend="netware-installation"/>.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            OpenBSD &gt; 2.5 with native threads. OpenBSD &lt; 2.5 with
-            the MIT-pthreads package. See <xref linkend="openbsd"/>.
+            OpenBSD 2.5 and with native threads. OpenBSD earlier than
+            2.5 with the MIT-pthreads package. See
+            <xref linkend="openbsd"/>.
           </para>
         </listitem>
 
@@ -319,13 +316,13 @@
 
         <listitem>
           <para>
-            SCO UnixWare 7.1.x. See <xref linkend="sco-unixware"/>.
+            SCO Openserver 6.0.x. See <xref linkend="sco-openserver"/>.
           </para>
         </listitem>
 
         <listitem>
           <para>
-            SCO Openserver 6.0.x. See <xref linkend="sco-openserver"/>.
+            SCO UnixWare 7.1.x. See <xref linkend="sco-unixware"/>.
           </para>
         </listitem>
 
@@ -358,7 +355,7 @@
 
         <listitem>
           <para>
-            Windows 9x, Me, NT, 2000, XP, and 2003. See
+            Windows 9x, Me, NT, 2000, XP, and Windows Server 2003. See
             <xref linkend="windows-installation"/>.
           </para>
         </listitem>
@@ -414,9 +411,9 @@
 
         <listitem>
           <para>
-            If your tables are big, the ability of the filesystem to
-            deal with large files at all and to deal with them
-            efficiently.
+            If your tables are large, performance is affected by the
+            ability of the filesystem to deal with large files at all
+            and to deal with them efficiently.
           </para>
         </listitem>
 
@@ -438,10 +435,10 @@
 
         <listitem>
           <para>
-            The number of users that have successfully run MySQL on the
+            The number of users that have run MySQL successfully on the
             platform in similar configurations. If this number is high,
-            the chances of encountering platform-specific surprises are
-            much smaller.
+            the likelihood of encountering platform-specific surprises
+            is much smaller.
           </para>
         </listitem>
 
@@ -471,12 +468,12 @@
         to say that one operating system is better or worse than another
         in general. We are talking only about choosing an OS for the
         specific purpose of running MySQL. With this in mind, the result
-        of this comparison would be different if we considered more
-        factors. In some cases, the reason one OS is better than the
-        other could simply be that we have been able to put more effort
-        into testing and optimizing for a particular platform. We are
-        just stating our observations to help you decide which platform
-        to use for running MySQL.
+        of this comparison might be different if other factors were
+        considered. In some cases, the reason one OS is better for MySQL
+        than another might simply be that we have been able to put more
+        effort into testing and optimizing for a particular platform. We
+        are just stating our observations to help you decide which
+        platform to use for running MySQL.
       </para>
 
     </section>
@@ -544,31 +541,35 @@
 
         <itemizedlist>
 
+          <remark role="note">
+            These series numbers cannot be given using the
+            current-series, previous-series, next-series entities.
+          </remark>
+
           <listitem>
             <para>
-              MySQL &next-series; is the next development release series
-              and is the series in which new features are to be
-              implemented. Alpha releases will be made available in the
-              near future to allow widespread testing by interested
-              users.
+              MySQL 5.1 is the next development release series and is
+              the series in which new features are to be implemented.
+              Alpha releases are available now to allow widespread
+              testing by interested users.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              MySQL &current-series; is the current stable
-              (production-quality) release series. New releases are
-              issued for bugfixes only; no new features are being added
-              that could effect stability.
+              MySQL 5.0 is the current stable (production-quality)
+              release series. New releases are issued for bugfixes only;
+              no new features are being added that could effect
+              stability.
             </para>
           </listitem>
 
           <listitem>
             <para>
-              MySQL &previous-series; is the previous stable
-              (production-quality) release series. New releases are
-              issued for critical bugfixes and security fixes. No
-              significant new features are to be added to this series.
+              MySQL 4.1 is the previous stable (production-quality)
+              release series. New releases are issued for critical
+              bugfixes and security fixes. No significant new features
+              are to be added to this series.
             </para>
           </listitem>
 
@@ -584,22 +585,22 @@
         </itemizedlist>
 
         <para>
-          We do not believe in a complete freeze, as this also leaves
-          out bugfixes and other fixes that must be done. By
-          <quote>somewhat frozen</quote> we mean that we may add small
-          things that should not affect anything that currently works in
-          a production release. Naturally, relevant bugfixes from an
-          earlier series propagate to later series.
+          We do not believe in a complete code freeze because this
+          prevents us from making bugfixes and other fixes that must be
+          done. By <quote>somewhat frozen</quote> we mean that we may
+          add small things that should not affect anything that
+          currently works in a production release. Naturally, relevant
+          bugfixes from an earlier series propagate to later series.
         </para>
 
         <para>
           Normally, if you are beginning to use MySQL for the first time
           or trying to port it to some system for which there is no
           binary distribution, we recommend going with the production
-          release series. Currently this is MySQL &current-series;. All
-          MySQL releases, even those from development series, are
-          checked with the MySQL benchmarks and an extensive test suite
-          before being issued.
+          release series. Currently this is MySQL 5.0. All MySQL
+          releases, even those from development series, are checked with
+          the MySQL benchmarks and an extensive test suite before being
+          issued.
         </para>
 
         <para>
@@ -640,8 +641,8 @@
         <para>
           The MySQL naming scheme uses release names that consist of
           three numbers and a suffix; for example,
-          <emphasis role="bold">mysql-5.0.9-beta</emphasis>. The numbers
-          within the release name are interpreted as follows:
+          <emphasis role="bold">mysql-5.0.12-beta</emphasis>. The
+          numbers within the release name are interpreted as follows:
         </para>
 
         <itemizedlist>
@@ -664,7 +665,7 @@
 
           <listitem>
             <para>
-              The third number (<emphasis role="bold">9</emphasis>) is
+              The third number (<emphasis role="bold">12</emphasis>) is
               the version number within the release series. This is
               incremented for each new release. Usually you want the
               latest version for the series you have chosen.
@@ -771,7 +772,7 @@
         </indexterm>
 
         <para>
-          All releases have been tested at least with:
+          All releases have been tested at least with these tools:
         </para>
 
         <itemizedlist>
@@ -823,9 +824,9 @@
         </itemizedlist>
 
         <para>
-          Another test is that we use the newest MySQL version in our
-          internal production environment, on at least one machine. We
-          have more than 100GB of data to work with.
+          We also test the newest MySQL version in our internal
+          production environment, on at least one machine. We have more
+          than 100GB of data to work with.
         </para>
 
       </section>

Thread
svn commit - mysqldoc@docsrva: r1038 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul25 Jan