On 31 Jul 2011, at 23:04, johnbohn wrote: > Not sure if this belongs in the user's or developer's group but I think it'll > make more progress posted here. I've run into a few people lately that wanted > to put their symfony2 app under version control with git but were confused > about the best strategy to do this with the app. The vendors install/update > seem to be the biggest point of confusion with the people I've talked to. > They're not sure whether to add them as submodules or what. I'm pretty sure > there's a few different things that people are doing now but it would be > great to come up with some kind of pattern that people could follow when > starting a new project. I think it would be great to add a section to the > cookbook about best practices for putting your symfony2 project under version > control. > > Thoughts?
I couldn't agree more, though I think the docs list is probably the better place for it. :) I'd love to see another Jobeet/Askeet-style tutorial, but which covers more than just Symfony2. -- Matt -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
