Make versioning-policy up-to-date with Spark 4.2.0#661
Merged
dongjoon-hyun merged 2 commits intoapache:asf-sitefrom Jan 14, 2026
Merged
Conversation
Member
Author
|
I sent out an email to the spark@dev mailing list. |
yaooqinn
approved these changes
Jan 13, 2026
Member
yaooqinn
left a comment
yaooqinn
left a comment
There was a problem hiding this comment.
+1, LGTM. Thank you @dongjoon-hyun
Member
Author
|
Thank you, @yaooqinn . |
LuciferYang
approved these changes
Jan 14, 2026
cloud-fan
approved these changes
Jan 14, 2026
Member
Author
|
Thank you, @yaooqinn and @LuciferYang and @cloud-fan . |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Apache Spark Versioning Policy page is outdated. This PR aims to make it up-to-date with Spark 4.2.0 schedule.
Note that this is the last release before applying SPIP: Accelerating Apache Spark Release Cadence. We decided to keep the existing policy for Spark 4.2.x.