Bug Scrub Schedule for 5.3

Now that 5.3 has been officially kicked off, bug scrubs will happen weekly all the way up to the final release. Keep an eye on this schedule – it will change often to reflect the latest information.

  1. 8/27/2019 18:00 UTC
  2. 9/5/2019 14:00 UTC
  3. 9/12/2019 05:00 UTC (APAC-Friendly)
  4. 9/18/2019 23:00 UTC
  5. 9/25/2019 17:00 UTC
  6. 10/2/2019 16:00 UTC
  7. 10/9/2019 17:00 UTC Led by @marybaum
  8. 10/17/2019 TBD (If Needed)
  9. 10/23/2019 TBD (If Needed)
  10. 10/30/2019 TBD (If Needed)

These scrubs are separate and in addition to the normal scrubbing and triage by individual components. Some of those sessions include:

Design Triage: Every Monday 16:30 UTC at #design
Gutenberg Design Triage: Every Tuesday 16:00 UTC at #design
Accessibility Scrub: Every Friday 14:00 UTC at #accessibility

Also, @pento recently announced a new, ongoing APAC-friendly #core bug scrub session every Thursday at 06:00 UTC.

As the release date nears, one-off, “flash” scrubs pop up for individual components. These are typically focused on a specific group of tickets or an individual feature. Some of these sessions include:

Twenty Twenty Theme Scrub: 9/20/2019 16:00 UTC at #core-themes
Media Accessibility Scrub: 9/23/2019 06:00 UTC at #core-media (APAC-Friendly)
Media Accessibility Scrub: 9/25/2019 14:00 UTC at #core-media

Finally, a reminder that anyone — Yes, you! — can host a bug scrub at anytime. You can work through any tickets you’re comfortable with. In fact, if you plan one that’s 5.3-focused, we’ll add it to the schedule here along with your name. Finally, you’ll get well deserved props in the weekly Dev Chat, as well as in the #props Slack channel!

All open tickets for 5.3, in order of priority, can be found here. Tickets that haven’t seen any love in a while are in particular need. Those can be found in this query.

If you’d like to lead a bug scrub or have any questions or concerns about the schedule, please leave a comment or reach out to me directly.

#5-3, #bug-scrub

WP Notify meeting for 23 September 2019 cancelled.

Due to availability constraints, the WP Notify meeting for the 23rd of September 2019 is canceled.

We will pick up again on Monday the 30th of September 2019.

#feature-notifications

Editor chat summary: 18 September 2019

This post summarizes the weekly editor chat meeting on Wednesday, 18 September 2019 at 1300 UTC held in Slack.

The agenda can be found here.

Many folks were in transit, which made this a less busy meeting than usual.

Gutenberg 6.5 Release

Releasing shortly. You can see the RC here.

This will be the last release that goes completely into WordPress 5.3.

This is released now!

Weekly Priorities

Help test the RC!

Now released and in trunk — Please help test!

Task Coordination

  • @nadir is working with @joen on improvements to the Separator block (may end up as new Divider block), and looking into making the Stylelint config more strict.

Open Floor

@paaljoachim wanted to bring attention to a couple tickets:

@mikeschroder brought up https://github.com/WordPress/gutenberg/issues/6652, which is in regards to adding height and width attributes back to images in Gutenberg.

This ticket had conversation that started on Twitter with a tweet from Jen Simmons. There is a WICG recommendation that Mozilla is testing (and sounds like Chrome is planning as well) that makes rendering faster if height and width attributes are provided for images.

@desaiuditd is looking for feedback on https://github.com/WordPress/gutenberg/pull/17311, specifically regarding details on how the proposed useFilter would work.


Note: If you’re reading this summary outside of the meeting, please leave a comment if you can/want to help with something.

The next meeting is on 25 August 2019 at 13:00 UTC.

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

Twenty Twenty Bug Scrub

We will be having our first bug scrub for Twenty Twenty on Friday, Sept 20th at 16:00 UTC, led by @ianbelanger in the #core-themes channel. All are invited to attend. Come help us scrub some bugs before the 5.3 Beta 1 release.

Reminder #1 – Monday, Sept 23rd is 5.3 Beta 1

Reminder #2 – We will be freezing commits to the github repo on Sunday, Sept 22nd 4:00 UTC to prepare for 5.3 Beta 1

As a refresher, here’s a post from the 4.7 release cycle answering questions about bug scrubs.

#5-3, #bug-scrub, #twentytwenty

Media Meeting Recap – September 19, 2019

The following is a summary of the weekly media component meeting that occurred on Thursday, September 19, 2019. Weekly media meetings are held every Thursday at 13:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @anevins, @joemcgill , @FahimMurshed, @mikeschroder, @antpb, @afercia

