<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: SVN migration</title>
	<atom:link href="http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/</link>
	<description>Dave Neary's view of the world</description>
	<lastBuildDate>Sun, 11 Dec 2011 14:17:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Marius Gedminas</title>
		<link>http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/comment-page-1/#comment-484</link>
		<dc:creator>Marius Gedminas</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/#comment-484</guid>
		<description>bzr and baz-ng (actually, bazaar-ng) is one and the same.  bzr is the command name, Bazaar 2.0 (previously Bazaar NG) is the project name.  Sort of like svn and Subversion.&lt;p/&gt;I think the future belongs to either bzr or git.  The present belongs to Subversion, which has proven itself in the field.  Just stay away from Subversion&#039;s bsddb backend!&lt;p/&gt;Have you read Keith Packard&#039;s blog posts about choosing the revision control system for X.org?  They&#039;re worth reading:&lt;p/&gt;&lt;a href=&quot;http://keithp.com/blog/Repository_Formats_Matter.html&quot;&gt;http://keithp.com/blog/Repository_Formats_Matter.html&lt;/a&gt;&lt;p/&gt;&lt;a href=&quot;http://keithp.com/blog/Tyrannical_SCM_selection.html&quot;&gt;http://keithp.com/blog/Tyrannical_SCM_selection.html&lt;/a&gt;&lt;p/&gt;(hmm, I don&#039;t see a &#039;Preview&#039; button...)</description>
		<content:encoded><![CDATA[<p>bzr and baz-ng (actually, bazaar-ng) is one and the same.  bzr is the command name, Bazaar 2.0 (previously Bazaar NG) is the project name.  Sort of like svn and Subversion.
<p />I think the future belongs to either bzr or git.  The present belongs to Subversion, which has proven itself in the field.  Just stay away from Subversion&#8217;s bsddb backend!
<p />Have you read Keith Packard&#8217;s blog posts about choosing the revision control system for X.org?  They&#8217;re worth reading:
<p /><a href="http://keithp.com/blog/Repository_Formats_Matter.html">http://keithp.com/blog/Repository_Formats_Matter.html</a>
<p /><a href="http://keithp.com/blog/Tyrannical_SCM_selection.html">http://keithp.com/blog/Tyrannical_SCM_selection.html</a>
<p />(hmm, I don&#8217;t see a &#8216;Preview&#8217; button&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Germán Poo-Caamaño</title>
		<link>http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/comment-page-1/#comment-485</link>
		<dc:creator>Germán Poo-Caamaño</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/#comment-485</guid>
		<description>&gt; Obviously there&#039;s some argument about the Right Way to do &lt;br/&gt;&gt; distributed version control - otherwise, why so many to &lt;br/&gt;&gt; choose from?&lt;p/&gt;Please, don&#039;t use such argument.  In that case, use Windows, because there are some many Linux distributions.&lt;p/&gt;The only strong argument to use SVN instead anyother tool, is because there is one sysadmin working in SVN but nobody else has taken the job to test other tools.  That&#039;s enough.</description>
		<content:encoded><![CDATA[<p>&gt; Obviously there&#8217;s some argument about the Right Way to do <br />&gt; distributed version control &#8211; otherwise, why so many to <br />&gt; choose from?
<p />Please, don&#8217;t use such argument.  In that case, use Windows, because there are some many Linux distributions.
<p />The only strong argument to use SVN instead anyother tool, is because there is one sysadmin working in SVN but nobody else has taken the job to test other tools.  That&#8217;s enough.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/comment-page-1/#comment-486</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/#comment-486</guid>
		<description>&gt; Also, none of those systems has reached a level of maturity and acceptance that you can reasonably expect every developer to have it installed - so you&#039;re adding an entry barrier (compiling the revision control system) for everyone who you want to build your stuff.&lt;p/&gt;All the major distributions have packaged already.</description>
		<content:encoded><![CDATA[<p>&gt; Also, none of those systems has reached a level of maturity and acceptance that you can reasonably expect every developer to have it installed &#8211; so you&#8217;re adding an entry barrier (compiling the revision control system) for everyone who you want to build your stuff.
<p />All the major distributions have packaged already.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikael Hallendal</title>
		<link>http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/comment-page-1/#comment-487</link>
		<dc:creator>Mikael Hallendal</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/#comment-487</guid>
		<description>I don&#039;t buy the argument that the barrier of having to install another version control system is going to make anyone turn in the door. And for those that don&#039;t having Subversion it&#039;s a huge beast to install.&lt;p/&gt;I do however agree that going with Subversion for the bulk of GNOME makes a lot of sense. Simply because of it&#039;s similarity to CVS but with features that people have requested for a long time.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t buy the argument that the barrier of having to install another version control system is going to make anyone turn in the door. And for those that don&#8217;t having Subversion it&#8217;s a huge beast to install.
<p />I do however agree that going with Subversion for the bulk of GNOME makes a lot of sense. Simply because of it&#8217;s similarity to CVS but with features that people have requested for a long time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Howard</title>
		<link>http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/comment-page-1/#comment-488</link>
		<dc:creator>Simon Howard</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2006/12/26/svn-migration/#comment-488</guid>
		<description>Considering that Gnome consists of a bunch of independent(ish) modules maintained by separate users, the question I have to ask is: why all the fighting over which version control system to use?  Can&#039;t different projects use different systems?&lt;p/&gt;There are two types of version control system as I see them: the centralised CVS/Subversion approach and the decentralised Git approach.  Subversion is good because it&#039;s a &quot;better CVS&quot; - it provides an upgrade path for existing users, which means that the projects hosted on cvs.gnome.org don&#039;t need to change their development processes.  As a centralised version control system, it&#039;s pretty decent - I doubt you&#039;ll find many others better.  &lt;p/&gt;Now, Git (and other decentralised systems) do have distinct advantages.  It seems to me that the best way to introduce decentralised development is for individual maintainers to change their projects over.  If enough people do so, Gnome should consider adding a git repository.&lt;p/&gt;I do not dispute the advantages of Git-like version control systems in any way, but the Subversion migration isn&#039;t the place to promote it.  Switch your projects over to Git, get a large body of people using it, make it the common practise _then_ deprecate the older Subversion repository.</description>
		<content:encoded><![CDATA[<p>Considering that Gnome consists of a bunch of independent(ish) modules maintained by separate users, the question I have to ask is: why all the fighting over which version control system to use?  Can&#8217;t different projects use different systems?
<p />There are two types of version control system as I see them: the centralised CVS/Subversion approach and the decentralised Git approach.  Subversion is good because it&#8217;s a &#8220;better CVS&#8221; &#8211; it provides an upgrade path for existing users, which means that the projects hosted on cvs.gnome.org don&#8217;t need to change their development processes.  As a centralised version control system, it&#8217;s pretty decent &#8211; I doubt you&#8217;ll find many others better.
<p />Now, Git (and other decentralised systems) do have distinct advantages.  It seems to me that the best way to introduce decentralised development is for individual maintainers to change their projects over.  If enough people do so, Gnome should consider adding a git repository.
<p />I do not dispute the advantages of Git-like version control systems in any way, but the Subversion migration isn&#8217;t the place to promote it.  Switch your projects over to Git, get a large body of people using it, make it the common practise _then_ deprecate the older Subversion repository.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/bolsh/2006/12/26/svn-migration/feed/ ) in 1.18916 seconds, on Feb 10th, 2012 at 3:15 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 10th, 2012 at 4:15 pm UTC -->
