svn commit - mysqldoc@docsrva: r3756 - in trunk: . refman-5.0

[paul]

Author: paul
Date: 2006-10-26 16:50:38 +0200 (Thu, 26 Oct 2006)
New Revision: 3756

Log:
 r11272@frost:  paul | 2006-10-26 09:48:41 -0500
 Revisions to bug fix text.


Modified:
   trunk/refman-5.0/service-pack.txt

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:14864
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:11267
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10957
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:14864
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:11272
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:10957


Modified: trunk/refman-5.0/service-pack.txt
===================================================================
--- trunk/refman-5.0/service-pack.txt	2006-10-26 13:46:18 UTC (rev 3755)
+++ trunk/refman-5.0/service-pack.txt	2006-10-26 14:50:38 UTC (rev 3756)
Changed blocks: 9, Lines Added: 74, Lines Deleted: 67; 12543 bytes

@@ -1,3 +1,7 @@
+[Some of the following assumes that the reader understands the ES/CS
+release numbering policy, so we need to have that in the manual.
+3.10 might be the most logical place.]
+
 3 Service-Pack, Hot-fix, and Bug-fix-Related FAQ 
 
 3.1 In General, what are the differences between how Bugs are addressed 

@@ -5,25 +9,32 @@
 
 In general, bugs are first corrected in the Enterprise Server code
 and then released to MySQL customers in regularly scheduled service
-pack drops. The same bug fixes are applied to the Community server
-also, but are not done so on a predictably scheduled basis and are
+pack drops. The same bug fixes are applied to the Community server,
+but are not done so on a predictably scheduled basis and are
 released later than for Enterprise customers.
 
 In particular, when a MySQL version is ready for Enterprise release,
-we will create a second tree: one tree will be the Enterprise Server
-tree and the other will be the Community Server tree.  Both trees
-will be available to the public.
+we create a second tree: One tree is the Enterprise Server
+tree and the other is the Community Server tree.  Both trees
+are available to the public.
 
+[Q: These are actual version-numbered distributions, distinct from
+the BitKeeper developer source tree?]
+
 3.2 How can an open source user obtain the latest and up-to-date MySQL 
 server code for a particular release? 
 
-We will make our source available via Bitkeeper at
-http://mysql.bkbits.net/; instructions for building binaries from
-source can be found at
-http://dev.mysql.com/doc/refman/5.0/en/installing-source.html.
+We make our source available via Bitkeeper at
+<ulink url="http://mysql.bkbits.net/"/>.
+Instructions for building binaries from source can be found at
+<xref linkend="installing-source"/>.
 
-This will always be available for community users. 
+This is always available for Community users. 
 
+[Q: The wording of the last line suggests that this is a special
+"community" source tree.  Is it actually the single developer source
+tree from which both ES and CS builds are made?]
+
 3.3 What is an Enterprise Server Service Pack? 
 
 As part of the effort to continually improve MySQL AB software,

@@ -35,22 +46,23 @@
 have to install an earlier version of a service pack before they
 install the latest service pack.
 
-Note that a MySQL service pack is a complete replacement of an
-existing MySQL binary/executable and not just patches that are
-applied to an existing MySQL binary.
+A MySQL service pack contains complete replacements of existing
+MySQL binaries (executable) and not just patches that are applied
+to existing MySQL binaries.
 
+[Q: delete next para?]
 In effect, the quarterly service packs replace MySQL Network's
 current "certified binaries".
 
 3.4 How does the Enterprise Server Service Pack Program Work? 
 
-MySQL Enterprise will have two service pack programs: 
+MySQL Enterprise has two service pack programs: 
 
 1. Rapid Update Program. This program serves customers who desire
 to stay as up to date as possible with releases of the MySQL
-Enterprise server. Service packs will be issued once a month for
-current Enterprise versions and be available for download on the
-MySQL Enterprise web site.
+Enterprise server. Service packs are issued once a month for
+current Enterprise versions and are available for download on the
+MySQL Enterprise Web site.
 
 2. Quarterly Service Pack Program. This program serves conservative
 customers who wish to stay current with fixes to the MySQL Enterprise

