[spark-website] branch asf-site updated: Update Spark 3.4 release window (#407)

[do...@apache.org]

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 ad25dd72b Update Spark 3.4 release window (#407)
ad25dd72b is described below

commit ad25dd72b599178afd2390e131869b78d877b5c4
Author: Xinrong Meng <xi...@apache.org>
AuthorDate: Fri Jul 22 17:37:32 2022 -0700

    Update Spark 3.4 release window (#407)
---
 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 0851b5be3..437149a49 100644
--- a/site/versioning-policy.html
+++ b/site/versioning-policy.html
@@ -250,7 +250,7 @@ available APIs.</p>
 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.3 release window</h3>
+<h3>Spark 3.4 release window</h3>
 
 <table>
   <thead>
@@ -261,15 +261,15 @@ in between feature releases. Major releases do not happen according to a fixed s
   </thead>
   <tbody>
     <tr>
-      <td>March 15th 2022</td>
+      <td>January 15th 2023</td>
       <td>Code freeze. Release branch cut.</td>
     </tr>
     <tr>
-      <td>Late March 2022</td>
+      <td>Late January 2023</td>
       <td>QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.</td>
     </tr>
     <tr>
-      <td>April 2022</td>
+      <td>February 2023</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 55a0bd331..c1136de67 100644
--- a/versioning-policy.md
+++ b/versioning-policy.md
@@ -103,13 +103,13 @@ In general, feature ("minor") releases occur about every 6 months. Hence, Spark
 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.3 release window</h3>
+<h3>Spark 3.4 release window</h3>
 
 | Date  | Event |
 | ----- | ----- |
-| March 15th 2022 | Code freeze. Release branch cut.|
-| Late March 2022 | QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.|
-| April 2022 | Release candidates (RC), voting, etc. until final release passes|
+| January 15th 2023 | Code freeze. Release branch cut.|
+| Late January 2023 | QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.|
+| February 2023 | Release candidates (RC), voting, etc. until final release passes|
 
 <h2>Maintenance releases and EOL</h2>
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org