We have been talking about adopting a new release process for quite some time now, and I'm proud to announce that the new process has been formalized and published in the official documentation.
To make a long story short, Symfony now manages its releases through a time-based model. If you want to learn more about the Symfony release process, or about the first Symfony Long Term Support release, or about the release date for next version of Symfony, please take a minute to read the new process. You are also going to learn when we will start working on Symfony 3!
Published in
#Documentation
I hope it will help people to migrate their applications to recent versions, and avoid the gap between minor versions, like between symfony1.1 to 1.4
Great job! This will make the releases much more consistent.
I hope the docs can keep on track with this release circle, it was a little slow on the 2.1 documentation (which isn't complete yet)
please extend sf2.0 LTS support term until the new LTS is released. The half year gap would force to upgrade to a minor standart supported version, which is very costly for big projects..
#3 Laurynas : Don't worry, it says so in the post: "Paid support after the three year support provided by the community can also be bought from SensioLabs."
The 2.0 version is not a LTS and was never advertised as such.
@Laurynas: i feel your pain. supporting 2.0 is however also a big cost for the Symfony2 project itself. that being said, its very stable and so if you really dont want to upgrade to 2.1 or 2.2, then you should be able to hold out until 2.3. of course you might miss out on a few fixes for edge cases, but if the application is already written, then you will likely already have stumbled over the edge cases affecting you. now obviously if you do bigger code development, new things might pop up .. if you do plan a larger code push you might need to consider an upgrade to 2.1 after all.
The "You have 1 year to upgrade" on the LTS releases only works if Symfony 3.0 doesn't move entirely to Java and there is no upgrade path like with 1.4 -> 2.0 in which case there is no "upgrade" only "throw out and start again".
for a large application upgrading 2.0 -> 2.1 -> 2.3 in less then a year period is not a solution. I hope there will be a possibility to upgrade from 2.0 straight to 2.3 without having to rewrite most of the code..