Weekly field notes · 2026-09-08

WordPress Trend Report — 2026-09-08

Weekly human-reviewed analysis of changes across the WordPress ecosystem, covering releases, tools, and developer implications.

Report settings

Weekly Summary

Article Inventory (11 articles)
  1. Join the PHPUnit test cleanup for 7.2 (Make Core) — WordPress core runs ~31,000 PHPUnit tests per commit, and the Build/Test Tools component's goal for the 7.2 release is to cut build time across wordpress-develop by fixing test isolation (restoring state in tear_down()/base testcase rather than special-casing), adding an external-http guard that fails tests hitting the network without being grouped, tightening assertions against documented return types, and splitting large classes into four claimable work tracks (#65893, #63083/#13407, #64895, #65208).
  2. Performance Chat Summary: 8 September 2026 (Make Core) — spacedmonkey shared ongoing query cache improvements (PR #12220, originating from RTC ticket #65487); testing is difficult because the change adds no new functionality, though other query caches already have coverage.
  3. WordPress 7.1 Release Retrospective (Make Core) — WordPress 7.1 ("Mary Lou") has shipped and the core team is soliciting developer feedback on the release cycle's processes, squads, and overall experience via a form or comments by September 30, 2026.
  4. Runnable code examples are now live in the Code Reference (Make Core) — WordPress 7.1 shipped the first two runnable Code Reference examples, powered by WordPress Playground, letting developers click "Run" to execute snippets like WP_HTML_Processor::class_list() directly in their browser.
  5. Replacing Dashicons in the admin bar and menu (Make Core) — A patch replaces Dashicons in the admin bar (and super admin bar) and sidebar with WordPress's wp_get_icon() function (introduced in 7.1), moving from an icon font to SVGs.
  6. WordCamp US 2026: PHP conversation (Make Core) — WordCamp US 2026 contributors discussed WordPress's friction with the broader PHP ecosystem, driven by its long backwards-compatibility window (PHP 7.4+) that outpaces versions most plugins and third-party packages support.
  7. Dev Chat summary: September 2, 2026 (Make Core) — This September 2, 2026 Dev Chat announced a WordPress 7.2 proposal for a Secrets API (still awaiting release squad assignment) and confirmed a published schedule for the WordPress 7.1.1 release.
  8. What’s new in Gutenberg 23.9? (2 September) (Make Core) — Gutenberg 23.9 (released September 2) focuses on block insertion and custom styling quality-of-life improvements.
  9. Dev Chat Agenda – September 2, 2026 (Make Core) — WordPress Dev Chat is scheduled for Wednesday, September 2, 2026 at 15:00 UTC in the core channel on Make WordPress Slack, with a live meeting focused on upcoming releases plus an open floor for ticket assistance and general discussion.
  10. WordPress 7.1.1 Release Schedule (Make Core) — WordPress 7.1.1 is a bug-fix-only maintenance release, with tickets limited to those introduced during the 7.1 cycle or intentionally deferred at its end.
  11. Students Built 108 Websites in Two Weeks in Bangladesh (WordPress.org News) — WordPress Campus Connect delivers free, hands-on WordPress sessions to schools via local volunteers following a shared curriculum, while WordPress Credits places mentored interns in paid-credit roles contributing directly to core WordPress across 38 institutions in 16 countries.

Release planning is the dominant theme this week, appearing across four sources. The core team published a schedule for the bug-fix-only maintenance release WordPress 7.1.1 (RC1 September 10, general release September 17), and separately opened a retrospective process to gather developer feedback on the 7.1 cycle by September 30. Two Dev Chat sessions this week covered upcoming releases and confirmed both items.

WordPress 7.2 development is moving forward with concrete proposals rather than vague direction. The Build/Test Tools component has a stated goal of cutting build time across wordpress-develop for 7.2, and a new Secrets API proposal was announced (still awaiting release squad assignment).

Two technical tracks are ongoing but not yet at decision points:

  • Query cache improvements continue in PR #12220 (originating from RTC ticket #65487), discussed in the September 8 Performance Chat.
  • A migration away from Dashicons toward wp_get_icon() (introduced in 7.1) is being applied to the admin bar and menu, moving from an icon font to SVGs.

Gutenberg 23.9 shipped on September 2 with block-insertion and custom-styling quality-of-life improvements. Separately, WordPress Playground now powers runnable examples in the Code Reference (two live as of 7.1). On a community track, WordPress Campus Connect and Credits are placing mentored interns across 38 institutions in 16 countries to contribute directly to core.

Developer Implications

Release schedule you can act on. If your plugin or theme has bugs introduced during the 7.1 cycle or tied to tickets deferred at its end, WordPress 7.1.1 is bug-fix-only with RC1 on September 10 and general release on September 17. Use those dates to plan a scrub or translation contribution (locales still need strings from 7.1). This is not a feature release; do not expect changes here beyond fixes.

Monitor the 7.2 decisions, but treat them as proposals. The Secrets API proposal and the PHPUnit test-cleanup work are both for 7.2 and neither has an assigned squad or final spec yet. If you build on secrets handling in core, watch the release channel rather than assume a stable API exists. The PHPUnit cleanup targets faster wordpress-develop builds via better test isolation (tear-down state restoration, an external-http guard that fails tests hitting the network without grouping, tighter assertions against documented return types). Expect build times to change once 7.2 work lands; plan CI accordingly rather than expecting current timings to hold.

PHP support is a live friction point. WordCamp US contributors flagged that WordPress's backwards-compatibility window (PHP 7.4+) outpaces what most plugins and third-party packages support. If you are choosing a PHP minimum for new or maintained code, treat this as a compatibility risk worth discussing with clients rather than an afterthought.

Adopt wp_get_icon() where feasible. It shipped in 7.1 and is now being used to replace Dashicons in the admin bar and menu (SVGs instead of an icon font). If you maintain themes or admin-facing code, migrating to wp_get_icon() reduces reliance on a deprecated-style icon system; check whether your build still needs Dashicons loaded.

Feedback deadline for process only. The 7.1 retrospective form closes September 30; submissions are non-anonymous but anonymized in the follow-up summary. This affects core release-process design, not shipped code or plugin compatibility — no action needed on client projects beyond optional input if you want it heard.

Since Last Report

  • New topic: Join the PHPUnit test cleanup for 7.2 (Make Core) — WordPress core runs ~31,000 PHPUnit tests per commit, and the Build/Test Tools component's goal for the 7.2 release is to cut build time across wordpress-develop by fixing test isolation (restoring state in tear_down()/base testcase rather than special-casing), adding an external-http guard that fails tests hitting the network without being grouped, tightening assertions against documented return types, and splitting large classes into four claimable work tracks (#65893, #63083/#13407, #64895, #65208).
  • New topic: Performance Chat Summary: 8 September 2026 (Make Core) — spacedmonkey shared ongoing query cache improvements (PR #12220, originating from RTC ticket #65487); testing is difficult because the change adds no new functionality, though other query caches already have coverage.
  • New topic: WordPress 7.1 Release Retrospective (Make Core) — WordPress 7.1 ("Mary Lou") has shipped and the core team is soliciting developer feedback on the release cycle's processes, squads, and overall experience via a form or comments by September 30, 2026.

What I'm Watching

The patch to replace the Dashicon icon font with SVGs is exciting. It could use more eyes and testing. Be sure to read: Replacing Dashicons in the admin bar and menu and drop your feedback either as a comment on the post, or on the related Trac ticket.

Reader Action Summary

<!-- Human-authored: add up to 4 action items here -->

Source Articles

Make Core

WordPress.org News

Build Notes

  • Articles analyzed: 11
  • Sources: Make Core, WordPress.org News
  • Model: openai-compatible/ornith-1.5-9b
  • Tokens: 11441 prompt + 5668 completion
  • Estimated cost: $0.00 (local model)
  • Review time: ~10 minutes