Menu
▾
▴
#126 Upgrade PLCSlib@Sourceforge to Allura platform
We have been informed by the SourceForge team that they are upgrading SourceForge to a new platform (code-named Allura).
As a result they will be retiring the Classic SourceForge platform, which PLCSlib (and DEXlib) is still using.
Their goal is to have everybody off of the old platform in the first quarter of next year, so that they can retire that code.
Hence they would like us to upgrade to Allura.
More information is available at:
https://sourceforge.net/p/upgrade/
https://sourceforge.net/p/allura/wiki/Features/
I have confirmed with SourceForge that the CVS repository will be migrated and that we can continue to use CVS.
They would however prefer us to migrate to Subversion.
PLCS CCB telecon: 2012-12-17
Agreed that we should:
1) notify all PLCS OASIC TC and upgrade to Allura
2) migrate to Subversion at some point once the upgrade to Allura has taken place, and once resource with appropriate CVS/Subversion expertise has been identified.
The reference to the issues in the model releasenotes needs to be updated to
reflect the new url of the tickets
/cvsroot/plcslib/plcslib/xsd/release_notes.xsd,v <-- release_notes.xsd
new revision: 1.3; previous revision: 1.2
/cvsroot/plcslib/plcslib/xsl/common.xsl,v <-- common.xsl
new revision: 1.36; previous revision: 1.35
/cvsroot/plcslib/plcslib/xsl/models/model_releases.xsl,v <-- model_releases.xsl
new revision: 1.4; previous revision: 1.3
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