conversion of CVS to SVN

Hi there,

We're planning to upgrade our Infrae CVS contents at cvs.infrae.com to
Subversion on monday january 16, 2006.

After this upgrade, developers will need to use subversion (svn) in
order to check code in and out of our repository. Subversion offers the
same features as CVS, and more, and offers a more consistent and modern
implementation. We will also retain the ViewCVS functionality for our
site, but on top of the subversion repository instead.

Important:

If you are a developer working with a CVS checkout be sure you have
everything needed checked in before january 16. If you do not, it's not
a huge problem, but you'll have to copy your changed files manually into
a SVN checkout of the same codebase before you can check your changes in.

Many of you will already be familiar with Subversion, but for those of
you new to Subversion or those who need a refresher, this is a good
introduction concerning the use of the zope.org svn repository; note
though that many details will be different in our case:

http://www.zope.org/DevHome/Subversion/ZopeSVNFAQ

When the upgrade has taken place, we will follow up with an email
describing the new location of the repository, along with checkout
instructions and the like. Another step (made easier with SVN) we want
to take in the time following is to clean up our repository, removing
old cruft and improving the organization.

Regards,

Martijn