Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Make versioning-policy up-to-date with Spark 4.1.0 #627

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 10, 2025
+8 −8
Merged

Make versioning-policy up-to-date with Spark 4.1.0 #627

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions site/versioning-policy.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.0 release window</h3>
<h3>Spark 4.1 release window</h3>

<table>
<thead>
Expand All @@ -288,15 +288,15 @@ <h3>Spark 4.0 release window</h3>
</thead>
<tbody>
<tr>
<td>January 15th 2025</td>
<td>November 1st 2025</td>
<td>Code freeze. Release branch cut.</td>
</tr>
<tr>
<td>February 1st 2025</td>
<td>November 15th 2025</td>
<td>QA period. Focus on bug fixes, tests, stability and docs. Generally, no new features merged.</td>
</tr>
<tr>
<td>February 15th 2025</td>
<td>November 23th 2025</td>
<td>Release candidates (RC), voting, etc. until final release passes</td>
</tr>
</tbody>
Expand Down
8 changes: 4 additions & 4 deletions versioning-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.0 release window</h3>
<h3>Spark 4.1 release window</h3>

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

<h2>Maintenance releases and EOL</h2>

Expand Down