<?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"
	>
<channel>
	<title>Comments on: Should I or Shouldn&#8217;t I?</title>
	<atom:link href="http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i</link>
	<description>Everything I used to bore people on newsgroups and mailing lists with, now in one inconvenient place.</description>
	<pubDate>Fri, 22 Aug 2008 00:01:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Tina Marie</title>
		<link>http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i#comment-54494</link>
		<dc:creator>Tina Marie</dc:creator>
		<pubDate>Sun, 30 Sep 2007 00:06:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i#comment-54494</guid>
		<description>I agree.  I'd worry about security holes.  Even if 2.3 doesn't fix any, if they find one, is someone going to patch it in 2.2?</description>
		<content:encoded><![CDATA[<p>I agree.  I&#8217;d worry about security holes.  Even if 2.3 doesn&#8217;t fix any, if they find one, is someone going to patch it in 2.2?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Gerard</title>
		<link>http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i#comment-54454</link>
		<dc:creator>David Gerard</dc:creator>
		<pubDate>Sat, 29 Sep 2007 20:51:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i#comment-54454</guid>
		<description>Yeah. I'm wondering about upgrading from 2.2 as well. The question is how long 2.2 remains supported.

Wordpress has a low pain-in-the-arse factor if you can cope with the command line (as we all can).</description>
		<content:encoded><![CDATA[<p>Yeah. I&#8217;m wondering about upgrading from 2.2 as well. The question is how long 2.2 remains supported.</p>
<p>Wordpress has a low pain-in-the-arse factor if you can cope with the command line (as we all can).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Tomblin</title>
		<link>http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i#comment-54432</link>
		<dc:creator>Paul Tomblin</dc:creator>
		<pubDate>Sat, 29 Sep 2007 19:02:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i#comment-54432</guid>
		<description>Rone, the biggest reason for upgrading is that Wordpress, like so many other PHP applications, is prone to "security hole of the week" syndrome so you have to keep it up to date.</description>
		<content:encoded><![CDATA[<p>Rone, the biggest reason for upgrading is that Wordpress, like so many other PHP applications, is prone to &#8220;security hole of the week&#8221; syndrome so you have to keep it up to date.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ronebofh@livejournal</title>
		<link>http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i#comment-54402</link>
		<dc:creator>ronebofh@livejournal</dc:creator>
		<pubDate>Sat, 29 Sep 2007 16:58:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i#comment-54402</guid>
		<description>You list many reasons why you shouldn't upgrade but none why you should.  I think that's pretty clear-cut.</description>
		<content:encoded><![CDATA[<p>You list many reasons why you shouldn&#8217;t upgrade but none why you should.  I think that&#8217;s pretty clear-cut.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i#comment-54398</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Sat, 29 Sep 2007 16:12:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xcski.com/2007/09/29/should-i-or-shouldnt-i#comment-54398</guid>
		<description>There's a plugin (http://smithsrus.com/downloads/wordpress-upgrade-preflight-check/) that checks your other plugins and tries to determine if they'll be broken by the 2.3 upgrade.  I ran it, and it detected some potential problems even in the handful of plugins I use.  From the feature list of WordPress 2.3 there doesn't seem to be any really compelling reason to change yet, so I figure I'll give it at least a few months and see if things change.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a plugin (http://smithsrus.com/downloads/wordpress-upgrade-preflight-check/) that checks your other plugins and tries to determine if they&#8217;ll be broken by the 2.3 upgrade.  I ran it, and it detected some potential problems even in the handful of plugins I use.  From the feature list of WordPress 2.3 there doesn&#8217;t seem to be any really compelling reason to change yet, so I figure I&#8217;ll give it at least a few months and see if things change.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
