Agenda, Dev Chat, Wednesday June 12, 2024

The next WordPress Developers Chat will take place on  Wednesday June 12, 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 Beta 2 was released on June 11. Contributors will now be focused on testing and fixing bugs discovered during betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. testing.

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. WordPress 6.6 Beta 2 was released on Tuesday, June 11. Please continue testing.

Next maintenance release

No maintenance releases are currently being planned.

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

Gutenberg 18.6 is scheduled for June 19 and will include these issues. This version will NOT be included in the WordPress 6.6 release.


As we’re in the middle 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 of several key features related to this release.

Highlighted Posts

Editor updates

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

Props to @annezazu for putting together these updates.

6.6 related updates:

  • Color & style variations: changes were made to this feature in light of the discussion in Allow theme authors to opt out of color and typography preset autogeneration in WordPress 6.6. TLDR: color and typography presets will not be autogenerated from current style variations and instead will need to be intentionally made.
  • Unified publish flows: after a discussion revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. have been returned to a higher level of prominence in the publish flow. Thank you everyone who chimed in.

Outside of 6.6:

  • Phase 3: Data views: Bootstrap Actions Extensibility API has merged to allow third-party developers to register and unregister post type actions, a new issue has been opened for bringing DataViews to Posts, Categories and Tags, and a very basic PR was merged for Posts Dashboard: Add a new experimental empty page. All of this helps move forward opening up data views to third parties and to more places in the WordPress experience, starting as experiments.
  • Phase 3: In line commenting: PR continues to be worked on to bring about an initial experimental feature for in line 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. commenting. This will also be implemented as an experiment in order to get feedback.
  • Phase 3: Media Library: Designs were updated for Phase 3: Collaboration > Media Library and folks are looking to implement an initial experiment.
  • Block bindings: a new issue has been opened to support a better user experience when modifying post metadata.
  • Site Editor: a PR is underway for Feature: Set editor rendering mode by post type which would allow developers to set the default rendering mode of the block editor (show template or not). In the PR a discussion is underway about setting the template lock view as the default for pages for 6.7 and having this as a user setting in a follow up PR that users can override.
  • Styles: a PR is underway to add a Font size presets UI and is ready for broader testing/feedback.

Outside of the above, @annezazu has published the 6.6 source of truth early look. It’s expected things might shift during the beta period but hopefully this helps folks prepare for the release and help educate others on what’s to come.

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 @mikachan for reviewing.

#agenda, #core, #dev-chat