WP Notify Kick off meeting agenda for August 26th 2019

Here is the agenda for the kick off meeting happening next week, Monday, August 26, 2019, 14:00 UTC and Monday, August 26, 2019, 22:00 UTC. Please share any items you’d like to include in the comments below!

  • Opening and welcome
  • Review of current project status
  • Discussion of next steps
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #feature-notifications channel , to join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #feature-notifications

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

JavaScript Chat Summary: Aug. 20th, 2019

Below is a of the discussion from this week’s JavaScript chat (agenda, Slack Transcript). Thanks to @c4rl0sbr4v0 for taking these notes.

Our agenda was empty this week so all discussion arose from the open floor.

Introducing a new icon package

@nadir says that they will clean the PR of files auto-generated files and also that they were looking at a way to treeshake without the need to import individual icons manually.

There has been a discussion about including all icons in a wp.icons variable

  • Advantages:
    • Plugin developers that don’t use any build system have the ability to access our icons in their code.
  • Disadvantages:
    • We can’t load +1000 icon in a single script.

Possible solutions:

  • Select, download and manually include your icons in a web/cli tool like lodash or Material design.

This is a tough issue exploring the requirement for devs to include or not a build system and if this is overkill just to include a few icons.


Keep the discussion going in the ticket and hopefully we can arrive at a way forward.

Source maps in firefox

@pierlo asks for help with this issue:

Unable to load source maps from webpack in Firefox

@swissspidy asked if this is also a Gutenberg issue, referring a solution here


No actions debated in Slack channel.

#core-js, #javascript, #meeting-notes

WordPress 5.3 Schedule and Scope

Following the open call for tickets and the planning roundup, we are ready to kickoff the release cycle for WordPress 5.3!


After checking with the focus leads, the proposed timeline is confirmed, as follows:

  • Beta 1: 23 September, 2019
  • Release Candidate: 15 October, 2019
  • General Release: 12 November, 2019


The focus will be polishing current interactions and make the UIs more user friendly.


  • Release Lead: Matt (@matt)
  • Release Coordinator: Francesca Marano (@francina)
  • Triage PM: David Baumwald (@davidbaumwald)
  • Editor Tech: Riad Benguella (@youknowriad)
  • Editor Design: Mark Uraine (@mapk)
  • Core Tech: Andrew Ozz (@azaozz)
  • Docs Coordinator: Justin (@justinahinon) + TBC
  • Marketing/Release CommsTBC
  • Media/UploaderTBC
  • Accessibility: JB Audras (@audrasjb)
  • Default ThemeTBC


At the moment of writing, there are 327 tickets open in the milestone: https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&milestone=5.3&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority

Weekly Bug Scrubs

We will work our way through them via weekly scrubs

Proposed schedule will be discussed today, August 21st 2019, during the weekly Core chat. Ideally we will get assistance from component maintainers, that can help run specifically focused bug scrubs.

Let’s do this, ad maiora!


Editor Chat Summary

This post summarizes the weekly editor chat meeting on August 21, 2019 at 1300 UTC held in the core-editor Slack channel.

The agenda can be found here.

Note: If you’re reading this summary async, please drop a comment if you can/want to help with something!

Priorities for the week

Slack transcript.


Being worked on / Needs more work:

Task Coordination

Slack transcript.

@youknowriad Refresh to reusable blocks that closes multiple issues, triagged issues and reviewed PRs.

@karmatosed Triagged, mainly issues/PRs that need design feedback.

@kjellr Improvements to the inserter help panel (1, 2), changes to NUX tips, and tidying up animations (1, 2).

@jorgefilipecosta Explored mobile viewport in the editor (1, 2). To work on text color formatting, gradient backgrounds, cover block resizing.

@mapk Looking into improving the sibling block inserter, helping on widgets work and @retrofox on a UI solution for screen height PR.

Components package reorganization and bundle sizes

Agenda | Slack Transcript | Issue

