Need a CVS system

Cheetah8799

Diamond Member
Apr 12, 2001
4,508
0
76
I'm doing research on CVS systems for our web development group. I'm finding that the GUI interfaces that show up in sourceforge for the original CVS system are outdated and not worked on anymore. Can anyone here suggest systems that they have used before, and that are still maintained?

Open-source is idea, but I am also interested in hearing about some purchasable products.

The ultimate goal is to be able to keep track of what files are checked out to be edited, who is editing them, who last edited, saved pervious versions, etc.

Thanks.
 

Armitage

Banned
Feb 23, 2001
8,086
0
0
I've been happy with Subversion, but my use of it is currently very elementary - command line only, very limited number of users, etc. Much nicer then CVS for some things like reorganizing source trees, renaming files, etc.
 

kamper

Diamond Member
Mar 18, 2003
5,513
0
0
If you're talking specifically about cvs (as opposed to subversion) and your devs are working on windows, I'd strongly recommend WinCVS. I haven't used TortoiseCVS but I have used TortoiseSVN (I assume they're similar) and thought it was almost as good. Getting them to learn the commandline is also a very good thing as it's really not all that much tougher. What dev environment do you use? Anything half-decently bloated probably has cvs builtin or available as a plugin or something.
 

Cheetah8799

Diamond Member
Apr 12, 2001
4,508
0
76
The group I work in is a small group of true developers, doing actual coding. Unfortunately we have a lot of "developers" outside of our group who I highly doubt will want to have anything to do with a command-line based version control system.

WinCVS looks to be currently updated, so I'll look at that some more. Most of our users are on Windows desktops.

Our current dev environment basically involves our developers mapping drives to various Solaris servers running Samba shares. The devs edit files on a dev server, and we have scripts to push to production. Only a few people run the push scripts. We have no current way to keep track of who edited what, when, and what the old version looked like. That's why we really would like a version control system, and one that all of our "devs" can manage to use and not freak out over.