The big issue with waiting is it just increases the risk and expectations on the eventual 2.1 as it becomes heavier and heavier.
Documentation will fall farther behind as new stuff is committed, upgrades will become more complicated, more features will need to be assimilated, and the number of tasks to organize and make the release process successful will grow too large, which in itself is a huge risk. We will all be much better off if we release the stuff we have working now, even if it means reverting some BC breaking stuff, as Fabien and a number of other core developers have recommended. This will create a necessary checkpoint where people are up to date with things again. It will be easier to move forward from there, with less risk to the subsequent releases. -- 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
