On 30 Apr 2012, at 11:29, Thomas Lundquist wrote: > On Mon, Apr 30, 2012 at 12:19:46PM +0200, Christophe COEVOET wrote: > >> We will not remove all BC breaks as not all of them are related to >> forms. There is no reason to revert the refactoring of the Session >> for instance as the new architecture is better and users starting to >> code with Symfony 2.1 should benefit from the new (fixed) >> architecture instead of using the old one and having to rewrite >> their code. > > So, simple questions: When can the users expect a Symfony release they > can use for a few years without minor or major rewrites because of BC breaks? > > Right now, and with the story so far, both symfony 1 and 2, the answer > seems to be "never".
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?) 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. Look at RHEL/CentOS or Ubuntu LTS - they're supported for 3-5 years, and in that time usually get only bug-fixes, not new features. -- Matt -- 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
