+1 from me on this. It has been difficult for us to explain to clients why the newest 1.2 release is only supported until 11/2009 when the next release isn't out yet and the 1.0 release has support which is expiring only 2 months later.
This makes any kind of conservative long term planning very difficult. If I'm starting a project today, do I pick the old release which will expire in 3 months, the newest release which will expire in 1, or the unfamiliar beta release? On Wed, Oct 28, 2009 at 2:23 PM, Tom Boutell <[email protected]> wrote: > > I understand that support for Symfony 1.2 is supposed to end in > November with the release of Symfony 1.3. > > What practices, if any, in Symfony 1.2 code are expected to be > incompatible with Symfony 1.3? > > I know Symfony 1.3 won't be the huge change that Symfony 1.1/1.2 were. > But I still don't think it's wise to drop support for practices > considered valid in 1.2 the moment 1.3 appears. > > Other long-established open source projects do not do this on such a > scale. Valid PHP 5.0.x code runs on PHP 5.3.x, with deprecation > warnings sometimes, but it runs. And 5.2.x is definitely still being > actively supported after the release of 5.3.x. > > It is very difficult to make responsible proposals to clients without > ongoing support for at least the previous minor version series for > Symfony. > > I know Symfony 1.2 wasn't supposed to be an LTS release but the > reality is that it was the first stable-enough-to-use release of > Symfony since the end of the 1.0.x series, and people have migrated > long term projects to it out of necessity. I strongly feel it should > be supported for at least a year after the release of 1.3. > > I also think it is appropriate to fix serious bugs like > http://trac.symfony-project.org/ticket/6937 in the 1.2 series, making > features work substantially as advertised unless the only possible fix > is a backwards incompatible change. But I can live without embedded > M2M relation forms ever working in 1.2. What I find difficult to live > without is enough stability that the Symfony releases page doesn't > frighten clients off. > > BC breaks in a mature system should be a major-version thing (2.0, not > 1.0), and there should be ongoing support of the previous major > version for quite a while when they happen. > > I love this framework - please help me sell it to my clients as > something that will continue to work for at least a year. (: > > -- > Tom Boutell > P'unk Avenue > 215 755 1330 > punkave.com > window.punkave.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 -~----------~----~----~----~------~----~------~--~---
