Tone, One other thing to consider: the choice of how to integrate developers is important, but probably more so is deciding on a release schedule. Your choice of tools and developer cooperation will be dictated by this somewhat.
For example, if you decide you will make changes "as they are fixed/changed" (not something I normally recommend, although that's what I'm doing it on one project now), then you will probably want to have everybody make changes that are reflected on a single server. This way all of your developers can find problems as well, rather than all using separate instances of servers and probably missing problems that way. If you decide to go on a short time-based release schedule, you might want some sort of staging server. This would allow people to test their changes without committing them, to see if they are suitable for that release. This work pretty well for service-based solutions. You might want to look up information on Agile development for more tips with short time-based releases. You could also go with a more traditional longer time- or features-based release schedule. In this situation, developers would probably work on their own servers exclusively and rely upon a QA team to test all changes that have been checked in to the trunk. I avoid this approach now because not only is it generally slow to develop (and not adaptive to changing customer needs), it also tends to introduce a lot of bugs. You also have to consider data - coordinating data changes can be tricky within a team. You should at least have a policy on data in the servers (i.e. do developers have to have a "filled" database or can they work with an "empty" one), as well as a database conversion policy for changes to a staging & production machine. Again this depends a lot on how much testing you expect your developers to do. Anyway, the short story is don't neglect your release schedule when deciding how to operate in a team. -rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
