Le 01/05/2012 00:03, Marco Roello a écrit :
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.
This is simply a flaw in knpbundles: it displays only the Symfony
version required by the master branch of the bundle. But this does not
mean that other versions of the bundle cannot be compatible with Symfony
2.0.x. Many bundles out there are maintaining 2 branches, one for 2.0.x
and the other for 2.1
--
Christophe | Stof
--
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
