<?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: Subversion &quot;Shelving&quot;</title>
	<atom:link href="http://www.ofonesandzeros.com/2009/01/07/subversion-shelving/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ofonesandzeros.com/2009/01/07/subversion-shelving/</link>
	<description>a discussion of software and technology hosted by bryan napier</description>
	<lastBuildDate>Wed, 30 Jun 2010 11:06:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: bryan</title>
		<link>http://www.ofonesandzeros.com/2009/01/07/subversion-shelving/comment-page-1/#comment-67</link>
		<dc:creator>bryan</dc:creator>
		<pubDate>Tue, 21 Jul 2009 14:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ofonesandzeros.com/2009/01/07/subversion-shelving/#comment-67</guid>
		<description>I suppose the &quot;clumsiness&quot; is relative to your general subversion experience.  Branching/merging in Subversion is widely regarded as a somewhat unkempt process.  TortoiseSVN definitely does its part to simplify the process, but is it as straight-forward as TFS?  Nope.

As to whether shelving is branching or not, I would argue that it is very similar, if not identical, to the concept of private branches.  The difference is more semantic than functional.  Similar to how tags are handled in Subversion.  At the end of the day you are in effect creating a branch, but because it is within the tag parent, the semantic is that it should be read-only.  With shelves in this context, yes, it is a branch, but because the branch is within /shelf the semantic dictates that it is intended to be a &quot;parking lot&quot; for code for an indeterminate period of time, not a traditional branch that would have additional commits.

Great comments Galaxis, thanks.</description>
		<content:encoded><![CDATA[<p>I suppose the &#8220;clumsiness&#8221; is relative to your general subversion experience.  Branching/merging in Subversion is widely regarded as a somewhat unkempt process.  TortoiseSVN definitely does its part to simplify the process, but is it as straight-forward as TFS?  Nope.</p>
<p>As to whether shelving is branching or not, I would argue that it is very similar, if not identical, to the concept of private branches.  The difference is more semantic than functional.  Similar to how tags are handled in Subversion.  At the end of the day you are in effect creating a branch, but because it is within the tag parent, the semantic is that it should be read-only.  With shelves in this context, yes, it is a branch, but because the branch is within /shelf the semantic dictates that it is intended to be a &#8220;parking lot&#8221; for code for an indeterminate period of time, not a traditional branch that would have additional commits.</p>
<p>Great comments Galaxis, thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Galaxis</title>
		<link>http://www.ofonesandzeros.com/2009/01/07/subversion-shelving/comment-page-1/#comment-66</link>
		<dc:creator>Galaxis</dc:creator>
		<pubDate>Tue, 21 Jul 2009 13:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ofonesandzeros.com/2009/01/07/subversion-shelving/#comment-66</guid>
		<description>Actually Shelving is not Branchcing; only part of the equation.  Don&#039;t forget about the merge back!  THis process is clumsy and error-prone (as you&#039;ll see from the article you link to) especially after using TFS.  Subversion has a ways to go, but TFS is relatively new and MS never rests on its laurels, so the for a while, the gap (and TFS&#039;s adoption) will probably widen.</description>
		<content:encoded><![CDATA[<p>Actually Shelving is not Branchcing; only part of the equation.  Don&#8217;t forget about the merge back!  THis process is clumsy and error-prone (as you&#8217;ll see from the article you link to) especially after using TFS.  Subversion has a ways to go, but TFS is relatively new and MS never rests on its laurels, so the for a while, the gap (and TFS&#8217;s adoption) will probably widen.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
