WordPress 5.2.3 RC 1

WordPress 5.2.3 Release Candidate 1 (RC1) is now available for testing! So please do – every test helps the build get closer to the final release!

You have two options for testing the WordPress 5.2.3 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the point release nightlies option), or download the release candidate here (zip).

What’s in this release?

5.2.3 features 29 bug and regression fixes, with some to the block editor, accessibility, i18n, media, and administration.

Here’s the list:

  • #46899: Ensure that tables generated by the Settings API have no semantics
  • #47145: Feature Image dialog does not follow the dialog pattern
  • #47390: Improve accessibility of forms elements within some “form-table” forms
  • #47190: Twenty Seventeen: Native audio and video embeds have no focus state.
  • #47340: Twenty Nineteen: Revise Latest Posts block styles to support post content options.
  • #47414: Twenty Seventeen: Button block preview has extra spacing within button
  • #47543: Twenty Seventeen: buttons don’t change color on hover and focus
  • #47688: Color hex code in color picker displayed in RTL instead of LTR on RTL install (take 2)
  • #47693: customizer Color picker should get closed when click on color picker area.
  • #45739: Block Editor: $editor_styles bug.
  • #45935: A URL in do_block_editor_incompatible_meta_box function does not have classic-editor__forget parameter
  • #47604: Undefined variable: locked in wp-admin/edit-form-blocks.php
  • #47489: Emoji are substituted in preformatted blocks
  • #47079: Incorrect version for excerpt_allowed_blocks filter
  • #47538: Minor Verbiage Update – Switch ‘developer time’ for ‘a developer’
  • #46757: Media Trash: The Bulk Media options when in the Trash shouldn’t provide two primary buttons
  • #46758: Media Trash: Primary button(s) should be on the left
  • #47113: Media views: dismiss notice button is invisible
  • #47458: Fix tab sequence order in the Media attachment browser
  • #47502: Media modal bottom toolbar cuts-off content in Internet Explorer 11
  • #47687: Use alt tags for gallery images in editor
  • #38415: New Custom Link menu item has a wrong fallback label
  • #47723: Adding a custom link in nav-menus.php doesn’t trim whitespace
  • #47888: Adding a custom link in menu via Customize doesn’t trim whitespace.
  • #47561: Plugin: View details popup layout issue
  • #47835: PHP requirement always set to null for plugins
  • #47386: Fix headings hierarchy in the legacy Custom Background and Custom Header pages
  • #47603: My account toggle on admin bar not visible at high zoom levels
  • #47758: Font sizes on installation screen are too small

You can browse the full list of changes on Trac.

What’s next?

Committers: The dev-reviewed workflow (double-committer sign off) is now in effect. That means it takes two committers to approve any changes to the 5.2 branch.

Plus, we have a hard string freeze until the official 5.2.3 release, scheduled for Wednesday, September 4, 2019, 10:00 AM PDT

Happy testing!

#5-2, #5-2-3, #rc1, #releases

Dev chat summary: July 17

@earnjam led the meeting. @marybaum took notes and is writing this summary.

Announcements

Gutenberg 6.1

@earnjam announced the release of Gutenberg 6.1 last week. New features include animations/motion to block reordering, improved messaging for REST API errors and more.

Check out the release post for more details: https://make.wordpress.org/core/2019/07/10/whats-new-in-gutenberg-10-july/

Look for version 6.2 RC to land next week.

PHP Coding Standards

@pento posted a followup to some proposed coding standards changes from a few months back.
See the decisions on these changes here (they might surprise you!): https://make.wordpress.org/core/2019/07/12/php-coding-standards-changes/

And keep in mind these affect only the code for WordPress Core. In your own Themes and Plugins, use the coding conventions that make sense for you.

Releases

5.2.3

With four tickets in the queue and none of them affecting functionality, it’s still not clear that they warrant a separate 5.2.3 release. Scheduling for that is still pending further info on a roadmap for 5.3, which should land in early fall.

5.3

As yet the Core team is progressing on current open tickets — there are 57 in the queue — while @chanthaboune continues gathering data from component maintainers on feature priorities for 5.3.

Component maintainer updates

Core-media

@azaozz asked for more eyes on #40439.

If you can help test, please check out the ticket or head to #core-media.

Site-health

@clorith pointed to the call for input for bumping the PHP recommendation and said that soon a Make blogpost will outline next steps—and next versions.

For now, the site-health team isn’t looking to raise the hard minimum. This will be a soft bump up to nudge users toward the minimums that will follow.

Open Floor

Triage Team

@joyously asked about progress from the Triage Team, and the responses came from several quarters.

@desrosj posted a link to his three-month summary: https://jonathandesrosiers.com/2019/06/wordpress-triage-team-3-month-reflection/ and plans to post more often on https://make.wordpress.org/updates.

