IMPORTANT: It's time to migrate from CVS (your input needed)

* Please read and contribute to the discussion *


I'm forwarding details of an important notification from Sourceforge
that I received earlier today:

"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."


Next steps:
===========

The Sourceforge announcement answers the question of *when* we have to
move away from CVS on sourceforge, but *not* to which replacement
VCS/platform.

I'd like to hear from all active admins/developers to gauge how we as
a project migrate from CVS, in terms of which VCS we choose, and on
which service/platform the project is hosted.

It is perfectly possible to stay with Sourceforge and migrate to
svn/git "in place".


Questions:
==========

Please answer these two important questions:

1) Which version control system would you like to use instead of CVS?

2) Which platform would you like the project's code to be hosted on?


I'd say we have about 4 weeks to reach a decision, until we need to
start getting ready for the planned migration away from CVS.

Sourceforge will disable CVS commits by end of November 2017.


My 10c:
=======

As I've indicated over the past couple of years I'm still 100% certain
that moving to the git VCS is the most appropriate migration from CVS.

As a project we already have an account reserved on github, and I have
been maintaining a CVS->git mirror for some years which allows for
build testing (via TravisCI across 10 distros) and easier development.

Moving to SVN would be, in my opinion, a backwards step and do nothing to:

  * attract new developers;
  * ensure the project's full development history is as widely
available as possible; and
  * improve the local development/testing experience



My thanks to all fellow XMLTV developers past, present and future!

Let's get the discussion started.

Cheers,
Nick

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xmltv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xmltv-devel