This is an automated email from the ASF dual-hosted git repository.
gurwls223 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 f06babdb98 Document Spark 3.5 LTS period
f06babdb98 is described below
commit f06babdb98c4d97163c405622b2cc06c9d3c5797
Author: Dongjoon Hyun <[email protected]>
AuthorDate: Fri Nov 1 19:31:27 2024 +0900
Document Spark 3.5 LTS period
This PR aims to update Apache Spark versioning policy with Apache Spark 3.5
LTS period example.
Author: Dongjoon Hyun <[email protected]>
Closes #565 from dongjoon-hyun/v3.5_lts.
---
site/versioning-policy.html | 5 ++---
versioning-policy.md | 5 ++---
2 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/site/versioning-policy.html b/site/versioning-policy.html
index 40f28c8b22..6fce143b9c 100644
--- a/site/versioning-policy.html
+++ b/site/versioning-policy.html
@@ -312,9 +312,8 @@ in between feature releases. Major releases do not happen
according to a fixed s
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 2nd 2018 and had been maintained
for 31 months until 2.4.8 was released on May 2021. 2.4.8 is the last release
and no more 2.4.x releases should be expected even for bug fixes.</p>
-
+<p>The last minor release within a major release will typically be maintained
for longer as an “LTS” release.
+For example, 3.5.0 was released on September 13th 2023 and will be maintained
for 31 months until April 12th 2026.</p>
</div>
<div class="col-12 col-md-3">
diff --git a/versioning-policy.md b/versioning-policy.md
index 5cae78a3c5..8e500c11c1 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -117,6 +117,5 @@ Feature release branches will, generally, be maintained
with bug fix releases fo
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 2nd 2018 and had been maintained
for 31 months until 2.4.8 was released on May 2021. 2.4.8 is the last release
and no more 2.4.x releases should be expected even for bug fixes.
-
+The last minor release within a major release will typically be maintained for
longer as an "LTS" release.
+For example, 3.5.0 was released on September 13th 2023 and will be maintained
for 31 months until April 12th 2026.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
