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 50d6b6b7eb Make versioning-policy up-to-date with Spark 4.2.0 (#661)
50d6b6b7eb is described below
commit 50d6b6b7ebf4494ce83b450a342f46a9de2e71c9
Author: Dongjoon Hyun <[email protected]>
AuthorDate: Thu Jan 15 08:45:39 2026 +0900
Make versioning-policy up-to-date with Spark 4.2.0 (#661)
Apache Spark Versioning Policy page is outdated. This PR aims to make it
up-to-date with Spark 4.2.0 schedule.
Note that this is the last release before applying [SPIP: Accelerating
Apache Spark Release
Cadence](https://lists.apache.org/thread/31rx0xmwbhloljsowc9ksl6kk5vbb3r4). We
decided to keep the existing policy for Spark 4.2.x.
> Spark 4.2.x must also follow the current policy because development has
already progressed under that assumption.
---
site/versioning-policy.html | 8 ++++----
versioning-policy.md | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/site/versioning-policy.html b/site/versioning-policy.html
index 7259c44e9d..838f87c7f2 100644
--- a/site/versioning-policy.html
+++ b/site/versioning-policy.html
@@ -277,7 +277,7 @@ available APIs.</p>
Hence, Spark 2.3.0 would 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 4.1 release window</h3>
+<h3>Spark 4.2 release window</h3>
<table>
<thead>
@@ -288,15 +288,15 @@ in between feature releases. Major releases do not happen
according to a fixed s
</thead>
<tbody>
<tr>
- <td>November 1st 2025</td>
+ <td>July 15th 2026</td>
<td>Code freeze. Release branch cut.</td>
</tr>
<tr>
- <td>November 15th 2025</td>
+ <td>Late July 2026</td>
<td>QA period. Focus on bug fixes, tests, stability and docs. Generally,
no new features merged.</td>
</tr>
<tr>
- <td>November 23th 2025</td>
+ <td>August 2026</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 7969a97788..9a1625098a 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -100,13 +100,13 @@ The branch is cut every January and July, so feature
("minor") releases occur ab
Hence, Spark 2.3.0 would 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 4.1 release window</h3>
+<h3>Spark 4.2 release window</h3>
| Date | Event |
| ----- | ----- |
-| November 1st 2025 | Code freeze. Release branch cut.|
-| November 15th 2025 | QA period. Focus on bug fixes, tests, stability and
docs. Generally, no new features merged.|
-| November 23th 2025 | Release candidates (RC), voting, etc. until final
release passes|
+| July 15th 2026 | Code freeze. Release branch cut.|
+| Late July 2026 | QA period. Focus on bug fixes, tests, stability and docs.
Generally, no new features merged.|
+| August 2026 | Release candidates (RC), voting, etc. until final release
passes|
<h2>Maintenance releases and EOL</h2>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
