The project currently uses CVS for the source code repository. Since the project has been dormant for some time, I'm wondering if now might be a good opportunity to migrate it to SVN.
From what I've read, the general consensus appears to be that there's no good reason not to move to SVN, other than the obvious learning curve for anyone not familiar with it or if you're relying on tools that don't support it. I'm certainly a lot more familiar with SVN than CVS, and I suspect anyone new to SCM tools is also more likely to be learning SVN.
I understand there are a number of different ways of migrating (see http://cvs2svn.tigris.org/cvs2svn.html). The simplest is just to export the latest version out of CVS and import that into SVN. The downside of this is that all the history is left in CVS. It seems that the tool cvs2svn does allow the repository to be converted as a whole and migrate all the history into SVN. This sounds like the more complete option.
Does anyone have any thoughts on this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As a test, I have taken the CVS repository and converted it to SVN on my local machine (using cvs2svn linked to in my earlier post). I can browse the repository and it looks to have kept all the version history etc. I obviously haven't tried loading it back into Sourceforge yet...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, please move to SVN. Git as a bonus would be great, but SVN is still more widely used, probably more so in the Oracle PL/SQL world. As Paul said, should be straightforward.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The SVN repository is up and running. I've left the old CVS one up as well for the time being for historical reference, but as far as I can tell, all the history has been migrated into SVN.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The project currently uses CVS for the source code repository. Since the project has been dormant for some time, I'm wondering if now might be a good opportunity to migrate it to SVN.
From what I've read, the general consensus appears to be that there's no good reason not to move to SVN, other than the obvious learning curve for anyone not familiar with it or if you're relying on tools that don't support it. I'm certainly a lot more familiar with SVN than CVS, and I suspect anyone new to SCM tools is also more likely to be learning SVN.
I understand there are a number of different ways of migrating (see http://cvs2svn.tigris.org/cvs2svn.html). The simplest is just to export the latest version out of CVS and import that into SVN. The downside of this is that all the history is left in CVS. It seems that the tool cvs2svn does allow the repository to be converted as a whole and migrate all the history into SVN. This sounds like the more complete option.
Does anyone have any thoughts on this?
Or migrate to Git? My personal preference is SVN because that's what I'm used to, but I know Git is popular...
As a test, I have taken the CVS repository and converted it to SVN on my local machine (using cvs2svn linked to in my earlier post). I can browse the repository and it looks to have kept all the version history etc. I obviously haven't tried loading it back into Sourceforge yet...
Thanks for working on the migration to Subversion. I think it's a good decision.
Yes, please move to SVN. Git as a bonus would be great, but SVN is still more widely used, probably more so in the Oracle PL/SQL world. As Paul said, should be straightforward.
In the interest of getting things going, I've made a start on converting to SVN. I feel that is the safest and easiest option at this stage.
The SVN repository is up and running. I've left the old CVS one up as well for the time being for historical reference, but as far as I can tell, all the history has been migrated into SVN.