You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by sr...@apache.org on 2017/07/31 19:21:35 UTC
spark-website git commit: Add Spark 2.3 release timeframe guidance
Repository: spark-website
Updated Branches:
refs/heads/asf-site 0e09b2f58 -> 889909689
Add Spark 2.3 release timeframe guidance
Project: http://git-wip-us.apache.org/repos/asf/spark-website/repo
Commit: http://git-wip-us.apache.org/repos/asf/spark-website/commit/88990968
Tree: http://git-wip-us.apache.org/repos/asf/spark-website/tree/88990968
Diff: http://git-wip-us.apache.org/repos/asf/spark-website/diff/88990968
Branch: refs/heads/asf-site
Commit: 88990968962e5cc47db8bc2c11a50742d2438daa
Parents: 0e09b2f
Author: Sean Owen <so...@cloudera.com>
Authored: Mon Jul 31 20:21:21 2017 +0100
Committer: Sean Owen <so...@cloudera.com>
Committed: Mon Jul 31 20:21:21 2017 +0100
----------------------------------------------------------------------
site/versioning-policy.html | 43 +++++++---------------------------------
versioning-policy.md | 22 +++++++-------------
2 files changed, 14 insertions(+), 51 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/spark-website/blob/88990968/site/versioning-policy.html
----------------------------------------------------------------------
diff --git a/site/versioning-policy.html b/site/versioning-policy.html
index 6ca2ee7..e0afa7c 100644
--- a/site/versioning-policy.html
+++ b/site/versioning-policy.html
@@ -242,12 +242,12 @@ available APIs.</p>
<h2>Release Cadence</h2>
-<p>From Spark 2.0.0, in general, feature (“minor”) releases occur every 4 months. Hence, Spark 2.2.0 would
-generally be released about 4 months after 2.1.0. Maintenance releases happen as needed depending
-on need. A minor release usually sees 1-2 maintenance releases in the 6 months following its first
+<p>In general, feature (“minor”) releases occur about every 6 months. Hence, Spark 2.3.0 would
+generally be released about 6 months after 2.2.0. Maintenance releases happen as needed.
+A minor release usually sees 1-2 maintenance releases in the 6 months following its first
release. Major releases do not happen according to a fixed schedule.</p>
-<h3>Spark 2.1 Release Window</h3>
+<h3>Spark 2.3 Release Window</h3>
<table>
<thead>
@@ -259,46 +259,17 @@ release. Major releases do not happen according to a fixed schedule.</p>
</thead>
<tbody>
<tr>
- <td>~ Nov 1 2016</td>
+ <td>Mid Nov 2017</td>
<td> </td>
<td>Code freeze. Release branch cut.</td>
</tr>
<tr>
- <td>Early Nov 2016</td>
+ <td>Late Nov 2017</td>
<td> </td>
<td>QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.</td>
</tr>
<tr>
- <td>Late Nov 2016</td>
- <td> </td>
- <td>Release candidates (RC), voting, etc. until final release passes</td>
- </tr>
- </tbody>
-</table>
-
-<h3>Spark 2.2 Release Window</h3>
-
-<table>
- <thead>
- <tr>
- <th>Date</th>
- <th> </th>
- <th>Event</th>
- </tr>
- </thead>
- <tbody>
- <tr>
- <td>~ Mar 1 2017</td>
- <td> </td>
- <td>Code freeze. Release branch cut.</td>
- </tr>
- <tr>
- <td>Early Mar 2017</td>
- <td> </td>
- <td>QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.</td>
- </tr>
- <tr>
- <td>Late Mar 2017</td>
+ <td>Early Dec 2017</td>
<td> </td>
<td>Release candidates (RC), voting, etc. until final release passes</td>
</tr>
http://git-wip-us.apache.org/repos/asf/spark-website/blob/88990968/versioning-policy.md
----------------------------------------------------------------------
diff --git a/versioning-policy.md b/versioning-policy.md
index 1d1a7e9..509b595 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -53,23 +53,15 @@ available APIs.
<h2>Release Cadence</h2>
-From Spark 2.0.0, in general, feature ("minor") releases occur every 4 months. Hence, Spark 2.2.0 would
-generally be released about 4 months after 2.1.0. Maintenance releases happen as needed depending
-on need. A minor release usually sees 1-2 maintenance releases in the 6 months following its first
+In general, feature ("minor") releases occur about every 6 months. Hence, Spark 2.3.0 would
+generally be released about 6 months after 2.2.0. Maintenance releases happen as needed.
+A minor release usually sees 1-2 maintenance releases in the 6 months following its first
release. Major releases do not happen according to a fixed schedule.
-<h3>Spark 2.1 Release Window</h3>
+<h3>Spark 2.3 Release Window</h3>
| Date | | Event |
| ----- |-| ------ |
-| ~ Nov 1 2016 || Code freeze. Release branch cut.|
-| Early Nov 2016 || QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.|
-| Late Nov 2016 || Release candidates (RC), voting, etc. until final release passes|
-
-<h3>Spark 2.2 Release Window</h3>
-
-| Date | | Event |
-| ----- |-| ------ |
-| ~ Mar 1 2017 || Code freeze. Release branch cut.|
-| Early Mar 2017 || QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.|
-| Late Mar 2017 || Release candidates (RC), voting, etc. until final release passes|
+| Mid Nov 2017 || Code freeze. Release branch cut.|
+| Late Nov 2017 || QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.|
+| Early Dec 2017 || Release candidates (RC), voting, etc. until final release passes|
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org