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 814b24a982 Document Spark 4.0 release window (#562)
814b24a982 is described below

commit 814b24a9828b3bfc1471f79a9f472865191fc418
Author: Dongjoon Hyun <[email protected]>
AuthorDate: Wed Oct 2 11:10:35 2024 -0700

    Document Spark 4.0 release window (#562)
---
 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 75f1a2e772..c13d1e52ea 100644
--- a/site/versioning-policy.html
+++ b/site/versioning-policy.html
@@ -281,7 +281,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 3.5 release window</h3>
+<h3>Spark 4.0 release window</h3>
 
 <table>
   <thead>
@@ -292,15 +292,15 @@ in between feature releases. Major releases do not happen 
according to a fixed s
   </thead>
   <tbody>
     <tr>
-      <td>July 16th 2023</td>
+      <td>January 15th 2025</td>
       <td>Code freeze. Release branch cut.</td>
     </tr>
     <tr>
-      <td>Late July 2023</td>
+      <td>February 1st 2025</td>
       <td>QA period. Focus on bug fixes, tests, stability and docs. Generally, 
no new features merged.</td>
     </tr>
     <tr>
-      <td>August 2023</td>
+      <td>February 15th 2025</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 0f3892e8a2..5cae78a3c5 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -103,13 +103,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 3.5 release window</h3>
+<h3>Spark 4.0 release window</h3>
 
 | Date  | Event |
 | ----- | ----- |
-| July 16th 2023 | Code freeze. Release branch cut.|
-| Late July 2023 | QA period. Focus on bug fixes, tests, stability and docs. 
Generally, no new features merged.|
-| August 2023 | Release candidates (RC), voting, etc. until final release 
passes|
+| January 15th 2025 | Code freeze. Release branch cut.|
+| February 1st 2025 | QA period. Focus on bug fixes, tests, stability and 
docs. Generally, no new features merged.|
+| February 15th 2025 | 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]

Reply via email to