Development

WordPress 4.2 Release Candidate

The release candidate for WordPress 4.2 is now available.

We’ve made more than 140 changes since releasing Beta 4 a week and a half ago. RC means we think we’re done, but with millions of users and thousands of plugins and themes, it’s possible we’ve missed something. We hope to ship WordPress 4.2 on Wednesday, April 22, but we need your help to get there.

If you haven’t tested 4.2 yet, now is the time! (Please though, not on your live site unless you’re adventurous.)

Think you’ve found a bug? Please post to the Alpha/Beta support forum. If any known issues come up, you’ll be able to find them here.

To test WordPress 4.2 RC1, you can use the WordPress Beta Tester plugin or you can download the release candidate here (zip).

For more information about what’s new in version 4.2, check out the Beta 1, Beta 2, Beta 3, and Beta 4 blog posts.

Developers, please test your plugins and themes against WordPress 4.2 and update your plugin’s Tested up to version in the readme to 4.2 before next week. If you find compatibility problems, we never want to break things, so please be sure to post to the support forums so we can figure those out before the final release.

Be sure to follow along the core development blog, where we’ll continue to post notes for developers for 4.2.

Im-Press-ive saving
Achievement unlocked: RC
Release here we come

WordPress 4.1 Release Candidate 3

The next release candidate for WordPress 4.1 is now available for testing.

Seventy changes have gone in since the first release candidate. With no known issues left, we plan to release 4.1 tomorrow, December 18.

To test, try the WordPress Beta Tester plugin (you’ll want “bleeding edge nightlies”). Or you can download the release candidate here (zip). If you’d like to learn more about what’s new in WordPress 4.1, visit the updated About screen in your dashboard ( ? About in the toolbar) and also check out the Beta 1 post.

Plugin authors: Remember to test your plugins against 4.1, and if they’re compatible, make sure they are marked as tested up to 4.1. Be sure to follow along the core development blog; we’ve been posting notes for developers for 4.1 as always.