Summary, Dev Chat, July 9, 2025

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 @jeffpaul. 🔗 Agenda post.

Highlighted Posts ✨

Forthcoming releases 🚀

WordPress 6.8.2 RC1 Now Available for Testing

The release candidate (RC1) for WordPress 6.8.2 is here! This is your chance to help test and ensure everything runs smoothly before the official release on Tuesday, July 15th. Developers, testers, and contributors are encouraged to get involved — every test helps make WordPress better!

Discussion 💬

Maintenance Mode for Components

The proposal to place under-maintained CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. components into “Maintenance Mode” received broad support. Some contributors found the term unclear and requested transparent roadmaps—especially for components like Bulk Edit, where the future remains uncertain. Frustrations were expressed regarding stalled patches and unclear priorities, highlighting the need for better communication and planning.

Removal of “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. Support” Label for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.3

The “Beta Support” label for PHP 8.3 has been officially removed, reflecting its stable support status.

Raising the Minimum PHP Version to 7.4

WordPress 6.9 plans to raise the minimum required PHP version to 7.4. Although not yet finalized, this is likely as less than 5% of users run older versions. The change aims to improve security, performance, and compatibility while reducing maintenance efforts.

Props to @audrasjb and @jeffpaul for review.

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

WordPress 6.8.2 RC1 is now available

WordPress 6.8.2 Release Candidaterelease candidate One 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). 1 (RC1) is available for testing! Some ways you can help test this minor releaseMinor Release A 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.:

  • Use the WordPress Beta Tester pluginPlugin A 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
    • As this is a minor RCrelease candidate One 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). release, select the Point ReleaseMinor Release A 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. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision..
  • Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ to test: wp core update https://wordpress.org/wordpress-6.8.2-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.8.2 RC1 is a release candidate for a maintenance release with a focus on bugs introduced in WordPress 6.8 and small enhancements or bugfixes. In total, this RC features fixes 20 issues throughout Core and 15 for the Block Editor.

WordPress 6.8.2 is led by @audrasjb@estelaris and @zunaid321.

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets are included:

  • #63399 – Twenty Twenty-Five: editor style isn’t enqueued
  • #14110 – Expose height and width attributes to ‘wp_get_attachment_image_attributes’ filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.
  • #42007 – rpc.pingomatic.com still using HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands.
  • #47595 – Re-evaluate whether comment form should still get the HTML5 novalidate attribute
  • #61941 – Removing app.screencast.com as an oEmbed provider
  • #62995 – Uploading Mac screenshots results in broken images, due to question marks inserted in filenames
  • #63029 – Better align restore revision buttons on mobile devices
  • #63073 – Twenty Twelve: theme’s figcaption styles do not apply in the editor
  • #63254 – Introduce development mode for 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. editor styles
  • #63308 – tinymce cache key should be updated
  • #63324 – Update Twemoji to v16.0.1
  • #63377 – Pin specific 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/ plugin version for E2E tests in 6.6 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".
  • #63390 – Add version number tests for package-lock and composer files.
  • #63424 – Twenty Sixteen: Quote block Plain style has border in the editor
  • #63520 – Twenty Fourteen: Latest Comments block link color does not belong in Content SidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.
  • #63543 – Environment variable WP_CONFIG_PATH should be set on cli container in wordpress-develop env
  • #63564 – Dev environment should incorporate enhancements from wp-env for speed and non-interactive usage
  • #63588 – do_blocks(): Free up transient memory leak
  • #63595 – Cease support for 4.1 – 4.6
  • #63613 – Twenty Twenty-One: menu toggle is not responsive until after “load” event

The following Gutenberg PR are included:

  • #69627 – Navigation Link: Don’t check validity when block editing is disabled
  • #69631 – Navigation Link: Optimize ‘getBlockParentsByBlockName’ selector call
  • #69633 – Navigation Link: Improve performance by only requesting entities when selected
  • #69698 – Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.: Don’t overwrite the ‘query.inherit’ attribute value
  • #69741 – Block Editor: Remove truncation from media tab preview tooltips
  • #69985 – Image: Avoid stale URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org when reselecting the same image from the library
  • #70020 – Post Template: Don’t rely on the default ‘ignore_sticky’ 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/. value
  • #70043 – MediaPlaceholder: Fix Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. with media URL input type to allow a local URL path
  • #70051 – DOM: Add summary element to focusable elements
  • #70054 – Button: Limit scope of width style for link
  • #68741 – Details: Enable all non-interactive formats
  • #70056 – Details Block: Fix keyboard accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issues and allow list view selection to show up inner blocks
  • #70078 – URL: Handle HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. entities and ampersand in ‘cleanForSlug’
  • #70480 – Remove screencast.com embed block variation
  • #70553 – Fix Floating UIUI User interface packages dependencies

What’s next?

Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 6.8 branch.

The final release is expected on Tuesday, July 15, 2025. This date is subject to change if any issues with RC1 are discovered. Coordination will happen in the WordPress.orgWordPress.org The 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/ 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/. #6-8-release-leads channel, and releases are always packaged and tested in #core.

A special thanks to everyone who reported issues, helped test, and helped create patches. The success of 6.8.2 depends on proper testing, so please lend a helping hand.

Thanks to @audrasjb, @zunaid321, @wildworks and @tacoverdo for pre-publication review.

#6-8, #6-8-x, #minor-releases, #releases

Summary, Dev Chat, July 2, 2025

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 @audrasjb. 🔗 Agenda post.

Announcements 📢

Forthcoming releases 🚀

Discussion 💬

PHPStan Code Quality Improvements

Over 15 small pull requests have been submitted under #63268, addressing code quality issues revealed by PHPStan. While a few contributors have been handling most of the reviews and commits, additional committers are invited to help reduce the workload. Coordination has so far been informal, with contributors commenting on tickets and pull requests to avoid overlap.

PHPUnit Test Suite Updates

Ongoing work on #53010 (namespacing test classes) and #62004 (updating for PHPUnit 10–12 compatibility) aims to modernize the test suite. These tasks are considered related to the ongoing PHPStan efforts. A suggestion was made to form a dedicated team to accelerate progress, though the main blockerblocker A bug which is so severe that it blocks a release. remains limited commit time and unresolved technical feedback.

PHPStan Integration into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

A proposal is in progress to formally integrate PHPStan into the Core test suite. Current efforts are manual and patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.-based. The upcoming proposal will aim to provide a sustainable and automated approach for ongoing code analysis.

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 Privacy Tools and Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. Consideration

#43738 suggests extending personal data export/delete tools to support networknetwork (versus site, blog)-wide functionality. Discussion focused on whether the scope of the enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. justifies building a feature plugin. While the feature could be useful for multisite operators, it was noted that it does not address a critical GDPR requirement and may not meet the criteria for core inclusion. Prototyping the feature as a pluginPlugin A 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 was recommended to assess usage and value.

Handling of .git-blame-ignore-revs

The .git-blame-ignore-revs file, used to exclude formatting-only commits from blame output, was discussed. While a few entries have been added manually, the file is not systematically maintained. Suggestions were made to either update it regularly or de-prioritize it due to limited practical impact.

Props to @audrasjb for review.

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

Dev Chat Agenda – July 2, 2025

The next WordPress Developers Chat will take place on Wednesday, July 2, 2025, at 15:00 UTC in the core channel on Make WordPress Slack.

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 ticketticket Created 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.

Announcements 📢

Highlighted Post

Proposal: Clarifying Core’s Database Support Policy

Forthcoming releases 🚀

WordPress 6.8.2 is underway.

Discussions 💬

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

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.

#6-8, #agenda, #dev-chat, #wceu-25

Summary, Dev Chat, June 25, 2025

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 @francina. 🔗 Agenda post.

