It seems like just yesterday that we released WordPress 3.1, but it’s actually been almost three months. We’ve spent that time putting together a new release focused on performance improvements, and are ready for our first beta testers!<\/p>\n
As always, this is software still in development and we don’t recommend that you run it on a production site<\/strong> — set up a test site just to play with the new version. If you break it (find a bug), please report it, and if you’re a developer, try to help us fix it.<\/p>\n If all goes well, we hope to release WordPress 3.2 by the end of June, though that is (again, as always) subject to change depending 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<\/a>.<\/p>\n Here’s some of what’s new:<\/strong><\/p>\n Remember, if you find something you think is a bug, report it! You can bring it up in the alpha\/beta forum<\/a>, you can email it to the wp-testers list<\/a>, or if you’ve confirmed that other people are experiencing the same bug, you can report it on the WordPress Core Trac<\/a>. (I recommend starting in the forum or on the mailing list.)<\/p>\n Theme and plugin authors, if you haven’t been following the 3.2 development cycle, please start now<\/strong> so that you can update your themes and plugins to be compatible with the newest version of WordPress.<\/p>\n 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<\/a> we already know about.<\/p>\n\n
\n
\n