WordPress 6.6 RC2 is ready for download and testing!
This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, please evaluate RC2 on a test server or a local environment.
Reaching this phase of the release cycle is a worthy achievement. While release candidates are considered ready for release, your testing is still vital to make sure everything in WordPress 6.6 is the best it can be.
You can test WordPress 6.6 RC2 in four ways:
| Plugin | Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream). |
|---|---|
| Direct Download | Download the RC2 version (zip) and install it on a WordPress website. |
| Command Line | Use the this WP-CLI command:wp core update --version=6.6-RC2 |
| WordPress Playground | Use the 6.6 RC2 WordPress Playground instance (available within 35 minutes after the release is ready) to test the software directly in your browser without the need for a separate site or setup. |
The target for the WordPress 6.6 release is July 16, 2024. Get an overview of the 6.6 release cycle, and check the Make WordPress Core blog for 6.6-related posts in the next few weeks for further details.
Thanks to your testing and many other contributors‘ up to now, this release includes more than 19 bug fixes for the Editor and more than 20 tickets for WordPress Core.
Get a recap of WordPress 6.6’s highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since Beta 3, you can browse the following links:
Want to look deeper into the details and technical notes for this release? You might want to make your first stop The WordPress 6.6 Field Guide. Then, check out this list:
WordPress is the world’s most popular open source web platform, thanks to a passionate community of people who collaborate on its development in a wide variety of ways. You can help—whether or not you have any technical expertise.
Testing for issues is critical to keeping WordPress speedy, stable, and secure. It’s also a vital way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.6. If you’re new to testing, follow this general testing guide for more details on getting set up.
If you encounter an issue, please report it to the Alpha/Beta area of the support forums. If you are comfortable writing a reproducible bug report, you can also report it on WordPress Trac. Before you do either, you may want to check your issue against a list of known bugs.
Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.
From now until the final release candidate of WordPress 6.6 (scheduled for July 9), the financial reward for reporting new, unreleased security vulnerabilities doubles. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.
If you build themes, plugins, blocks, or patterns, your products play an integral role in extending the functionality and value of WordPress for all users.
Thanks for continuing to test your products with the WordPress 6.6 beta releases. With RC2, you’ll want to finish your testing and update the “Tested up to” version in your plugin’s readme file to 6.6.
If you find compatibility issues, please post detailed information to the support forum.
Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? You can help translate WordPress into more than 100 languages.
6.6 draws near.
In two weeks the final’s here.
Test. Test. Then test more.
Props to @juanmaguitar, @meher, @desrosj and @atachibana for peer review.