Announcements 📢

Forthcoming releases 🚀

Discussion 💬

CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.: Bugfixes Only

The Customizer is no longer under active development. New feature requests will not be considered, though bugfixes are still welcome to ensure compatibility. A manual review of the 78 open tickets is planned—no automatic closures. A proposal to introduce an official “maintenance mode” for legacy components (e.g., Customizer, Widgets, TinyMCE) is in the works.

Unicode Email Addresses Patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.

A patch enabling support for Unicode email addresses was introduced and is under review. Initial feedback is positive. Targeted for WordPress 6.9, not for 6.8.x minor releases.

Custom Error Handling Revisited

The long-standing ticketticket Created for both bug reports and feature development on the bug tracker. on registering custom error and exception handlers (#59282) was brought back into focus. Progress is stalled but will be revisited for a future release.

Improving FSE PluginPlugin A 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 Discoverability

A suggestion to improve the visibility of Full Site Editing (FSE) plugins was raised. The idea needs clearer definition—whether it’s a metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. issue or an initiative for contributors remains open.

Next Bug Scrubs: June 26 and June 30

  • A 6.8.2 bugbug A 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 is scheduled for Thursday, June 25 at 3 PM GMT.
  • A bug scrub is scheduled for Monday, June 30 at 3 PM GMT to help triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and manage open tickets.

Props to @audrasjb for review.

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

Dev Chat Agenda – June 25, 2025

The next WordPress Developers Chat will take place on Wednesday June 25, 2025 at 15:00 UTC in the core channel on Make WordPress Slack.

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 ticketticket Created 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.

Announcements 📢

None for this week

Forthcoming releases 🚀

WordPress 6.8.2 is underway.

Discussions 💬

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

  • Brainstorming suggested by @paaljoachim “The Full Site Editor is fairly new and there are naturally features that could be improved. It would be great with an overview of current FSE plugins that aim to improve what we have today. I find it difficult to locate external FSE plugins. How can be make FSE plugins more visible in the repo?
    This could perhaps also be extended to walk through the current 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/ pluginPlugin A 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 -> experiments and where these currently are at in their development phase.”

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.

#6-8, #agenda, #dev-chat, #wceu-25

Summary, Dev Chat, June 18, 2025

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 @audrasjb. 🔗 Agenda post.

Announcements 📢

Forthcoming releases 🚀

WordPress 6.8.2 and beyond

A release squad was announced for 6.8.2: @audrasjb@estelaris and @zunaid321 will lead this version. The detailed 6.8.2 schedule is available.

Discussion 💬

Discussion on Old Dependencies

#47218 (Update TinyMCE to 5.x or 6.x) and #48277 (Update plupload library) were discussed due to frequent security audit flags. While the plupload ticketticket Created for both bug reports and feature development on the bug tracker. is closed as WordPress already the last license-compatible version, updating TinyMCE is technically very difficult. Instead, better documentation explaining the current status and reasons for keeping older versions (and how the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team ensures their security) is planned, for example as a page in the developer handbook.

PHPStan Integration in Core Development

#61175 covers how to handle PHPStan errors in the core development process. The team is deciding which errors to ignore, baseline, or fix. Help with fixing these errors is welcomed.

Errors from Direct File Execution

#62722 (Fix all ABSPATH direct access errors) and #63316 address warnings caused by direct file execution. Some think this should be handled at the server level, but it was suggested to review and fix security-relevant cases individually.

Improving Testing Processes

The need to revive structured user testing and better use of 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. plugins was discussed. The goal is closer collaboration between Core and Test teams to improve test quality and timing. Ideas include live usability tests at WordCamps and providing easy testing environments like Playgrounds.

Props to @audrasjb for review.

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

Dev Chat Agenda – June 18, 2025

The next WordPress Developers Chat will take place on Wednesday June 18, 2025 at 15:00 UTC in the core channel on Make WordPress Slack.

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 ticketticket Created 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.

Forthcoming releases 🚀

WordPress 6.8.2 and beyond

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core 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:
  • Mentioned by @justlevine:
    • Concerning  #61175 (Integrate PHPStan into the core development workflow): “We still to have a serious look at what PHPPHP The 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 conflictconflict A 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 Support A 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”.
  • @sirlouen mentioned: as per Monday’s bugbug A 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 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. pluginPlugin A 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.

#6-8, #6-8-2-2, #agenda, #dev-chat, #wceu-25

WordPress 6.8.2 Release Schedule

Since WordPress 6.8 on April 2025, contributors have kept a close eye on incoming reports to the WordPress.orgWordPress.org The 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, TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and the 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/ repository on 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 be the repository owner. https://github.com/. There are currently a handful of tickets planned for 6.8.2.

Release squad

WordPress 6.8.2 is led by @audrasjb, @estelaris and @zunaid321.

Schedule

Date/TimeEvent
June 19, 2025 at 15:00 UTCBug scrub by @audrasjb
June 21, 2025 at 15:00 UTCBug scrub by @zunaid321
June 26, 2025 at 13:00 UTCBug scrub by @audrasjb
Milestone 6.8.3 will be opened
July 3, 2025 at 15:00 UTCBug scrub by @audrasjb
July 5, 2025 at 15:00 UTCBug scrub by @zunaid321
July 8, 2025 at 15:00 UTCWordPress 6.8.2 RC1
July 15, 2025 at 15:00 UTCWordPress 6.8.2 Final Release

Specific times for RCrelease candidate One 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 ticketticket Created for both bug reports and feature development on the bug tracker. has high priority:

When writing this post, there were also 16 tickets in the 6.8.2 milestone and 15 Gutenberg PR marked as “Backport to WP minor Release”. These are the main goal for this version.

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 Release A 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.

Props to @wildworks, @estelaris and @zunaid321 for assistance with this post.

#6-8, #6-8-x, #minor-releases

Summary, Dev Chat, June 11, 2025

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 @francina. 🔗 Agenda post.

Announcements 📢

WordCampWordCamp WordCamps 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 2025 Recap

Missed WordCamp Europe? No worries — catch up with a recap by @benjamin_zekavica and see here what happened at this year’s event.

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/ Release posts are online

Thank you @luminuu and @cbravobernal for your great work! 🥳

AI Team – First Team Chat

The first AI Team chat takes place tomorrow at 16:00 UTC in #core-ai. Open to all – a great opportunity to learn more about ongoing projects, ask questions, and connect with the team.

Forthcoming releases 🚀

WordPress 6.8.2 and beyond

The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 should be announced soon. Follow #6-8-release-leads for updates.

Discussion 💬

Discussion on Ticketticket Created for both bug reports and feature development on the bug tracker. #49442 (parse_blocks() Filter)

Ticket #49442, which proposes adding a filter to the result of parse_blocks(), is currently assigned to the 6.9 milestone. During the discussion, it was noted that the ticket still lacks test coverage (needs-test-info).

Creating a minimal test case was suggested to help move the ticket forward. It was also recommended to raise the topic in the Gutenberg repository for broader feedback and discussion.

Open Floor 🎙️

Improvements to the Docker Environment

@westonruter is working on several enhancements to the built-in Docker environment for wordpress-develop. The goal is to address various minor issues and “paper cuts” encountered during development. The first pull request with initial changes is ready for review, with more substantial improvements to follow in separate PRs. Feedback and reviews are welcomed to help improve the development environment for everyone involved.

PHPStan Code Quality

@justlevine has submitted several small pull requests aimed at improving code quality using PHPStan for version 6.9. The PRs are intentionally kept small to minimize conflicts and speed up integration. Support from reviewers and committers is appreciated to help keep the codebase cleaner and more maintainable. See #63268

Props to @francina and @audrasjb for review.

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