Unless the current form stuff in Master will make life difficult because it's not well thought out (in which case I agree it should be reverted regardless of the pain), it might be appropriate to give further consideration to either freeze new features on Master and cut a RC as is, or delay another couple of months until you're happy enough with the state of Master to release it as an RC.
There are really two groups of people to consider: Those upgrading from 2.0 will be facing some BC breaks in any case elsewhere in the release, so there is not much additional testing effort if you include the current form stuff. On the other hand, for those building new sites, there are now several dozen, solid, 3rd party bundles working well with Master. Anyone building a new site can leverage them and get going pretty quickly. That is fairly valuable. If you create this new creature called "2.1 less some stuff", there will be 0 (zero) working 3rd party bundles initially. The incentive for 3rd party bundle owners to revert their code may not be so big, because after all, the code still works with Master. Some bundle owners may decide to skip 2.1 and stay on Master until 2.2 (which will be a quick release). That would be a shame. -- 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
