Dev Chat Summary: September 4

@audrasjb was our chat leader today and did an excellent job as usual. (backscroll)


JB shared some posts that are currently open for discussion, feedback, or volunteering.

  • About page design:
  • New feature plugin proposal:

Upcoming Release(s) Update

  • WordPress 5.2.3
    • This is due out today!
    • Right after devchat the plan is to begin the final packaging and release process.
  • WordPress 5.3 has a new batch of focus leads!
    • @miker joined the team as Marketing Focus Lead
    • @ianbelanger joined the team as Default Theme Wrangler
    • @andersnoren joined the team as Default Theme Designer
  • WordPress 5.3 also has an updated timeline posted here:
  • All bug scrubs are listed here: . The next general bug scrub is Sept 5, 2019 at 14:00 UTC in #core channel.

Call for Component Maintainers

  • @azaozz has put up a challenge to his fellow maintainers for 5.3 (and hopefully beyond!)
  • @chanthaboune shared that the maintainers of the default themes are due for a change
    • @ianbelanger and @williampatton raised their hands to help with that transition.
    • @clorith suggested it’s time to have a clearer support plan for working with default themes

Open Floor

  • If anyone is local to the Orlando area, there’s a community event coming up.

Important WP5.3 Dates

  • September 23: Beta 1 (begin writing Dev Notes and About page, and last chance to merge feature projects)
  • September 30: Beta 2 (continue writing Dev Notes and About page)
  • October 7: Beta 3 (continue writing Dev Notes and About page, and soft string freeze)
  • October 15: Release candidate 1 (publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze)
  • October 22: Release candidate 2 (update About page images, and continue drafting release post) (also @audrasjb‘s birthday!)
  • October 29: Release candidate 3 (update About page images, and continue drafting release post)
  • November 5: Release candidate 4 (if needed)
  • November 11: Dry run for release of WordPress 5.3 and 24 hour code freeze.
  • November 12: Release Day!

#devchat #summary #5-2-3 #5-3

Dev Chat Summary: August 14

After the close of our every-two-weeks new contributor chat, the weekly core chat started at 2000 UTC, give or take a few minutes. (backscroll)


Next Minor: 5.2.3

Next Major: 5.3

  • All but two focus lead type people are settled. An update post is upcoming (and will be shared by the end of the week regardless of whether those final two are settled or not).

Open Floor

To Do List from this Chat

  • First 5.2.3 bug scrub Thursday, August 15 @ 1700 UTC
  • If you want to help with the 5.2.3 minor release and weren’t mentioned above, you can indicate your interest in the comments of this post.

#summary #5-2-3 #5-3 #rest-api #auto-update

Dev Chat Summary: August 7, 2019

@chanthaboune led a lively discussion that touched on a variety of things that affect the substance and timing of version 5.3.

@marybaum took notes.


@chanthaboune started off by thanking all the posters who commented on the Backporting Security Fixes post.

Then she pointed the group to a little light reading: a new proposal on how we auto-update old versions.

@chanthaboune‘s third announcement: after much discussion on the implementation of Minimum PHP Versions, a consensus has emerged, so here’s the plan:

Anyone running PHP 5.1.1 through 5.6 will see a warning that they’re on an outdated version and a recommendation to update.

For now, it’ll be just a recommendation and not a forced upgrade, according to maintainers @clorith and @miss_jwo.

Next Major: 5.3


It’s time to weigh in on the target dates. The place to do it is here:

@chanthaboune said final decisions will happen this week on that post.

Default Theme:

Yes, there will be a Twenty Twenty default theme, and it will be in 5.3! The group discussed choosing a theme that’s already doing cool stuff with all the new WP features—and limiting changes to what’s required in a default theme.

@mapk will champion that effort.


@chanthaboune opened the floor to 5.3 questions, and here’s what came up.

@miss_jwo asked how component maintainers can get committers’ eyes on code ahead of time, and @karmatosed suggested triage sessions. With confirmation from @sergeybiryukov, @chanthaboune said there’s a workflow tag for early review.

