WordPress 3.1 Beta 1
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! 
)
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 how to report bugs. Some of the new features to check out include:
- Post Formats (#14746)
- Theme Search (#14936)
- Internal Linking (#11420)
- Admin Bar (#14772)
- Ajaxified Admin (#14579)
- Updated Tiny MCE (#12574)
- Multi-taxonomy Queries (#12891)
- Custom Post Type Index Pages (#13818)
- Admin CSS Cleanup (#14770)
- User Admin (#14696)
- Network Admin (#14435)
- Password Reset Redux (#5919)
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:
- Fatal error: Call to a member function is_page() on a non-object in /wp-includes/query.php. is_page() may be any conditional tag. 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. (#14729)
- All known issues slated for fixing before launch are listed in Trac. Please check this list to see if a bug is already on the list before reporting it.
Remember, if you find something you think is a bug, report it! You can bring it up in the alpha/beta forum, you can email it to the wp-testers list, or if you’ve confirmed that other people are experiencing the same bug, you can report it on the WordPress Core Trac. (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 many bugs 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!