<?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: WordPress SVN</title>
	<atom:link href="http://thefragens.com/blog/2008/02/wordpress-svn/feed/" rel="self" type="application/rss+xml" />
	<link>http://thefragens.com/blog/2008/02/wordpress-svn/</link>
	<description>My time out of the operating room.</description>
	<pubDate>Tue, 06 Jan 2009 03:49:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jonathan</title>
		<link>http://thefragens.com/blog/2008/02/wordpress-svn/comment-page-1/#comment-104</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Mon, 09 Jun 2008 18:00:13 +0000</pubDate>
		<guid isPermaLink="false">http://thefragens.com/blog/?p=473#comment-104</guid>
		<description>&lt;p&gt;It's more "current"-ish than tags. It will give you all the updates for that branch until the next branch comes out. So right now &lt;code&gt;branches/2.5/&lt;/code&gt; will get you v2.5.2 alpha. You can set up cron to &lt;code&gt;svn up&lt;/code&gt; for you every night. Then, the only &lt;code&gt;svn sw&lt;/code&gt; you have to do is at branch changes. This is the one I hit.&lt;/p&gt;

&lt;p&gt;If you're feeling froggy, you can always hit &lt;code&gt;trunk/&lt;/code&gt;. That gives you the developement version. Which works. Sometimes. But if set up cron to &lt;code&gt;svn up&lt;/code&gt; for you every night, there's no input from you, except for the occasional database update.&lt;/p&gt;

&lt;p&gt;In the end, though, I agree with you, Andy. They need a stable trunk we can point to and forget about it. I cannot think of any reason not to, and I can also think of no reason to have the current system! :-&#92;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It&#8217;s more &#8220;current&#8221;-ish than tags. It will give you all the updates for that branch until the next branch comes out. So right now <code>branches/2.5/</code> will get you v2.5.2 alpha. You can set up cron to <code>svn up</code> for you every night. Then, the only <code>svn sw</code> you have to do is at branch changes. This is the one I hit.</p>

<p>If you&#8217;re feeling froggy, you can always hit <code>trunk/</code>. That gives you the developement version. Which works. Sometimes. But if set up cron to <code>svn up</code> for you every night, there&#8217;s no input from you, except for the occasional database update.</p>

<p>In the end, though, I agree with you, Andy. They need a stable trunk we can point to and forget about it. I cannot think of any reason not to, and I can also think of no reason to have the current system! :-&#92;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://thefragens.com/blog/2008/02/wordpress-svn/comment-page-1/#comment-14</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 06 Feb 2008 16:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://thefragens.com/blog/?p=473#comment-14</guid>
		<description>&lt;p&gt;But Barry, is the branch current? Does it only have the 2.x releases and not the 2.x.x releases? Or does it?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>But Barry, is the branch current? Does it only have the 2.x releases and not the 2.x.x releases? Or does it?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Barry</title>
		<link>http://thefragens.com/blog/2008/02/wordpress-svn/comment-page-1/#comment-13</link>
		<dc:creator>Barry</dc:creator>
		<pubDate>Wed, 06 Feb 2008 15:07:26 +0000</pubDate>
		<guid isPermaLink="false">http://thefragens.com/blog/?p=473#comment-13</guid>
		<description>&lt;p&gt;I would recommend using the branch url rather than the tag:&lt;/p&gt;

&lt;p&gt;http://svn.automattic.com/wordpress/branches/2.3/&lt;/p&gt;

&lt;p&gt;That way you only have to svn switch every time there is a new major release (every 3-4 months).  For all minor releases you just need to svn up (or just automate it).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I would recommend using the branch url rather than the tag:</p>

<p><a href="http://svn.automattic.com/wordpress/branches/2.3/" rel="nofollow">http://svn.automattic.com/wordpress/branches/2.3/</a></p>

<p>That way you only have to svn switch every time there is a new major release (every 3-4 months).  For all minor releases you just need to svn up (or just automate it).</p>]]></content:encoded>
	</item>
</channel>
</rss>
