[ruby-core:25372] Re: [Feature #2033] Move Core Development to Git

Hi all,

2009/9/3 Yukihiro Matsumoto <[e-mail]>:
> For various reasons, we cannot move to git at once, so as a small
> step, use <git://github.com/shyouhei/ruby.git>.  See
>
> http://wiki.github.com/shyouhei/ruby/committerhowto
> http://wiki.github.com/shyouhei/ruby/noncommitterhowto


I like the phrase 'History repeats Itself.'

Subversion is not the first SCM for development of Ruby.
Ruby had used CVS in old days. I guess it is good thing
for us to know (or remember) when and how to move
from CVS to SVN.


On 2005-07-01, about 4 years ago, Shugo suggested to use SVN
as official SCM of Ruby. ([ruby-dev:26421])
At that time, some pros and cons were posted in ML.

1. In SVN, making branch is fast
2. In SVN, making diff to HEAD is fast too
3. WinCVS's graph function is good; TortoiseSVN's one is bad
4. TortoiseSVN in 1.14 is not stable(but 1.2.1 seems stable)
5. In SVN, commit is atomic; its commit log is useful when
   many files are modified.
6. BerkleyDB backend is(was?) not stable. FSFS is stable(?)

We also talked about tools for Windows (as we do now for git).
Some people said TortoiseSVN seemed good but unstable,
and svn commandline client is stable and good for CLI people.

On 2005-07-03, Kouhei Sutou made an experimental repository
of Ruby used by cvs2svn. Some commiters used it and found
some functions of svn was slower than CVS, such as
annotate and log.

But for a while, CVS was continued to use as one true official
SCM tool of Ruby. I could not find the main reason of it.

On 2006-11-28 (more than one year later), usa wrote a summary
of 1.8, 1.9 and moving to SVN ([ruby-dev:29964]).
In the background of this, there was a problem how to merge
YARV into Ruby. Some thought It's the chance to move to SVN.
(cf. [ruby-core:9385])

On 2006-12-20,  the mail '[ruby-dev:30039] CVS freeze' was posted
by Shugo. CVS repository was freezed.

On 2006-12-21, the mail '[ruby-dev:30043] SVN ready' was posted
by ko1. SVN repository was ready for use.

Since then, Ruby has used SVN as the official SCM.


That's all.
IMHO, the change of development environment of Ruby is not fast,
but when the chance has come, it happens at the end.
So, if git is better than SVN for Ruby, we will move to git some day.


Thanks,

Masayoshi Takahashi