On 3/16/06, tonemcd <[EMAIL PROTECTED]> wrote: > > 3. People run their own local django installations, and commit changes > to a development server for testing before those changes are sent to > the deployment server. This means each individual user machine has to > have access to the databases and keeps a copy of the source on their > machine. It also means a lot of django trunk duplication on each > machine (I guess we could do an 'svn up' where the target is our own > django installation on the server - nice thought!). We have very little > experience of using svn etc however.
I couldn't imagine managing 10 developers on a project without a revision control system. Subversion is easy to learn and easy to use; I'd highly recommend you go that route with your project. Good luck -- and I'm glad to see you picked Django! :-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
