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.
The full chat log is available beginning here on Slack.
Open Floor
@swissspidyshared a previous question from @spacedmonkey, regarding the use of static variables in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. for in-memory caching, and whether the object caching APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. with a non-persistent cache group might be a better alternative. Benefits noted included cache invalidation capabilities and improved testing scenarios. In the original discussion thread:
@flixos90 questioned the practical advantages of cache invalidation for non-persistent caches.
@spacedmonkey clarified it would allow developers to optionally enable persistent caching, improve testability by clearing caches between tests, and align with the intended usage of the object cache API.
@flixos90 agreed that while making these caches persistent could introduce issues, improved testing practices were indeed a valid benefit.
@spacedmonkey also requested feedback on PR #8728, inviting further input from contributors.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
The various curated agenda sections below refer to additional items. 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 or bring them up during the dev chat.
The discussion section of the agenda is for discussing 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. 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.
The following tickets were mentioned by Will Garcia on Slack. They asked whether these tickets are likely to be fixed, since the related dependencies are frequently pointed out as outdated by security compliance audits:
Concerning #61175 (Integrate PHPStan into the core development workflow): “We still to have a serious look at what PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Static Analysis errors we want to ignore (e.g. bc they conflictconflictA conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with WPCSWordPress Community SupportA public benefit corporation and a subsidiary of the WordPress Foundation, established in 2016., should be handled in a follow-up after the tool is merged, etc) vs baselined (enforced on new code, but not justifiable enough on it’s own to the required criteria for a code refactor).” For more info on this topic, see this thread in the #core-coding-standards channel.
Also they pointed out that “there’s some PHPStan Level 0 +1 errors that I need help remediating (if we dont baseline/ignore them in the previous bullet) […] If anyone else is interested in lending a hand here, please chime in on the ticket, in chat, or via DM”.
@sirlouenmentioned: as per Monday’s 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. scrub there are two tickets that need to discussed about errors in Direct Execution of Files. See tickets #62722 and #63316. The discussion should go around if this kind of issues should be covered or is not something of priority for WP.
Finally, @krupajnanda proposed the following: “I’d love to discuss some pointers shared in the recent WCEU Core Committers notes, especially around improving the quality and timing of testing, reviving structured user testing, and making better use of tools like the 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.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. Looking forward to some guidance and input on how test team can align better with the Core team’s needs.”
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.
Since WordPress 6.8 on April 2025, contributors have kept a close eye on incoming reports to the WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Support Forums, TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and the 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/ repository on 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 be the repository owner. https://github.com/. There are currently a handful of tickets planned for 6.8.2.
Specific times for RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). and General release will be announced in the 6.8 Release Leads room and will be based on availability of individuals helping with the release.
Targeted Fixes
One ticketticketCreated for both bug reports and feature development on the bug tracker. has high priority:
WordPress 6.8.2 is intended to be mainly focused on bugfixes introduced in 6.8, but some other bugs may be fixed in this release, depending on how self contained and straightforward the related changes are, and how confident are committers to ship these changes within a minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..
Get Involved with 6.8.2
Bug Scrubs will happen in the #core Slack channel during the times posted above. Everyone is welcome to attend these sessions to help moving milestoned tickets towards a resolution. Each of the open tickets is going to require development work along with testing and review.
You can also run your own scrubs to help ensure that all of the correct tickets are fixed in this release. If you plan to run a 6.8.2 focused scrub, please get in touch with @audrasjb, @zunaid321 or @estelaris so it can be added to the release schedule.
General coordination for the release will happen in the #6-8-release-leads channel and decisions around code for the release will be made in the #core room.
At WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe last week, CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers in attendance (including emeritus) gathered for a brief informal meeting.
