Le 20/06/2011 18:45, keymaster a écrit :
Does anyone else think we should be keeping 3rd party bundles separate
from the Symfony2 Standard Edition distribution, as a means of easing
future upgrades once Symfony2 becomes stable?
ie.
app/
bin/
src/
vendor/ (containing only 3rd party bundles not in the Symfony2
SE distribution)
SymfonySE/ (the Standard Edition code only)
Basically, once Symfony2 stabilizes, I would like to think the only
directory which Symfony2 maintenance changes effect, will in most
cases only be the SymfonySE/ directory.
Ideally, upgrading to a new maintenance release becomes a snap, just
replace one SymfonySE directory. The rest of your code should be
unaffected.
Am I out to lunch?
The SE is about creating a project. So it contains configuration files
with a default configuration. These are in app/ as it is the place where
they belong to. And I don't understand what you mean by "(containing
only 3rd party bundles not in the Symfony2 SE distribution)". The SE
comes with some third party bundles and libraries. If you want to add
more, you can. If you want to drop some of them because you don't use
them, you can. But I don't see the point of separating them in another
folder which would not follow the convention about the structure of a
Symfony2 project.
--
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 users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