@@ -67,33 +79,33 @@
 Extended Support? 
 
 Service Packs for releases of the MySQL Enterprise server that are
-under Extended Support will be handled in the following way:
+under Extended Support are handled in the following way:
 
 In accordance with the MySQL Lifecycle policy only security and S1
-issues will be considered for a Service pack resolution. This will
-apply to all releases under the Extended support umbrella regardless
+issues are considered for a Service pack resolution. This
+applies to all releases under the Extended support umbrella regardless
 of their proximity to the current GA version of the product.
 
 There is no rapid update program for releases under Extended support. 
 
-Service Packs for releases under Extended support will be released
+Service Packs for releases under Extended support are released
 on a quarterly basis.
 
 A major release of the MySQL server is defined as the first two
-digits in the version number (e.g.  5.1).
+digits in the version number (for example, 5.1).
 
 3.6 What is an Enterprise Hot-Fix? 
 
 MySQL offers hot-fix support to MySQL Enterprise customers who
 encounter a known or undiscovered MySQL Enterprise server bug, not
 currently available in a current service pack, which causes a major
-business interruption. In this situation, MySQL AB will create a
-hot-fix patch for the customer, which will be delivered and applied
+business interruption. In this situation, MySQL AB creates a
+hot-fix patch for the customer, which is delivered and applied
 to correct the reported issue.
 
-Note that a MySQL hot-fix is a complete replacement of an existing
-MySQL binary/executable and not just patches that are applied to
-an existing MySQL binary.
+A MySQL hot-fix contains complete replacements of existing MySQL
+binaries (executable) and not just patches that are applied to
+existing MySQL binaries.
 
 3.7 How does the Enterprise Hot-Fix Program Work? 
 

@@ -113,21 +125,21 @@
 There are two ways in which a hot-fix may be supplied to a MySQL customer: 
 
 1. If the fix currently exists in a yet-to-be published MySQL service
-pack, MySQL Support will create a new MySQL binary that contains
-the needed patch using the unpublished service pack, which may
-include other bug fixes that may or may not be related to the
-reported problem.
+pack, MySQL Support creates a new MySQL binary that contains
+the needed patch using the unpublished service pack. It is possible
+that this service pack includes other bug fixes that may or may
+not be related to the reported problem.
 
 2. If the fix does not currently exist in any published or unpublished
-MySQL service pack, then MySQL Support will validate the bug and
-assign it to a MySQL developer for investigation. While MySQL cannot
-make time to delivery promises for unknown bugs, MySQL Support will
+MySQL service pack, then MySQL Support validates the bug and
+assigns it to a MySQL developer for investigation. While MySQL cannot
+make time-to-delivery promises for unknown bugs, MySQL Support will
 update the customer as often as possible on the progress of the
 fix.  When a fix is delivered from MySQL development, MySQL Support
-will create a new MySQL server binary that contains only that fix
-and deliver it to the customer.
+creates a new MySQL server binary that contains only that fix
+and delivers it to the customer.
 
-It should be understood that a hot-fix will likely always include
+It should be understood that a hot-fix will probably include
 other bug fixes that may or may not be related to the customer's
 hot-fix issue.
 

@@ -138,37 +150,36 @@
 Extended Support? 
 
 Hot-fixes for releases of the MySQL Enterprise server that are under
-Extended Support will be handled in the following way:
+Extended Support are handled in the following way:
 
-
 In accordance with the MySQL Lifecycle policy only security and S1
-issues will be considered for a hot fix resolution. This will apply
+issues are considered for a hot-fix resolution. This applies
 to all releases under the Extended support umbrella regardless of
 their proximity to the current GA version of the product.
 
