On 15-Oct-07, at 8:31 PM, Rytis Sileika wrote:
> I was just wondering, what are the best practices to setup/manage > django projects? > > Let's assume two developers working on the same project, same machine. > Models, views are constantly changing, that would make me think that > the best way is to have two separate DBs and two separate django > projects for each developer, and merge these branches every week or > so. So branch per developer approach. Is that the normal approach to > manage django based projects? django projects - like all other projects - are managed by having a central repository. Each developer checks out the code and works on his own machine with his own local database. He then checks in his work to the repository. The guy in charge, tests the code, and if it works he the n does an svn up on the production site. Depending on the status of the developer he may get full, partial or no commit rights. -- regards kg http://lawgon.livejournal.com http://nrcfosshelpline.in/web/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
