WordPress 3.2 Release Candidate 2 is ready for you

4 Comments

WordPress 3.2 Release Candidate 2 is now ready for testing. Andrew Nacin posted the update to the WordPress news blog, along with an update on what has happened since Release Candidate 1. In the last ten days tweaks have been made to Twenty Eleven (the new default theme) and various RTL fixes.

Nacin recommends that theme and plugin authors should be testing their work by now so that compatibility issues can be caught before the public release.

The features to test and work with are the same as the ones listed during the first beta, so keep those in mind while you work with the new version..

This marks another step toward the full release of 3.2, which we’ve been closely documenting as it progresses. You can help prepare the software for a full public release by either update your test install via SVN or by downloading it directly. See Nacin’s blog post for more information regarding testing WordPress and reporting any bugs you might find.

We’ll be seeing a full public release of WordPress 3.2 soon. Are you ready?

4 thoughts on “WordPress 3.2 Release Candidate 2 is ready for you

  1. Sweet!

    Anyone have experience or an opinion on switching from a Release Candidate to the Tagged Version, on release? Or from Trunk to Tagged?

    Going back and forth from RC/Trunk to 3.1.3 with subversion works flawlessly on my local install. It’s as easy as “svn sw http://core.svn.wordpress.org/trunk/ .” and to go back “svn sw http://core.svn.wordpress.org/tags/3.1.3/ .”

    I’m curious if anyone toe’s the line like this with their production site. I’d sure love to!

    • Eyecool, you don’t install a release candidate on a production site, I did it quite some time ago with 3.0-beta and it turned out to be a mess in the end, so you’d better just wait a week until the release is out and an auto-upgrade is available.

  2. Didn’t change much from the first release candidate. Question. Does anybody know whether Duster *is* the Twenty Eleven theme or whether Twenty Eleven was a fork of Duster and went it’s own way? They keep referring to it as Twenty Evelen, but Duster gets it’s updates in the .org repository too, how’s that?

Comments are closed.