[Geomview-devel] Sourceforge cvs support for geomview ending 30 Nov 2017

[Lloyd W. <llo...@ya...>]

We've had a long 17-year run out of cvs in SourceForge, but it's now reached end of life, and cvs clients are getting as rare as telnet clients in distros these days (e.g. not in current Mac OS X Xcode). So, geomview has to migrate to a new primary repository, per the SourceForge note below.

Mark was playing with github, and could bring that up to date:

https://github.com/geomview

which is one possibility, as are git on Sourceforge, mercurial on sourceforge -- or even svn on sourceforge, which I'll be looking at migrating SaVi to (as I'm pretty much the only developer there, and mercurial and git are complex configuration overkill for that project and this user. if you're capable of building the development geomview autoconf toolchain, git probably won't cause you too many difficulties.)

thoughts on the approach to take?

thanks, 

Lloyd Wood
http://savi.sf.net 
----- Forwarded Message -----
From: SourceForge Support <cvs...@so...>
Sent: Sunday, 8 October 2017, 3:22
Subject: CVS support at SourceForge and Nov. 30



Greetings project admin,


We have been planning to discontinue CVS support here at SourceForge for several years now, and that time has finally arrived. Since your project is making use of CVS for your source version control, you should now convert your repository over to another version control system.


The current plan is to stop allowing CVS commits by November 30th. To be able to continue making source code changes you’ll need to have your CVS repo converted by then. The ssh access method will stop working, but read-only access via both pserver, rsync, and interactive shell will continue to be available past the cutoff date (we haven’t determined if or when the read-only support will end). This means that you will have plenty of time to convert your data to a new SCM format, even well past the cutoff date.


If you don’t have a particular SCM choice in mind, we recommend choosing Subversion (SVN) since it has a workflow that is most similar to that of CVS. You might also want to choose Git, which is very popular these days, though it does have a steeper learning curve compared to switching to Subversion. You can even give each one a try and keep the one you like best. Don’t be afraid to experiment.


For information on how to convert your repository from CVS to SVN or Git, visit the following web page: https://sourceforge.net/p/forge/documentation/CVS/


The page also documents the rsync backup method.


We hope that your conversion goes smoothly. You can let us know if you run into any issues by replying to this email.


Sincerely,


SourceForge Support