<?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.3 Beta 2</title>
	<atom:link href="http://www.bloggingpro.com/archives/2007/09/04/wordpress-23-beta-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloggingpro.com/archives/2007/09/04/wordpress-23-beta-2/</link>
	<description>News, plugins and themes for blogging applications</description>
	<lastBuildDate>Thu, 09 Feb 2012 19:29:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Kirk M</title>
		<link>http://www.bloggingpro.com/archives/2007/09/04/wordpress-23-beta-2/#comment-207800</link>
		<dc:creator>Kirk M</dc:creator>
		<pubDate>Wed, 05 Sep 2007 11:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2007/09/04/wordpress-23-beta-2/#comment-207800</guid>
		<description>And that&#039;s a good argument too. One that could also include a bit about letting plugin authors do that kind of work and &lt;i&gt;if&lt;/i&gt; it works well then it can be incorporated into the core. There&#039;s a certain &quot;community&quot; type logic in that I suppose. Kind of like letting folks like you and me and others write up easy to read &quot;how to&#039;s&quot; because WordPress...uh...doesn&#039;t. There&#039;s a &quot;darkside&quot; to everything isn&#039;t there?

But as you said...another argument for another day. It&#039;s still my favorite blogging platform.

Blog well....</description>
		<content:encoded><![CDATA[<p>And that&#8217;s a good argument too. One that could also include a bit about letting plugin authors do that kind of work and <i>if</i> it works well then it can be incorporated into the core. There&#8217;s a certain &#8220;community&#8221; type logic in that I suppose. Kind of like letting folks like you and me and others write up easy to read &#8220;how to&#8217;s&#8221; because WordPress&#8230;uh&#8230;doesn&#8217;t. There&#8217;s a &#8220;darkside&#8221; to everything isn&#8217;t there?</p>
<p>But as you said&#8230;another argument for another day. It&#8217;s still my favorite blogging platform.</p>
<p>Blog well&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Peralty</title>
		<link>http://www.bloggingpro.com/archives/2007/09/04/wordpress-23-beta-2/#comment-207769</link>
		<dc:creator>David Peralty</dc:creator>
		<pubDate>Wed, 05 Sep 2007 02:30:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2007/09/04/wordpress-23-beta-2/#comment-207769</guid>
		<description>Thanks Kirk... most of my blogs are upgraded via SVN... I upgrade basically all of Bloggy Network&#039;s blogs in a few minutes... I thing Automatic upgrades should be in WP Core... but that&#039;s an argument for another day.</description>
		<content:encoded><![CDATA[<p>Thanks Kirk&#8230; most of my blogs are upgraded via SVN&#8230; I upgrade basically all of Bloggy Network&#8217;s blogs in a few minutes&#8230; I thing Automatic upgrades should be in WP Core&#8230; but that&#8217;s an argument for another day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirk M</title>
		<link>http://www.bloggingpro.com/archives/2007/09/04/wordpress-23-beta-2/#comment-207767</link>
		<dc:creator>Kirk M</dc:creator>
		<pubDate>Wed, 05 Sep 2007 00:44:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2007/09/04/wordpress-23-beta-2/#comment-207767</guid>
		<description>Hi David,

Tried out beta 1, ran it through it&#039;s paces, like what I saw and promptly got rid of it. I don&#039;t mind using my main personal blog to do this with. I have plenty of experience in reverting back. My readers are forgiving that way which is a good thing since beta testing is an very old addiction of mine. I&#039;m glad they kept to what they said about weekly beta releases.

I may just wait until beta 3 comes out before trying again. I usually stick with the beta that comes out one or two weeks before the final release. That&#039;s when the bug hunting gets interesting.

BTW, have you tried out the Wordpress Automatic Upgrades plugin. In it&#039;s current configuration it works very well and will be a boon for those who fear or downright &lt;i&gt;hate&lt;/i&gt; upgrading their Wordpress install (like the ones still using the 2.0 or even the 1.0 series).</description>
		<content:encoded><![CDATA[<p>Hi David,</p>
<p>Tried out beta 1, ran it through it&#8217;s paces, like what I saw and promptly got rid of it. I don&#8217;t mind using my main personal blog to do this with. I have plenty of experience in reverting back. My readers are forgiving that way which is a good thing since beta testing is an very old addiction of mine. I&#8217;m glad they kept to what they said about weekly beta releases.</p>
<p>I may just wait until beta 3 comes out before trying again. I usually stick with the beta that comes out one or two weeks before the final release. That&#8217;s when the bug hunting gets interesting.</p>
<p>BTW, have you tried out the WordPress Automatic Upgrades plugin. In it&#8217;s current configuration it works very well and will be a boon for those who fear or downright <i>hate</i> upgrading their WordPress install (like the ones still using the 2.0 or even the 1.0 series).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

