Dev Chat Summary: October 30th 2019

This post summarizes the weekly dev chat meeting from October 30th 2019 (agenda / Slack Archive).


WordPress version 5.3 Release Candidate 3 was released on Tuesday. Everyone please help by testing out the RC.

Core editor team released Gutenberg version 6.8.

Dev chat meeting time

Like every year, with end of DST (daylight saving time), the meeting time should be moved from 20:00 UTC to 21:00 UTC.

Two options are proposed:

  • Moving on Wednesday November 13th (the day after WP 5.3 is going to be released)
  • Moving on Wednesday November 20th (one week later)

Please share your thoughts in this post’s comments.

WordCamp US Contributor Day

WordCamp US’s contributor day is planned for Sunday 3rd November.

5.3 was branched last week, so contributors will be able to work on WordPress 5.4 milestone since trunk is now version 5.4-alpha.

@earnjam and @wpscholar will be leading the core table, Helping people get set up, learn how to get started, find places to focus on work, etc. They also should have several component leads present that can split off and focus on their areas for people who are interested.

Upcoming Releases

WordPress 5.3 Release Candidate 4 is scheduled next Tuesday if needed.

There is still 7 tickets open in the milestone.

@azaozz regrets that things weren’t reported much earlier, during beta. By the way, two tickets have patches already, one is almost there, and one may be a candidate for 5.3.1. As 5.3 was branched, all fixes are probably going to be committed to trunk (5.4-alpha) but hold on on merging to 5.3 for couple of days to allow easier testing and review. All are (possible) regressions with the way some plugins use particular hooks around image post-processing and image meta updates.

@joyously reported a feedback found in Alpha/Beta support forum. It was already merged to Gutenberg and looks fixed in 5.3 block editor code. @youknowriad was pinged as Editor focus lead for WP 5.3.

Open floor

@joyously asked about backporting security fixes to old versions request’s status.

@clorith and @audrasjb noted there will be a panel session at WordCamp US. For those who are not attending WordCamp US, questions can be sent via Twitter.

@desrosj added that there was a very large amount of feedback. @chanthaboune and others are working to compile all that feedback so that all of it can receive proper consideration.

#5-3, #contributor-day, #wcus

How you can help with the Network Admin UI during contributor day

A previous write-up explains how you can help test and capture the network admin UI. Here’s a specific version for how you can help during contributor day this weekend.

There are four steps to the workflow at the moment:

  1. Capture a visual record of network admin screens.
    • Ideally on a device/browser combination that has not yet been captured.
    • If comfortable, post the screen captures and notes on
    • If you need access to Make/Flow, ask in #core-flow on Slack or around the physical room you’re in (if it’s full of contributors).
  2. Observe screens, actions, and results throughout the network admin.
    • This can happen during or after step 1. You can also just do this without the first step.
    • Look for things that don’t make sense, visual errors, pieces that are difficult on mobile, etc…
  3. Document observations in the screen sweep sheet.
    • This can be with or without a Trac ticket. With or without a screenshot.
    • Acts as a note so that we know that to come back to as part of the overall admin UI improvement effort.
  4. Help with the screen sweep sheet.
    • Open a ticket if there is none. Add screenshots if there are none. Confirm/deny the issue.
    • And patch. If there’s a ticket on the screen sweep sheet that you can patch, submit away.

While this is an ordered list, you do not need to treat it like one. Pick a step that feels comfortable and concentrate on that. If you need guidance, there are folks in Slack that are always happy to help.

Current captured visual records:

By all means, if you have a device that is already captured, don’t hesitate to capture it in your own way or to skip step 1 entirely and start observing.

Thanks for the help!

#contributor-day, #multisite