Agenda, Dev Chat, Wednesday July 10, 2024

The next WordPress Developers Chat will take place on  Wednesday July 10, 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.6 RC3 was released on July 9. We are in a hard string freeze. Note that the dev-feedback and dev-reviewed workflow is required prior to committing to the 6.6 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". (handbook reference).

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 currently in the WordPress 6.6 release cycle. The WordPress 6.6 is scheduled for Tuesday, July 16. There will be a dry run of the release on Monday, July 15 which starts a 24-hour code freeze of the 6.6 branch.

Next maintenance release

No maintenance releases are currently being planned. We will take time to discuss any important tickets that may require a maintenance release.

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.8

Gutenberg 18.8 is scheduled for July 17 and will include these issues. This version will NOT be included in the WordPress 6.6 release and will be included with 6.7.


As we’re at the end of the 6.6 release cycle, we’ll prioritize any items for this release. Please review the Editor Updates section of this agenda for a list of updates on several key features related to this release.

  • Review status of any outstanding issues (if applicable)
  • Coordination of the release post (@marybaum)

Please suggest other important topics for the agenda in the comments of this post.

Highlighted Posts

Editor updates

You can keep up to date with the major Editor features that are currently in progress by viewing these Iteration issues.

Props to @annezazu for putting together these updates each week.

  • Canonical blocks: there’s a latest update from some folks working to explore the idea. TLDR: work on a few requested blocks but put these blocks behind an opt-in feature flag in the GB 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 to allow for quickly iterating and experimenting.
  • The propotype for the DataForm APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. has landed in the plugin. It renders the Duplicate action modal for pages and follow-up work includes replacing other action modals until the pieces are in place to create a details panel for a post type.
  • Data Views: landed the first version of posts list as a Gutenberg experiment and a new tracking issue has been opened around what’s next, design wise.
  • Font Library: a PR is underway to group fonts by source to better distinguish what might be installed by a theme vs a user and a new PR building on a prior effort is in process to add a font size preset UIUI User interface to allow users to edit the font size presets using the editor.
  • Inserter: A PR landed to Remove the dialog behaviour, meaning the Inserter now remains open to match how all the other panels work.
  • Interactivity API: new iteration issue has been shared Interactivity API iteration for WordPress 6.7. TLDR: work will begin on the Gallery 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. lightbox and the Query block’s Instant Search along with internal improvements to ensure that the Interactivity API’s code is as simple and stable as possible.
  • Styles: a PR is underway to Create new public function to make it easier to expose style variations from other themes. This work would help create the foundation to import variations from other themes. Separately, another PR is underway to Add colors and typograpghy to the browse styles section to the browse style panel for improved consistency.
  • Writing Experience: New tracking issue for Writing and Editing Flow / Block Editor Core Polish.

Tickets for assistance

Tickets for 6.6 will be prioritized.

Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting if there are any questions or you will be async.

Open floor

Items for this can be shared in the comments.

Props to @annezazu for reviewing.

#6-6, #agenda, #dev-chat