Work

I started the process to convert our organization's CVS repository to Subversion. I decided to do a mock implementation as my "pilot". I took the CVS repository and made a copy to another machine (Mac OS X 10.3.7) which serves as the "mock" Subversion server.

Our current CVS repository consists of two "major" projects and 26 small projects (support pieces, tools, scripts, etc). I decided to try to convert one of the major projects to start with.

Continue reading "Moving from CVS to SVN - Diving In"

I work as a Software Configuration Management (SCM) Engineer at a fairly large company who just happens to make a couple of widely used applications for Macintosh. As the person who is responsible for the source code repository (among many other things), I am burdened with providing the developers tools to increase their productivity and efficiency.

To that end, we have decided that we might want to make the move from CVS to Subversion. In other blog entries, I will chronicle the pilot and eventual move and detail what I experienced during the process.

I am using Making the Jump to Subversion as the "jumping off" point to switch to Subversion.

The following is a short synopsis of that article:

Making the Jump to Subversion by Adam Swift -- Subversion can run standalone or on a network as a repository server with multiple clients. The preferred client/server configuration uses Apache and WebDAV for network communication. It's a powerful alternative to CVS, and Adam Swift shows you the ins and outs in this tutorial.

We'll see how it goes!