New VCS Choice; SCM SIG

Nicolas Mailhot nicolas.mailhot at laposte.net
Tue Jan 23 15:20:37 UTC 2007


Le Mar 23 janvier 2007 15:00, Ralf Corsepius a écrit :

> So, all in all, you should better make all these VCS stuff entirely
> transparent (Implement applications around it), or you'd better off
> using something standardized, ... which ATM, would reduce the choice to
> svn or CVS.

A lot of big projects (Linux, Xorg, Java VM, etc) are moving either to git
or hg today. hg/git are not "exotic", bazar/svn increasingly are (git/hg
are really the same choice as they're very similar fonctionnality-wise)

You have the following history

A. CVS sucks, but everybody but Linus uses it

B. lots of next-gen FLOSS VCS projects created after Linus starts using
bk. Two philosophies : slightly better CVS (SVN), radical new experimental
designs

C. ... a few projects choose SVN as a better CVS. Experimental scares people

D. Linus dumps bk, looks are next-gen VCSes, decides to write git. hg
announced at about the same time, with similar design

E. Public use of git and hg by big projects inspire confidence. New
projects go A->D or nothing->D. C starts loosing momentum fast. B never
took of

SVN was last year's good choice. CVS was last decade bad default.

-- 
Nicolas Mailhot




More information about the fedora-devel-list mailing list