Closed
Description
Some history
- Back in July 2011, Symfony 2.0 released
- In October 2012, Fabien published a release process for symfony. This release process brought LTS releases to Symfony: Long bug and security support without having to upgrade your application with the risk of BC break
- In April 2013, Fabien introduced a new idea for Symfony: Stability over features
- In Januari 2014, Bernhard formalized this idea into the Symfony BC promise
The BC promise replaced LTS releases
With the BC promise, everyone can upgrade their applications to newer minor versions without having to worry about updating their code: It's BC! This means that it would no longer be neccesary to keep maintaining LTS releases, the whole 2.* version serie after 2.3 is one big LTS release.
3 Years of Symfony 2.*
3 days ago, we've all celebrated 3 years of Symfony 2.* (didn't you?). I believe it's time to move on and start working on Symfony 3.0. Why?
- The 3.0 upgrade guide already contains lots of things
- There are already enough features to fill 3.0 with lots of surprises: 3.0 milestone and others, which aren't milestoned yet, like [WIP] Refactored argument resolving out of the ControllerResolver #11457
- The DX initiative has brought up even more things which can't be fixed in a BC manner
- There is already a drive to bring new features to 2.* minor versions, which only caused confusion and angry devs (because of BC breaks). Those are for instance, the 3.0 directory structure and the Validation Visitor rewrite.
- Starting now means releasing somewhere in 2015 or later, there is so much to do before we can get there!