<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Factory Automation Software Blog &#187; accurev</title>
	<atom:link href="http://factoryswblog.org/tag/accurev/feed/" rel="self" type="application/rss+xml" />
	<link>http://factoryswblog.org</link>
	<description>Merging modern software development with electrons and metal</description>
	<lastBuildDate>Wed, 09 May 2012 00:34:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Subversion and Other Version Control Choices</title>
		<link>http://factoryswblog.org/2008/01/18/subversion-and-other-version-control-choices/</link>
		<comments>http://factoryswblog.org/2008/01/18/subversion-and-other-version-control-choices/#comments</comments>
		<pubDate>Sat, 19 Jan 2008 05:37:47 +0000</pubDate>
		<dc:creator>Tony</dc:creator>
				<category><![CDATA[Version Control]]></category>
		<category><![CDATA[accurev]]></category>
		<category><![CDATA[bazaar]]></category>
		<category><![CDATA[darcs]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[mercurial]]></category>
		<category><![CDATA[perforce]]></category>
		<category><![CDATA[svn]]></category>

		<guid isPermaLink="false">http://factoryswblog.org/2008/01/18/subversion-and-other-version-control-choices/</guid>
		<description><![CDATA[Quick overview of version control software for automation developers]]></description>
			<content:encoded><![CDATA[<p><strong>Version Control and Software Configuration Management Resources</strong></p>
<p>In the end, good developers and good processes matter more than the tools. So here are two good sources for information and answers on version control and software configuration management: comp.software.config-mgmt newsgroup (low level of traffic, but I&#8217;ve seen some good conversations there) and <a href="http://www.cmcrossroads.com">CMCrossroads</a>.</p>
<p><strong>Commerical Version Control Software</strong></p>
<p>A few years ago, I did an extensive look at commercial version control software.  The two I was most impressed with were <a href="http://www.perforce.com">Perforce </a>and <a href="http://www.AccuRev.com">AccuRev</a>.  Perforce is a traditional VCS, with a reputation for speed and good support.  AccuRev has an innovative approach (streams) .  Both are worth consideration, but are $750/developer or more, plus yearly maintenance fees.  At work, I&#8217;ve been very happy with Subversion, but Larry O&#8217;Brian has seen some speed <a href="http://www.knowing.net/index.php/2007/12/29/">bumps</a>.</p>
<p><strong>Subversion</strong></p>
<p>I&#8217;ve been using <a href="http://subversion.apache.org/">Subversion</a>, and have been very happy with it.  I still think it is an excellent version control system for most automation companies, and I will be doing a series of blog posts using it.  Some of its good points:</p>
<ul>
<li>It&#8217;s free (and open source)</li>
<li>Its centralized approach fits the model of most automation developers (unlike open source projects, which tend to be highly distributed).</li>
<li>It runs well on Windows (unlike some open source version control systems)</li>
<li>It has good, free documentation</li>
<li>It is widely available for hosting (<del>for example, it&#8217;s the only VCS available on Webfaction&#8217;s Control Panel</del>)</li>
<li>It has excellent tool support, including on Windows</li>
<li>It is constantly updated (V1.5 will have substantial improvements)</li>
</ul>
<p><strong>Innovative Version Control Systems</strong></p>
<p>The open source version control field has been very fertile, with several innovative approaches.  I&#8217;d say the open source side has been more innovative than the commercial side.  The ones that have caught my attention are <a href="http://git.or.cz/">git</a> (of Linux fame, and right now probably the &#8220;hot&#8221; one), <a href="http://darcs.net/">darcs</a>, <a href="http://www.selenic.com/mercurial/wiki/">mercurial</a>, and <a href="http://bazaar-vcs.org/">bazaar-ng</a>.  All of these systems are designed for distributed development, unlike most version control which is based around a central server.  Later I plan on looking into them in-depth, and trying one out &#8211; I have a few project ideas that would benefit from a more distributed approach.</p>
<p><em>Tony</em></p>
 <img src="http://factoryswblog.org/wp-content/plugins/wordpress-feed-statistics/feed-statistics.php?view=1&post_id=38" width="1" height="1" style="display: none;" />]]></content:encoded>
			<wfw:commentRss>http://factoryswblog.org/2008/01/18/subversion-and-other-version-control-choices/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

