I would like to introduce a (personal) problem that I encountered in the development of applications with symfony. My feeling when I waited for the "big jump" to version 2.0, was that of a framework that among the various goals, had to transparently handle version management. One of the major management problems at the end of the application has been (at least for me) just the upgrade procedure. "Everything is a Bundle": Symfony is a collection of bundles .... If we explore knpbundles.com, the downloads of the most important bundles already points to 2.1, creating confusion about who develops on the stable version instead.
Personally, I would opt to leave the updates that contain important BC alone , in the sense that the programmer, in the specific update, should focus mainly on the impact of the BC side effects and not on changes of other behaviors. -- 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
