Accessibility Focused Bug Scrub – 15 May 2025

In celebration of Global Accessibility Awareness Day, a scrub of stagnant Accessibility focused tickets will be held in the #core slack channel at Thursday, May 15, 2025 at 15:30 UTC. The goal of this scrub is to help move tickets towards a resolution (which may include being added to a future milestone or closing).

If you’ve never participated in a 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, reading the documentation on leading a bug scrub will help you understand what to expect!

Thanks to @joedolson for pre-publication review

#accessibility, #bug-scrub, #core-accessibility

Dev Chat Agenda – May 14, 2025

The next WordPress Developers Chat will take place on Wednesday May 14, 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 📢

  • In case you missed it, A Month in Core – April 2025 is out.
  • ETA: Gutenberg 20.8 is out! Tentative: 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/ 20.8 might be released in time for the dev chat. An update will be given.

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.

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.

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.

Summary, Dev Chat, May 7, 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 📢

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 need to set up a release squad, a plan/scope and a schedule for 6.8.2 (and beyond)

Forthcoming releases 🚀

Call for 6.8.x release leads

@michelleames and @jeffpaul published a Call for 6.8.x Release Managers. Anyone interested to lead a 6.8.x release can drop a comment in this P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post.

Discussion 💬

CSSCSS Cascading Style Sheets. Regressions in 6.8

