Summary, Dev Chat, November 29, 2023

Notes from the weekly WordPress developers chat which took place on Wednesday, November 29, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

  • Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at
  • Props to @hellofromtonya for facilitating the live meeting and @webcommsat for preparing the agenda used.
  • Dev Chat summary from November 27, 2023 – props to @marybaum for facilitating and the summary.
  • If you can help with Dev Chat summaries in future, please raise your hand in the meeting or let a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. know by commenting on this post.


What’s new in Gutenberg 17.1

Gutenberg v17.2.0 Release Candidate 1 is out! Let’s get testing.

Highlighted posts

Summary of the Hallway Hangout on the triage extensibility issue

Hallway Hangout: let’s explore WordPress 6.5 – this will take place on Zoom on Tuesday, January 14, 2024 at 21:00 UTC. All welcome to join, whether it is to listen or participate too. There will be a recording and recap published. The event will be in the form of a free flowing demo/ presentation going through as many 6.5 release priorities as possible. The release has a proposed schedule of March 26, 2024.

No other posts were highlighted during the meeting.

Update from core-editor

This is an experimental new section.

Update on the Core Editor via @annezazu

@annezazu requests some feedback on these topics:

  • please add an emoji (green for good, orange for okay, red for bad) to each point in the slack discussion or comment on this post indicating which topic you are commenting on
  • for anything other than green, feel free to thread a comment in the slack discussion.

Please also add your thoughts to the discussion on the future of the core-editor chat.

Forthcoming release updates

Current WordPress release: 6.4

No issues raised.

Updates on the minor releases

@jorbin: “I have been chatting with a handful of folks to identify a team to lead 6.4.2. Waiting on some responses to DMs, but hope to have a team in place this week. Once that team is in place, the first task will be to identify a time table for the release. As of now, it’s unknown if that will be next month or the month after. From my scrubbing of TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., I haven’t seen severe enough to make next month a must release time.

“I’ll also add that I am going to be one of the folks leading 6.4.2 and I intend to get some scrubs started next week either way.”

4.x queue:

  • All tickets in the milestone
  • A query of all tickets Awaiting Review that are flagged as 6.4 being the version that introduced the bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority..
  • @hellofromtonya highlighted: Want to help? One way is to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. the tickets in the Awaiting Review query.

Next major WordPress release: 6.5

Are you able to help with future bug scrubs?

A number of early scrubs have been scheduled – Bug scrubs post. The next scrub: December 5, 2023 at 19:00 UTC in the core Slack channel. Can you help with any of the tickets that were discussed at the last bug scrub on November 28, 2023. Some of these tickets require testing. Please add any comments or test results to the actual tickets on Trac.

@chanthaboune thanked those preparing and organizing scrubs, and all involved with discussing tickets.

To help with asynchronous contribution and encourage more people to take part in scrubs, @webcommsat is adding a link to the start of each scrub on the Bug Scrub post.

Tickets or Components help requests

  1. View 6.4 section above for tickets being discussed at bug scrubs.
  2. @jorbin highlighted that Gutenberg PR 56574 is proposing changing how synced patterns are edited to require users to leave the post editor to edit them. Additional discussion requested.
  3. @afragen: asked if any additional feedback was available on Trac Ticketticket Created for both bug reports and feature development on the bug tracker. #59448?
  4. @afragen re-requested feedback on #58281. Discussion followed on raising awareness to garner additional feedback:
    • Suggestion was made for a call for testing on Make/core blogblog (versus network, site). @afragen highlighted there has been minimal responses during the past two years plus to calls for testing from the Make WordPress posts for Rollback 1/2. Feedback calls also posted in the #core-test channel
    • a Hallway Hangout was suggested if @afragen and @costdev‘s schedule would allow for it. A previous discussion on Slack was highlighted. Running a live session where people can watch it in action, view what needs to be tested, and ask questions could raise greater awareness, testing and feedback. It would enable greater testing for complicated features.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

a) @webcommsat: If any devs familiar with the release are able to work alongside Documentation for reviews on the update to End User docs, you can find the 6.4 HelpHub list in this tracker view.

b) Reminder from last week: Josepha has asked in the Team Reps channel for highlights from the last year. To be inclusive, if you have any item you feel should be included about core’s achievements or items in progress, please add them to the comments on this post for @webcommsat and @hellofromtonya who are preparing the bullet points to send for core.

b) Nominations for Core Team Reps: 2024 edition – reshare of the draft post.
There are discussions on shared voting approach and an embedded voting block. This may not be available in time for the current core elections, and other options discussed in team reps, such as, more teams using the project’s Learn WordPress poll facility for voting rather than a mixture of platforms and personal accounts, and move towards similar processes to especially help new team reps.

– Abha & Tonya: dates to be updated for end of nominations and voting close so the post can be published
– final proof (tweak of previous posts)
– set up of the voting tool and host ready for the election post
– list of what core has achieved this past year to be completed, and the nominations post can link to this to encourage people to stand and support core team as a rep for 2024
– all: please do consider whether you could stand for the core team rep for next year.

Matrix bridge issues raised during the meeting:

  • thanks all for the reports on Matrix bridge.
  • the reports are being tracked at 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.
  • delay in Matrix messages coming through during Dev Chat, and reports of only seeing Matrix messages in Element on macOS, not seeing all the messages that otherwise are likely posted directly to Slack
  • @chanthaboune suggested a testing exercise of the Matrix bridge in a social chat outside of Dev Chat

Props to @afragen for review.