<?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: The Problem with WordPress 2.5</title>
	<atom:link href="http://www.majorspoilers.com/archives/3267.htm/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.majorspoilers.com/archives/3267.htm/</link>
	<description>We Know You Love Comics.  We Do Too.</description>
	<pubDate>Sat, 11 Oct 2008 08:20:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Per Soderlind</title>
		<link>http://www.majorspoilers.com/archives/3267.htm/#comment-55984</link>
		<dc:creator>Per Soderlind</dc:creator>
		<pubDate>Sat, 19 Apr 2008 21:07:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.majorspoilers.com/?p=3267#comment-55984</guid>
		<description>Just a FYI, ImageManager v2.5.2 is available at my site: www.soderlind.no/ImageManager</description>
		<content:encoded><![CDATA[<p>Just a FYI, ImageManager v2.5.2 is available at my site: <a href="http://www.soderlind.no/ImageManager" rel="nofollow">http://www.soderlind.no/ImageManager</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Schleicher</title>
		<link>http://www.majorspoilers.com/archives/3267.htm/#comment-55132</link>
		<dc:creator>Stephen Schleicher</dc:creator>
		<pubDate>Tue, 01 Apr 2008 16:34:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.majorspoilers.com/?p=3267#comment-55132</guid>
		<description>in the last two years, I've waited until the second or third (dot) release before making the upgrade.  This time the enticement of actually having a working gallery and some of the other workflow enhancements were too much for me and I caved.  

NEVER AGAIN!  It will probably be WP3.5.8 before I upgrade again.</description>
		<content:encoded><![CDATA[<p>in the last two years, I&#8217;ve waited until the second or third (dot) release before making the upgrade.  This time the enticement of actually having a working gallery and some of the other workflow enhancements were too much for me and I caved.  </p>
<p>NEVER AGAIN!  It will probably be WP3.5.8 before I upgrade again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: doubledumbassonyou</title>
		<link>http://www.majorspoilers.com/archives/3267.htm/#comment-55129</link>
		<dc:creator>doubledumbassonyou</dc:creator>
		<pubDate>Tue, 01 Apr 2008 15:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.majorspoilers.com/?p=3267#comment-55129</guid>
		<description>I'm not what you call an early adopter.  I upgraded to WP2.3 probably only 6 months ago, and was very happily cruising along with 2.1.  As long as my backend isn't compromised or there is a MAJOR security risk I like utilizing scripts and plugins that I write with whatever version of WP that I'm running at the time.  

Upgrades never go smoothly regardless of your skill level or competency, it is something that I realized after my most recent WP snafu ... when I upgraded to WP2.3.  At the end of the day, WP remains the most viable blogging software available.  There are times however I yearn for the olden days when I hardcoded ever single line and in-line image.  Those were the days.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not what you call an early adopter.  I upgraded to WP2.3 probably only 6 months ago, and was very happily cruising along with 2.1.  As long as my backend isn&#8217;t compromised or there is a MAJOR security risk I like utilizing scripts and plugins that I write with whatever version of WP that I&#8217;m running at the time.  </p>
<p>Upgrades never go smoothly regardless of your skill level or competency, it is something that I realized after my most recent WP snafu &#8230; when I upgraded to WP2.3.  At the end of the day, WP remains the most viable blogging software available.  There are times however I yearn for the olden days when I hardcoded ever single line and in-line image.  Those were the days.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
