A number of potential developers are unable to contribute to the CVS repository due to issues with corporate firewalls (even when they follow the SourceForge recommendations of using port 433 for SSH communication)
Moving to Subversion would avoid the need for SSH since Subversion appears to use HTTPS instead which has the advantage of being less likely to be blocked by corporate firewalls.
If you would like to move to Subversion (or would like to remain with CVS or even move to Git) please respond to this thread so we can see what the opinion of the members is.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like to move to SVN - assuming that it does enable access from behind our corporate firewall and, of course, that access to the actual code repository becomes a requirement.
SVN is emerging as the current SCM tool of choice within BAE Systems Maritime - Naval Ships and Maritime Services.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In addition to eliminating the SSH barrier, SVN supports version control of directory trees. CVS will only version-manage individual files, making it cumbersome to configuration-manage Templates and other semantically meaningful collections of files. Experience with stepmod.sf.net has shown the limitations of CVS for managing STEP modules which, like templates, are composed of multiple source files.
The user interface to SVN is, by design, similar to that of CVS. So anyone already familiar with CVS should have a pretty easy time learning SVN.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We do not appear to have anybody disagreeing with the proposal to move to SVN. However, we have not had anybody step forwards and offer to perform the change. Speaking personally, I am a user of Subversion but as yet have not been involved with SVN admin so would be nervous of taking on the responsibility of moving us over to SVN.
Is there anybody that has SVN admin experience or can call on it from inside their organizations that could offer to make the change for PLCSlib?
Of course this process is being managed by the CCB so if anybody would like to step forwards could they respond to the Infrastructure ticket here
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
I am creating a backup of the repository in order to move to SVN over the next few days.
Can everyone please refrain from making any commits until we have moved over to SVN.
I will make the CVS repository read only this evening as soon as I have my backup completed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have completed the conversion to SVN and all seems to be working fine.
I have created a clone of the repository on my machine and everything looks good including all history from CVS.
I beleive I have made the CVS repository read-only now, so all commits must be made to the SVN repository. For details of the SVN repository please look at the Code tabe on the PLCSlib project page.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Phil,
Thanks for taking the time to that ceonversion to SVN.
Few questions :
* Will the CVS repository still be available (in read-only) and synchronised with the SVN repo ?
* Is there a procedure somewhere describing how to update the local copy of the former CVS structure to the new SVN one ?
Thanks in advance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A number of potential developers are unable to contribute to the CVS repository due to issues with corporate firewalls (even when they follow the SourceForge recommendations of using port 433 for SSH communication)
Moving to Subversion would avoid the need for SSH since Subversion appears to use HTTPS instead which has the advantage of being less likely to be blocked by corporate firewalls.
If you would like to move to Subversion (or would like to remain with CVS or even move to Git) please respond to this thread so we can see what the opinion of the members is.
I would like to move to SVN - assuming that it does enable access from behind our corporate firewall and, of course, that access to the actual code repository becomes a requirement.
SVN is emerging as the current SCM tool of choice within BAE Systems Maritime - Naval Ships and Maritime Services.
To me, moving to SVN is a no-brainer.
In addition to eliminating the SSH barrier, SVN supports version control of directory trees. CVS will only version-manage individual files, making it cumbersome to configuration-manage Templates and other semantically meaningful collections of files. Experience with stepmod.sf.net has shown the limitations of CVS for managing STEP modules which, like templates, are composed of multiple source files.
The user interface to SVN is, by design, similar to that of CVS. So anyone already familiar with CVS should have a pretty easy time learning SVN.
We do not appear to have anybody disagreeing with the proposal to move to SVN. However, we have not had anybody step forwards and offer to perform the change. Speaking personally, I am a user of Subversion but as yet have not been involved with SVN admin so would be nervous of taking on the responsibility of moving us over to SVN.
Is there anybody that has SVN admin experience or can call on it from inside their organizations that could offer to make the change for PLCSlib?
Of course this process is being managed by the CCB so if anybody would like to step forwards could they respond to the Infrastructure ticket here
Message from SourceForge:
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
I am creating a backup of the repository in order to move to SVN over the next few days.
Can everyone please refrain from making any commits until we have moved over to SVN.
I will make the CVS repository read only this evening as soon as I have my backup completed.
I have completed the conversion to SVN and all seems to be working fine.
I have created a clone of the repository on my machine and everything looks good including all history from CVS.
I beleive I have made the CVS repository read-only now, so all commits must be made to the SVN repository. For details of the SVN repository please look at the Code tabe on the PLCSlib project page.
Hi Phil,
Thanks for taking the time to that ceonversion to SVN.
Few questions :
* Will the CVS repository still be available (in read-only) and synchronised with the SVN repo ?
* Is there a procedure somewhere describing how to update the local copy of the former CVS structure to the new SVN one ?
Thanks in advance.