On Mon, Apr 30, 2012 at 12:20:42PM +0100, Matt Robinson wrote: > > Actually Symfony 1.0.x, 1.4.x and 2.0.x are exactly this way - they had/have > long-term support and compatibility guarantees (this hasn't changed, right?)
I haven't followed 1.0 alot so I have no idea if this is being supported or not but 1.4 seems to be at least. 1.0 is not mentioned as an LTS here: http://www.symfony-project.org/installation Btw, an expiration of november 2012 for symfony 1.4 is way too early for it to be called *long term* support. In my view, three years after the next major release as an LTS is a minimum. Others would say five years all in all. Regarding 2.0, if it is an LTS it's a well hidden secret on symfony.com, I tried to find it but could not. Alot of blurb but no hints as far as I could find. I would expect it both on the download page and in a few places in points and pages linked to from http://symfony.com/what-is-symfony http://en.wikipedia.org/wiki/Symfony points at 2.2 as the first LTS for Symfony 2. > It's pretty typical for long-term support releases of software to fail to > get feature upgrades. It's the easiest way to guarantee stability. But of course, stability is the key. New features that does not break BC or API can be added, either as backports or just plainly added. It's all about breakage and API. You can do alot with even a framework while keeping the stability. In my view, you don't break API between minor versions. I guess I'm a dinosaur. Thomas. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
