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 @@

Release cadence

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.

-

Spark 4.1 release window

+

Spark 4.2 release window

@@ -288,15 +288,15 @@

Spark 4.1 release window

- + - + - + 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. -

Spark 4.1 release window

+

Spark 4.2 release window

| 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|

Maintenance releases and EOL

November 1st 2025July 15th 2026 Code freeze. Release branch cut.
November 15th 2025Late July 2026 QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.
November 23th 2025August 2026 Release candidates (RC), voting, etc. until final release passes