docs: Set an EOL for v3.x series - #237
Merged
Merged
Conversation
Our policy says that we will set an EOL for each major series at the release of the next major, and that we will give at least 12 months of bugfix and 24 months of security. Now that 4.0 is released, we can set the EOL for 3.x. We have intentionally restricted the scope of 4.0 so that it should be possible to upgrade most of the way with automated tools (Rector to convert to attributes, in-built tools to migrate to PHP config, etc). We also know that 3.x has been out for a long time and is generally stable - we don't get huge numbers of new bug reports. Therefore I think it's fine to offer our minimum 12 month / 24 month EOLs for 3.x.
Now that 4.0 is out, symfony 8 "is" supported :)
acoulton
force-pushed
the
docs-4.x-release
branch
from
September 28, 2026 16:30
7fb3534 to
e1a7a85
Compare
stof
reviewed
Sep 28, 2026
| ======= ========== ============ ============ ======================================================================= | ||
| Major Released Bugfix EOL Security EOL | ||
| ======= ========== ============ ============ ======================================================================= | ||
| `v3.x`_ April 2014 28 Sep 2027 28 Sep 2028 `Changelog <https://github.com/Behat/Behat/blob/3.x/CHANGELOG.md>`__ |
Member
There was a problem hiding this comment.
I suggest using the end of the month as limit, to simplify things (PHP did something similar for instance)
Contributor
Author
There was a problem hiding this comment.
Makes sense, thanks - done.
| Major Released Bugfix EOL Security EOL | ||
| ======= ========== ============ ============ ======================================================================= | ||
| `v3.x`_ April 2014 28 Sep 2027 28 Sep 2028 `Changelog <https://github.com/Behat/Behat/blob/3.x/CHANGELOG.md>`__ | ||
| `v4.x`_ tbc 2025/6 See below See below `Changelog <https://github.com/Behat/Behat/blob/4.x/CHANGELOG.md>`__ |
Member
There was a problem hiding this comment.
the release date should probably be updated
Contributor
Author
There was a problem hiding this comment.
Yep, missed that at first. Added now.
Simpler than fixing to the exact 12 months from now.
stof
approved these changes
Sep 28, 2026
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
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.
Our policy says that we will set an EOL for each major series at the release of the next major, and that we will give at least 12 months of bugfix and 24 months of security.
Now that 4.0 is released, we can set the EOL for 3.x.
We have intentionally restricted the scope of 4.0 so that it should be possible to upgrade most of the way with automated tools (Rector to convert to attributes, in-built tools to migrate to PHP config, etc).
We also know that 3.x has been out for a long time and is generally stable - we don't get huge numbers of new bug reports.
Therefore I think it's fine to offer our minimum 12 month / 24 month EOLs for 3.x.