David Baumwald 5:34 pm on August 27, 2019
Tags: ,   

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 17:00 UTC
  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
Accessibility Scrub: 10/1/2019 16:00 UTC at #accessibility

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

Grzegorz (Greg) Ziółkowski 3:37 pm on October 31, 2019
Tags: , , , ,   

JavaScript chat summary, October 29nd, 2019

Below is a summary of the discussion from last week’s JavaScript chat (agenda, Slack Transcript)

Have a topic for discussion for the next meeting? Leave a suggested edit on this week’s agenda.

React prerelease channels

Slack Conversation

There was an announcement from the React team about official prerelease channels:

The long story short is they are promoting react@next prereleases and share some guidelines on how to test projects with the upcoming changes to their libraries. If you want to get involved and explore how the Gutenberg project could participate please comment on the corresponding issue.

Time of the meeting

Slack Conversation

Weekly meetings discuss JavaScript in the context of the WordPress ecosystem and we value the input from people working with JavaScript in WordPress. We wanted to survey people whether they would like to participate in the weekly chat if there was a different time?

As of today, we expect you’ll come to the meeting prepared to contribute your perspectives and help influence direction. You can also share in comments what would you expect from such meetings.

Testing components

Slack Conversation

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

Jb Audras 9:57 pm on October 30, 2019
Tags: , ,   

Dev Chat Summary: October 30th 2019

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

Announcements

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

Riad Benguella 4:37 pm on October 30, 2019
Tags: , ,   

What’s new in Gutenberg? (30 October)

Work on block content areas and the navigation menu block is accelerating in this release.

In the meantime, this release continues the work on Gradients support and expand it to the Cover block while relying on classnames instead of inline styles

Screenshot 2019-10-17 at 14 59 27

Block Nested selection and interactions is still being improved with a new Block Breadcrumb Bar allowing to quickly navigate the block hierarchy of . the current selection.

Capture d’écran 2019-10-16 à 11 34 50 AM

6.8

Features

Enhancements

Bugs

Experiments

New APIs

Various

Add knobs to the ColorIndicator Story.

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.8.0 5.68s 47.28ms
Gutenberg 6.7.0 5.83s 47.92ms
WordPress 5.2 6.1s 63.22ms

👏 Kudos to all the contributors. Thank you.

#core-editor, #editor, #gutenberg

Jb Audras 3:02 pm on October 30, 2019
Tags: , ,   

Dev Chat Agenda for October 30, 2019 (5.3 week 11)

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

  • Announcements
    • Highlighted posts
    • Move Dev chat meeting time (end of daylight saving time)
  • WCUS/contributor day
  • 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

Miguel Fonseca 2:47 pm on October 29, 2019  

Editor Chat Agenda: October 30th

Note taker: @pbrocks

This is the agenda for the weekly editor chat scheduled for Wednesday, 30th October 2019, 13:00 UTC.

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

If you have anything to share for the Task 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

Riad Benguella 1:01 pm on October 29, 2019
Tags:   

What’s next in Gutenberg? (November)

This is a monthly update containing the high-level items, Gutenberg contributors are and should focus on for the next month.

Block Content Areas

In previous Gutenberg releases, a new wp_template Custom Post Type has been created to store block content areas and enable using Gutenberg outside the post content. In the next weeks, contributors will be working on expanding on this work:

  • Render the frontend template loader to support wp_templates 17626.
  • Add a temporary UI to edit these templates 17625.
  • Experiment with blocks targeting site options (title) 17207.
  • Work on a UI to save multiple entities (post, site, template…) from the same interface. 18029.
  • Nested template areas.

Menu Navigation Block

The Menu Navigation is also one of an important focus for this month. You . can follow all the related work on this project and the overview issue.

Tightening up

Existing interactions and blocks will be iterated on:

  • Gradients support across blocks 18001.
  • Theme API for gradients. 17841, 18008, 18028.
  • Improvements to the Media Flows. 16200.
  • Improve nested block navigation through a block hierarchy breadcrumb and explore selection tools. 17838 17088.

#core-editor

Omar Reiss 10:44 pm on October 28, 2019
Tags: , , , ,   

JavaScript chat summary, October 22nd, 2019

Below is a summary of the discussion from last week’s JavaScript chat (agenda, Slack Transcript)

Have a topic for discussion for the next meeting? Leave a suggested edit on this week’s agenda.

Agenda: Node LTS

Slack Conversation

Recently, Node 12 became the new LTS version for Node. A pull request to make WordPress scripts compatible with Node 12 was merged.

Agenda: Code style

Slack Conversation

A change to the JSDoc plugin triggered new ESLint warnings. These were fixed in a pull request: https://github.com/WordPress/gutenberg/pull/18025.

