Skip to content

Update release policy page#688

Draft
HyukjinKwon wants to merge 2 commits into
apache:asf-sitefrom
HyukjinKwon:faster-release-update
Draft

Update release policy page#688
HyukjinKwon wants to merge 2 commits into
apache:asf-sitefrom
HyukjinKwon:faster-release-update

Conversation

@HyukjinKwon
Copy link
Copy Markdown
Member

This PR updates Release Policy page per SPIP: Accelerating Apache Spark Release Cadence.

@HyukjinKwon HyukjinKwon marked this pull request as draft May 14, 2026 00:29
Comment thread site/versioning-policy.html Outdated
Comment thread site/versioning-policy.html Outdated
Comment thread site/versioning-policy.html Outdated
Copy link
Copy Markdown
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The bootstrapping is always difficult. Given that, why don't we give an explicit example like 2026 and 2027 release plan, @HyukjinKwon and @cloud-fan ?

For example, I guessed like the following but it seems that this PR has a different timeline.

  • 4.2.0 (The original plan): 2026 Summer + 18 months.
  • 4.3.0 (LTS based on SPIP)
    • 4.3.0 RC1 will start after 3 months from the release day of Apache Spark 4.2.0 in 2026.
  • In 2027, Spark 5 will start as the annual release with the quarterly feature releases.
    • Spark 5.0: 2027.1
    • Spark 5.1: 2027.4
    • Spark 5.2: 2027.7
    • Spark 5.3: 2027.10 (LTS based on SPIP)

I just want to understand our plan of migration toward this SPIP. So, if there is an explicit example for 2026 and 2027. It would be perfect for me and all. The above is only one of personal understanding.

@dongjoon-hyun
Copy link
Copy Markdown
Member

cc @peter-toth , too.

Comment thread versioning-policy.md
Comment thread versioning-policy.md Outdated
Comment thread site/versioning-policy.html Outdated
@HyukjinKwon
Copy link
Copy Markdown
Member Author

I believe this is ready for another look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants