Also, I believe IOhannes already did a lot of work to get SVN running; last I saw we were basically just waiting for everyone else to be ready? I'll let him confirm but it would be a shame to have wasted his time : ).
<div><br class="webkit-block-placeholder"></div><div>Info on SVN 1.5 is here:</div><div><a href="http://subversion.tigris.org/svn_1.5_releasenotes.html">http://subversion.tigris.org/svn_1.5_releasenotes.html</a><br><br><div>
<span class="gmail_quote">On 10/23/07, <b class="gmail_sendername">Luke Iannini (pd)</b> <<a href="mailto:lukexipd@gmail.com">lukexipd@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><span class="q"><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">Actually, it would be good if you did push the idea. :D I think if<br>we aren't switching to SVN, we really should consider a distributed
<br>system. I am just not sure which one is the best one for the Pd<br>community. While Linus' personality is funny, his ideas about<br>software usability are what make me think there are better systems<br>than git.
<br><br> From what I see, Git is good for someone who's immersed in it,<br>therefore the extra complexity is beneficial. Pd committers don't do<br>it that often, and are rarely immersed in coding everyday. That says
<br>that we should use something that is really easy to learn, setup, and<br>administer, even if that means it might be less efficient for more<br>advanced tasks.<br><br>For example, GNU Arch says on the first page (<a href="http://www.gnu.org/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.gnu.org/</a><br>software/gnu-arch/) that "GNU arch has some features that make it<br>particularly useful for public free software projects: it's easy to<br>learn; it's inexpensive and easy to administer". Git (http://
<br><a href="http://git.or.cz/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">git.or.cz/</a>) repeatedly mentions "speed and efficiency".</blockquote><div><br> </div></span><div>Sigh, anything is better than CVS... so I won't complain too loudly if we go with something other than SVN. But considering how long it's taking to go to SVN, which everyone agrees with, I'm worried we'll just get bogged down in discussion of the myriad options.
</div><div><br> </div><div>Many of SVN's deficiencies are being addressed in the very-very-soon upcoming 1.5 update, which includes vastly improved merging to compete with Git.</div><div>
<br> </div><div>Also, since SVN has such wide adoption, it has really excellent client tools. I use SCPlugin, which integrates SVN with the Mac OS X Finder, along with TextMate's absolutely incredible SVN bundle. Windows users have access to the amazing TortoiseSVN, which offers the best integration I've seen.
</div><div><br> </div><div>Anyways, here's to a swift death for CVS.</div><div>Cheers</div><div>Luke</div></div>
</blockquote></div><br> </div>