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, #5-2-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, #5-2-2, #releases

Some changes to the 5.2.2 release schedule

A minor release of WordPress generally addresses between 20 and 35 issues, with a focus on those that arise from the new features and fixes in the current major release, which is 5.2.

Here’s the schedule the release team (@marybaum, @audrasjb @chanthaboune and @justinahinon) published a week ago.

The current schedule shows final release for 5.2.2 on Wednesday, June 12, 2019, 7:00 PM CDT.

Proposed agenda for this minor release cycle:

Already complete:

Going forward:

During devchat last week the active participants pointed out there are just twelve tickets milestoned for 5.2.2.

Meanwhile, almost 100 tickets for 5.3 already have patches and are a good fit for a minor release.

So let’s move 15-20 of those to 5.2.2 and take a little time to issue a more robust release. (There was a public discussion on this blog as well.)

Here’s a new proposed schedule for this week:

We’ll use Monday to triage those 5.3 tickets for the best candidates to move to this release. If you have favorites, let us (the release squad) know Saturday and Sunday, and we’ll see you Monday!

Then, based on the outcome of that scrub, we can use Wednesday’s devchat to finalize dates for RC2 and release.

#5-2-2

5.2.2 Release Agenda

The last weekly dev chat meeting featured a call for leads for 5.2.2.

@marybaum, @justinahinon and @audrasjb are leading the release. @chanthaboune is managing communications among the different teams involved.

The current schedule shows final release for 5.2.2 on Thursday 13 June 2019.

Proposed agenda for this minor release cycle:

#5-2, #5-2-2, #agenda, #bug-scrub