Hi, W dniu 28 kwietnia 2012 12:10 użytkownik canni <[email protected]> napisał: > Hey, > > I think we can have best of both worlds, linux kernel for years had similar > this technique, why not to follow guidelines like this: > > 1) Even minor numbers are considered stable (like 2.0, 2.2) > 2) Odd minor versions are "community" versions
This doesn't makes sense for Symfony. Linux doesn't use this model since 2003. > > 3) Every time when mainline "even" aka stable version come up, community > starts its job and post version like 2.1 > 4) when things from 2.1 are getting stable, over a time, they can be merged > into 2.2-beta/alpha whatever... > 5) 2.0 stable continues to evolve without BC breaks and with fixes, 2.1 may > or may not merge them into community > > > With this guidelines anybody can be satisfied, people may play with beading > edge version, and anyone can go for Even version, and wait till next stable > version, to minor numbers achead > > cheers, > canni > > W dniu piątek, 27 kwietnia 2012 20:09:50 UTC+2 użytkownik Fabien Potencier > napisał: >> >> 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 -- Best regards, Michal http://eventhorizon.pl/ -- 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
