The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
Next major releasemajor releaseA 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
We discussed the plan to release WP 6.7.1 on Thursday, November 21, at 13:30 UTC, according to this schedule.
Next GutenbergGutenbergThe 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/ release: 19.8
The next Gutenberg release will be 19.8, scheduled for December 4.
Discussion
@johnbillion mentioned doing some analysis of how often tickets are bumped from one major release to the next, as there are currently >200 tickets in the 6.8 milestone on Trac. @joemcgill suggested doing a scrub of the existing tickets and moving any that have been bumped more than one release to “Future Release”. We also discussed keeping an eye on how often tickets are bumped during the 6.8 cycle.
Open Floor
We started with a call for volunteers that @bph shared:
From the Developer Blogblog(versus network, site) content board we identified six approved topics that are looking for writers. Check out the issues and if you want to tackle a topic, comment on it. For questions, join us in the #core-dev-blog channel or pingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.”@bph (me) .
@remy mentioned ticketticketCreated for both bug reports and feature development on the bug tracker.#51525, which proposes adding two new functions, apply_filters_single_type() and apply_filters_ref_array_single_type():
we have a separate repo where we are doing the changes and testing them live in our plugins, but we were waiting for feedbacks before merging the changes up to coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.
We discussed that it would be good to look at this soon and consider it for the 6.8 release.
Notice: This week the Dev Chat time will be changing back to 20:00 UTC.
The next WordPress Developers Chat will take place on Wednesday at 20:00 UTC in the core channel on Make WordPress Slack. Please note that this has changed to the original time which is later than the previous Dev Chats during the 6.7 release.
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 below. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda.
Announcements
WordPress 6.7 “Rollins” was released on November 12, 2024. Thank you and congratulations to everyone who participated in this release!
Forthcoming releases
Next major releasemajor releaseA 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
We are currently in the WordPress 6.8 release cycle.
Next maintenance release: 6.7.1
We are discussing releasing 6.7.1 for this week, with @desrosj offering to lead the release.
Next GutenbergGutenbergThe 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/ release: 19.7
The next Gutenberg release will be 19.7, scheduled for November 20. It will include the following issues.
Discussions
The discussion section of the agenda is to provide a place to discuss important topics affecting the upcoming release or larger initiatives that impact the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team.
This week, we can discuss the 6.7.1 maintenance release, including which issues should be included (trac milestone, Editor board) and who is available to help as part of the release squad. It’s worth noting that GB 19.6.3 was released on Nov 18, which may or may not mitigate #62413 (see thread)
If you want to nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.
Block Themes and site editor: Refactoring templates: new overview issue that seeks to “adapt our mental model regarding these theme-provided entities” to solve some long standing problems, like mix and matching templates from different sources.
You can keep up to date with the major Editor features that are currently in progress by viewing these Iteration issues.
Open floor
Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release 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 for discussion or if you will be async.
