This is an interesting thread and I see very valid points from both sides of the debate.
My opinion would be for not causing pain, regardless of how easy (easier) it is to manage with Git, and delay the 2.1 release. Call a feature freeze, and from then until release, only allow bug fixes and the stabilizing pieces to go in. There's no reason a 2.1 release has to happen now, regardless of people clamoring for one. 2.0 is just fine, and another month or two won't hurt. Rather than a BC break now, and more again in July/August with 2.2, delay 2.1 and make July/August the 2.1 time frame, giving enough time to get the components stabilized, the BC breaks published, and bundle authors time to be ready. Just my 2 cents, FWIW. Cheers! --mark -- 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
