Menu
▾
▴
Re: A plea for volunteers (Fwd: CVS support at SourceForge ends Nov. 30)
|
From: Daniel J S. <dan...@ie...> - 2017-10-07 20:08:36
|
On 10/07/2017 01:30 PM, sfeam via gnuplot-beta wrote: > Well guys, it's been fun. > > SourceForge has announced that they will shut down CVS support next month. > I have little time available to deal with this, and minimal prior experience with git. First, building the git repository sans change history is simple. Just get a fresh CVS checkout and build a git repository from scratch. So there's that option to fall back on. One big question is whether there is a simple way to take the whole CVS data base and convert all the change history into a git repository with associated changesets. I think we've discussed before that the ChangeLog contents probably can't be sliced and diced into all the associated changesets--would have been nice, but at least we'll keep the ChangeLog file. [Or, for someone interested in taking on the transfer, I'll write below something that could be done.] There will no longer be a ChangeLog file. Instead all the per-changeset comments will be inherent in the changeset itself. That means that the person writing the changeset also writes the comments similar to the format used in ChangeLog then exports the whole changeset as a diff-file which has the comment at the top. That can be edited by the maintainers and the pushed into the canonical repository. That actually can save maintainers a lot of work. You'll like git (or mercurial), though, once used to it. It's not too difficult to use if utilizing only the simple commands, or working with the repository via gitg or something similar is easy. But the diff tools and so on are much nicer than CVS. Another question is SourceForge's support for an HTML interface to the git repository. It's nice to have an HTML-viewable log of what's going on rather than have to pull all the latest changesets. Do maintainers want to go all out with pull-requests, etc.? Probably not, seeing as changes are sort of funneled down to a few people for review, rather than having a whole large team of players committing to the canonical repository. So, in that respect, SourceForge's support for pull-requests isn't that critical. Just a nice log and difference viewer is good. Staying with SourceForge is fine with me, if that criteria can be met. For any volunteer thinking about taking on the transference from CVS to git, my idea of what to do with the old ChangeLog is the following: The nice thing about git changesets is that one can do git log and then use the usual unix-like vi searching through the pager-log it generates. I wonder if as the very first changeset in the new repository (or even if there is a comment associated with the "git init" process) that we take the whole contents of the current ChangeLog and copy that as the initial comment. It will be big, but at least we can then do a git log and that whole long ChangeLog history is right there at hand for searching purposes along with all the change-logs that come after it. Dan > So I am making a plea for a volunteer to step up and transfer the project files > to some git repository. > > I don't really care much where the repository lives, but unless the associated > gnuplot web site, bug trackers, mailing lists, etc are also moved it would > seem simplest to continue using SourceForge. > > If no one steps up, then I'm afraid gnuplot development will be offline > indefinitely. I will try to put out a 5.2.1 release before the deadline so > that at least the current state of development is captured. > I'll also make and keep an rsync backup. > > Please feel free to contact me privately if you don't want to reply here, > but everyone reading this has a stake in the project and is welcome > to offer opinions, suggestions, or whatever help you can. > > Ethan > > ---------- Forwarded Message ---------- > > Subject: CVS support at SourceForge and Nov. 30 > Date: Saturday, 07 October 2017, 16:20:47 > From: SourceForge Support <cvs...@so...> > > 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 > > ----------------------------------------- > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > gnuplot-beta mailing list > gnu...@li... > Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta |
