The second release candidate for WordPress 3.1 is now available. The requisite haiku:<\/p>\n
Rounding up stragglers
\nLast few bugs for 3.1
\nGo test RC2<\/p>\n
As I outlined in 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.<\/p>\n 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!<\/strong><\/p>\n Select changes since RC1:<\/p>\n If you are testing the release candidate and think you’ve found a bug, there are a few ways to let us know:<\/p>\n To test WordPress 3.1, try the WordPress Beta Tester plugin<\/a> (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here<\/a> (zip).<\/p>\n If any known issues crop up, you’ll be able to\u00a0find them here<\/a>.\u00a0If you’d like to know which levers to pull in your testing,\u00a0check out a list of features<\/a> in our Beta 1 post.<\/p>\n\n
\n