From 993b6e666280022168224bab88aae6d390c3b674 Mon Sep 17 00:00:00 2001
From: Dongjoon Hyun <dongjoon@apache.org>
Date: Tue, 13 Jan 2026 10:03:20 +0900
Subject: [PATCH 1/2] Make versioning-policy up-to-date with Spark 4.2.0

---
 site/versioning-policy.html | 8 ++++----
 versioning-policy.md        | 9 +++++----
 2 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/site/versioning-policy.html b/site/versioning-policy.html
index 7259c44e9d5..838f87c7f25 100644
--- a/site/versioning-policy.html
+++ b/site/versioning-policy.html
@@ -277,7 +277,7 @@ <h2>Release cadence</h2>
 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 @@ <h3>Spark 4.1 release window</h3>
   </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 7969a977881..95f33a691b0 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -100,13 +100,14 @@ 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>
 

From e35901c50bed83298fe5a1dde01669d7a8bfaad8 Mon Sep 17 00:00:00 2001
From: Dongjoon Hyun <dongjoon@apache.org>
Date: Tue, 13 Jan 2026 10:04:10 +0900
Subject: [PATCH 2/2] a

---
 versioning-policy.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/versioning-policy.md b/versioning-policy.md
index 95f33a691b0..9a1625098a2 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -108,7 +108,6 @@ in between feature releases. Major releases do not happen according to a fixed s
 | 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>
 
 Feature release branches will, generally, be maintained with bug fix releases for a period of 18 months.