Re: SourceForge reorganization may affect gnuplot development site

[Mojca M. <moj...@gm...>]

On Thu, Oct 4, 2012 at 10:29 AM, Daniel J Sebald wrote:
>
> I'm not sure the repositories themselves are being replaced, but the
> other items are changing (e.g., bug tracker, etc.).  However, CVS seems
> to be downplayed a bit and only SVN, mercurial and git are listed as
> supported.  So, if when upgrading, gnuplot is forced to choose one of
> those three, then it is essentially the same as replacing.  Not that
> "upgrading" from CVS is bad.  (I've used mercurial pretty much and that
> seems nice.)

Probably not at this point, but I suspect that sooner or later CVS
will be phased out and it might happen that it won't be supported in
future at all. They wanted to completely drop support for CVS already,
but maybe too many projects complained, so they left it. CVS does
forget parts of history (when folder is deleted, file
properties/executable bits etc. are lost) and I find it very difficult
to navigate through changes.

I have found a nice workaround (which works for me) - converting CVS
to git and then working with git. And I don't seem to be the only one
doing that. Once I got used to cherry-picking commits (that works
amazing) and other sugars, it is difficult to think of going back.
That feature would be extremely useful in particular for "backporting"
bug fixes from trunk to branch-X-Y-stable.

In my opinion switching to a different version control system will be
necessary at one point, so it might be better to do it sooner rather
than later. (I love git, but any other version control you mention
above is better than CVS, and the decision/transition has to be made
by those who are contributing most. It would only make me happy as the
user if the upstream would use a different VCS.)

Mojca