Media Focus update: @mikeschroder has been hard at work on a 5.3 intro post. In it will be a focus on calling for testing.  Coming soon!

Add width and height attributes to <img> elements – https://github.com/WordPress/gutenberg/issues/6652
Discussion is taking place in this Slack thread. Maintainers in attendance all agreed that this would be great to be considered a bug and a potential impactful improvement to the editor experience. @joemcgill said, “Realistically, I think a first step is just adding a proof of concept that modifies the save attribute of the image block so the h/w attributes are always saved and then see what breaks.”

5.3 Ticket Triage

#47120Media modals: Upload errors and field information are not associated with their control : @antpb has taken ownership of the ticket and will investigate how we would best inject the recommended code into the various buttons/views.

#47137Insufficient form semantics : This issue was split into two issues (the other below) to allow the overall problem to improve in pieces. Ownership for this one is needed. It’s a bit of a tough issue that no one has yet to see an immediate solution.

#48028Media Library ‘featured image’ dialogue missing link text that describes ‘opens in new tab’.@afercia said “I think there’s the need to check how editState is implemented in the post frame and what is intended for. That implementation completely lacks in other frames. I think this is for historical reasons because the post frame was the only frame supposed to be used in the “edit post” context.” and @joemcgill responded “The classic editor used the Post frame in most places, rather than the Select frame. Now that most of Gutenberg is using the Select frame, some odd bits aren’t working the same—just like that other featured image bug you (@antpb) just fixed” @antpb assigned the issue to himself given his recent exposure to the featured image frames. A github issue is needed also to track this change in the Gutenberg plugin @antpb is working on that. More to come!

#47144Text inadvertently rendered by assistive technologies – Was mentioned at end of meeting but discussion was not able to be had. This issue is in need of ownership for the 5.3 release.

#47611Media views: hide the “file upload button” from assistive technologies – Was mentioned at end of meeting but discussion was not able to be had. This issue is in need of ownership for the 5.3 release.

Bug Scrubs next week!

@mikeschroder and @antpb have offered to lead two bug scrubs in #core-media next week to find ownership for the remaining accessibility issues planned for the 5.3 milestone:

Feedback

If you have any feedback on the above, please feel free to leave a comment, join in #core-media for a chat, or attend the next meeting on September 26, 2019 at 1300UTC!

#core, #core-accessibility, #core-media, #media, #summary

What’s new in Gutenberg? (18 September)

More than 46 contributors participated in the Gutenberg 6.5 release. It’s the last release that is going to be entirely included in the upcoming WordPress 5.3.

This release comes with a huge number of features, improvements and bug fixes. Among these, the long asked for Social links block.

It also adds support for local auto-saves to avoid content loss even in environments with unstable internet connections. Edits are saved locally, and a warning is displayed with the possibility to restore the local edits if available.

Several blocks have been updated with new features such as the support for border radius changes in the Button block and the possibility to add a caption to the Gallery block.

This release includes the possibility to install blocks that are not available locally directly from the block inserter if you have the required permissions. This feature is marked as experimental feature. A dedicated call for testing will be published soon.

6.5

Features

Enhancements

Bug Fixes

Experiments

APIs

Various

Documentation

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~ 36000 words, ~ 1000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

Version Loading Time KeyPress event (typing)
Gutenberg 6.5.0 4.46s 54.43ms
Gutenberg 6.4.0 4.67s 53.30ms
Gutenberg 5.3 (WordPress 5.2) 6.16s 62.43ms

👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg

WP Notify Meeting Recap – September 16, 2019

This post summarises the weekly WP Notify chat meeting from 16 September 2019.

Weekly WP Notify meetings are held every Monday at 14:00 UTC and 22:00 UTC respectively.

Project contributors document

@hrmervin has created a Project contributors document. If you haven’t already, and you’re keen to contribute to this project, please add your details there. Putting in things like areas of interest will help us determine who to ask for specific help. We’d also add that things like email address we consider non-compulsory, so you don’t have to put in your email.

Requirements gathering document

The requirements gathering document has been created, and is currently empty. Our goal is to have the bulk of the info we have so far in this document by the time of the next meeting. We’d like to get two other contributors on board (besides @psykro and @hrmervin) to help collate the information. If you’re keen to help, comment on this post. @dinhtungdu expressed interest in contributing to this document.

Project naming

We will be sticking with WP Notify for now, as it also ties into the namespace @schlessera proposed for the API and should help avoiding confusion when discussing any specific parts of the project later on.

Meeting host availability and contingency plans

Right now this project has a bus factor of 1, in that if @psykro cannot post the agenda or host the first meeting, that weeks set of meetings are usually cancelled. It was suggested that this is acceptable as the nature of open source.