The issue created by @nerrad sparked a conversation on how to control bundle size and offer options to bundle “what you need”:

  • The `wp_enqueue_script` model encourages people to use the whole bundle for a package, not the specific pieces you want.
  • There are concerns over creating too many packages that make discoverability difficult.
  • Overrall, this ties into how to make WordPress play nicely with dynamically loading dependencies as you need them (the SPA model).

To be discussed more in the issue and/or in future core-js chats.

e2e test and block deprecations

Agenda | Slack Transcript | Issue

  • @isabel_brison raised the issue that e2e tests fail due to block deprecations triggering a `console.warning`.
  • The restriction have been very valuable when it came to deprecate APIs, as to make sure core wasn no longer using them. It is not that useful in other contexts.
  • There is a draft PR to address the deprecation issue.

#core-editor, #editor-chat, #summary

Dev Chat Agenda for August 21st 2019 (5.3 week 1)

Here is the agenda for the weekly meeting happening later today: Wednesday, August 21, 2019, 20:00 UTC. Please share any items you’d like to include in the comments below!

  • Announcements
  • Upcoming Release Discussions
    • 5.2.3 Updates after the latest bug scrub
    • 5.3 Kickoff (missing focus leads, general and focussed bug scrubs, development cycle guide)
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel, to join the meeting, you’ll need an account on the Making WordPress Slack.

#5-3, #5-2-3, #agenda, #core, #devchat

WP Notify Kick off meeting announcement

I’d like to announce the first meeting of the WP Notify project. The meeting will be held on Monday 26 August 2019 in the #feature-notifications channel.

In order to allow for multiple time zones, we’ll be having two meetings, one at 14:00 UTC, run by myself, and one at 22:00 UTC, run by @hrmervin. We’ll do our best to keep these two meeting times going forward.

I will post an agenda for the meeting closer to the time, and to allow folks to propose agenda items for the meeting.


Editor Chat Agenda: August 21st

Note taker: @nosolosw

This is the agenda for the weekly editor chat scheduled for August 21, 2019 at 1300 UTC.

This meeting is held in the #core-editor channel in the Making WordPress Slack.

  • Tasks Coordination
  • Open Floor

If you have anything to share for the Tasks Coordination section, please leave it as a comment on this post.

As always, if you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #editor-chat

Editor chat summary: 14 August 2019

This post summarizes for the weekly editor chat meeting on Wednesday, August 14, 2019 at 1300 UTC held in Slack.

The agenda can be found here.

Gutenberg 6.3 

  • @riad noted that this release is a very important release in terms of Accessibility because it introduces the Navigation Mode

Priorities for next week

Please don’t hesitate to help there. Provide a11y and design feedback. Help with tests… Let’s move these forward.

Task Coordination

Based on the links in Task Coordination, Riad extracted a list of PRs where feedback is needed:

Open Floor

There was a discussion about new core blocks being developed. The central idea is that some ideas, while good, are low priority, for example the gists block or the multi select dropdown.

Riad explained that the ideas for the blocks themselves are good but “we added components as we needed them in Core and Core blocks. Doesn’t mean we can’t add components for third-party authors if they prove to be useful for a lot of persons but we’d need contributors to champion these”

There is also a list of new blocks that are high priority and considered “blessed tasks” and the list includes: icons, menu, social icons, divider and other Full site editing related blocks (site title, post title, post categories).

Note: Anyone reading this summary outside of the meeting, please drop a comment if you can/want to help with something.

The agenda for the next meeting, 21 August 2019 13:00 UTC is here, please add anything you want to discuss.

#core-editor, #core-restapi, #editor, #gutenberg, #meeting-notes

Follow-up Discussion on Major Auto Updates

Last week’s proposal to automatically upgrade old sites to 4.7 has garnered a lot of feedback, which has been very helpful in refining the idea and getting a sense of how different parts of the community feel about it.

To follow up on that, I’d like to have a meeting in #core on Tuesday, August 20, 2019, 2100 UTC to continue the discussion. No decisions will be made during the meeting, but I hope that we can have a productive conversation and move closer to some kind of resolution.

To join the meeting, you’ll need an account on the Making WordPress Slack. If you’re not able to attend, but would like to give feedback, please leave a comment on the proposal.

#auto-update, #security