18 Aug 2019

feedSymfony Blog

A Week of Symfony #659 (12-18 August 2019)

This week, Symfony added support for an alternative directory convention for bundles which is similar to the one used in full Symfony apps. In addition, it continued adding types for arguments across its entire codebase.

Symfony development highlights

This week, 104 pull requests were merged (52 in code and 52 in docs) and 29 issues were closed (22 in code and 7 in docs). Excluding merges, 46 authors made 5,747 additions and 4,703 deletions. See details for code and docs.

3.4 changelog:

4.3 changelog:

4.4 changelog:

Master changelog:

Symfony Local Server

Symfony Local Server, the best way to run Symfony applications on your local machine, released its new 4.6.4 version with the following changes:

Newest issues and pull requests

They talked about us

Upcoming Symfony Events

Call to Action


Be trained by Symfony experts - 2019-08-26 Lyon - 2019-09-2 Clichy - 2019-09-2 Clichy

18 Aug 2019 8:02am GMT

11 Aug 2019

feedSymfony Blog

A Week of Symfony #658 (5-11 August 2019)

This week, Symfony continued working on adding compatibility with the latest PHPUnit versions and made the PHPUnit Bridge component act as a polyfill for newest PHPUnit features. The translations of validation messages were also updated for some languages. Finally, Symfony announced some changes for standard version releases to align their end of support for both regular and security issues.

Symfony development highlights

This week, 141 pull requests were merged (121 in code and 20 in docs) and 69 issues were closed (68 in code and 1 in docs). Excluding merges, 50 authors made 8,033 additions and 4,067 deletions. See details for code and docs.

3.4 changelog:

4.3 changelog:

4.4 changelog:

Master changelog:

Newest issues and pull requests

They talked about us

Upcoming Symfony Events

Call to Action


Be trained by Symfony experts - 2019-08-26 Lyon - 2019-09-2 Clichy - 2019-09-2 Clichy

11 Aug 2019 8:35am GMT

05 Aug 2019

feedSymfony Blog

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.


Be trained by Symfony experts - 2019-08-26 Lyon - 2019-09-2 Clichy - 2019-09-2 Clichy

05 Aug 2019 6:47pm GMT