2/9 I'm starting a personal programming project and I need some revision
control system. What would you suggest given that the client and
server must run on Windows?
\_ Subversion
\_ Seconded. Subversion is probably the best revision control
system I've used. It is as easy to use and maintain as cvs
but has almost all the features of clearcase (including
versioned directories and symlinks).
\_ what is wrong with CVS? --clueless
\_ Does it have to be free?
\_ Free or <$50 for 1 user.
\_ Perforce is free for two users. If you make your project open
source, you can get a free multi-user license from them; I don't
know how willingly they give those out. I've heard svn is close to
p4 in functionality, even if it does pollute your file system. -gm
\_ p4 does a lot more than svn, but if you are a one or two person
team you probably won't ever use all that lot more.
\_ I didn't know that. Since that's what we use at work and I'm
reasonably happy with it that sounds like a good solution. Is
there anything better about Subversion I should know? -op
\_ I used Perforce in my previous job and now I use ClearCase.
Perforce has a nice feature called "change list" which ClearCase
doesn't. It's for grouping together related changes in multiple
files. Submitting changes in multiple files using change list
is atomic. You can include and exclude changes using the change
list number. You can also look up which changes in which other
files are tied to this change in this file, via the change list
number. I wish there is something similar in ClearCase. Now
in ClearCase we have to create labels for every change, and rely
on the individual engineer to manually list all the changed files
in the label description. Using labels doesn't make checking-in
atomic either. |