Dev Chat Summary – 21 October 2020

This post summarizes this week’s meetings happening on Wednesday, October 21, 2020, 07:00 AM GMT+2 and Wednesday, October 21, 2020, 10:00 PM GMT+2 on the agenda.

0500 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devchat

0500 Full meeting transcript on SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at

@peterwilsoncc facilitated the meeting and took notes.

2000 core devchat

The meeting was facilitated by @laurora while @thelmachido took notes. Full meeting transcript on slack

Both groups followed this agenda.

First item: celebrating the first beta release of WordPress 5.6 on October 20! Please download the 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. version, experiment with it on a test installation (not a live site!) and share any bugs you find or issues that come up.


@annezazu announced the Widgets Screen won’t land in 5.6. A Make Core post is coming soon that will discuss where the feature is and what the next steps will be. And though the feature isn’t ready for the current release, it is still on the roadmap, and the team points out they still need feedback on the current work. You can give them that feedback, or share any other thoughts, here or on GitHub.

Highlighted Posts

Introducing Github actions for automated testing.

Please check it out! Your contributions are welcome.

Component Updates

PHP 8 call for testing

@sergeybiryukov highlighted the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher call for testing.

Build/Test Tools

Again, GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. Actions are now running automated tests. See this post and this ticket for more.

@whyisjake is looking at a 5.5.2 release on Tuesday, October 27 or Thursday. October 29. He hopes to run a scrub tomorrow and then put the release docs together over the weekend.

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (

With the Beta 1 released, the team plans to switch gears to accessibility: namely, to review and package the Accessibility Statement feature as a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party. @jonnyvaughan and Alice Williams, who have begun coding the feature, would love some feedback and testing. Interested? Check out this GitHub repo.


@mikeschroder asked for testing on #42663, which landed on October 20. He’s especially interested in your help if you write plugins that use stream wrappers.

He has two priorities:

  1. Make sure existing stream implementations still work.
  2. How hard is it to integrate those implementations with this new one?

Look for a dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. from Mike as we get closer to final release. slack

Open Floor

@garrett-eclipse opened #51584 to ask if anyone else had hit the problem. After some discussion, the group concluded it is reproducible but doesn’t appear to be a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in WP 5.6 slack

@garrett-eclipse shared that he’s been wondering if WP notices should be active or passive. He has been leaning towards the convention that Google has and was wondering if he can add that to the handbook? @pbiron mentioned that US English spelling is mentioned in the handbook. Follow the conversation here slack.

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 28, 2020, 07:00 AM GMT+2 and Wednesday, October 28, 2020, 10:00 PM GMT+2 in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

#5-6, #dev-chat, #summary