I'd vote against separating core bundles into repositories. I understand you might want to do that for SecurityBundle, since it will have a separate release timeline, but for things like FrameworkBundle or TwigBundle, it seems like an extra step and will make project management much more complicated (both for Symfony admins and developers).
Veering off topic here, but the proposal to put bundles and components side-by-side makes the difference between how they each organize unit tests all the more apparent. If both sit under a top-level src/Symfony namespace, components have their tests in tests/Symfony and bundles have tests within the src/XXXBundle/Tests directory. That's probably necessary to keep autoloading sane (esp. given how third-party submodules will essentially all be in their own repositories). On Sat, Feb 5, 2011 at 9:58 AM, Kris Wallsmith < [email protected]> wrote: > I would like to keep the current namespaces. Symfony is composed of > components and bundles. It makes sense to categorize them accordingly. > > Namespaces are a case-by-case thing. If we're violating a best practice by > including a Bundle namespace, the best practice should be changed. > > k > > On Feb 5, 2011, at 6:28 AM, Bulat Shakirzyanov <[email protected]> > wrote: > > I agree with Benjamin, think Doctrine\Common and Doctrine\ORM > > On Sat, Feb 5, 2011 at 9:18 AM, Benjamin Eberlei < <[email protected]> > [email protected]> wrote: > >> I disagree that we don't follow the best practice. Bundle is actually the >> Category namespace. >> >> That separates the code (component vs bundle) much better. >> >> greetings, >> Benjamin >> >> On Sat, 05 Feb 2011 04:46:15 +0100 >> Fabien Potencier < <[email protected]> >> [email protected]> wrote: >> >> > Hi all, >> > >> > Some time ago, we decided the best practice for bundle namespaces: >> > >> > Vendor\NameBundle >> > >> > like in: >> > >> > Sensio\BlogBundle >> > >> > But the Symfony bundles are different as they still have the Bundle\ >> > category: >> > >> > Symfony\Bundle\FrameworkBundle >> > >> > The more I think about it, the more I think this is not a good idea: >> > >> > * First, because Symfony itself does not respect its best practices, >> > which is weird; >> > >> > * Then, because at some point, each bundle will be hosted in its own >> > repository; so the need to differentiate between a bundle and a >> > component will be less important. My idea is for the symfony repository >> > to only contain the components and each bundle will have its own >> repository. >> > >> > So, what about removing the Bundle\ and Component\ categories >> altogether? >> > >> > Symfony\FrameworkBundle -> dedicated repository >> > Symfony\DoctrineBundle -> dedicated repository >> > >> > Symfony\Form -> in the components repository (the current symfony one) >> > Symfony\Security -> in the components repository >> > ... >> > >> > I was not in favor of dropping the Bundle\ category but now that the >> > decision has been taken, I think we should remove it everywhere. >> > >> > Fabien >> > >> > -- >> > Fabien Potencier >> > Sensio CEO - Symfony lead developer >> > <http://sensiolabs.com>sensiolabs.com | <http://symfony-project.org> >> symfony-project.org | <http://fabien.potencier.org>fabien.potencier.org >> > Tél: +33 1 40 99 80 80 >> > >> > -- >> > If you want to report a vulnerability issue on symfony, please send it >> to security at <http://symfony-project.com>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]> >> [email protected] >> > To unsubscribe from this group, send email to >> > <symfony-devs%[email protected]> >> [email protected] >> > For more options, visit this group at >> > <http://groups.google.com/group/symfony-devs?hl=en> >> http://groups.google.com/group/symfony-devs?hl=en >> > >> >> -- >> If you want to report a vulnerability issue on symfony, please send it to >> security at <http://symfony-project.com>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]> >> [email protected] >> To unsubscribe from this group, send email to >> <symfony-devs%[email protected]> >> [email protected] >> For more options, visit this group at >> <http://groups.google.com/group/symfony-devs?hl=en> >> http://groups.google.com/group/symfony-devs?hl=en >> > > > > -- > *Bulat Shakirzyanov* | Software Alchemist > > *a: *about.me/avalanche123 > *e:* <[email protected]>[email protected] > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at <http://symfony-project.com>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]> > [email protected] > To unsubscribe from this group, send email to > <[email protected]> > [email protected] > For more options, visit this group at > <http://groups.google.com/group/symfony-devs?hl=en> > http://groups.google.com/group/symfony-devs?hl=en > > -- > 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]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- jeremy mikola -- 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
