Author: paul
Date: 2006-10-24 20:39:29 +0200 (Tue, 24 Oct 2006)
New Revision: 3723
Log:
r14814@polar: paul | 2006-10-24 13:28:09 -0500
Update release policy description for ES/CS.
Modified:
trunk/refman-5.0/installing.xml
trunk/refman-5.1/installing.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:14527
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:11200
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:14814
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:11200
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/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml 2006-10-24 18:38:31 UTC (rev 3722)
+++ trunk/refman-5.0/installing.xml 2006-10-24 18:39:29 UTC (rev 3723)
Changed blocks: 2, Lines Added: 16, Lines Deleted: 18; 2890 bytes
@@ -1061,29 +1061,25 @@
<listitem>
<para>
- Releases are issued within each series. For each release,
- the last number in the version is one more than the
- previous release within the same series.
+ Enterprise Server releases are meant to appear every 18
+ months, supplemented by quarterly service packs and
+ monthly rapid updates. Community Server releases are meant
+ to appear 2−3 times per year.
</para>
</listitem>
<listitem>
<para>
- Production (stable) releases are meant to appear about 1-2
- times a year. However, if small bugs are found, a release
- with only bugfixes is issued.
+ Releases are issued within each series. Enterprise Server
+ releases are numbered using even numbers (for example,
+ ¤t-series;.20). Community Server releases are
+ numbered using even numbers (for example,
+ ¤t-series;.21).
</para>
</listitem>
<listitem>
<para>
- Working releases/bugfixes to old releases are meant to
- appear about every 4-8 weeks.
- </para>
- </listitem>
-
- <listitem>
- <para>
Binary distributions for some platforms are made by us for
major releases. Other people may make binary distributions
for other systems, but probably less frequently.
@@ -1094,16 +1090,18 @@
<para>
We make fixes available as soon as we have identified and
corrected small or non-critical but annoying bugs. The
- fixes are available immediately from our public BitKeeper
- repositories, and are included in the next release.
+ fixes are available in source form immediately from our
+ public BitKeeper repositories, and are included in the
+ next release.
</para>
</listitem>
<listitem>
<para>
- If by any chance a fatal bug is found in a release, our
- policy is to fix it in a new release as soon as possible.
- (We would like other companies to do this, too!)
+ If by any chance a security vulnerability or critical bug
+ is found in a release, our policy is to fix it in a new
+ release as soon as possible. (We would like other
+ companies to do this, too!)
</para>
</listitem>
Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml 2006-10-24 18:38:31 UTC (rev 3722)
+++ trunk/refman-5.1/installing.xml 2006-10-24 18:39:29 UTC (rev 3723)
Changed blocks: 2, Lines Added: 16, Lines Deleted: 18; 2890 bytes
@@ -1034,29 +1034,25 @@
<listitem>
<para>
- Releases are issued within each series. For each release,
- the last number in the version is one more than the
- previous release within the same series.
+ Enterprise Server releases are meant to appear every 18
+ months, supplemented by quarterly service packs and
+ monthly rapid updates. Community Server releases are meant
+ to appear 2−3 times per year.
</para>
</listitem>
<listitem>
<para>
- Production (stable) releases are meant to appear about 1-2
- times a year. However, if small bugs are found, a release
- with only bugfixes is issued.
+ Releases are issued within each series. Enterprise Server
+ releases are numbered using even numbers (for example,
+ ¤t-series;.20). Community Server releases are
+ numbered using even numbers (for example,
+ ¤t-series;.21).
</para>
</listitem>
<listitem>
<para>
- Working releases/bugfixes to old releases are meant to
- appear about every 4-8 weeks.
- </para>
- </listitem>
-
- <listitem>
- <para>
Binary distributions for some platforms are made by us for
major releases. Other people may make binary distributions
for other systems, but probably less frequently.
@@ -1067,16 +1063,18 @@
<para>
We make fixes available as soon as we have identified and
corrected small or non-critical but annoying bugs. The
- fixes are available immediately from our public BitKeeper
- repositories, and are included in the next release.
+ fixes are available in source form immediately from our
+ public BitKeeper repositories, and are included in the
+ next release.
</para>
</listitem>
<listitem>
<para>
- If by any chance a fatal bug is found in a release, our
- policy is to fix it in a new release as soon as possible.
- (We would like other companies to do this, too!)
+ If by any chance a security vulnerability or critical bug
+ is found in a release, our policy is to fix it in a new
+ release as soon as possible. (We would like other
+ companies to do this, too!)
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3723 - in trunk: . refman-5.0 refman-5.1 | paul | 24 Oct |
