[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Any recommendations on best practices to help non-developers with CVS?

From: Denis Haskin
Subject: Any recommendations on best practices to help non-developers with CVS?
Date: Tue, 07 Dec 2004 13:08:49 -0500
User-agent: Mozilla Thunderbird 0.8 (Windows/20040913)

I checked the archives but wasn't able to find anything quite on this topic...

Our developers use CVS for all version control. However, for historical reasons non-developers (e.g. business analysys, etc) use VSS.

We'd really like to be on only one version control system, and we also have had some difficulty with VSS that we haven't been able to figure out.

I've started introducing some of the business people to CVS (using TortoiseCVS and other client-side tools) and they've got some pretty serious reservations.

The biggest one (as you might expect) is the optimistic locking model. Given that more (most?) of their files are going to be binary, not text, the fact that there's no locking on checkout gives them the willies. Is there any way to address this? I've looked a bit at watch/edit/unedit, but it's unclear to me whether that would really address their concerns. Any comments?

Any other way to address this?

Their other concern so far is that they're used to being able to check out single files (instead of a whole project), but I'm a little less concerned about that--I think once they get used to having a local working copy, that won't be as much of an issue.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]