<?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 2.0.5 &#8211; Ronan &#8211; new release that also includes important security fixes</title>
	<atom:link href="http://www.gabrielserafini.com/blog/2006/10/28/wordpress-205-ronan-new-release-that-also-includes-important-security-fixes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gabrielserafini.com/blog/2006/10/28/wordpress-205-ronan-new-release-that-also-includes-important-security-fixes/</link>
	<description>Web Design, Development and Business</description>
	<lastBuildDate>Tue, 24 Jan 2012 01:30:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Brian Layman</title>
		<link>http://www.gabrielserafini.com/blog/2006/10/28/wordpress-205-ronan-new-release-that-also-includes-important-security-fixes/comment-page-1/#comment-19993</link>
		<dc:creator>Brian Layman</dc:creator>
		<pubDate>Sat, 28 Oct 2006 20:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabrielserafini.com/archives/2006/10/28/wordpress-205-ronan-new-release-that-also-includes-important-security-fixes#comment-19993</guid>
		<description>Thanks for spreading the word about the update. With the number of people still running older releases, and the major security holes that continue to be closed in each 2.0.x release, it is very important to get everyone off of the older versions. The two biggest reasons to upgrade to 2.0.5, as I see it, are:
1. This is, again, major security release. There was a major hole plugged;
2. If you started your blog with version 2.0 or newer, youâ€™re missing a DB index on the post table and that will slow down your site.

Iâ€™ve provided more detail in a top 5 list &lt;a href=&quot;http://www.thecodecave.com/article269&quot; title=&quot;The Code Cave&quot;&gt;on my own site&lt;/a&gt;, but you can always look at the official list of all 60 tickets addressed. I use &lt;a href=&quot;http://trac.wordpress.org/query?status=closed&amp;milestone=2.0.5&amp;order=priority&amp;desc=1&quot;&gt;this link&lt;/a&gt; to look at it in order of priority.

Please continue to convince your friends and everyone on your blog roll to upgrade, it is important. If any of them are worried about upgrading, Iâ€™ve included a 35 second upgrade script on my site. Itâ€™s been reviewed by the members of the WP-Hackers list. So, it is safe. Iâ€™d post the link here, but Iâ€™m releasing an updated version of it later today and donâ€™t want the old links floating around. Just look at the Code Cave article link I posted above and follow it from there. 35 seconds for multiple blogs beats 20 minutes to do it by hand.</description>
		<content:encoded><![CDATA[<p>Thanks for spreading the word about the update. With the number of people still running older releases, and the major security holes that continue to be closed in each 2.0.x release, it is very important to get everyone off of the older versions. The two biggest reasons to upgrade to 2.0.5, as I see it, are:<br />
1. This is, again, major security release. There was a major hole plugged;<br />
2. If you started your blog with version 2.0 or newer, youâ€™re missing a DB index on the post table and that will slow down your site.</p>
<p>Iâ€™ve provided more detail in a top 5 list <a href="http://www.thecodecave.com/article269" title="The Code Cave">on my own site</a>, but you can always look at the official list of all 60 tickets addressed. I use <a href="http://trac.wordpress.org/query?status=closed&amp;milestone=2.0.5&amp;order=priority&amp;desc=1">this link</a> to look at it in order of priority.</p>
<p>Please continue to convince your friends and everyone on your blog roll to upgrade, it is important. If any of them are worried about upgrading, Iâ€™ve included a 35 second upgrade script on my site. Itâ€™s been reviewed by the members of the WP-Hackers list. So, it is safe. Iâ€™d post the link here, but Iâ€™m releasing an updated version of it later today and donâ€™t want the old links floating around. Just look at the Code Cave article link I posted above and follow it from there. 35 seconds for multiple blogs beats 20 minutes to do it by hand.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

