A week of Symfony

A weekly summary of everything that happened around Symfony development.

A week of symfony #596 (28 May - 3 June 2018)

This week, Symfony 4.1.0 was released, which includes more than 200 big and small new features. In addition, the registration for the SymfonyCon Lisbon 2018 conference opened with the first 100 early bird tickets available.

A week of symfony #595 (21-27 May 2018)

This week Symfony released 2.7.48, 2.8.41, 3.3.17, 3.4.11 and 4.0.11 versions to address several security vulnerabilities. Meanwhile Symfony 4.1.0 beta3 was published in preparation for next week's final release. Lastly, it was announced that the SymfonyLive USA 2018 conference will take place in San Francisco on October 11th and 12th.

A week of symfony #594 (14-20 May 2018)

This week, we continued polishing Symfony 4.1 before its stable release in two weeks. Our focus was on the Messenger component, which gained a ChainSender to implement multiple senders and also added support for middleware factories in config. Meanwhile, the work on Symfony 4.2 has already started and we added support for meta refresh in the BrowserKit component. Lastly, the dates for the SymfonyCon 2018 conference in Lisbon (Portugal) were announced for December 6th to 8th.

A week of symfony #593 (7-13 May 2018)

This week, the first beta of Symfony 4.1 was released, allowing you to test it more easily in your projects. We also posted some important updates about our diversity initiative. Lastly, we unveiled some new features for symfony.com, such as a new "dark theme" / "night mode".

A week of symfony #592 (30 April - 6 May 2018)

This week Symfony introduced new polyfills for PHP 7.3 and Ctype and started using the Ctype polyfill in Symfony's code. In addition, we made the Symfony command exceptions more concise and introduced a new Serializer interface to enable caching support. Lastly, the German Symfony community celebrated the SymfonyLive Phantasialand 2018 conference with great success.

A week of symfony #590 (16-22 April 2018)

This week, Symfony improved the performance of the Cache component inlining some function calls and simplified the usage of the new Messenger component allowing to omit the sender tag name and to use the adapter name instead of the service name. In addition, we added a new dd() helper which is useful when you can't or don't want to use a debugger.

A week of symfony #589 (9-15 April 2018)

This week, Symfony continued working on the new features of the upcoming 4.1 version, such as iterable support in the SymfonyStyle methods and a new AMQP adapter for the Messenger component. In addition, we opened the Call for Papers for SymfonyLive London 2018 conference.

A week of symfony #588 (2-8 April 2018)

This week was the first of the "feature freeze" period of Symfony 4.1. Development activity focused on finishing and polishing some of the pending features, such as a middleware that validates Messenger messages, a Monolog activation strategy for ignoring specific HTTP codes, the ability to set the rounding strategy for MoneyType and a feature to use custom functions inside allow_if security expressions.

A week of symfony #587 (26 March - 1 April 2018)

This week, Symfony 4.1 entered into its "feature freeze" period, so we finished some of its pending features: improved the Ajax panel in the debug toolbar, made exception pages more compact, avoid the double cache generation when running cache:clear command and lots of other minor changes. In addition, the French Symfony community celebrated the SymfonyLive Paris 2018 conference with great success. Lastly, we added Samuel Rozé as a new member of the Symfony Core Team.

A week of symfony #586 (19-25 March 2018)

This week Symfony focused on finishing important features before the Symfony 4.1 feature freeze starts next week: introduced a new Messenger component, internationalized routing, inlined routing config, transition blockers for workflows, allow to define multiple sections in Console output and added a server to collect VarDumper dumps. In addition, we updated the status of our diversity initiative.