bk commit - mysqldoc tree (paul:1.2775)

[paul]

Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2775 05/03/25 11:14:59 paul@stripped +1 -0
  manual.texi:
    Add dire warnings to 5.0 upgrade and 5.0.3 changelog sections.

  Docs/manual.texi
    1.2609 05/03/25 11:14:29 paul@stripped +14 -0
    Add dire warnings to 5.0 upgrade and 5.0.3 changelog sections.

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	paul
# Host:	frost.snake.net
# Root:	/Volumes/frost2/MySQL/bk/mysqldoc

--- 1.2608/Docs/manual.texi	2005-03-24 11:47:33 -06:00
+++ 1.2609/Docs/manual.texi	2005-03-25 11:14:29 -06:00
@@ -10514,6 +10514,13 @@
 @cindex compatibility, between MySQL versions
 @cindex upgrading, to 5.0
 
+@strong{Note}: Currently, MySQL 5.0 is at Beta status and, as for any other
+pre-production release, should not be installed on ``production'' level
+systems or systems with critical data. It is good practice to back up your
+data before installing any new version of software.  Although MySQL has done
+its best to ensure a high level of quality, protect your data by making a
+backup as you would for any software beta release.
+
 In general, you should do the following when upgrading to MySQL 5.0 from 4.1:
 
 @itemize @bullet
@@ -97812,6 +97819,13 @@
 
 @node News-5.0.3, News-5.0.2, News-5.0.4, News-5.0.x
 @appendixsubsec Changes in release 5.0.3 (release imminent)
+
+@strong{Note}: This Beta release, as any other pre-production release,
+should not be installed on ``production'' level systems or systems with
+critical data. It is good practice to back up your data before installing
+any new version of software.  Although MySQL has done its best to ensure a
+high level of quality, protect your data by making a backup as you would for
+any software beta release.
 
 @c NOTE: References to bug numbers should be written after the sentence
 @c NOTE: describing the bugfix, like this: