Dev Chat Agenda – September 17, 2025

Announcements 📢

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

The new Core Program Team focuses on how Core’s sub-teams work together. The goal is to make processes simpler, lower barriers for new contributors, and support smoother collaboration—for example through new handbooks or GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ project flows. Everyone’s welcome to get involved.

Help Test WordPress 6.9

@krupa and @psykro are preparing the Help Test WordPress 6.9 post. They’re asking for input on which features need a dedicated testing call, what should be tested early before 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. 1, and which workflows may need extra coverage.

Forthcoming releases 🚀

WordPress 6.9 Timeline

WordPress 6.9 is planned for December 2, 2025, with Beta 1 beginning October 21.

Bug Scrub Schedule

Regular scrubs are already underway, led by @wildworks and @welcher across time zones.
Full details are in the Bug Scrub Schedule for WordPress 6.9.

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. 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.

REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/ Sites Endpoints

@realloc suggests revisiting the inactive wp-api-sites-endpoints repo, originally meant for Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site REST API work, to discuss how this could be restarted as part of modernizing Networknetwork (versus site, blog) Adminadmin (and super admin).

Onboarding with WPCredits

@devmuhib notes that the WPCredits initiative is now used in universities, bringing new contributors into Core. Discussion will look at how to make onboarding simple and effective.

Strong Typing in Core

@SirLouen raises the question of how type hints should be handled in WordPress, since they are being introduced inconsistently. Input is welcome, with ticket #63975 as a reference.

Component Maintainer Request: Post/Post Types

@sirlouen is requesting to join as Component Maintainer for Post/Post Types.

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 indicate whether you intend to be available during the meeting for discussion or will be async.

Thanks to @francina for reviewing this agenda.