-Hot-fixes for releases under Extended support will be released on
-an as needed basis.  A major release of the MySQL server is defined
-as the first two digits in the version number (e.g.  5.1).
+Hot-fixes for releases under Extended support are released on
+an as-needed basis.  A major release of the MySQL server is defined
+as the first two digits in the version number (for example, 5.1).
 
 3.9 How often are bug fixes released to the Community? 
 
 Formally speaking, bug fixes to the Community server are released
-on an "as-needed" basis, and are not scheduled or predictable in
-nature. They will, however, be frequent enough to ensure the community
+on an as-needed basis, and are not scheduled or predictable in
+nature. However, they will be frequent enough to ensure that the Community
 binaries do not become antiquated or contain crippling bugs that
 prohibit use of the Community server. Once a new major version of
-an Enterprise server ships, the current goal will be to have two
+an Enterprise server ships, the current goal is to have two
 drops of Community server binaries in a calendar year. These drops
-of community binaries will contain cumulative bug fixes and minor
-enhancements that community users have requested.
+of Community binaries will contain cumulative bug fixes and minor
+enhancements that Community users have requested.
 
-Note that the number of community binary drops will be more frequent
+The number of Community binary drops will be more frequent
 just after a new major release of the Community server. In the 2-3
-months it takes to reach enterprise quality in the Enterprise server,
+months it takes to reach Enterprise quality in the Enterprise server,
 there will be as many binary drops of the Community server as it
 takes to reach an acceptable level of quality. Once a new major
 version of the Enterprise server ships, then a very infrequent
-binary drop schedule for community will be followed (with exceptions
+binary drop schedule for Community will be followed (with exceptions
 being made for critical security or data corruption issues).
 
 Bug fixes are always supplied in the MySQL source code and are

@@ -188,29 +199,25 @@
 3.11 What is done to protect the quality of Enterprise Service pack 
 releases? 
 
-First, MySQL's internal QA area will be strengthened in the coming
-months to provide deeper coverage in finding and fixing critical
-server bugs.
-
 Each month, a rapid update is issued for MySQL Enterprise subscribers.
 Monthly updates are cumulative in nature. Before each quarterly
 service pack is issued, the prior month's rapid update release is
-'baked' into the customer base, with the goal being to have MySQL's
+"baked" into the customer base, with the goal being to have MySQL's
 cutting-edge customers find any regressions prior to issuing a
 quarterly service pack.
 
-In addition, this 'bake time' for each quarterly service pack will
-allow internal QA to thoroughly test the build candidate and locate
+In addition, this "bake time" for each quarterly service pack
+allows internal QA to thoroughly test the build candidate and locate
 any quality issues.
 
-Finally, it should be noted that MySQL Engineering requires two
-code reviewers (other than the developer that implemented a particular
+MySQL Engineering requires two
+code reviewers (other than the developer who implemented a particular
 bug fix) to assess all submitted fixes, and automated checking tools
-(e.g. Valgrind) are also in play. The code review process used at
+(such as Valgrind) are also in play. The code review process used at
 MySQL is more stringent than many other shops, and this contributes
 to higher quality.
 
-With each issued quarterly service pack being handled this way, the
+With each quarterly service pack being handled this way, the
 quality of each release should be at a level of excellence that
 meets enterprise standards.
 

@@ -219,10 +226,10 @@
 
 Critical security vulnerabilities that are discovered are corrected
 immediately, with new binaries being provided to both Enterprise
-customers and Community users, with a new software update bulletin
-being issued to Enterprise customers.
+customers and Community users. A new software update bulletin
+is issued to Enterprise customers.
 
-The three main incidents that will trigger emergency fixes to both
+The three main incident types that trigger emergency fixes to both
 Enterprise and Community are:
 
 Critical security vulnerabilities. 

@@ -235,10 +242,10 @@
 
 5.0.36a was the last issued Enterprise service pack 
 
-5.0.37 was the last issued community binary 
+5.0.37 was the last issued Community binary 
 
 A new critical security fix is needed 
 
-In this case, the fix would be made with 5.0.36b being issued for
+In this case, the fix is made with 5.0.36b being issued for
 Enterprise and 5.0.37a for Community.