RE: Re: Shared working copy
From: Michael Miller <mmiller_at_unitrindirect.com>
Date: Sun, 21 Jun 2009 18:56:17 -0700 (PDT)
I want to thank everyone for your comments. I'm not new to change control, just Subversion, I've worked with ClearCase, Dimensions, Version Manager (PVCS) and SourceSafe in the past. Since management feels a shared working copy should work I was looking for concrete reasons why it wouldn't work with Subversion.
The problem is the way the development teams work. They check out from SourceSafe, make changes and check in when the change goes to production (maybe). If one developer has a file checked out that doesn't stop others from working on the same file, merging when necessary. They rely on good communications?
Each developer has an empty workspace (2000+ folders) and checks out only the files their working on. They compile and if the program requires other files not in their workspace their retrieved them from the dev server, qa server or production depending on where it's 1st found.
Checking out the full Subversion repository 23,000+ files into each developer's working copy doesn't work well with their build process (which is an in-house written Client/Server VB program which no one wants to take ownership of since the developer left). No surprise, but they would have the same issue with a ClearCase View and I'm sure with many other source control systems.
The fear is compiling from an SVN working copy with a full copy of the source they won't pick up the latest copy of includes from dev or qa. This wouldn't be a problem if they keep their working copy up to date. Most of these developers are used to a mainframe environment, not a Windows environment, and don't grasp the concepts of a good source control system.
For those of you who wanted to know more about the problem to be solved, you're probably sorry you asked. Thanks again for all your comments and suggestions.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
This is an archived mail posted to the Subversion Users mailing list.