We are announcing that we are discontinuing support for CVS commits as of November 30th, 2017. The CVS data will still be available for historical access beyond that, but only for read-only access.
For our projects that are still actively using CVS for their development, we are suggesting a conversion to Subversion (SVN) since its workflow is pretty similar to CVS. We also recommend Git, a more distributed, advanced SCM (which might be a bit harder to get up-to-speed on).
We have conversion instructions available in our wiki to assist you in keeping your project going without too long of a pause (if any).
At SourceForge we have supported source-code commits using the Concurrent Versions System (CVS) since our earliest days. This SCM is one of the classics that were used at the start of the Open Source / Free Software movements. Two decades later most people have moved on to newer SCM setups, and a part of that is probably because CVS hasn’t been in active development for nearly 10 years now. It is finally time to say goodbye.
The CVS software has always been harder for us to support in a High-Availability environment than our other SCMs due to its lock files not working properly over NFS. We set things up to try to keep downtime as low as we could, but it has always been a single-point-of-failure in our setup, and thus CVS gets more outages for maintenance and such than our other SCMs. We have been planning to retire CVS for several years now, and it has finally run out of reprieves.
It is a bit sad to see such a classic SCM go away, but the move will help improve our ability to support the site, as well as to ensure that the unmaintained CVS code doesn’t harbor security issues that could compromise your project’s code.
Thank you for your understanding in this time of transition and let us know if you run into issues.
It was about time!
Well done, thanks!
I’m curious: any statistics on current CVS usage? how many projects are still actively using it, commits per day, etc? Thanks!