This is an automated email from the ASF dual-hosted git repository.
srowen 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 0cace05 Update EOL version info with 2.3.x
0cace05 is described below
commit 0cace05d36c23d84bc1fa272003b7dca7725cc8e
Author: Dongjoon Hyun <[email protected]>
AuthorDate: Sun Oct 20 10:41:43 2019 -0500
Update EOL version info with 2.3.x
This is not mandatory for release process, but I still get the questions
like the following.
- https://github.com/apache/spark/pull/25255#issuecomment-544116478
It would be great we keep our website up-to-date with the latest EOL
explicitly.
Author: Dongjoon Hyun <[email protected]>
Closes #225 from dongjoon-hyun/v2.3_EOL.
---
site/versioning-policy.html | 4 ++--
versioning-policy.md | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/site/versioning-policy.html b/site/versioning-policy.html
index 1961683..7df2de1 100644
--- a/site/versioning-policy.html
+++ b/site/versioning-policy.html
@@ -283,8 +283,8 @@ in between feature releases. Major releases do not happen
according to a fixed s
<h2>Maintenance Releases and EOL</h2>
<p>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.</p>
+For example, branch 2.3.x is no longer considered maintained as of September
2019, 18 months after the release
+of 2.3.0 in February 2018. No more 2.3.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,
diff --git a/versioning-policy.md b/versioning-policy.md
index b01c125..205588d 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -68,8 +68,8 @@ in between feature releases. Major releases do not happen
according to a fixed s
<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.
+For example, branch 2.3.x is no longer considered maintained as of September
2019, 18 months after the release
+of 2.3.0 in February 2018. No more 2.3.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,
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