@karmatosed mentioned that Design holds two triages a week, and that from where she sits, triage seems to be going gangbusters and spreading across the WordPress Project.

@azaozz pointed the group to his efforts on TinyMCE: https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&component=TinyMCE&order=priority

@marybaum mentioned having been in an accessibility triage last Friday.

Gutenberg Phase 2

Newcomer @Lu asked about the timing of Gutenberg Phase 2, with a particular interest in widget blocks. @earnjam answered with a summary of the release discussion earlier in the chat.

Strings

@marybaum asked the group for their thoughts on a more systematic, global approach to the copy in strings.

For now, the group agreed to have #meta add two keywords to tickets—needs-copy-review and has-copy-review.

Props to @garrett-eclipse, who opened meta#4609 and its counterpart meta#4610 on the spot.

Right at the close of the official chat, @audrasjb linked to https://make.wordpress.org/core/handbook/best-practices/post-comment-guidelines/#style-and-substance

#dev-chat, #gutenberg, #releases, #strings, #triage-team

#summary

WordPress 5.2.2 RC 2

WordPress 5.2.2 Release Candidate 2 (RC2) is now available for testing! So please do – every test helps the build get closer to final release!

You have two options for testing the WordPress 5.2.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the point release nightlies option), or you can download the release candidate here (zip).

What’s in this release?

5.2.2 features 13 bug and regression fixes, with some improvements to the block editor, accessibility, i18n, media and administration. Plus, this release adds a little bit of polish to the Site Health feature that made its debut in 5.2.

Here’s the list:

  • #45094: Dashboard elements don’t always have clear focus states, tab order
  • #46289: RTL Bug: wrong navigation arrows in media modal
  • #46749: Extra border is displaying at bottom of Help section in Firefox (Responsive : 778 * 841)
  • #46881: Site Health: improve the header elements horizontal centering
  • #46957: Site Health: Make site health page access be filterable
  • #46960: Site Health: Table design issue in small devices(iphone 5/SE).
  • #46997: Theme update links show in Customizer and don’t work
  • #47070: Recovery Mode Exit button not visible in responsive view
  • #47158: Merge similar strings introduced in WP 5.2
  • #47227: i18n: Merge similar translation strings – site health tabs
  • #47429: Editor: Update packages for WordPress 5.2.2
  • #47457: Fix the mediaelements player controls bar sizing
  • #47475: I18n: Merge similar strings and fix typo

You can browse the full list of changes on Trac.

What’s next?

Committers: The dev-reviewed workflow (double-committer signoff) is now in effect. That means it takes two committers to approve any changes to the 5.2 branch.

Plus, we have a hard string freeze until the official 5.2.2 release, scheduled for Tuesday, June 18 at 17:00 UTC.

Happy testing!

#5-2, #releases

WordPress 5.2.2 RC 1

WordPress 5.2.2 Release Candidate 1 (RC 1) is now available for testing! So please do – every test helps the build get closer to final release!

There are two ways to test the WordPress 5.2.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the point release nightlies option), or you can download the release candidate here (zip).

What’s in this release?

5.2.2 features ten bug and regression fixes, like some improvements to the block editor, accessibility, i18n, media and administration. And adds a little bit of polish to the Site Health feature that made its debut in 5.2.

Here’s the full list:

  • #45094: Dashboard elements don’t always have clear focus states, tab order
  • #46289: RTL Bug: wrong navigation arrows in media modal
  • #46749: Extra border is displaying at bottom of Help section in Firefox (Responsive : 778 * 841)
  • #46957: Site Health: Make site health page access be filterable
  • #46960: Site Health: Table design issue in small devices(iphone 5/SE).
  • #47158: Merge similar strings introduced in WP 5.2
  • #47227: i18n: Merge similar translation strings – site health tabs
  • #47429: Editor: Update packages for WordPress 5.2.2
  • #47457: Fix the mediaelements player controls bar sizing
  • #47475: I18n: Merge similar strings and fix typo

You can browse the full list of changes on Trac.

What’s next?

Committers: The dev-reviewed workflow (double-committer signoff) is now in effect. That means it takes two committers to approve any changes to the 5.2 branch.

The official 5.2.2 release is scheduled for Tuesday, June 18.

Happy testing!

#5-2, #releases

WordPress 5.2.1-RC2

WordPress 5.2.1-RC2 is now available for testing!

There are two ways to test the newest WordPress 5.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “point release nightlies” option), or you can download the release candidate here (zip).

What’s in this release?

In addition to the everything included in RC1, 5.2.1-RC2 fixes 3 issues discovered by those who tested RC1:

  • #47323 prevents a fatal error that occurs when upgrading to 5.2.1 from WordPress < 5.2.
  • #47304 fixes a regression that can affect the accuracy of <lastBuildDate> in feeds.
  • #47312 changes the string used on the About page for 5.2.1 to one that is already translated.

You can browse the full list of changes in 5.2.1 on Trac.

