<?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: Upgrading WordPress sucks.</title>
	<atom:link href="http://michaelshadle.com/2007/10/30/upgrading-wordpress-sucks/feed" rel="self" type="application/rss+xml" />
	<link>http://michaelshadle.com/2007/10/30/upgrading-wordpress-sucks</link>
	<description>&#34;Lazy people are efficient.&#34; - My boss.</description>
	<lastBuildDate>Wed, 21 Dec 2011 11:35:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: mike</title>
		<link>http://michaelshadle.com/2007/10/30/upgrading-wordpress-sucks/comment-page-1#comment-2268</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Wed, 31 Oct 2007 21:12:41 +0000</pubDate>
		<guid isPermaLink="false">http://michaelshadle.com/2007/10/30/upgrading-wordpress-sucks/#comment-2268</guid>
		<description>Thanks. I saw something related to this, but it still probably winds up being the same amount of effort.

Just being notified of which files are deprecated would be a start. Perhaps in the upgrade.php script for each upgrade - regardless of database updates. It could check for files that are in the base install against the base install directories (wp-content/*, wp-config.php, .htaccess, wp-includes/languages/* would be ignored for example)

I still think the directory structure could be setup a little bit better. Having the language information mixed in to wp-includes, having wp-config.php in the same directory as core code, etc... that mixes things up. It would be nice to have a totally &quot;3rd party&quot; area and a core code area that is completely separate :)</description>
		<content:encoded><![CDATA[<p>Thanks. I saw something related to this, but it still probably winds up being the same amount of effort.</p>
<p>Just being notified of which files are deprecated would be a start. Perhaps in the upgrade.php script for each upgrade - regardless of database updates. It could check for files that are in the base install against the base install directories (wp-content/*, wp-config.php, .htaccess, wp-includes/languages/* would be ignored for example)</p>
<p>I still think the directory structure could be setup a little bit better. Having the language information mixed in to wp-includes, having wp-config.php in the same directory as core code, etc... that mixes things up. It would be nice to have a totally "3rd party" area and a core code area that is completely separate <img src='http://michaelshadle.com/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlo</title>
		<link>http://michaelshadle.com/2007/10/30/upgrading-wordpress-sucks/comment-page-1#comment-2267</link>
		<dc:creator>Carlo</dc:creator>
		<pubDate>Wed, 31 Oct 2007 21:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://michaelshadle.com/2007/10/30/upgrading-wordpress-sucks/#comment-2267</guid>
		<description>I use something like this
http://perassi.org/2007/02/21/updating-wordpress-with-subversion-and-sitecopy/
(I also create and use a patch file when I want to be fast)</description>
		<content:encoded><![CDATA[<p>I use something like this<br />
<a href="http://perassi.org/2007/02/21/updating-wordpress-with-subversion-and-sitecopy/" rel="nofollow">http://perassi.org/2007/02/21/updating-wordpress-with-subversion-and-sitecopy/</a><br />
(I also create and use a patch file when I want to be fast)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