@luminuu reported regressions in several third-party plugins caused by bugfixes introduced in WordPress 6.8 (PR #64770). Affected projects include Jetpack and WooCommerce. One key issue—buttons stretching full width—was tracked in Trac ticket #63373 and is scheduled to be fixed in version 6.8.2.

The group discussed how to prevent similar issues in the future. Suggestions included:

  • Introducing a Dev Notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. format to track frontend CSS changes per release
  • Improving visibility of such changes before they ship
  • Investing in visual 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. testing
  • Collecting and surfacing CSS-related changes in “What’s new in 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/?” posts

Better communication, testing, and transparency are needed to reduce the risk of regressions in future releases.

Thanks to @audrasjb for proofreading this post.

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

Performance Chat Summary: 6 May 2025

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter asked if any performance-related fixes were included in the WordPress 6.8.1 release.
    • @b1ink0 confirmed that the update focused primarily on general 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. fixes across WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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, with no specific performance items.
  • @westonruter noted that he has some pending PRs to review and merge.

Performance Lab 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 (and other performance plugins)

  • @flixos90 has started work on the new View Transitions feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. (see issue #1997). The work is being tracked through a series of iterative PRs, starting with theme support and dynamic transition name handling. It builds on the experimental Core PR wordpress-develop#8370 and will include a UIUI User interface for customizing transitions.
    • @flixos90 plans to work on the next PRs later this week, with most work focused on porting the experimental code into plugin shape.
    • When asked if the plugin would be considered stable or experimental upon release by @mukesh27, @flixos90 noted that it depends on the final feature set and the team’s evaluation at that time.
  • @mukesh27 briefly noted progress on Accurate Sizes (part of the Auto Sizes plugin) and will share a more detailed update later this week.

Our next chat will be held on Tuesday, May 20, 2025 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Dev Chat Agenda – May 7, 2025

The next WordPress Developers Chat will take place on Wednesday May 7, 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.

Additional items will be referred to in the various curated agenda sections below. 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.

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 need to set up a release squad, a plan/scope and a schedule for 6.8.2 (and beyond)

Highlighted posts ✨

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

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.

X-post: A Month in Core – April 2025

X-comment from +make.wordpress.org/updates: Comment on A Month in Core – April 2025

Summary, Dev Chat, Apr 30, 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 📢

WordPress 6.8.1 is now available 🥳

WordPress 6.8.1 was released right after the dev chat. It is a maintenance release.

For now, 6.8 is identified as the last major release of the year.

Forthcoming releases 🚀

WordPress 6.8.2

There are currently 7 tickets in the 6.8.2 milestone on Trac. Bugfixes currently located in milestone 6.9 can probably start to be moved to 6.8.x milestones, but 6.8.2 will most probably still be focused on remaining issues/regressions found on 6.8.

Call for 6.8.x release leads

@michelleames and @jeffpaul published a Call for 6.8.x Release Managers. Anyone interested to lead a 6.8.x release can drop a comment in this P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post.

Discussion 💬

@sirlouen wanted to bring attention to this ticketticket Created for both bug reports and feature development on the bug tracker.: #43936. He commented this ticket with a recap of everything that must be known if someone doesn’t want to read all the way through. @audrasjb pointed out that this ticket is a good candidate for a further 6.8.x release, as the 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. shouldn’t add any new file.

@sirlouen pointed out that publishing a call for dev chats topics should ideally be posted on the Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Slack channel, ideally 2 days before each meeting to help gather topics for the agenda. @audrasjb proposed to post such a call on next Monday and to iterate on this process.

@sirlouen added another topic coming from the Core Test Team: “I’m writing a guide on creating Testing Use-Cases for core developers. The thing is that I’ve found over the period of ~100 ticket reviews, that most old stuck tickets with patches that have been pretty much abandoned, the main cause is that the patch creator did not provide enough information to test and help patch progress (even sometimes other reviewers asked for it). I’ve been ideating some examples and ideas, to help people build testing cases, and I’m going to publish this in the Test WP blogblog (versus network, site).” He is looking for people able and willing to review his proposal. @audrasjb volunteered.

@justlevine proposed to discuss the following ticket: #62622: Bump minimum PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version to 7.4.
This ticket is on @johnbillion‘s radar. Everyone agreed that this ticket is a major goal for 6.9.

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

Summary, Dev Chat, Apr 23, 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 🚀

WordPress 6.8.1

@jorbin is leading WP 6.8.1 which is scheduled for Wednesday April, 30, after the dev chat.

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/ 20.7

Gutenberg 20.7 was released on Tuesday April, 22.

Discussion 💬

@mamaduka and @karmatosed are planning to start working on the backlog management in the Gutenberg repository. The plan is to close non-actionable issues/tickets and stale PRs. This was mentioned during the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers call and they just trying to get things moving at this moment. They will try to publish a more detailed announcement once the path is clear.

@sirlouen reported that the 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. between the needs-testing and needs-testing-info keywords in search results on WordPress Core TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. (Ticketticket Created for both bug reports and feature development on the bug tracker. 7935) was about to be resolved by the next #core-test team meeting.

@justlevine is looking for discussion and assistance to move forward with the following tickets:

  • #49442: a parse_blocks 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., so we can stop dumping parsing functionality on render_blocks
  • #61175: Implementing PHPStan in core, which was recently discussed

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

Dev Chat Agenda – April 30, 2025

The next WordPress Developers Chat will take place on Wednesday April 30, 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.

Additional items will be referred to in the various curated agenda sections below. 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.

Forthcoming releases 🚀

WordPress 6.8.1 and 6.8.2

  • WordPress 6.8.1 final release is scheduled on Wednesday April, 30
  • The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team will then set up a plan for 6.8.2

Highlighted posts ✨

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

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.

WordPress 6.8.1 RC1 is now available

WordPress 6.8.1 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release:

  • 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 Release channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • 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.1-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.8.1 RC1 is a 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). for a maintenance release with a focus on bugs introduced in WordPress 6.8. In total, this RC features fixes for 15 bugs throughout Core and the Block Editor.

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

  • #62718 Automatic updater of WordPress always fails if FS_METHOD is ftpext since 6.6 with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.0+
  • #63005 Replacing certain bulk-edit fields blocks all bulk edits
  • #63269 Duplicate array key `Code` in `_WP_Editors::get_translation()`
  • #63285 Call to undefined function is_super_admin() in /wp-includes/ms-files.php
  • #63287 Unexpected output from apply_block_hooks_to_content_from_post_object
  • #63302 SVG images can’t be uploaded anymore due to a resizing issue
  • #63307 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/.: Returns incorrect post when querying by slug if sticky posts exist
  • #63323 Reduce copy from 6.8 about page
  • #63339 WordPress 6.8 REST API returns all sticky posts regardless of per_page setting
  • #63358 Adminadmin (and super admin) Bar: Restore the Edit Site link to its previous link (link to templates)
  • GB-69958 Use split view for 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. boxes only when canvas is iframed and “Desktop” view
  • GB-70006 Fix ‘wp-polyfill’ script dependents unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression.
  • GB-70001 Author, Author Name 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.: fix PHP warning error when there is no context
  • GB-69998 Keyboard Shortcuts: Revert delete shortcut to access + z 
  • GB-70000 ToggleGroupControl: Fix active background for empty string value

What’s next?

Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 6.8 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"..

The final release is expected on Wednesday, April 30, 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.1 depends on proper testing, so please lend a helping hand.

Thanks to @desrosj and @presskopp for pre-publication review.

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