CVS is no longer available for new projects, we only offer limited support for CVS for projects previously using it on the Classic SourceForge system.
We recommend that projects upgrade to a more modern SCM, like Subversion, rather than using CVS. CVS has limitations which newer SCM solutions have been designed to overcome. We continue to support CVS for those projects who decide that CVS adequately supports their needs.
SourceForge.net provides the following features in its CVS offering:
The standard way to modify the contents of your repository is using a CVS client.
CVS admins may also directly modify the repository contents via the interactive shell service. The adminrepo command line tool is used to manage CVS repositories; see adminrepo --help from within a project shell for more information on how to use adminrepo.
SourceForge.net performs routine backups for all of our servers and will restore from these backups in the event of catastrophic server failure. We encourage projects to make their own backups of CVS data as that data restore can be performed by the project in the event of accidental data destruction by a member of the project team.
Backups of a CVS repository may be made using rsync.
Example (replace PROJECTNAME with the UNIX group name of your project):
rsync -av rsync://PROJECTNAME.cvs.sourceforge.net/cvsroot/PROJECTNAME/\* cvs
We encourage all CVS projects to convert to git (or svn). Here are unofficial instructions for converting to git: http://bsdpower.com/sourceforge-cvs-to-git-conversion/
Documentation: CVS Adminrepo
Documentation: CVS Clients
Documentation: CVS Hook Scripts
Documentation: CVS Permissions
Documentation: CVS Syncmail
Documentation: SSH Key Fingerprints