tag:blogger.com,1999:blog-8209375572317710657.post566747021711686024..comments2019-12-10T09:20:53.758-05:00Comments on Rooneg::Weblog: ApacheCon US 2006 WrappupGarretthttp://www.blogger.com/profile/03388064732574616062noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-8209375572317710657.post-30475396457344949702006-11-06T10:24:00.000-05:002006-11-06T10:24:00.000-05:00Garrett,Please don't misunderstand me, I'm not ask...Garrett,<br>Please don't misunderstand me, I'm not asking you to do my homework...<br>"Upgrade svn.apache.org to Subversion 1.4.x"<br>I would like to ask you to write a blog entry about deploying Subversion at ASF. I own your Subversion book (http://www.apress.com/book/bookDisplay.html?bID=360), but I miss an example about real life and large scale Subversion deployment. According to http://uptime.netcraft.com/up/graph?site=svn.apache.org is FreeBSD). Why FreeBSD is a better choice than Linux? Because it is easier to keep Subversion &amp; Co up to date through Ports (unlike with Ubuntu/Debian stable)? Better performance? Both? What kind of hardware is required to run a site like svn.apache.org? What is the &quot;best&quot; layout for storing svn repositories (/var/lib/svn vs ...) What is your upgrade &quot;policy&quot;? 1.3.1 is still better/safer than 1.3.2 or 1.4.0? What hooks are you running? Do you have a backup strategy? Your choice of backend (fsfs, bdb)?<br>Thank you in advance.<br>--zx<br>Anonymousnoreply@blogger.com