What’s next?

Committers: The dev-reviewed workflow (double committer sign-off) still applies when making any changes to the 5.2 branch.

The official 5.2.1 release is still scheduled for Tuesday, May 21.

Happy testing!

#5-2, #5-2-1, #releases

WordPress 5.2.1-RC1

WordPress 5.2.1-RC1 is now available for testing! But, your help is needed to test!

There are two ways to test the WordPress 5.2 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the “point release nightlies” option), or you can download the release candidate here (zip).

What’s in this release?

5.2.1 contains 32 high priority bug fixes and regressions, improvements to the block editor, accessibility, i18n, and polishes the Site Health feature introduced in 5.2. Here are some changes of note:

  • #47180: An issue typing in the block editor while using a RTL language has been fixed.
  • #47186: An bug causing 32-bit systems to run out of memory when using sodium_compat was fixed.
  • #47189: The “Update your plugins” link in Site Health now links to the correct page in multisite installs.
  • #47185: An issue in wp_delete_file_from_directory() where files were not deleting on Windows systems has been fixed.
  • #47205: A bug was fixed where spaces could not be added in the Classic Editor after pressing shift+enter.
  • #47265: 2 fatal errors on the error protection page when a PHP error was encountered in a drop-in (such as advanced-cache.php) were fixed.
  • #47244: wp_targeted_link_rel() has been improved to prevent instances where single and double quotation marks were incorrectly staggered.
  • #47169: PHP/MySQL minimum version requirement checks now return proper error codes when requirements are not met in test environments.
  • #47177: The backwards compatibility of get_search_form() was improved.
  • #47297: The accuracy of the HTTP requests test in Site Health was improved.
  • #47229: TinyMCE has been updated to version 4.9.4.

You can browse the full list of changes on Trac.

What’s next?

Committers: The dev-reviewed workflow (double committer sign-off) should now be enforced when making any changes to the 5.2 branch.

The official 5.2.1 release is scheduled for Tuesday, May 21.

Happy testing!

#5-2, #5-2-1, #releases

WP REST API: Version 2.0 Beta 5

Version 2.0 Beta 5 “¡Ay, caramba!” of the REST API is now available. Download it from the plugin repository or from GitHub.

This is a compatibility release with WordPress 4.4 Beta 1, and is required to use the plugin alongside WordPress 4.4.

Here’s some highlights:

  • Load api-core as a compatibility library
  • Now api-core has been merged into WordPress trunk (for 4.4) we should no longer load the infrastructure code when it’s already available. This also fixes a fatal error for users who were on trunk.

    (props @rmccue)

  • Switch to new mysql_to_rfc3339
  • (props @rmccue)

  • Double-check term taxonomy
  • (props @rmccue)

  • Load admin functions
  • This was removed from the latest beta of WordPress in the REST API infrastructure, a more long term fix is planned.

    (props @joehoyle)

  • Add compat shim for renamed rest_mysql_to_rfc3339()
  • (props @danielbachhuber)

  • Compat shim for wp_is_numeric_array()
  • (props @danielbachhuber)

  • Revert switch to register_post_type_args filter
  • (props @joehoyle)

We have a detailed changelog as well as the full set of changes if you’re interested.

#json-api, #releases, #rest-api

Beta 2 is out There are currently more…

Beta 2 is out.

There are currently more than 150 open tickets. Many need patches, many have patches that need testing. If you want to help, head over to https://core.trac.wordpress.org/report/6 and look for a ticket (or several) that you think you can help with. Many of them are not overly complicated, they just need people to give them some love.

Remember, if you find something in beta 2 that you think is a bug, report it! You can bring it up in the alpha/beta forum, you can email it to the wp-testers list, or if you’ve confirmed that other people are experiencing the same bug, you can report it on the WordPress Core Trac. (We recommend starting in the forum or on the mailing list.) If you’ve never reported a bug before, check out the Codex article on how to report bugs.

#3-3, #beta, #releases

A couple of hours ago the first 3.2…

A couple of hours ago, the first 3.2 beta release hit the ground. You know the drill: you break it, you buy it. Oh, wait. I meant, you break it, report it, and we all work together to fix it. Would be great to get more people helping with bug fixes between now and RC. Tell your friends.

#3-2, #releases

WordPress 3.0.1 is released. 55 tickets …

WordPress 3.0.1 is released. 55 tickets went into it. I opened the 3.0.2 milestone last week, and just now I’ve closed 3.0.1.

We pushed 3.0.1 twice, the second time about 20 minutes later, as we forgot about #14454. Not a big deal, but we’ve recommended over Twitter and on the announcement that you update again if you downloaded it before 2200 UTC.

We did a db version bump with the hope that we could force the API to return 3.0.1 again if you’re not at the proper version, but we don’t pass the db version via wp_update_check(). (@todo).

#releases, #trac