Skip to content

Update EOL version info with 2.3.x #225

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

Closed
dongjoon-hyun wants to merge 1 commit into from
Closed

Update EOL version info with 2.3.x #225

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
4 changes: 2 additions & 2 deletions site/versioning-policy.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -283,8 +283,8 @@ <h3>Spark 3.0 Release Window</h3>
<h2>Maintenance Releases and EOL</h2>

<p>Feature release branches will, generally, be maintained with bug fix releases for a period of 18 months.
For example, branch 2.2.x is no longer considered maintained as of January 2019, 18 months after the release
of 2.2.0 in July 2017. No more 2.2.x releases should be expected after that point, even for bug fixes.</p>
For example, branch 2.3.x is no longer considered maintained as of September 2019, 18 months after the release
of 2.3.0 in February 2018. No more 2.3.x releases should be expected after that point, even for bug fixes.</p>

<p>The last minor release within a major a release will typically be maintained for longer as an &#8220;LTS&#8221; release.
For example, 2.4.0 was released in November 2018, but will likely see releases for more than 18 months,
Expand Down
4 changes: 2 additions & 2 deletions versioning-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,8 +68,8 @@ in between feature releases. Major releases do not happen according to a fixed s
<h2>Maintenance Releases and EOL</h2>

Feature release branches will, generally, be maintained with bug fix releases for a period of 18 months.
For example, branch 2.2.x is no longer considered maintained as of January 2019, 18 months after the release
of 2.2.0 in July 2017. No more 2.2.x releases should be expected after that point, even for bug fixes.
For example, branch 2.3.x is no longer considered maintained as of September 2019, 18 months after the release
of 2.3.0 in February 2018. No more 2.3.x releases should be expected after that point, even for bug fixes.

The last minor release within a major a release will typically be maintained for longer as an "LTS" release.
For example, 2.4.0 was released in November 2018, but will likely see releases for more than 18 months,
Expand Down