CINXE.COM

<?xml version="1.0" encoding="UTF-8"?> <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" 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:slash="http://purl.org/rss/1.0/modules/slash/" > <channel> <title>WordPress News</title> <atom:link href="http://wordpress.org/news/feed/" rel="self" type="application/rss+xml" /> <link>http://wordpress.org/news</link> <description>WordPress News</description> <lastBuildDate>Sat, 01 Jan 2011 23:57:06 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.1-RC1-17163</generator> <item> <title>WordPress 3.1 Release Candidate 2</title> <link>http://wordpress.org/news/2011/01/wordpress-3-1-release-candidate-2/</link> <comments>http://wordpress.org/news/2011/01/wordpress-3-1-release-candidate-2/#comments</comments> <pubDate>Sat, 01 Jan 2011 23:57:06 +0000</pubDate> <dc:creator>Andrew Nacin</dc:creator> <category><![CDATA[Releases]]></category> <category><![CDATA[Testing]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1649</guid> <description><![CDATA[The second release candidate for WordPress 3.1 is now available. The requisite haiku: Rounding up stragglers Last few bugs for 3.1 Go test RC2 As I outlined in the announcement post for RC1, release candidates are the last stop before the final release. It means we think we’re done, and we again have no bugs [...]]]></description> <content:encoded><![CDATA[The second release candidate for WordPress 3.1 is now available. The requisite haiku: Rounding up stragglers Last few bugs for 3.1 Go test RC2 As I outlined in <a title="WordPress 3.1 Release Candidate" href="http://wordpress.org/news/2010/12/wordpress-3-1-release-candidate/">the announcement post for RC1</a>, release candidates are the last stop before the final release. It means we think we’re done, and we again have no bugs to squash. But with tens of millions of users, many server configurations and setups, and thousands of plugins and themes, it’s still possible we’ve missed something. Beta 1 came on Thanksgiving, RC1 on Christmas, and RC2 on New Year’s Day. We won’t be waiting for another holiday for the final release, though, so if you haven’t tested WordPress 3.1 yet, now is the time! Select changes since RC1: <ul> <li>The security fixes included in WordPress 3.0.4</li> <li>Fix issues related to handling a static front page</li> <li>Fixes and enhancements for the pagination buttons</li> <li>Fix searching for partial usernames</li> <li>Properly reactivate plugins after editing them</li> <li>Always show the current author in the author dropdown when editing a post</li> <li>Fixes for attachment taxonomies</li> <li>Fix node removal for the admin bar</li> <li>Fix the custom post type show_in_menu argument</li> <li>Various fixes for right-to-left languages</li> <li>and <a href="http://core.trac.wordpress.org/log/trunk/?action=stop_on_copy&mode=stop_on_copy&rev=17204&stop_rev=17149&limit=100&verbose=on">a few dozen more changes</a></li> </ul> If you are testing the release candidate and think you’ve found a bug, there are a few ways to let us know: <ul> <li>Post it to the <a href="http://wordpress.org/support/forum/alphabeta/">Alpha/Beta area in the support forums</a></li> <li>Report it to the <a href="http://lists.automattic.com/mailman/listinfo/wp-testers">wp-testers mailing list</a></li> <li>Join the development IRC channel and tell us live at irc.freenode.net #wordpress-dev</li> <li>File a bug ticket on the <a href="http://core.trac.wordpress.org/">WordPress Trac</a></li> </ul> To test WordPress 3.1, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester plugin</a> (you’ll want “bleeding edge nightlies”). Or you can <a href="http://wordpress.org/wordpress-3.1-RC2.zip">download the release candidate here</a> (zip). If any known issues crop up, you’ll be able to <a href="http://core.trac.wordpress.org/report/5">find them here</a>. If you’d like to know which levers to pull in your testing, <a href="http://wordpress.org/news/2010/11/wordpress-3-1-beta-1/">check out a list of features</a> in our Beta 1 post. <a href="http://wordpress.org/wordpress-3.1-RC2.zip">Download WordPress 3.1 RC 2</a> ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/01/wordpress-3-1-release-candidate-2/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>3.0.4 Important Security Update</title> <link>http://wordpress.org/news/2010/12/3-0-4-update/</link> <comments>http://wordpress.org/news/2010/12/3-0-4-update/#comments</comments> <pubDate>Wed, 29 Dec 2010 21:50:23 +0000</pubDate> <dc:creator>Matt Mullenweg</dc:creator> <category><![CDATA[Releases]]></category> <category><![CDATA[Security]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1641</guid> <description><![CDATA[Version 3.0.4 of WordPress, available immediately through the update page in your dashboard or for download here, is a very important update to apply to your sites as soon as possible because it fixes a core security bug in our HTML sanitation library, called KSES. I would rate this release as “critical.” I realize an [...]]]></description> <content:encoded><![CDATA[Version 3.0.4 of WordPress, available immediately through the update page in your dashboard or <a href="http://wordpress.org/download/">for download here</a>, is a very important update to apply to your sites as soon as possible because it fixes a core security bug in our HTML sanitation library, called KSES. I would rate this release as “critical.” I realize an update during the holidays is no fun, but this one is worth putting down the eggnog for. In the spirit of the holidays, consider helping your friends as well. If you are a security researcher, we’d appreciate you <a href="http://core.trac.wordpress.org/changeset/17172/branches/3.0">taking a look over this changeset</a> as well to review our update. We’ve given it a lot of thought and review but since this is so core we want as many brains on it as possible. Thanks to <a href="http://www.sneaked.net">Mauro Gentile</a> and <a title="duck undah" href="http://joncave.co.uk">Jon Cave (duck_)</a> who discovered and alerted us to these XSS vulnerabilities first. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2010/12/3-0-4-update/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>Coming Up: Meet the Makers</title> <link>http://wordpress.org/news/2010/12/coming-up-meet-the-makers/</link> <comments>http://wordpress.org/news/2010/12/coming-up-meet-the-makers/#comments</comments> <pubDate>Mon, 27 Dec 2010 20:34:09 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Community]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1633</guid> <description><![CDATA[I am often asked how decisions are made for WordPress, who’s involved in decision-making, and how the open source project is structured in general. WordPress is a meritocracy, meaning that anyone can get involved, and a combination of the quality of someone’s contributions and their level of interest/time commitment will determine how much influence they [...]]]></description> <content:encoded><![CDATA[I am often asked how decisions are made for WordPress, who’s involved in decision-making, and how the open source project is structured in general. WordPress is a meritocracy, meaning that anyone can get involved, and a combination of the quality of someone’s contributions and their level of interest/time commitment will determine how much influence they have over decisions. Because these factors vary, we have several levels of contributors to the core WordPress application, ranging from full-time lead developers to casual one-patch contributors. I loved it when that Intel commercial in 2009 gave Ajay Bhatt, co-inventor of the USB, some recognition as a rock star of geekland (though I hated it that it wasn’t actually Ajay Bhatt, but an actor — way to kill the message, Intel).1 In WordPress-land, most people know who Matt Mullenweg is, but most of the other leaders and contributors are much less visible. Moving forward, I’m going to be posting profiles here of some of our more dedicated contributors. Why now? We’re coming up on the second annual WordPress core leadership meetup in January 2011, and we’re thinking we’ll hold a video town hall at some point during our time together. Between now and then the profiles I post will be of the core developers who will be at the meetup. After that, I’ll be branching out and posting about other contributors, including developers, designers, forum moderators, etc. I’ll post here in January when we have dates/times set for the video town hall. In the meantime, you can submit questions for us to answer then in the forum thread <a title="Suggestions thread" href="http://wordpress.org/support/topic/what-should-2011-hold-for-wordpress?">What Should 2011 Hold for WordPress?</a> To get a sense of how all these people fit together and how decisions are made, you can check out the presentation I did at WordCamp Portland in October on <a title="How WordPress Decisions Get Made video" href="http://wordpress.tv/2010/09/18/jane-wells-how-wordpress-decisions-get-made/">How WordPress Decisions Get Made</a>. 1 – And how lame is it that Conan O’Brien’s interview with the real Ajay Bhatt is no longer available on the The Tonight Show’s website, and everyone’s embedded videos are blank? I found a copy of it <a title="Conan interviews the real Ajay Bhatt" href="http://vimeo.com/10662430">here</a>. And here’s the <a title="Intel rock star commercial" href="http://video.intel.com/?fr_story=8d8f50ebfdded3db4eb14514d66e4f9628f653b5&rf=sitemap">original Intel commercial</a> if you were living under a rock and never saw it. <img src='http://wordpress.org/news/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2010/12/coming-up-meet-the-makers/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.1 Release Candidate</title> <link>http://wordpress.org/news/2010/12/wordpress-3-1-release-candidate/</link> <comments>http://wordpress.org/news/2010/12/wordpress-3-1-release-candidate/#comments</comments> <pubDate>Sat, 25 Dec 2010 23:59:05 +0000</pubDate> <dc:creator>Andrew Nacin</dc:creator> <category><![CDATA[Releases]]></category> <category><![CDATA[Testing]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1606</guid> <description><![CDATA[The first release candidate (RC1) for WordPress 3.1 is now available. An RC comes after the beta period and before final release. That means we think we’re done. We currently have no known issues or bugs to squash. But with tens of millions of users, a variety of configurations, and thousands of plugins, it’s possible [...]]]></description> <content:encoded><![CDATA[The first release candidate (RC1) for WordPress 3.1 is now available. An RC comes after the beta period and before final release. That means we think we’re done. We currently have no known issues or bugs to squash. But with tens of millions of users, a variety of configurations, and thousands of plugins, it’s possible we’ve missed something. So if you haven’t tested WordPress 3.1 yet, now is the time! Please though, not on your live site unless you’re extra adventurous. Things to keep in mind: <ul> <li>With <a href="http://core.trac.wordpress.org/milestone/3.1">nearly 700 tickets closed</a>, there are tons of changes. Plugin and theme authors, please test your plugins and themes now, so that if there is a compatibility issue, we can figure it out before the final release.</li> <li>Users are also encouraged to test things out. If you find problems, let your plugin/theme authors know so they can figure out the cause.</li> <li>If any known issues crop up, you’ll be able to <a href="http://core.trac.wordpress.org/report/5">find them here</a>.</li> </ul> If you are testing the release candidate and think you’ve found a bug, there are a few ways to let us know: <ul> <li>Post it to the <a href="http://wordpress.org/support/forum/alphabeta/">Alpha/Beta area in the support forums</a></li> <li>Report it to the <a href="http://lists.automattic.com/mailman/listinfo/wp-testers">wp-testers mailing list</a></li> <li>Join the development IRC channel and tell us live at irc.freenode.net #wordpress-dev</li> <li>File a bug ticket on the <a href="http://core.trac.wordpress.org/">WordPress Trac</a></li> </ul> To test WordPress 3.1, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester plugin</a> (you’ll want “bleeding edge nightlies”). Or you can <a href="http://wordpress.org/wordpress-3.1-RC1.zip">download the release candidate here</a> (zip). We <a href="http://wordpress.org/news/2010/11/wordpress-3-1-beta-1/">released</a> WordPress 3.1 Beta 1 on Thanksgiving, so it’s only fitting that the release candidate comes as a Christmas present. Happy holidays and happy testing! <a href="http://wordpress.org/wordpress-3.1-RC1.zip">Download WordPress 3.1 RC 1</a> If you’d like to know which levers to pull in your testing, <a href="http://wordpress.org/news/2010/11/wordpress-3-1-beta-1/">check out a list of features</a> in our Beta 1 post. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2010/12/wordpress-3-1-release-candidate/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.1 Beta 2</title> <link>http://wordpress.org/news/2010/12/wordpress-3-1-beta-2/</link> <comments>http://wordpress.org/news/2010/12/wordpress-3-1-beta-2/#comments</comments> <pubDate>Wed, 15 Dec 2010 03:18:57 +0000</pubDate> <dc:creator>Andrew Nacin</dc:creator> <category><![CDATA[Releases]]></category> <category><![CDATA[Testing]]></category> <category><![CDATA[3.1]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1572</guid> <description><![CDATA[Haikus from Jane on her 39th birthday: Practice makes perfect is what they say about things, but sometimes it’s not. In this case it is not practice but refinement, and then more testing. You can help WordPress! Now: 3.1, beta 2 is here; needs testing. But! Remember this: Only install on test sites, as YMMV. [...]]]></description> <content:encoded><![CDATA[Haikus from Jane on her 39th birthday: <blockquote>Practice makes perfect is what they say about things, but sometimes it’s not. In this case it is not practice but refinement, and then more testing. You can help WordPress! Now: 3.1, beta 2 is here; needs testing. But! Remember this: Only install on test sites, as YMMV.</blockquote> The second beta of WordPress 3.1 is now available! For things to test, please review our <a href="http://wordpress.org/news/2010/11/wordpress-3-1-beta-1/">Beta 1 release announcement</a>. A <a href="http://core.trac.wordpress.org/report/5">list of known issues</a> can be found on our bug tracker. Already have a test install that you want to switch over to the beta? <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">Try the beta tester plugin</a>. Please test 3.1 on a test site, not on your live site, as interactions with plugins that haven’t been updated may be unpredictable, and we can’t predict (see how that works?) whether something will break or not… that’s why we’re asking people to help us test everything! <img src='http://wordpress.org/news/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> Testers, don’t forget to use the <a href="http://lists.automattic.com/mailman/listinfo/wp-testers">wp-testers mailing list</a> to discuss bugs you encounter. Plugin and theme authors, please test your plugins for compatibility. <a href="http://wordpress.org/wordpress-3.1-beta2.zip">Download the WordPress 3.1 Beta 2</a> now. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2010/12/wordpress-3-1-beta-2/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.0.3</title> <link>http://wordpress.org/news/2010/12/wordpress-3-0-3/</link> <comments>http://wordpress.org/news/2010/12/wordpress-3-0-3/#comments</comments> <pubDate>Wed, 08 Dec 2010 18:35:36 +0000</pubDate> <dc:creator>Peter Westwood</dc:creator> <category><![CDATA[Releases]]></category> <category><![CDATA[Security]]></category> <category><![CDATA[xmlrpc]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1557</guid> <description><![CDATA[WordPress 3.0.3 is available and is a security update for all previous WordPress versions. This release fixes issues in the remote publishing interface, which under certain circumstances allowed Author- and Contributor-level users to improperly edit, publish, or delete posts. These issues only affect sites that have remote publishing enabled. Remote publishing is disabled by default, but [...]]]></description> <content:encoded><![CDATA[<a href="http://wordpress.org/download/">WordPress 3.0.3 is available</a> and is a security update for all previous WordPress versions. <a href="http://codex.wordpress.org/Version_3.0.3">This release</a> fixes issues in the remote publishing interface, which under certain circumstances allowed Author- and Contributor-level users to improperly edit, publish, or delete posts. These issues only affect sites that have remote publishing enabled. Remote publishing is disabled by default, but you may have enabled it to use a remote publishing client such as one of the WordPress mobile apps. You can check these settings on the “Settings → Writing” screen. <a href="http://wordpress.org/download/">Download 3.0.3</a> or update automatically from the “Dashboard → Updates” screen in your site’s admin area. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2010/12/wordpress-3-0-3/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.0.2</title> <link>http://wordpress.org/news/2010/11/wordpress-3-0-2/</link> <comments>http://wordpress.org/news/2010/11/wordpress-3-0-2/#comments</comments> <pubDate>Tue, 30 Nov 2010 23:33:57 +0000</pubDate> <dc:creator>Mark Jaquith</dc:creator> <category><![CDATA[Releases]]></category> <category><![CDATA[Security]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1550</guid> <description><![CDATA[WordPress 3.0.2 is available and is a mandatory security update for all previous WordPress versions. Haiku has become traditional: Fixed on day zero One-click update makes you safe This used to be hard This maintenance release fixes a moderate security issue that could allow a malicious Author-level user to gain further access to the site, [...]]]></description> <content:encoded><![CDATA[<a href="http://wordpress.org/download/">WordPress 3.0.2 is available</a> and is a mandatory security update for all previous WordPress versions. Haiku has become traditional: Fixed on day zero One-click update makes you safe This used to be hard <a href="http://codex.wordpress.org/Version_3.0.2">This maintenance release</a> fixes a moderate security issue that could allow a malicious Author-level user to gain further access to the site, addresses a handful of bugs, and provides some additional security enhancements. Big thanks to <a href="http://blog.sjinks.pro/wordpress/">Vladimir Kolesnikov</a> for detailed and responsible disclosure of the security issue! <a href="http://wordpress.org/download/">Download 3.0.2</a> or update automatically from the Dashboard > Updates menu in your site’s admin area. You should update immediately even if you do not have untrusted users. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2010/11/wordpress-3-0-2/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.1 Beta 1</title> <link>http://wordpress.org/news/2010/11/wordpress-3-1-beta-1/</link> <comments>http://wordpress.org/news/2010/11/wordpress-3-1-beta-1/#comments</comments> <pubDate>Thu, 25 Nov 2010 16:40:13 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Releases]]></category> <category><![CDATA[3.1]]></category> <category><![CDATA[beta]]></category> <category><![CDATA[Testing]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1532</guid> <description><![CDATA[It’s that time in the release cycle again, when all the features are basically done, and we’re just squashing bugs. To the brave of heart and giving of soul: Won’t you help us test the new version of WordPress? As always, this is software still in development and we don’t recommend that you run it [...]]]></description> <content:encoded><![CDATA[It’s that time in the release cycle again, when all the features are basically done, and we’re just squashing bugs. To the brave of heart and giving of soul: Won’t you help us test the new version of WordPress? As always, this is software still in development and we don’t recommend that you run it on your normal live site — set up a test site just to play with the new version. If you break it (find a bug), report it, and if you’re a developer, try to help us fix it. (Especially you U.S. types who are taking a long weekend for Thanksgiving! <img src='http://wordpress.org/news/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> ) If all goes well, we hope to release WordPress 3.1 to the world at large by the end of the year, though that is (as always) subject to change/dependent on how the beta period goes. The more help we get with testing and fixing bugs, the sooner we will be able to release the final version. If you want to be a beta tester, you should check out the Codex article on <a title="Reporting Bugs for WordPress" href="http://codex.wordpress.org/Reporting_Bugs">how to report bugs</a>. Some of the new features to check out include: <ul> <li>Post Formats (<a title="http://core.trac.wordpress.org/ticket/14746" href="http://core.trac.wordpress.org/ticket/14746">#14746</a>)</li> <li>Theme Search (<a title="http://core.trac.wordpress.org/ticket/14936" href="http://core.trac.wordpress.org/ticket/14936">#14936</a>)</li> <li>Internal Linking (<a title="http://core.trac.wordpress.org/ticket/11420" href="http://core.trac.wordpress.org/ticket/11420">#11420</a>)</li> <li>Admin Bar (<a title="http://core.trac.wordpress.org/ticket/14772" href="http://core.trac.wordpress.org/ticket/14772">#14772</a>)</li> <li>Ajaxified Admin (<a title="http://core.trac.wordpress.org/ticket/14579" href="http://core.trac.wordpress.org/ticket/14579">#14579</a>)</li> <li>Updated Tiny MCE (<a title="http://core.trac.wordpress.org/ticket/12574" href="http://core.trac.wordpress.org/ticket/12574">#12574</a>)</li> <li>Multi-taxonomy Queries (<a title="http://core.trac.wordpress.org/ticket/12891" href="http://core.trac.wordpress.org/ticket/12891">#12891</a>)</li> <li>Custom Post Type Index Pages (<a title="http://core.trac.wordpress.org/ticket/13818" href="http://core.trac.wordpress.org/ticket/13818">#13818</a>)</li> <li>Admin CSS Cleanup (<a title="http://core.trac.wordpress.org/ticket/14770" href="http://core.trac.wordpress.org/ticket/14770">#14770</a>)</li> <li>User Admin (<a title="http://core.trac.wordpress.org/ticket/14696" href="http://core.trac.wordpress.org/ticket/14696">#14696</a>)</li> <li>Network Admin (<a title="http://core.trac.wordpress.org/ticket/14435" href="http://core.trac.wordpress.org/ticket/14435">#14435</a>)</li> <li>Password Reset Redux (<a href="http://core.trac.wordpress.org/ticket/5919">#5919</a>)</li> </ul> There are also some known issues: things that aren’t *quite* finished, but that weren’t worth holding up the beta release. They will be fixed before 3.1 is released for general use. Note that as things get fixed, the beta release will update nightly. What you should know: <ul> <li>Fatal error: Call to a member function is_page() on a non-object in /wp-includes/query.php. is_page() may be <a href="http://codex.wordpress.org/Conditional_Tags">any conditional tag</a>. This issue occurs when a theme or plugin is doing something wrong. Some code is checking the value of a conditional tag before we actually set up the Query, which means they don’t work yet. In 3.0, they silently failed and always returned false. In 3.1 Beta 1, this is throwing a fatal error. This will be handled in the final release, so use this opportunity to fix your plugins. (<a title="http://core.trac.wordpress.org/ticket/14579" href="http://core.trac.wordpress.org/ticket/14729">#14729</a>)</li> <li>All known issues slated for fixing before launch are <a href="http://core.trac.wordpress.org/query?status=reopened&status=assigned&status=reviewing&status=new&status=accepted&group=status&milestone=3.1">listed in Trac</a>. Please check this list to see if a bug is already on the list before reporting it.</li> </ul> Remember, if you find something you think is a bug, report it! You can bring it up in the <a title="Alpha/Beta Support Forum" href="http://wordpress.org/support/forum/alphabeta">alpha/beta forum</a>, you can email it to the <a title="WP-testers mailing list info page" href="http://lists.automattic.com/mailman/listinfo/wp-testers">wp-testers list</a>, or if you’ve confirmed that other people are experiencing the same bug, you can report it on the <a title="WordPress Core Trac" href="http://core.trac.wordpress.org/">WordPress Core Trac</a>. (I recommend starting in the forum or on the mailing list.) Theme and plugin authors, if you haven’t been following the 3.1, please start now so that you can update your themes and plugins to be compatible with the newest version of WordPress. Note to developers: WordPress is built by the contributions of hundreds of developers. If you’d like to see this release come out on time, I encourage you to pitch in. Even if you don’t have time to do testing on the beta version, you could help us by contributing a fix for one of the <a title="3.1 bugs that need a patch" href="http://core.trac.wordpress.org/report/16">many bugs</a> we already know about. To those of you in the U.S., have a lovely long holiday weekend, and if you’re looking for something to occupy your post-turkey hours, we hope you’ll take the beta for a spin! <a title="Download WordPress 3.1 Beta 1" href="http://wordpress.org/wordpress-3.1-beta1.zip">Download WordPress 3.1 Beta 1</a> ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2010/11/wordpress-3-1-beta-1/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>Android Update: 1.3.8</title> <link>http://wordpress.org/news/2010/11/android-update-1-3-8/</link> <comments>http://wordpress.org/news/2010/11/android-update-1-3-8/#comments</comments> <pubDate>Thu, 25 Nov 2010 03:00:56 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Cousins]]></category> <category><![CDATA[Releases]]></category> <category><![CDATA[android]]></category> <category><![CDATA[mobile]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1536</guid> <description><![CDATA[This post will be short and to the point: Dan Roundhill announced that a new version of WordPress for Android has been released, fixing numerous bugs and adding the ability to set post status from within the app. Version 1.3.8 hit the Android Market today. For more details, check out the post on the WordPress [...]]]></description> <content:encoded><![CDATA[This post will be short and to the point: Dan Roundhill announced that a new version of WordPress for Android has been released, fixing numerous bugs and adding the ability to set post status from within the app. Version 1.3.8 hit the Android Market today. For more details, check out the<a href="http://android.wordpress.org/2010/11/24/version-1-3-8-post-status-bug-fixes/"> post on the WordPress for Android blog</a>. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2010/11/android-update-1-3-8/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress Wins CMS Award</title> <link>http://wordpress.org/news/2010/11/cms-award/</link> <comments>http://wordpress.org/news/2010/11/cms-award/#comments</comments> <pubDate>Fri, 19 Nov 2010 15:49:25 +0000</pubDate> <dc:creator>Matt Mullenweg</dc:creator> <category><![CDATA[Awards]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1527</guid> <description><![CDATA[I was just informed that WordPress, in head-to-head voting against Joomla and Drupal, has won this year’s Open Source CMS Hall of Fame award. We have to be careful because if this trend continues people might think WordPress is a real CMS, useful for more than just a blog. This would ruin our stealth campaign [...]]]></description> <content:encoded><![CDATA[I was just informed that WordPress, in head-to-head voting against <a href="http://joomla.org/">Joomla</a> and <a href="http://drupal.org/">Drupal</a>, has won this year’s <a href="http://www.packtpub.com/open-source-awards-home">Open Source CMS Hall of Fame award</a>. We have to be careful because if this trend continues people might think WordPress is a real CMS, useful for more than just a blog. This would ruin our <a href="http://wordpress.org/showcase/">stealth campaign</a> and might bring dozens of new users to the WordPress community. If you could keep this on the DL we’d appreciate it. We don’t want WordPress to develop a reputation. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2010/11/cms-award/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>