<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule">

<channel>
	<title>yergler.net &#187; upgrade</title>
	<atom:link href="http://yergler.net/blog/tag/upgrade/feed/" rel="self" type="application/rss+xml" />
	<link>http://yergler.net</link>
	<description>Because eventually I&#039;ll be right. Theoretically.</description>
	<lastBuildDate>Tue, 31 Jan 2012 05:43:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Upgrading WordPress</title>
		<link>http://yergler.net/blog/2008/08/21/upgrading-wordpress/</link>
		<comments>http://yergler.net/blog/2008/08/21/upgrading-wordpress/#comments</comments>
		<pubDate>Fri, 22 Aug 2008 00:33:19 +0000</pubDate>
		<dc:creator>Nathan Yergler</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[subversion]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[version control]]></category>
		<category><![CDATA[wordpres]]></category>

		<guid isPermaLink="false">http://yergler.net/blog/?p=630</guid>
		<description><![CDATA[WordPress 2.6.1 is out. Reading feeds on my flight from IND to PHX this afternoon I ran across the WordPress Automatic Upgrade Plugin (shouldn&#8217;t that be the Automattic?). Nice, but I&#8217;d like to plug my approach to managing WordPress upgrades, which I think is even easier, assuming you&#8217;re OK with minimal command-line interaction. First, install [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://wordpress.org/development/2008/08/wordpress-261/">WordPress 2.6.1</a> is out.  Reading feeds on my flight from IND to PHX this afternoon I ran across the <a href="http://techie-buzz.com/wordpress-plugins/wordpress-automatic-upgrade-12-release.html">WordPress Automatic Upgrade Plugin</a> (shouldn&#8217;t that be the <em>Automattic</em>?).  Nice, but I&#8217;d like to plug my approach to managing WordPress upgrades, which I think is even easier, assuming you&#8217;re OK with minimal command-line interaction.</p>
<p>First, install WordPress from a Subversion checkout; do:<br />
<code><br />
$ svn co http://svn.automattic.com/wordpress/tags/2.6/<br />
</code><br />
instead of downloading the .zip or .tar.gz file.  Configure as directed.</p>
<p>Then, when a new version is available, log into your webhost and run:<br />
<code><br />
$ svn switch http://svn.automattic.com/wordpress/tags/2.6.1/<br />
</code><br />
from your install directory.</p>
<p>Done.</p>
<p>Note that you can also do something similar (but an order of magnitude more complex, at least for my brain) using <a href="http://en.wikipedia.org/wiki/Git_(software)">git</a> and <a href="http://www.kernel.org/pub/software/scm/git/docs/git-svn.html">git-svn</a> if you want to version your local settings as well.  Perhaps one day <a href="http://asheesh.org">Asheesh</a> or I will get that written up.</p>
]]></content:encoded>
			<wfw:commentRss>http://yergler.net/blog/2008/08/21/upgrading-wordpress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

