WordPress iteration issues get a real update schedule
The Gutenberg repo is changing how iteration issues work: a fresh issue per release, monthly updates before beta, weekly through RC, and a template that asks for scope and blockers up front.
The Gutenberg repo is changing how iteration issues work: a fresh issue per release, monthly updates before beta, weekly through RC, and a template that asks for scope and blockers up front.
@wordpress/build is the tooling Gutenberg already uses internally: esbuild in place of Webpack, entry points discovered by folder, and a generated PHP file that handles enqueueing. It is not ready to replace wp-scripts on an ordinary plugin yet.
WordPress 7.0 has gone back to beta work over real-time collaboration bugs, but it keeps shipping as RC3 and RC4 because version_compare() would reject a beta string. What that means for testing and backports until April 17th.
WordPress 7.0 ships real-time collaboration over HTTP polling, which is fine until traffic picks up. Here is how I swap in a WebSocket transport with Yjs and the sync.providers filter, and what the auth side has to look like.
Notes from the Dev Chat on WordPress 7.0: the AI Client and Connectors API, why the release cycle got extended, the left navigation rethink, and the argument over YouTube support in the Cover block.
WordPress 7.0 brings AI into core through the AI Client and the Abilities API. Here is what wp_ai_client_prompt() actually does, how to test it now, and what the Core AI team will work on during Contributor Day at WordCamp Asia 2026 in Mumbai.
Contributor Day in Mumbai on April 9 overlaps with the WordPress 7.0 release, so the usual morning of setup troubleshooting is not an option. Here is what I get working before the flight, and where an experienced dev is most useful on the day.
WordPress 7.0 slipped a few weeks so the collaboration layer can sit on a custom table instead of transients. What that means for polling load, cache invalidation, and any plugin still using classic metaboxes.
Trac #64393 pushed the 7.0 branch back to RC2, so every trunk commit now needs two committers to sign off and the Polyglots team cannot start yet. Here is what is still allowed on the milestone.
WordPress 7.0 RC2 landed on March 26 and trunk is now 7.1-alpha. What that means for your test environments, the two-committer backport rule, the string freeze, and which tickets still make the 7.0 milestone.