Josepha also commented that she thinks having a dedicated coordinator for each of the last several releases has worked very well.

@joemcgill suggested naming specialty leads for the release above and beyond the editor and Core leads—for example, a design lead for things like the About page and marketing materials, at a minimum.

@desrosj then commented on the fact that the last two releases have had a designated person coordinating and publishing dev notes. He noted that meant the notes got published sooner than usual, and @marybaum couldn’t resist saying that the sooner they get written, the sooner they get edited for conversation and clarity. Or, as we’re calling it in Core, folksing up the copy, notes and strings. 😜

Ben Matthews asked when we’ll know what the feature-improvement details are, and Angelika Reisiger had a similar question about the scope of 5.3.

@chanthaboune answered that in the past, the docs maintainers aimed for the first beta, with an absolute deadline of the first RC.

@presskopp asked about news from the Triage Team, and whether there will be patches coming in for 5.3. That question led to a round of praise for regular triages and kudos for Design, Gutenberg and WordCamp Meta for using triages extensively.

Here’s a point @desrosj made:

It’s also important to note that while committing may occur as a result of triaging when tickets are just ready, the goal of the triage team is not to commit changes. The goal is to make tickets actionable. That could mean different things for tickets (committing, closing, or unblocking). There are many committers that are not actively trying to triage many tickets.


A final question asked about the status of XML sitemaps in Core. @chanthaboune said she’d been told the feature isn’t likely for 5.3.

Next Minor: 5.2.3

@chanthaboune said she thinks the current 5.3 schedule leaves room for a minor or two if we need it for important fixes. She added that @jeffpaul has started pulling things together for a 5.2.3. He wasn’t in the chat, so look for updates here in this very blog on that subject!

Calls from Component Maintainers

@garrett-eclipse announced a new discussion around consent and logging for user privacy. For info and to weigh in or contribute, here’s the post.

@chanthaboune brought a component need to the group: apparently user docs for the block editor need a champion. @marybaum and @paaljoachim showed interest in helping.

Open Floor

@chanthaboune asked for eyes on ticket #18857, and with that, the devchat hit the one-hour mark.

#2020theme, #5-3, #devchat, #summary

Dev Chat Summary: July 31

This post summarizes the weekly devchat meeting from July 31st, 2019 ( Slack Archive).


@chanthaboune reported that she was recently told what a patient and welcoming group Core is. Kudos to all for being so welcoming!

The following announcements were posted requesting feedback in the last week:

Also, PHP 7.4 has hit the beta stages and is target for public release in late November.

@kadamwhite asked what the most productive way to express support for the proposed plan to raise the minimum PHP version. The fear expressed was that +1 comments would be unproductive noise. @miss_jwo confirmed she was OK with +1 comments.

Upcoming Releases

5.3 Update

@chanthaboune has a few updates that she still needs to post.

However, after reaching out to a few people (and being proactively reached out to by several others), the picture being painted indicates an early November release is feasible. This would mean a post WordCamp US (November 1-3) but pre US Thanksgiving (November 28) timeframe.

Some attendees expressed hesitation to committing to a release date too soon after WCUS. But there seemed to be a sentiment that with enough advance notice and an early enough release candidate (early October at the latest), a date within this general timeline could work. There is currently no new default theme planned for 5.3.


A few people thought that 5.2.3 could still be warranted between now and November. #47797 was raised as a possible ticket (and anything else needed to prepare for a PHP version bump in 5.3) for inclusion in 5.2.3.

Component Maintainers:

The following upcoming meetings were called out by component maintainers in attendance:

  • Media – Thursday, August 1, 2019 @ 13:00UTC
  • REST API – Thursday, August 1, 2019 @ 1800 UTC

@jorbin also called out that now is a great time to make the push for PHP 7.4 compatibility. Getting the 7.4 job to pass in Travis is a good first step.

#dev-chat, #summary #5-3

Dev Chat Summary: July 10

In @chanthaboune‘s scheduled absence, @ianbelanger served as the facilitator for the chat.


@joyously called attention to the recent Make post for feedback regarding the upcoming User & Developer Survey.

