A week of symfony #412 (17->23 November 2014)
November 23, 2014 · Published by Javier Eguiluz
This week, Symfony project focused on tweaking and polishing all its features before the big Symfony 2.6 launch of the next week, including its shiny new installer. Meanwhile, preparations continued for the SymfonyCon conference, which will take place in Madrid next week and it will be the biggest event in Symfony's history.
Symfony2 development highlights
- 367ed3c: compared version using PHP_VERSION_ID constant instead of version_compare() function
- e28f5b8: [FrameworkBundle] be smarter when guessing the document root for the server:run command
- 92c8dfb: [SecurityBundle] authentication entry point is only registered with firewall exception listener, not with authentication listeners
- 76273bf: [FrameworkBundle] cache:clear command fills *.php.meta files with wrong data
- 4162713, 3039935: [HttpFoundation] made Request::get more performant
- 6e9642a: [WebProfilerBundle] fixed the profiler markup when the form has no name
- 8cf3d69: [TwigBundle/DebugBundle] moved dump extension & cleanups
- 5526dd7: [HttpKernel] fixed parse error in DumpDataCollector
- 8871368: [EventDispatcher] extracted an AbstractEventDispatcherTest from EventDispatcherTest and also use it in ContainerAwareEventDispatcherTest
- 2065e00, b3db574: [TwigBundle] fixed error page preview for custom twig.exception_controller
- 0d20753: [WebProfilerBundle] added abbrs with type classes
Newest issues and pull requests
- The Filesystem component cannot rename between different drives
- [DX] integrate database EXPLAIN analyzer in the profiler
- Add references from the API doc to the documentation on symfony.com
- integer and number do not return correct empty_data
- [Process] Controlling an interactive process
They talked about us
- Continuous Integration for Symfony apps, the modern stack: quality checks, private Composer, headless browser testing...
- Configuration dynamique avec Symfony ExpressionLanguage
- I Love WordPress but it Just Won’t Do it All. Hello Again Symfony.
- Symfony2: Get the templating service in a twig extension
- Deploying a Symfony2 app using Doctrine and PostgreSQL to Heroku
- A Week of Elcodi #3 (10/11 - 17/11)
- Más novedades sobre SymfonyCon Madrid 2014
- Faster Functional Tests
- Enhanced Symfony2 autoloader
- The Routing Component
- Form Type リファレンス
- Kit de survie : Les bonnes pratiques Symfony
- Symfony Best Practice 筆記2
- Lightning fast Symfony2 with some simple caching
- Symfony – Create a Soap server with Zend Soap
- The Security Component
- Symfony – Internationalisation des dates pour Twig
- Symfony 2.3.3のチュートリアル動画（英語)
- The Console Component
Published in #A week of symfony
Help the Symfony project!
As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.
seems bit redundant, why not use composer not good enough?
Really don't see the benefit of a installer like this at all.
* It's orders of magnitude faster (about 10 seconds vs. minutes when Composer cache is empty)
* It doesn't ask you anything (Composer installation asks you several questions and asks you to provide some configuration parameter values).
* It allows you to have a global "symfony" command in your system which in the future it could provide more useful commands for Symfony.
Most points I don't agree with,
* Faster installation great but not that valuable, if it becomes issue there ways with composer to make it faster.
* I like the questions also you can disable them during installation.
* I already have composer installed globally
Finally we had a good package manager for PHP and now we going the same route as NodeJS with it's army of package managers. Just going to make things more confusing I think.