Also take a look at writing a few hook scripts. When ever a developer checks in code to SVN that code gets immediately deployed to a central dev server. It also generates a changelog email and sends it to the team.
You can even set it up so that checkins to different branches go to different servers. An easier path is to run a cron job on a central server that does svn update every 10 min. (svn export will always pull in all the files, update will only pull in changes) But with a large group of developers you really need to get a dev process with lots of automation down now. Once you get code into production you probably won't have time to set this up. 2 more tips. pysvn makes it really easy for the hook script to talk to the repsitory, BUT if you running solaris (and using the binary subversion from sunfreeware that does not include the pysvn binding, and your sysadmin is too busy to recompile and upgrade because you didn't setup this level of automation a year ago...) then you should know that most svn commands have a -xml switch that generates xml output. -Aaron Held --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
