You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by do...@apache.org on 2020/06/19 21:35:07 UTC
[spark-website] branch asf-site updated: Update Release Window from
3.0 to 3.1
This is an automated email from the ASF dual-hosted git repository.
dongjoon pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/spark-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 803a92f Update Release Window from 3.0 to 3.1
803a92f is described below
commit 803a92f73fb1c03edd65c765a679bb02a2879b93
Author: Dongjoon Hyun <do...@apache.org>
AuthorDate: Fri Jun 19 14:34:56 2020 -0700
Update Release Window from 3.0 to 3.1
---
site/versioning-policy.html | 12 ++++--------
versioning-policy.md | 9 ++++-----
2 files changed, 8 insertions(+), 13 deletions(-)
diff --git a/site/versioning-policy.html b/site/versioning-policy.html
index da9f2ef..f59eeac 100644
--- a/site/versioning-policy.html
+++ b/site/versioning-policy.html
@@ -328,7 +328,7 @@ available APIs.</p>
generally be released about 6 months after 2.2.0. Maintenance releases happen as needed
in between feature releases. Major releases do not happen according to a fixed schedule.</p>
-<h3>Spark 3.0 Release Window</h3>
+<h3>Spark 3.1 Release Window</h3>
<table>
<thead>
@@ -339,19 +339,15 @@ in between feature releases. Major releases do not happen according to a fixed s
</thead>
<tbody>
<tr>
- <td>Late Oct 2019</td>
- <td>Preview release</td>
- </tr>
- <tr>
- <td>01/31/2020</td>
+ <td>Early Nov 2020</td>
<td>Code freeze. Release branch cut.</td>
</tr>
<tr>
- <td>Early Feb 2020</td>
+ <td>Mid Nov 2020</td>
<td>QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.</td>
</tr>
<tr>
- <td>Mid Feb 2020</td>
+ <td>Early Dec 2020</td>
<td>Release candidates (RC), voting, etc. until final release passes</td>
</tr>
</tbody>
diff --git a/versioning-policy.md b/versioning-policy.md
index 86eabeb..a081890 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -103,14 +103,13 @@ In general, feature ("minor") releases occur about every 6 months. Hence, Spark
generally be released about 6 months after 2.2.0. Maintenance releases happen as needed
in between feature releases. Major releases do not happen according to a fixed schedule.
-<h3>Spark 3.0 Release Window</h3>
+<h3>Spark 3.1 Release Window</h3>
| Date | Event |
| ----- | ----- |
-| Late Oct 2019 | Preview release |
-| 01/31/2020 | Code freeze. Release branch cut.|
-| Early Feb 2020 | QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.|
-| Mid Feb 2020 | Release candidates (RC), voting, etc. until final release passes|
+| Early Nov 2020 | Code freeze. Release branch cut.|
+| Mid Nov 2020 | QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.|
+| Early Dec 2020 | Release candidates (RC), voting, etc. until final release passes|
<h2>Maintenance Releases and EOL</h2>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org