Issue #14551 has been updated by Eregon (Benoit Daloze).


naruse (Yui NARUSE) wrote:
> You need to read previous discussion in detail.
> #10547 has a point.

What's the point?
That we need a planner showing the merits and listing issues?

The title of #10547 sounds like that issue should be about listing issues to move to Git but as far as I see there is no list of issues there.
This is why I filed this issue.
I think it would be valuable to answer my 4 questions above about what are the problems to migrate to Git.
Some people might be willing to help once it's clear what needs to be done.

----------------------------------------
Feature #14551: What's missing to switch to Git instead of using Subversion?
https://bugs.ruby-lang.org/issues/14551#change-70677

* Author: Eregon (Benoit Daloze)
* Status: Rejected
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Target version: 
----------------------------------------
I know migrating to Git get asked at least every year at RubyKaigi, and this should be a motivation to change.
#14470 is one example making me wonder why we still use such an ancient technology like Subversion.

To be clear, this does NOT mean changing the issue tracker, that is orthogonal.

1) I have heard some scripts might stop working if we switch to Git and nobody knows a list of those scripts.
But, can't we just switch and adapt them as needed?
As long as this is not close to a release, I expect there will be a couple days where scripts are fixed
but after that pretty much everything should work just as well as before.

2) Are there Ruby committers still using Subversion? I would guess the vast majority is using Git.
Could they use https://help.github.com/articles/support-for-subversion-clients/ maybe if they want to keep using Subversion?

3) Does Redmine lack Git support? Is there an estimation of how much work it would take to add it?

4) Something else?

Advantages include:
* External people can contribute more directly with Pull Requests on GitHub, if they want (which is what most external contributors do).
  There is no need to squash their commits or manually checkout their branch, which delays integration significantly and loses the original author in the process
  (only mentioned as text while they really deserve to be marked as having contributed to Ruby).
* We use a non-obsolete technology and don't look like a language from the past.
* The setup for contributing to Ruby becomes much simpler (git clone, not a mix of SVN/git all the time)
* Many others advantages but listing them is not the point of this issue.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>