<br><br><div><span class="gmail_quote">On 9/4/06, <b class="gmail_sendername">Stefan Sperling</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sun, Sep 03, 2006 at 08:05:24PM +0200, Stefan Sperling wrote:<br>> On Sun, Sep 03, 2006 at 06:54:34PM +0200, Vapula wrote:<br>> > PS : how about moving to SVN, it should be lighter on the server, shouldn't<br>
> > it ?<br><br>The following has to be said about migrating to git:<br><br>On the plus side: It will rock!<br>Git suits our development model very well. Branching is encouraged,<br>and much more easy to use and natural than with cvs. We can move things
<br>around seemlessly without spoiling the history. Git seems to allow almost<br>anything in the repository, even symlinks! And there is no binary/text<br>data problem.<br><br>On the downside:<br>Committers will have to learn how to use git properly.
<br>This takes a bit of time. The documentation is very good,<br>but uses very informal style with a couple of jokes thrown<br>in here and there. While this keeps things from getting<br>too boring, you have to get used to the style of the
<br>documentation a bit before you know what is going on.</blockquote><div><br><br>SVN doesn't have that downside, my company recently switched to SVN from CVS over 2 days for more than 100 projects (and even more developers).
<br>Migration looked seamless, as you can keep the history of revisions from CVS.<br>The main features are :<br>- command-line client use mostly the same syntax for checkin/checkout as CVS, so there is virtually no learning curve
<br>- anonymous access is easy, through a simple web-like access and no auth needed. Checking out is way faster than CVS.<br>- documentation is pretty good (<a href="http://svnbook.red-bean.com/">http://svnbook.red-bean.com/
</a>) and there are GUIs for it if you want (TortoiseSVN, ...)<br><br>In the end, I guess it's just a matter of choosing one VC system and sticking to it.<br><br>I personnally prefer SVN, but then it's my only opinion and I'm not driving this project :)