Upcoming Releases

Minor Release (5.2.3)

Currently, there are only three tickets milestoned for a potential minor before 5.3.

@audrasjb encouraged a quick decision regarding a 5.2.3 release given the current list of tickets deal with regressions. @desrosj suggested that some block editor features could be backported for a point release.

Major Release (5.3)

Final features and focuses have yet to be determined for the next major release, nor has a final schedule been announced.

Open Floor

@francina mentioned ticket #11302.
@ramiy called attention to ticket #35774.

This summary was drafted by @davidbaumwald and proofread by @sergeybiryukov.

#5-3, #devchat, #summary

Dev Chat Summary: July 3

In @chanthaboune scheduled absence, @davidbaumwald served as the facilitator for the chat.


@desrosj called attention to the Site Health component that was added to WordPress Core earlier this week. Congratulations and many thanks to all involved in the project, and special thanks to the maintainers. If you’d like to learn more, you can read the announcement here. To get involved, join the new Slack channel for Site Health, #core-site-health.

Upcoming Releases

Minor Release (5.2.3)

Currently, there are only three tickets milestoned for a potential minor before 5.3. There was no further discussion or decision making during this week’s chat for 5.2.3.

Major release (5.3)

The schedule and potential features and focuses for 5.3 has yet to be determined. No further discussion was had related to 5.3 during this week’s chat.

Calls from component maintainers

@kadamwhite brought attention to #core-restapi Bug Scrubs being led by @timothyblynjacobs, in the run-up to 5.3. Those who can are invited to participate. Recent scrubs have been happening at 1800 UTC on Tuesdays, and they are usually announced ahead of time on the Make WordPress Core blog.

It was also announced that there will be no formal #core-restapi chat this week.

Finally, @sergeybiryukov called attention to a recent make/hosting post requesting feedback regarding a change in the recommended PHP version for WordPress. If you have additional data or an opinion you’d like to share, please comment on that post.

Open Floor

@pers requested movement on ticket #46197 for potential inclusion in the 5.3 release.

@mikeyarce mentioned ticket #34560, and asked for direction on next steps. @adamsilverstein offered to review the ticket, and will respond there.

Lastly, @justinahinon called attention to the recent creation of ticket #47644.

The next Dev Chat is scheduled for July 10, 2019 20:00 UTC in the #core Slack channel.

These notes were taken by @davidbaumwald and proofread by @sergeybiryukov.

#5-3, #devchat, #summary

Dev Chat Summary: 05 June

@desrosj facilitated a lively discussion with a number of contributors.


@chanthaboune posted earlier today about new material to help Team Leads get going. If you’d like to get started leading WordPress teams, check out her material and feel free to ask questions or leave comments. The link is

Upcoming Releases Discussion

Point release

@audrasjb, co-lead of 5.2.2, outlined some points about the small number of tickets for the milestone. Since more than 60 tickets are committed in trunk/5.3, the release team suggested looking at landing some of those in the minor. The criteria, per the release handbook: tickets need to be self-contained and may not add new functions/files/filters to Core.

As a result, we have made some minor adjustments to the schedule:

  • Release Candidate 1: Monday, June 10, 2019, 8:00 PM GMT
  • Bug scrub: Thursday, June 06, 2019, 5:00 PM GMT
  • Release Candidate 2: Thursday, June 13, 2019, 5:00 PM GMT
  • Final Release: Tuesday, June 18, 2019, 5:00 PM GMT

Major release

@desrosj reminded the group that @chanthaboune is still working on the logistics for the next major.

Got a ticket targeted for the milestone? Watching a few you’re really interested in? The team invites you to keep on scrubbing!

Call from Component Maintainers

Nothing major to say here

Open Floor

The theme review team is looking for a person with management skills to help accomplish goals and keep track of ongoing tasks.

If that interests you, please check this post out:

Some contributors asked for extra attention on these tickets:

#5-3, #5-2-1, #devchat, #summary

Dev Chat Summary: 22 May

@chanthaboune served as the facilitator for discussion and many contributors were in attendance.


