Beta 1 of WordPress 2.6 has been released! If you want to test it safely, you should be able to do so as soon as the WordPress 2.6 demo site is updated.
Update: Robert posted a comment pointing out an alternate demo site.
WordPress 2.6 was previously slated for an August 2008 release, but the WordPress Trac Roadmap has recently been updated with the following information on the WordPress 2.6 release date:
Originally published on April 24, 2008. Updated on May 5, 20, 22, June 16, and June 20.
WordPress 2.6 may not be due until August 2008, but already I’ve managed to compile a list of features and enhancements that we’ll likely be seeing in this next major WordPress release. (I’ll continue to update this post as we approach the release date.)
As reported in my updated WordPress 2.6 features list, support for Google Gears in the administrative back-end has been added to the WordPress Trunk (i.e. the current development version).
According to the development ticket for the Google Gears patch:
Although WordPress 2.6 is still in the early alpha stages (as of this writing), you can still check out the unofficial WordPress 2.6 Demo Site and give some of the new features a whirl.
Here’s a list of 5 features that have gone missing in WordPress 2.5:
WPCandy recently posted an interesting article called 30+ Things That Should Be Changed in WordPress 2.6. It’s essentially a big ideas list spanning the administration, the comment system, and more.
WordPress 2.5.1 has just been released. According to the development blog:
It includes a number of bug fixes, performance enhancements, and one very important security fix. We recommend everyone update immediately, particularly if your blog has open registration. The vulnerability is not public but it will be shortly.
Download it now
The question I have is: does this mean 2.3.3 is no longer safe?
WordPress 2.5 has been officially released! (You can download it here.)
A major upgrade, WordPress 2.5 packs a boatload of new features. Here are many that were listed in the official announcement at the WordPress Development Blog: