Symfony Maintenance: Changes for Standard Releases

As of Symfony 5.0, we are changing the way we manage security issues for standard releases. A standard release is any minor version that is not a LTS release: so, versions X.0, X.1, x.2, and x.3.

For these standard releases, we will align the EOM (end of maintenance) date with the EOL (end of life) date. So, instead of having 14 months of security fixes, we will only have 8 months.

For instance, Symfony 4.3 EOM date is January 2020 and EOL date is July 2020. With the new rules, EOL would have been January 2020. Symfony 5.0 will be the first release to implement the change: EOM and EOL dates will be July 2020.

We are making this change as backporting (or forwardporting) security issue patches on these versions proved to be difficult and time consuming (the code might have diverged a lot from the previous LTS but also from the current maintained minor version). We think that this extra time spent doing that is not worth it as projects following standard versions upgrade fast.

To be clear, this change does not affect LTS releases (4.4, 5.4, ...).

The "Release Process" page in the documentation has been updated accordingly.

Symfony Maintenance: Changes for Standard Releases symfony.com/blog/symfony-maintenance-changes-for-standard-releases

Tweet this

Comments

Makes sense, thank you!
Agreed. Merci.
Trying to better understand what comes with Symfony 5.0 I have found that you are using the word "Roadmap" on parts of this website in a way that seems to mean something different than it means for other software projects.

In the last paragraph of this blog post you are referencing to a page called "Release Process" for something, that is named "Roadmap" in different parts - e.g. https://symfony.com/roadmap

But a Roadmap usually contains information about *planned features* - this is not the case on that "Roadmap" page, that in fact shows the "Release Process".

Also there is a URL as part of the bottom menu of this website that contains the words "Symfony Roadmap" which leads to that thing that is in fact the description of the "Release Process", but does not show what usually would be expected to see in a "Roadmap", a list of planned features.

I believe it would be a great quality improvement for the Symfony project if you would like to adapt to the expected and established terminology used in software projects around the world.

However, now I still have not found the roadmap for Symfony 5 - yes, I mean "expected features" that will be released with that version :) - where can I find that?
@Quality Research Team there is no such public list of planned features for future Symfony versions.

We regularly scan the list of Symfony issues (https://github.com/symfony/symfony/issues) to check which features are the community asking. We also have a prioritized list of issues we would like to focus for the next Symfony version. It's here: https://github.com/orgs/symfony/projects/1

About the terminology, you are right that we don't follow the traditional usage of the "Roadmap" word, but so far we didn't receive feedback about this misuse. We'll change things in the future if we keep receiving feedback like this. Thanks!
Agreed

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.