Another PR tries to bring WP Prettier into WP Scripts. WP Prettier is a Prettier fork that follows the WordPress code conventions that allows to easily reformat all of WordPress JavaScript but also enable other developers in the community who leverage WP scripts to do the same.

Agenda: Storybook

Slack Conversation

In September, Storybook was added to Gutenberg. There’s an issue open discussing next steps, which includes adding stories for all @wordpress/components and adding support for React Native components. @mkaz published a tutorial video on his blog on how to code a storybook story.

The following questions could be explored:

  • How can we enable plugin and theme developers to leverage storybook in their own workflows? It was suggested storybook could be added to WP scripts.
  • How can we integrate storybook into https://developer.wordpress.org/block-editor/? Storybook could be a replacement for the components reference.

A few concerns were raised with regard to using storybook on wordpress.org:

– How do we keep the WP dev site header?
– How do we avoid iframes (and include the header) to keep routing?
– How do we keep the READMEs (or some aspects of them) as there’s a lot of good info there?

It seems storybook allows for enough customization to be able to address these concerns. Some help from the meta team would be required.

Open floor: Card component

Slack Conversation

@itsjonq worked on a PR for a new Card component. There’s still some ongoing discussion about the introduction of css-in-js and Enzyme in that PR. Feedback appreciated!

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

Jonathan Bossenger 11:51 am on October 28, 2019
Tags:   

WP Notify meeting for 28 October 2019 cancelled.

With WCUS just around the corner, the WP Notify meeting for 28 October 2019 is canceled.

If anyone wants to chat about WP Notify, @hrmervin will be available to connect with folks at the WCUS Contributor Day.

#feature-notifications

Mervin Hernandez 6:10 am on October 28, 2019
Tags: ,   

WP Notify – Meeting Recap – Oct 21, 2019

This is a recap of a meeting held October 21 for a Core project related to WordPress Admin Notifications. Meetings on this task are held every Monday at 14:00 UTC and 22:00 UTC respectively.

Related Links

Google Doc: WP Notify Project Requirements Document

Notes Per Agenda

Open Floor for Feedback

Our discussion this meeting further refined the focus of this project, to be a solution “… plugin and theme developers can leverage, again instead of using admin_notices.”

Present handling of admin_notices will require distinction between immediate (core) based notifications such as successful saves, and a queue of notifications to be followed up on at a later time.

This project seeks to pave the way so future projects can build upon the new notifications handling. Enhancement such as mail or push notifications handling, will be able to leverage the processing we create here.

Next Steps

We welcome feedback on the project either here in this post, or in the requirements (via Google Doc, comments). 

We invite you to attend our next meeting, held in Slack > #feature-notifications

  • Monday, October 28 2019 at 14:00 UTC 
  • Monday, October 28 2019 at 22:00 UTC

#summary

David Baumwald 9:04 pm on October 23, 2019
Tags: , , ,   

Dev Chat: 10/23/2019

The facilitator for this week’s chat was @audrasjb.

Announcements

WordPress version 5.3-RC2 was released on Tuesday. Everyone please help by testing out the RC.

The latest Dev Note published for 5.3 discuses “Noteworthy Admin CSS Changes in WordPress 5.3”.

Also, the official Field Guide for 5.3 was published!

@audrasjb called attention to the wonderful documentation work this cycle by @justinahinon and @jeffpaul. Thank you to both for their extraordinary efforts!

5.3 Updates

@azaozz Pointed out that there are only two tickets needing work after RC2, excluding the About Page. Follow the ticket progress in Trac here.

@ianbelanger informed the group that there are currently 0 tickets in the Bundled Themes component for Twenty Twenty. However, he added that an RC3 release would be helpful.

@audrasjb brought up ticket #48396 regarding @afercia‘s request to revert two lines of CSS to remove an unwanted changes on disabled buttons. @azaozz confirmed the revert to be a minor one and suggested that it move forward based on testing.

A pre-RC3 Bug Scrub in the #core channel was tentatively scheduled for Monday October 28, 2019 15:00 UTC. If there are no new tickets or regressions reported prior, the scrub will not take place.

@sergeybiryukov asked about branching for 5.3 this week. @peterwilsoncc suggested certainly branching before WordCamp US Contributor Day, as to allow for good-first-tickets to be committed for new contributors. @desrosj added that branching could be done at any time now that the dust has settled from RC2, but deferred to @azaozz‘s judgement as Core Tech Lead for 5.3. @azaozz suggested trying to resolve a couple of remaining issues in 5.3 prior to branching in the next few days, and a consensus was reached around this idea.

These notes were taking by @davidbaumwald and proofread by @audrasjb

#5-3, #dev-chat, #summary