On Oct 15, 10:01 am, Rytis Sileika <[EMAIL PROTECTED]> wrote: > Hi, > > I was just wondering, what are the best practices to setup/manage > django projects? [snip] > Thanks! > > Rytis
To expand on Chris' answer, here's what I would recommend: Create your project in Subversion (or CVS, or what have you). Have all your developers check out the head of this project. Have all developers work on the head, checking in small units of work and synchronizing repository changes often (at *least* daily). Let each developer maintain their own database and settings module. There are ideas on how to do this in this mailing list. I can give you my approach if you'd like. I'm not sure this is 'normal' to Django projects, but it's normal to all the other software projects I've worked on (10 years worth). I did briefly work with IBM ClearCase, where each developer maintained their own branch, syncing from and merging to head periodically, but I didn't find the extra separation very useful or helpful. Note that our team was 7 people. Maybe it's more useful in larger projects. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
