Le 24/08/2012 11:42, Lukas Kahwe Smith a écrit :
On Aug 24, 2012, at 11:06, Christophe COEVOET wrote:
Le 24/08/2012 10:57, William Durand a écrit :
Johannes wrote this bundle as well as many components in the core. I don't see
any problems with that. The Filesystem and the Routing components have been
improved by people who are not part of the core team.
William
PS: I still don't get who is part of the core team, who is not, why and why
not? :)
Well, the issue is that if it goes in the core, it has to be maintained by
Fabien: all changes in the core go through him, even when being done by
Johannes. So keeping it as a separate bundle makes the maintenance easier (and
also allows to have a separate release cycle for the bundle).
note that it is also the reason why MonologBundle and SwiftmailerBundle are not
in the core in 2.1 anymore (and why AsseticBundle was extracted before the 2.0
release).
Well the Bundle should stay separate .. if at all the "serializer" part of the
Bundle should be moved. If it doesnt get moved imho it would be great to at least
separate it from the Bundle either way. Of course Johannes has no small say in all of
this :)
regards,
Lukas Kahwe Smith
[email protected]
Well, Johannes already said on IRC he wants to split the bundle to
extract all the code independant from Symfony (i.e. 80% of the bundle at
least). I guess the main reason why it is not done is missing time :)
But then, if you move the serializer part ot the core, the issue is the
same: it is where all the complexity of the bundle lives. The DI
extension is not the heaviest part to maintain.
--
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
