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.
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.
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.
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.
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.
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.
This week, Symfony development activity was focused again on finishing the pending pull requests in time for the upcoming Symfony 4.1 "feature freeze" period which starts in just 2 weeks. We made testing easier by allowing to fetch private services from tests clients, improved the design of the new console "box" style and added some HTML5 features to the Symfony Profiler.
This week, Symfony 2.7.43, 2.8.36, 3.4.6 and 4.0.6 maintenance versions were published. Meanwhile, Symfony development activity focused on fixing minor bugs. Lastly, the "feature freeze" period for the upcoming Symfony 4.1 version starts in just 3 weeks, so we need your help to review issues and finish pull requests.
This week, Symfony 2.7.42, 2.8.35, 3.4.5 and 4.0.5 maintenance versions were published. In addition, Symfony improved the accessibility of the Bootstrap 4 form theme to comply with the WCAG standard: it fixed some HTML issues, added new attributes and improved how form errors are displayed. Finally, it was proposed a way to simplify the User and UserChecker.
This week, development activity was focused on finishing some of the new features for the upcoming Symfony 4.1 version: added support for 307 and 308 HTTP redirections, allowed writing prepared console commands, added support for configuring Argon2i encryption and deprecated the bundle notation.