VSS Code Synchronization
The funny thing about VSS is that the code synchronization is pretty slow when you are working on an onsite-offshore model. Consider this. I have a VSS Database in US. The developers are working here checking out and checking in files. There is another team working offshore. In a situation like this the synchronization becomes a nightmare if you have a separate VSS Database for the Offshore team.
Eventually the offshore team ends up checking out files remotely which is another development nightmare because the check out check in takes ages. And in case one of the developers is not disciplined enough and doesn't check in his files, then the onsite team doesn't know what to do and that module has to remain un-touched until the developer in India walks in the next day.
Visual Studio 2005 has come up with some new techniques to optimize the remote check out check in process as much as possible. But even so...
I am thinking about a strategy so that the team off shore works on a separate VSS Server and the synchronization isn't much of a nightmare... I am thinking that the responsibility of synchronizing should be handled by one person, who maintains the discipline and does his job efficiently... I have to come up with a strategy that makes sense... And i should be able to justify it...
Reader comments on this subject are welcome...