WordPress 5.2 Beta 1 Status Update (take two)

The remaining feature tickets in the milestone have been successfully committed! Thank you everyone for helping us get there. 🙂

During preliminary testing prior to the release, however, several folks discovered an issue with the new package signing feature, which would cause subsequent WordPress updates to fail (#46615).

Out of an abundance of caution, I’ve cancelled the WordPress 5.2 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 release that was scheduled for today, and tentatively rescheduled it for March 27, 2019, pending investigation of this package signing issue. I haven’t changed any other milestone dates, though they should be reviewed once we’ve released WordPress 5.2 Beta 1, to ensure they’re still realistic.

If you’re running the WordPress 5.2 Alpha nightly builds, you may not be able to update to subsequent nightly builds from the Dashboard due to this issue. Once #46615 is fixed, you can resume updates by manually copying the new files to your test site, or by updating with WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/: wp core update --version=trunk.