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 54fb09b Update note on 3.0 release timeline (#223)
54fb09b is described below
commit 54fb09b5c6021fe17692978da526cfa9ac5a6135
Author: Sean Owen <[email protected]>
AuthorDate: Wed Oct 16 17:53:15 2019 -0700
Update note on 3.0 release timeline (#223)
---
site/versioning-policy.html | 20 ++++++++++++--------
versioning-policy.md | 17 +++++++++++------
2 files changed, 23 insertions(+), 14 deletions(-)
diff --git a/site/versioning-policy.html b/site/versioning-policy.html
index f4316c8..8e1e0a7 100644
--- a/site/versioning-policy.html
+++ b/site/versioning-policy.html
@@ -251,30 +251,30 @@ 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 2.4 Release Window</h3>
+<h3>Spark 3.0 Release Window</h3>
<table>
<thead>
<tr>
<th>Date</th>
- <th> </th>
<th>Event</th>
</tr>
</thead>
<tbody>
<tr>
- <td>Mid Aug 2018</td>
- <td> </td>
+ <td>Late Oct 2019</td>
+ <td>Preview release</td>
+ </tr>
+ <tr>
+ <td>Early Dec 2019</td>
<td>Code freeze. Release branch cut.</td>
</tr>
<tr>
- <td>Late Aug 2018</td>
- <td> </td>
+ <td>Late Dec 2019</td>
<td>QA period. Focus on bug fixes, tests, stability and docs. Generally,
no new features merged.</td>
</tr>
<tr>
- <td>Early Sep 2018</td>
- <td> </td>
+ <td>Jan 2019</td>
<td>Release candidates (RC), voting, etc. until final release passes</td>
</tr>
</tbody>
@@ -286,6 +286,10 @@ in between feature releases. Major releases do not happen
according to a fixed s
For example, branch 2.2.x is no longer considered maintained as of January
2019, 18 months after the release
of 2.2.0 in July 2017. No more 2.2.x releases should be expected after that
point, even for bug fixes.</p>
+<p>The last minor release within a major a release will typically be
maintained for longer as an “LTS” release.
+For example, 2.4.0 was released in November 2018, but will likely see releases
for more than 18 months,
+beyond May 2020.</p>
+
</div>
</div>
diff --git a/versioning-policy.md b/versioning-policy.md
index 7c104a1..d68e169 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -56,16 +56,21 @@ 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 2.4 Release Window</h3>
+<h3>Spark 3.0 Release Window</h3>
-| Date | | Event |
-| ----- |-| ------ |
-| Mid Aug 2018 || Code freeze. Release branch cut.|
-| Late Aug 2018 || QA period. Focus on bug fixes, tests, stability and docs.
Generally, no new features merged.|
-| Early Sep 2018 || Release candidates (RC), voting, etc. until final release
passes|
+| Date | Event |
+| ----- | ----- |
+| Late Oct 2019 | Preview release |
+| Early Dec 2019 | Code freeze. Release branch cut.|
+| Late Dec 2019 | QA period. Focus on bug fixes, tests, stability and docs.
Generally, no new features merged.|
+| Jan 2019 | Release candidates (RC), voting, etc. until final release passes|
<h2>Maintenance Releases and EOL</h2>
Feature release branches will, generally, be maintained with bug fix releases
for a period of 18 months.
For example, branch 2.2.x is no longer considered maintained as of January
2019, 18 months after the release
of 2.2.0 in July 2017. No more 2.2.x releases should be expected after that
point, even for bug fixes.
+
+The last minor release within a major a release will typically be maintained
for longer as an "LTS" release.
+For example, 2.4.0 was released in November 2018, but will likely see releases
for more than 18 months,
+beyond May 2020.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