Comments/suggestions are encouraged and welcome.

#feature-notifications, #summary

Summary of Core Privacy Office Hours, Sept. 18th 2019

Below is a summary of the discussion from this week’s Core Privacy chat (agenda, Slack Transcript).

Agenda Item: 5.3 Enhancements

The following tickets were flagged as enhancements for 5.3 privacy component;

  • #43890 – Allow Admin to Skip e-mail confirmation for Export/Anonymization.
  • #44133 – Should the Data Export indicate when we have no information on the user.
  • #44135 – Have Erasure button workflow follow Export button workflow replacing with static link.
  • #44588 – Denote the Copy action is complete by updating the Copy button to state ‘Copied’.
  • #46303 – Update wp_privacy_send_personal_data_export_email to provide the same filters as _wp_privacy_send_erasure_fulfillment_notification.
  • #46895 – Personal Data Export Report: A way to display the group count.

#44133, #44135, #46303 and #46895 are all nearing completion but will need another set of eyes and review/testing before they can be marked commit.

#43890 and #44588 will need some work either a refresh or initial patch.
#43890 needs discussion but @garrett-eclipse is leaning towards the use of checkboxes instead of dropdown.
#44588 has site health example to follow and just needs coding.

@pputzer graciously offered to review some of these tickets.

Agenda Item: Privacy Data Request Form

Feature Plugin Proposal – https://make.wordpress.org/core/2019/09/04/feature-plugin-proposal-privacy-data-request-form/

Not much feedback has been received yet so will let it gestate a little more. Initial feedback is pointing towards plugin territory over a core merge.

@audrasjb indicated it would be nice to test as a featured plugin so will determine how that can be accomplished.

Agenda Item: Consent and Logging Mechanism for User Privacy

Feature Plugin Discussion – https://make.wordpress.org/core/2019/08/07/feature-plugin-discussion-a-consent-and-logging-mechanism-for-user-privacy/

@garrett-eclipse asked if the effort needs to be setup like the WP-Notify #feature-notifications team and meetings.

Neither @idea15 nor @garrett-eclipse have capacity currently to spearhead the effort so decided to collect names of interested parties to create a working group. If anyone is interested in working on the consent/logging mechanism please feel free to comment on this thread or reach out in #core-privacy on Slack.

#privacy

Dev Chat Agenda for September 18th 2019 (5.3 week 5)

Here is the agenda for the weekly meeting happening later today: Wednesday, September 17, 2019, 11:00 PM GMT+3. Please share any items you’d like to include in the comments below!

  • Announcements and highlighted posts
  • Upcoming Release Discussions
  • 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, #agenda, #devchat

Integer menu slugs are no longer supported from WordPress 5.3

Previously, menus could be registered with an integer slug. This used to cause unintended issues that are difficult to debug.

Consider the following use of register_nav_menus:

register_nav_menus(
    array(
        'primary' => 'Primary', 
        1 => 'First', 
        2 => 'Second',
    )
);

The assumption is that the resulting list of menus would match what was passed. Instead, the result is this:

array( 
    'primary' => 'Primary', 
    0 => 'First', 
    1 => 'Second', 
)

This would cause wp_nav_menu( array( 'theme_location' => 1 ) ) to return the wrong menu.

From WordPress 5.3, it will trigger a _doing_it_wrong() warning when registering a nav menu with a numeric index. This will at least inform developers of the potential issue, and would also encourage better practices of using a string slug for nav menus.

For reference, see the related Trac ticket: #45361

#5-3, #dev-notes

Privacy Office Hours Agenda: Wednesday September 18th, 2019

The following is the agenda for the privacy weekly office hours meeting. The meeting is held every Wednesday at 19:00 UTC in the #core-privacy room of the Making WordPress Slack.

  • Announcements / Housekeeping
  • Upcoming Release (5.3) Discussion & Planning
    Note: We have 6 enhancements pending for 5.3, they will need to be committed or punted by Sept. 23rd, 2019.
    • #43890 – Allow Admin to Skip e-mail confirmation for Export/Anonymization.
    • #44133 – Should the Data Export indicate when we have no information on the user.
    • #44135 – Have Erasure button workflow follow Export button workflow replacing with static link.
    • #44588 – Denote the Copy action is complete by updating the Copy button to state ‘Copied’.
    • #46303 – Update wp_privacy_send_personal_data_export_email to provide the same filters as _wp_privacy_send_erasure_fulfillment_notification.
    • #46895 – Personal Data Export Report: A way to display the group count.
  • Feature Plugin Proposal: Privacy Data Request Form
  • Feature Plugin Discussion: Consent and Logging Mechanism for User Privacy
  • Discussion / Open Floor

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

#core-privacy, #privacy