Personally I would prefer more smaller releases as much as possible. It makes code migration that much easier. I remember the absolute pain it was to go from 1.0 to 1.1 (granted some of that was due to poor code development on my end) but that was a hard transition.
Now I also realize 2.0 is nothing like 1.0. That being said one BC break is always ideal over several generations of BC breaks. However it does not sound terrible to get ready for a 2.1 release without the form component changes.
I can go either way, and I definitely see benefits/drawbacks to both possibilities.
On Apr 27, 2012, at 2:15 PM, Jordi Boggiano wrote:
> On 27.04.2012 20:09, Fabien Potencier wrote:
>> * 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.
> I'm for waiting. 2.0 was a first step, let's make 2.1 the one breaking
> release - because it's just not possible to get everything right the
> first time. A shorter release cycle with BC sounds great after that.
> Jordi Boggiano
> @seldaek - http://nelm.io/jordi >
> 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 symfon...@googlegroups.com > To unsubscribe from this group, send email to
> symfony-devs...@googlegroups.com > For more options, visit this group at