Agenda, Dev Chat, Wednesday April 3, 2024

The next WordPress Developers Chat will take place on  Wednesday April 3, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.


WordPress 6.5 “Regina” has been released. Thank you to everyone who worked on, tested, and supported this release 🎉.

Forthcoming releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.6

We are officially in the WordPress 6.6 release cycle. @priethor published this WordPress 6.6 Planning Proposal & Call for Volunteers post last week. Please take note of the following callouts on that post:

  • Please leave your feedback about the schedule and release squad size in the comments by April 7th.
  • If you are interested in participating in WordPress 6.6’s release squad as a lead or as a cohort, please show interest in the comments, specifying the role and the type of involvement (lead/cohort).

Next maintenance release: 6.5.1

There is no specific target date for WordPress 6.5.1 yet. However, we can start ensuring that all the correct bugs are targeted for it and that work progresses towards fixing them.

To assist with preparation for 6.5.1, an initial scrub will be held at Thursday, April 4, 2024 at 01:00 PM CDT in the #core slackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at channel.

@jorbin, Initial Bug Scrub for 6.5.1

Next GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. release: 18.1

Gutenberg 18.1 is scheduled for release on April 10 and will include these issues.


This week the discussion will be a follow-up from the WordPress 6.5 release to address any high priority topics that that need to be addressed following the release.

Feel free to suggest additional topics related to this release in the comments.

Highlighted posts

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Updates

Props to @annezazu for putting together these updates.

  • Project managementProviding more clarity in the Gutenberg GitHub Repo recapping some recent efforts to better organize the repo and ensure the high level labels and associated issues folks use to follow work at various scales are as accurate and robust as possible.
  • WordPress 6.6: Check out an early look at what’s on the mind already for 6.6: Block Hooks features for future WP releasesHTML API: Plans for 6.6Interactivity API – Iteration for WP 6.6. Keep in mind that these are meant to act as a container for iterations and will be actively updated as the cycle gets underway. If you want to follow a narrower scope of work for a release, this is the best way to do so.
  • Template extension: Allow extensions to customize the template name in the ‘Add template’ screen to help ease template registration and improve the experience extenders provide to end users when they add a custom template.
  • Styles: Filter out color and typography variations PR is underway, which gives theme authors the ability to create multiple color and typography settings. It does this by filtering out color and typography variations out of the list of style variations so that theme authors can add variations that target only these properties without having to create full variations.
  • Create BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Theme PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party: a community plugin that helps supercharge the Site Editor to create and edit block themes has a few efforts underway including early work to add a theme.json editor and bring creating theme variation to the site editor interface.
  • Design: recent design share has a slightly new format (links to useful design related figma links, issues, etc) to go along with some fresh, in progress designs. This includes the 18 min long walk through of current thinking with the Adminadmin (and super admin) Redesign, thoughts on the UXUX User experience for overrides in synced patterns, improvements to contentOnly experience, and more.
  • Patterns: a draft PR is underway to Merge Patterns & Template parts categories into a single group in the Site Editor > Patterns view allowing for less differentiation and easier access (no longer need to go into “manage all template parts”.  This is done as part of Advancing site editor index views.
  • Design tools: Allow negative values for margin controls has long been requested and is actively being explored in a promising draft PR.

Tickets for assistance

Tickets for 6.6 will be prioritized.
Please include detail of tickets / PR and the links into comments, and if you intend to be available during the meeting if there are any questions or will be async.

Open floor

Items for this can be shared in the comments.

Props to @mikachan for reviewing.

#agenda, #dev-chat