After I got back from my holiday in London, I was catching up on my RSS feeds. I was happy to see that Fabien has posted an update for the Symfony 2 schedule. At my work, we’re looking for a bit of stability, so having a schema and predictability is good news.
In this Symfony 2 schedule we’ll probably upgrade to Symfony 2.3, which will be the next LTS. Then we’ll wait out the next three small releases, and then make a big jump to 2.7. This part of the schedule works quite well. But how will we get along until the release of Symfony 2.3, which will be early May?
How does the Symfony 2 schedule look?
|Release||Release date||Supported untill|
|Symfony 2.0||Available||End of January|
|Symfony 2.1||Available||End of April|
|Symfony 2.2||End of February||End of October|
|Symfony 2.3||End of May||End of May 2016|
For the shorter term, the support for Symfony 2.0 will end in two weeks time, so we’ve been working to get all 2.0 applications to 2.1. Symfony 2.1 is not a safe haven to be at though, since it’s only supported until the end of April. Since we wait at least two weeks after a release to upgrade, this will give us 6 weeks of time to upgrade to Symfony 2.2. That’s a pretty tight schedule!
A bit of background
For the people that don’t know, Symfony is a PHP framework for web developers. You can use the whole framework, or you can pick some individual components that you like.
When you install a framework like this, you also have to maintain it. For Symfony 2 it comes down to updating the minor releases, and sometimes updating to a newer major version. Since a major version can break backwards compatibility this is harder to do. That’s why it’s nice that the Symfony 2 schedule is published, so we know how long security updates are provided.