Summary, Dev Chat, December 18, 2024

This meeting was the final Dev Chat for 2024.

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., facilitated by @mikachan. 🔗 Agenda post.

Announcements

The Nominations for 2025’s Core Team Reps are now open! Please nominate people in the comments of that post. Self-nominations are welcome. The deadline is January 31, 2025.

Also, 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. https://wordpress.org/gutenberg/ 19.9 was released prior to the start of the meeting. See, What’s new in Gutenberg 19.9?

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

The WordPress 6.8 call for volunteers closed on Dec 6. There will be more information about the release squad to follow soon based on these volunteers.

Next maintenance release: 6.7.2

There is currently no release date planned for WordPress 6.7.2. You can review the next minor release milestone. The 6.7.2 milestone was scrubbed during the week and the Gutenberg board is scrubbed with only a few PRs that need to be merged.

Discussion

There were no discussion topics for this meeting.

Open Floor

@luminuu raised the following on the agenda post:

how much work would it be to allow pseudo-styles on 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. style variations, for example on buttons? Talking about this issue: https://github.com/WordPress/gutenberg/issues/55359

@mikachan noted a similar issue being worked on for the stylebook: https://github.com/WordPress/gutenberg/issues/38277.

#6-8, #core, #dev-chat, #summary