Re: Source Code Control

Tom Lucas wrote:
In the past our source code control has been based largely around CD
backups and individual's memories of why a change was made and where
the source is stored. I think the time has come whereby a more ordered
method of control needed but I do not want to add a big administrative
burdon to my development processes.

We are a small R&D department and only one of us is ever likely to be
working on a piece of code at any one time and there are no major
approval processes to be integrated. However, we do produce special
cuts of code for most customers so we have an awful lot of slightly
different versions of the same software that need to be stored in a
manner that can keep on top of it.

What method/package would people recommend? I've read through the
"Alternatives to Visual Source Safe" thread from July and people there
seemed to advocate CVS/SVN and PVCS. Noone seems to like VSS.

I would need something that would run on Windows, because the
department is not readed to get nixed up just yet, and I would prefer
it to be cheap/free. I would like to avoid any unnecessary complexity
because I don't envisage the size or number of our projects to change
hugely in the medium term to take advantage of it.

I could probably survive with a restricted access drive on a network
server with a database/spread*** recording what is stored. Perhaps I
could implement a "live" production area and a "development" area and
only the QA director would have access to move development builds into
the live area for release.

What do you reckon?

Thanks
Tom

Another vote here for Subversion.

I have used VSS for years and have a few years experience of ClearCase. I
am currently trying to migrate (by winning "hearts and minds"!) our dept to
Subversion (from VSS).

I've never had any reliability issues with VSS myself, but I found it was
weak in a few key areas. If you are new to version control then you
probably won't know what I'm on about, but VSS is very poor when it comes to
branching support. The more you use version control, the more you will come
to appreciate good branching support :)
Anyone who's ever tried to make a version controlled minor modification to
an old (i.e. not "latest") version of software without interfering with the
latest version of code in the database, using VSS will know where I'm coming
from.

Also, in Subversion the check-ins are versioned "per change" rather than
"per file" as in VSS. Much nicer.

I've been experimenting with Subversion for months and have been very
impressed with it. There are still one or two things I find slightly quirky
but that's the same with any new product until you get used to it...

R.


.