+1 for releasing now As Bernhard said, most BC changes are not really a big deal. Sure it's better not to have them, but sometimes it cannot be avoided. Doing some minor adjustments in code and config files when upgrading is perfectly acceptable, when you weigh it against the benefits of having all the new features in 2.1.
Like many others, I'm anxiously waiting on 2.1. A trend I see more often these days, is that third party bundles are developed against master, and don't work with 2.0.x versions. This is not Symfony's fault off course, but it does indicate a problem: that we kind of have this situation where you have multiple codebases. Delaying 2.1 will increase the severity of this problem further. In my opinion this is far more annoying than doing some minor tweaks while upgrading. Also, keep in mind that large software vendors do not shy from breaking BC when needed, to keep the innovation going. Look at Apple for instance. -- 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
