+1 for releasing now By the time the Form part is stabilized there eventually will be another component which has a super new feature (that eventually breaks BC) -> then we are at the same situation as we are now. Do we wait for 4 months now and then for another 4 months again, and again...?
Also there are already some BC breaks. And if we wait the probaly will come even more BC changes besides the Form component. The more breaks there are the harder it gets to update from one version to the next. And it is a unpleasant work to go from one error (caused by a BC break) to the next, to the next... If there are fewer breaks people are more willing to upgrade and won't get too much bugged after the upgrade. On the other side, releasing now, will also give the people the choice if they want to wait until Symfony 2.2 or just upgrade to 2.1. Also releasing now (and in shorter cycles in general) lets the project look more active. Not everyone looks at the commits in the repository. The releases are what counts for end users. Am Freitag, 27. April 2012 20:09:50 UTC+2 schrieb Fabien Potencier: > > Hi all, > > The Symfony 2.1 release was expected to be published some time ago and > we struggle with it for two main reasons: > > * The number of contributions we have every single day. That's great but > it means that it is never a good time to release because of this last > minute great change that we want to merge first; > > * The recent BC breaks in the form/validator components. > > But basically, we cannot release 2.1 because of the second point. We > need to be sure that we only break BC for forms only once. So, we have > two options: > > * Wait for the form component to stabilize (which means that we are > happy with the state of the API and that enough people have played with > it and are happy with the features) > > * Release 2.1 as soon as possible (because we already have quite a few > nice enhancements). > > I thought that the second option was do-able by forking master and > reverting some PRs related to the form component (the ones that actually > break BC and are not stable yet because of some bugs or regressions -- > surprisingly, we are not talking about many of them). > > Many people think the contrary and so, I want to hear everybody's > opinion on this matter. > > 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. > > 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. > > Fabien > > -- > Fabien Potencier > Sensio CEO - Symfony lead developer > sensiolabs.com | symfony.com | fabien.potencier.org > Tél: +33 1 40 99 80 80 > > -- 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
