At the moment the options are: - wait for even longer before we can get 2.1 out because of a component - release earlier and fix / break the component later on;
[TL;DR version] I would suggest for moving to a release 2.1 one once all the fixes required for a stable Form component are done and tested and then to move to a faster release cycle (see link at the end for possible style). [Long version] Since Symfony2 Framework is in fact a bunch of Components tied together into a framework/repository and we have Symfony2 Standard which actually makes those Components act as a MVC framework, I see no reason not moving the Components to their own version/release cycle and have Symfony2 Standard become the Symfony2.X version release for the whole framework. Having the Components go on their own version would help the bundle authors go on and support only changes up to a certain release in a certain Component and also bring more clarity in the bundle universe where some authors don't mention which version of Symfony2 they support. So instead of having an entire framework version to support, they just need to support certain Components version(s), which Composer should take care of. Having faster release cycles is also welcomed as if we delay much longer before 2.1 is out, 2.2 will potentially have a BC break as long as the current one, which is not fun but I understand why they where needed. It would also help people be able to see PR merged faster and released under an increment version maybe, say Symfony2 Standard, version 2.1.Y. And speaking about BC breaks, having a more often released increment number version of Symfony2 that includes deprecation/forward compatibility features, where possible, would help out people who want to be on the edge with the framework release. I see no reason why we couldn't have a release cycle for components like the one Microsoft has for the Windows updates, every second Tuesday of every month, in Microsoft's case, maybe we can do a every six week release cycle for small increments of Symfony2.X.Y this way? After all, the more people can use the latest version the more people can contribute to it, either with fixes or additions. As for versioning, maybe Symfony2 can borrow the concept from here: http://docs.cpanel.net/twiki/bin/view/11_30/InstallationGuide/CpanelProductVersions which I think it's pretty neat? At least this is my understanding of how Components should act like and what Symfony2 Standard/Composer are/should be for and how I think people would be less scared by the wave of BC breaks in major releases. Best regards, Florin On Friday, April 27, 2012 9:09:50 PM UTC+3, Fabien Potencier wrote: > > 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
