Thanks for making this change. Those 3 months of overlap don't make a big difference to me as a developer, but they make a huge difference when trying to explain the symfony roadmap to a client.
David On Mon, Nov 2, 2009 at 4:13 AM, Fabien Potencier < [email protected]> wrote: > > After discussing the matter with the core team and especially Fabian > (the release manager of symfony 1.2), we have decided to extend the > support for symfony 1.2 for another 3 months. 3 months of overlap > seems like plenty of time to migrate your applications. The > installation page will be updated accordingly. > > Fabien > > On Nov 2, 8:18 am, Fabien Potencier <fabien.potenc...@symfony- > project.com> wrote: > > frédéric gontier wrote: > > > I love this framework too and in production mode i use only 1.0 > version. > > > I'm really afraid that Symfony could not be the success that it > > > deserves. > > > why? because backward compatibility is not supported with different > > > version of the framework, critic behavior's interface like email or > > > configuration are changed on every version. Maybe, it would be safe to > > > slow the releases and trace a stable roadmap for a LTS version. > > > I think that this discussion is really critic, so i hope that someone > > > like fabien would react. > > > > I have just answered to the original email. > > > > Fabien > > > > > > > > > Le mercredi 28 octobre 2009 à 17:23 -0400, Tom Boutell a écrit : > > > > 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/6937in 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. (: > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
