<?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: Wordpress 2.0.5 out</title>
	<atom:link href="http://anirudhsanjeev.org/wordpress-205-out/feed/" rel="self" type="application/rss+xml" />
	<link>http://anirudhsanjeev.org/wordpress-205-out/</link>
	<description>And with Oden on our side, we are victorious!</description>
	<pubDate>Thu, 04 Dec 2008 21:08:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Anirudh</title>
		<link>http://anirudhsanjeev.org/wordpress-205-out/#comment-107</link>
		<dc:creator>Anirudh</dc:creator>
		<pubDate>Tue, 31 Oct 2006 07:37:27 +0000</pubDate>
		<guid isPermaLink="false">http://anirudhsanjeev.org/?p=64#comment-107</guid>
		<description>Hi Brian,
I don't have any problems with wordpress. In fact it's my favorite piece of software in the world. It falls under my OMFG-I-can't-believe-those-idiots-actually-give-it-away-free
software category.

Wordpress' open API and plugin availability make it impossible to add decent new features. That's the problem with firefox and wordpress. What will you add which can't be done with a plugin. So the answer is security.

so, I'm looking forward to wordpress 2.1, And will be the first to upgrade.

Hmmm... need to write more on this.</description>
		<content:encoded><![CDATA[<p>Hi Brian,<br />
I don&#8217;t have any problems with wordpress. In fact it&#8217;s my favorite piece of software in the world. It falls under my OMFG-I-can&#8217;t-believe-those-idiots-actually-give-it-away-free<br />
software category.</p>
<p>Wordpress&#8217; open API and plugin availability make it impossible to add decent new features. That&#8217;s the problem with firefox and wordpress. What will you add which can&#8217;t be done with a plugin. So the answer is security.</p>
<p>so, I&#8217;m looking forward to wordpress 2.1, And will be the first to upgrade.</p>
<p>Hmmm&#8230; need to write more on this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Layman</title>
		<link>http://anirudhsanjeev.org/wordpress-205-out/#comment-106</link>
		<dc:creator>Brian Layman</dc:creator>
		<pubDate>Sat, 28 Oct 2006 21:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://anirudhsanjeev.org/?p=64#comment-106</guid>
		<description>You should like 2.1 then.  It is a pretty major overhaul with some old concepts gone. For instance there are no longer seperate link and post categories, there isn't even a category editor.  Heck, I even got them to change the "Blog URI" prompt over to "Blog URL" on the setup screens.  Now THAT's ground breaking!

BTW, I'm just shlogging around looking for people who have reported errors in updating and encouragine people to pass the word on about updating.  I'm doing a big campaign to get EVERYONE up to this release.  So, while the last three updates have been security related, it doesn't diminish the importance of any of them.  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.  That's not security.

And out of the 60 tickets, only a few of them are security related.

I?ve provided more detail in a top 5 list &lt;a href="http://www.thecodecave.com/article269" title="The Code Cave" rel="nofollow"&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="http://trac.wordpress.org/query?status=closed&#38;milestone=2.0.5&#38;order=priority&#38;desc=1" rel="nofollow"&gt;this link&lt;/a&gt; to look at it in order of priority.

You should try 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>You should like 2.1 then.  It is a pretty major overhaul with some old concepts gone. For instance there are no longer seperate link and post categories, there isn&#8217;t even a category editor.  Heck, I even got them to change the &#8220;Blog URI&#8221; prompt over to &#8220;Blog URL&#8221; on the setup screens.  Now THAT&#8217;s ground breaking!</p>
<p>BTW, I&#8217;m just shlogging around looking for people who have reported errors in updating and encouragine people to pass the word on about updating.  I&#8217;m doing a big campaign to get EVERYONE up to this release.  So, while the last three updates have been security related, it doesn&#8217;t diminish the importance of any of them.  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.</p>
<p>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.  That&#8217;s not security.</p>
<p>And out of the 60 tickets, only a few of them are security related.</p>
<p>I?ve provided more detail in a top 5 list <a href="http://www.thecodecave.com/article269" title="The Code Cave" rel="nofollow">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" rel="nofollow">this link</a> to look at it in order of priority.</p>
<p>You should try 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>

<!-- Dynamic Page Served (once) in 0.330 seconds -->