Nothing major to announce this week. Tune in next!

5.2.1 Debrief

WordPress 5.2.1 released yesterday! For information on the release you may refer to the 5.2.1 blog post. Thanks to @desrosj and @earnjam for leading such a smooth release. As of now, there are no notable issues. If you are seeing any issues, please discuss in the comments below or create a new ticket at:


There are a handful of tickets in the 5.2.2 milestone. A team is needed to help wrangle those tickets into a new release. Now is the time to volunteer for leading 5.2.2. This release would aim to be for a 2 week release cycle to clear up remaining tickets in the milestone. There were two volunteers to lead in chat today: @audrasjb and @justinahinon. Please volunteer in the comments below if you are also interested in leading or co-leading!

@aduth said there was mention of a few issues in #core-editor chat earlier today of Gutenberg bugs which would be nice to aim to include for the release:

Major release (5.3)

Comments were closed today in the call for 5.3 tickets post. @chanthaboune will be pulling those together the submissions and do some outreach to maintainers that have not included items to the post as we prepare for the next major release. These tickets will inform what focuses this release will have.

Calls from component maintainers

@azaozz, is continuing to plan for some recommended changes and focuses for the Uploads and Media components.

@desrosj reminded us that the following components: General Component, Comments, Pings/Trackbacks, External Libraries, Filesystem API, Rewrite Rules, and Script Loader are all currently without any maintainers. If those parts of core interest you, feel free to reach out to @chanthaboune to get involved!

@karmatosed mentioned that there is an editor component triage on Friday at 17:00 UTC, @desrosj and @karmatosed will be running it in #core-editor and the triage will focus on trac tickets.

@johnbillion asked if there were any component maintainers looking for new maintainers of their components and @chanthaboune made the important reminder, “open source is designed to let people move in and out of volunteer positions as needed” If you are not comfortable saying in dev chat that you would like to make changes, please feel free to reach out privately to @chanthaboune or other co-maintainers.

Open Floor

There was an ask by @afragen to have a committer review He also reminded us committers are not the only ones with valuable feedback. Please direct any thoughts about the issue to the ticket, even if you are not one. 🙂

#5-3, #5-2, #5-2-1, #devchat, #summary

Dev Chat Summary: 15 May

@chanthaboune served as the facilitator for discussion and a bevy of contributors participated.


Make sure to participate in the 5.2 release retrospective!

Gutenberg Developer docs now live in DevHub!

Upcoming Releases Discussion

Point release (5.2.1)

@desrosj has offered to be the leader of this point release, assisted by @earnjam. Many emojis welcomed William to the release lead club.

The 5.2.1 milestone in trac should accurately reflect priorities. Anything not marked as high priority is “puntable”. Currently targeting RC on Thursday or Friday this week with a release on Monday or Tuesday next week.

5.2.2 remains a possibility depending on how thing shake out from 5.2.1, what the schedule for 5.3 looks like, and the tickets that remain open after 5.2.1.

Major release (5.3)

The call for 5.3 tickets is posted. It will remain open through the weekend, so team reps and/or component maintainers will have a little time.

Next week the component maintainers should review the tickets in that thread, and then a date for 5.3 will become the target.

Calls from component maintainers

@azaozz, the maintainer for “Upload” is planning to do a “refresh” there. Mostly dev tickets that can be unblocked and fixed. He’s going to come up with a list and share it.

Open Floor

The question of if it made sense to have New Contributor office hours in #core-editor. This question was largely ignored in favor of talking about open issues, but @jorbin came in at the end to say yes since the more it is easy to contribute, the more contributors there will be.

The number of open issues in the editor component was discussed with issues being somewhat fragmented between the Gutenberg GitHub and trac. @aduth suggested using one of the core-editor scrubs each week to focus on the trac tickets. @karmatosed volunteered to organize such a scrub along with @desrosj. It will take place May 24, 2019 at 17:00 UTC in #core-editor

Along the same lines, the question of how to support the classic editor was brought up. In general, no enhancements will be added to it and bugs should be tracked in trac.

#5-3, #5-2-1, #devchat, #summary