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 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:
- The security fixes included in WordPress 3.0.4
- Fix issues related to handling a static front page
- Fixes and enhancements for the pagination buttons
- Fix searching for partial usernames
- Properly reactivate plugins after editing them
- Always show the current author in the author dropdown when editing a post
- Fixes for attachment taxonomies
- Fix node removal for the admin bar
- Fix the custom post type show_in_menu argument
- Various fixes for right-to-left languages
- and a few dozen more changes
If you are testing the release candidate and think you’ve found a bug, there are a few ways to let us know:
- Post it to the Alpha/Beta area in the support forums
- Report it to the wp-testers mailing list
- Join the development IRC channel and tell us live at irc.freenode.net #wordpress-dev
- File a bug ticket on the WordPress Trac
To test WordPress 3.1, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip).
If any known issues crop up, you’ll be able to find them here. If you’d like to know which levers to pull in your testing, check out a list of features in our Beta 1 post.
Read more:
WordPress 3.1 Release Candidate 2