<?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/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" > <channel><title>Comments on: Episode 41: WordPress 2.5.1 released, Webware 100</title> <atom:link href="http://wp-community.org/2008/05/18/episode-41/feed/" rel="self" type="application/rss+xml" /><link>http://wp-community.org/2008/05/18/episode-41/</link> <description>News, tips and information for WordPress users</description> <lastBuildDate>Sun, 05 Sep 2010 14:01:37 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=</generator> <xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" /> <item><title>By: Gary Fujioka</title><link>http://wp-community.org/2008/05/18/episode-41/#comment-650</link> <dc:creator>Gary Fujioka</dc:creator> <pubDate>Fri, 10 Oct 2008 08:39:46 +0000</pubDate> <guid isPermaLink="false">http://wp-community.org/?p=77#comment-650</guid> <description>In this podcast I believe Matt referenced a WP as CMS rules manager and said he would provide a link for the show notes. Am I just not finding it or is it here, not so much? Thanks.</description> <content:encoded><![CDATA[<p>In this podcast I believe Matt referenced a WP as CMS rules manager and said he would provide a link for the show notes. Am I just not finding it or is it here, not so much? Thanks.</p> ]]></content:encoded> </item> <item><title>By: Michael Clark</title><link>http://wp-community.org/2008/05/18/episode-41/#comment-529</link> <dc:creator>Michael Clark</dc:creator> <pubDate>Mon, 23 Jun 2008 16:34:09 +0000</pubDate> <guid isPermaLink="false">http://wp-community.org/?p=77#comment-529</guid> <description>Thanks for mentioning Login Error Cleanup. I was listening to the episode in the car this weekend and was very surprised to get the plug. Have a great summer.</description> <content:encoded><![CDATA[<p>Thanks for mentioning Login Error Cleanup. I was listening to the episode in the car this weekend and was very surprised to get the plug. Have a great summer.</p> ]]></content:encoded> </item> <item><title>By: Randy</title><link>http://wp-community.org/2008/05/18/episode-41/#comment-528</link> <dc:creator>Randy</dc:creator> <pubDate>Mon, 09 Jun 2008 14:20:22 +0000</pubDate> <guid isPermaLink="false">http://wp-community.org/?p=77#comment-528</guid> <description>An interesting question was raised in this episode about whether the new admin look should have been released in the midst of a version (as 2.5 instead of 3.0). I actually think WordPress has this correct. They maintain a legacy branch, releasing all security patches to the 2.0.x build. They believe that this version has enough features to work as a product with little change. Think of everything before 2.0 as early releases of 2.0, adding features that get tested and improved with each dot release until they are comfortable that it can be maintained.Now think of anything 2.1-3.0 in the same way, as as a single version. They add new features, even a new admin theme, all working towards reaching 3.0. At 3.0, they can freeze a branch again and support it as a legacy branch while they move forward to 4.0. No one would want to introduce a new admin theme in 3.0; because the changes are so pervasive, releasing it earlier in the 2.1-3.0 line will allow more time for testing. Ideally, they would have been able to release a new admin theme in 2.1.WordPress doesn&#039;t release security updates for 2.2 or other point releases. Upgrade from 2.0 to something in the 2.1-3.0 line is somewhat risky; you have to be sure that you will be willing to go with each release until it gets to 3.0. The new functionality after 2.0 is so good that I am willing to take this risk for my own sites, but for some of the sites I build for clients I still use the latest legacy branch (2.0): that way I know I can get them security updates without having to retrain them.</description> <content:encoded><![CDATA[<p>An interesting question was raised in this episode about whether the new admin look should have been released in the midst of a version (as 2.5 instead of 3.0). I actually think WordPress has this correct. They maintain a legacy branch, releasing all security patches to the 2.0.x build. They believe that this version has enough features to work as a product with little change. Think of everything before 2.0 as early releases of 2.0, adding features that get tested and improved with each dot release until they are comfortable that it can be maintained.</p><p>Now think of anything 2.1-3.0 in the same way, as as a single version. They add new features, even a new admin theme, all working towards reaching 3.0. At 3.0, they can freeze a branch again and support it as a legacy branch while they move forward to 4.0. No one would want to introduce a new admin theme in 3.0; because the changes are so pervasive, releasing it earlier in the 2.1-3.0 line will allow more time for testing. Ideally, they would have been able to release a new admin theme in 2.1.</p><p>WordPress doesn&#8217;t release security updates for 2.2 or other point releases. Upgrade from 2.0 to something in the 2.1-3.0 line is somewhat risky; you have to be sure that you will be willing to go with each release until it gets to 3.0. The new functionality after 2.0 is so good that I am willing to take this risk for my own sites, but for some of the sites I build for clients I still use the latest legacy branch (2.0): that way I know I can get them security updates without having to retrain them.</p> ]]></content:encoded> </item> <item><title>By: Jan Karlsbjerg</title><link>http://wp-community.org/2008/05/18/episode-41/#comment-527</link> <dc:creator>Jan Karlsbjerg</dc:creator> <pubDate>Wed, 21 May 2008 19:35:49 +0000</pubDate> <guid isPermaLink="false">http://wp-community.org/?p=77#comment-527</guid> <description>I think you were off the mark about the Sphere integration into WordPress.com. It doesn&#039;t look like it has any of the &quot;big brother&quot; aspects you talked about. It won&#039;t follow the user and keep track of what they read, etc. and it certainly won&#039;t make posts about your behavior (which is what Facebook&#039;s Beacon did).Sphere just adds links to each WordPress.com post based on the content in that post.</description> <content:encoded><![CDATA[<p>I think you were off the mark about the Sphere integration into WordPress.com. It doesn&#8217;t look like it has any of the &#8220;big brother&#8221; aspects you talked about. It won&#8217;t follow the user and keep track of what they read, etc. and it certainly won&#8217;t make posts about your behavior (which is what Facebook&#8217;s Beacon did).</p><p>Sphere just adds links to each WordPress.com post based on the content in that post.</p> ]]></content:encoded> </item> <item><title>By: James Dimick</title><link>http://wp-community.org/2008/05/18/episode-41/#comment-526</link> <dc:creator>James Dimick</dc:creator> <pubDate>Mon, 19 May 2008 23:24:18 +0000</pubDate> <guid isPermaLink="false">http://wp-community.org/?p=77#comment-526</guid> <description>Hey there, Thanks for linking to my Easy Admin Color Schemes plugin. I noticed it wasn&#039;t actually mentioned in the podcast so I&#039;m assuming maybe it was adding in after the fact. But anyway, thanks for mentioning it.I&#039;ve been listening to the podcast for the last few episodes and I&#039;m loving it. You guys are doing a great job. Keep it up.As for the poll question, I don&#039;t really have an opinion on that one. It doesn&#039;t really make that much difference to me. I still would have upgraded regardless.Anyway, great episode. Keep up the great work. ;)</description> <content:encoded><![CDATA[<p>Hey there,<br /> Thanks for linking to my Easy Admin Color Schemes plugin. I noticed it wasn&#8217;t actually mentioned in the podcast so I&#8217;m assuming maybe it was adding in after the fact. But anyway, thanks for mentioning it.</p><p>I&#8217;ve been listening to the podcast for the last few episodes and I&#8217;m loving it. You guys are doing a great job. Keep it up.</p><p>As for the poll question, I don&#8217;t really have an opinion on that one. It doesn&#8217;t really make that much difference to me. I still would have upgraded regardless.</p><p>Anyway, great episode. Keep up the great work. <img src='http://wp-community.org/wp/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: wp-community.org @ 2010-09-09 16:06:09 by W3 Total Cache -->