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.
Welcome to the CoreCoreCore 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 GitHubGitHubGitHub 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 BetaBetaA 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.
REST APIREST APIThe 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
Discussion focused on reviving the inactive MultisitemultisiteUsed 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 repo. References: #40365 and #63885. The goal is to support Networknetwork(versus site, blog)Adminadmin(and super admin) modernization with DataViews. Open questions are whether to proceed directly in Core, through a feature pluginFeature PluginA plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins, or as a canonical pluginPluginA 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party., and how to clearly define benefits and roadmap alignment.
Onboarding with WPCredits
The program brings university students into Core. Discussion centered on improving onboarding by adding better ticketticketCreated for both bug reports and feature development on the bug tracker. filters in TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., gathering structured feedback from new contributors via surveys or Contributor Days, and keeping materials such as the Handbook and Learn courses up to date. Lessons from programs like GSoC and OPW should be incorporated.
Strong Typing in Core
Numerous small tickets on type hints, including #63975, were viewed critically. Consensus was to handle these changes in bulk and support them with tools like PHPStan. Refactoring should only be done when it provides clear value.
