<?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.2 released - Security update</title>
	<atom:link href="http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/</link>
	<description>Random commentary...</description>
	<pubDate>Fri, 25 Jul 2008 17:39:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Peter Westwood &#187; WordPress 2.0.4 released (Security update)</title>
		<link>http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comment-13428</link>
		<dc:creator>Peter Westwood &#187; WordPress 2.0.4 released (Security update)</dc:creator>
		<pubDate>Sat, 29 Jul 2006 09:45:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comment-13428</guid>
		<description>[...] To simplfy the upgrade process I decided again to try generating a diff file between 2.0.3 and 2.0.4 and using that to patch my sites rather than uploading a full set of new files. The process for generating the diff file is actually simpler than the one I used last time! [...]</description>
		<content:encoded><![CDATA[<p>[...] To simplfy the upgrade process I decided again to try generating a diff file between 2.0.3 and 2.0.4 and using that to patch my sites rather than uploading a full set of new files. The process for generating the diff file is actually simpler than the one I used last time! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Code Cave</title>
		<link>http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comment-5085</link>
		<dc:creator>The Code Cave</dc:creator>
		<pubDate>Mon, 13 Mar 2006 22:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comment-5085</guid>
		<description>&lt;strong&gt;WordPress News for the week of 3/6/2006...&lt;/strong&gt;

With the &#8220;hacking&#8221; of the original Wordpress 2.0 theme competition and a new security release of WordPress 2.0, it has been an exciting week. First a (not so) quick word on the competition then a break down of the changes between .01 and .0...</description>
		<content:encoded><![CDATA[<p><strong>WordPress News for the week of 3/6/2006&#8230;</strong></p>
<p>With the &#8220;hacking&#8221; of the original Wordpress 2.0 theme competition and a new security release of WordPress 2.0, it has been an exciting week. First a (not so) quick word on the competition then a break down of the changes between .01 and .0&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: westi</title>
		<link>http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comment-5067</link>
		<dc:creator>westi</dc:creator>
		<pubDate>Fri, 10 Mar 2006 22:16:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comment-5067</guid>
		<description>Dickie: It wasn't written specifically for you but with you in mind.  I had two sites to update quickly and thought that this might be the quickest way.

Deoren: Yes rev 3637 should get Tagged as 2.0.2 Ryan will probably do that soon he usually does it soon after release.  As for running straight off an svn checkout there should be no problems - I have a number of test installs which get updated automatically running the various trunk and branch builds and they work reliably :-)</description>
		<content:encoded><![CDATA[<p>Dickie: It wasn&#8217;t written specifically for you but with you in mind.  I had two sites to update quickly and thought that this might be the quickest way.</p>
<p>Deoren: Yes rev 3637 should get Tagged as 2.0.2 Ryan will probably do that soon he usually does it soon after release.  As for running straight off an svn checkout there should be no problems - I have a number of test installs which get updated automatically running the various trunk and branch builds and they work reliably <img src='http://blog.ftwr.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: deoren</title>
		<link>http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comment-5065</link>
		<dc:creator>deoren</dc:creator>
		<pubDate>Fri, 10 Mar 2006 18:02:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comment-5065</guid>
		<description>Neat.  From what I can tell rev 3637 of http://svn.automattic.com/wordpress/branches/2.0 is what will be tagged as 2.0.2.

Also, I've read in places that some WordPress users use a working copy of the latest WordPress's tag or branch.  I haven't found anyone that really had a problem with that.  Thoughts?</description>
		<content:encoded><![CDATA[<p>Neat.  From what I can tell rev 3637 of <a href="http://svn.automattic.com/wordpress/branches/2.0" rel="nofollow">http://svn.automattic.com/wordpress/branches/2.0</a> is what will be tagged as 2.0.2.</p>
<p>Also, I&#8217;ve read in places that some WordPress users use a working copy of the latest WordPress&#8217;s tag or branch.  I haven&#8217;t found anyone that really had a problem with that.  Thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dickie</title>
		<link>http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comment-5064</link>
		<dc:creator>Dickie</dc:creator>
		<pubDate>Fri, 10 Mar 2006 17:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ftwr.co.uk/archives/2006/03/10/wordpress-202-released-security-update/#comment-5064</guid>
		<description>Hi Peter, was this written specifically for me, as I now you know I will ask you...!!!!
Anyway thanks for that
Dickie</description>
		<content:encoded><![CDATA[<p>Hi Peter, was this written specifically for me, as I now you know I will ask you&#8230;!!!!<br />
Anyway thanks for that<br />
Dickie</p>
]]></content:encoded>
	</item>
</channel>
</rss>
