On Fri, Apr 27, 2012 at 08:09:50PM +0200, Fabien Potencier wrote: > Let me reiterate the two possibilities here: > > * Wait for the form component to stabilize: we can probably schedule > 2.1 for August 2012. In the meantime, we should concentrate on the > form component and delay other big changes that can affect the > stability of the release. > > * Release 2.1 as soon as possible.
I vote for a proper 2.1 release with everything that's supposed to break as one big chunk. Aka: first option. > Whatever we choose, I want to next Symfony 2 releases to have > shorter release cycles (a bit like what I do with Twig); and for > that to happen, we need to keep BC as much as possible so that > people can upgrade to new versions without any fear. The way short release cycles work is with a pretty strict release manager. Do we have someone like that? The manager would have to cope with people nagging about just that little fix that saves the world and whales, aka "Just say no". With timed releases it's alot easier to be able to say no, just point at the time schedule and it should be understood. But we still need one. And tests, both compatibility and regression, loads. 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
