WordPress 7.0 development just hit a turning point. If you follow the trunk branch you have probably noticed the momentum drop off. The latest WordPress 7.0 Release Updates confirm that trunk is closed to 7.1 commits until further notice. The reason is the new real-time collaboration architecture, which the release team wants stable before anything else lands.
Pre-releases are paused while the core team works toward the next Release Candidate (RC). We are also in a hard string freeze, so no UI text changes go in. For developers that is the cue to stop refactoring and start stress-testing.
RTC and the custom sync provider pivot
The awkward part right now is real-time collaboration. The roadmap shifted to finalize a sturdier database table design for RTC, and a new dev note came out on building custom sync providers. WordPress 7.0 ships with a default HTTP polling provider, but a custom implementation can use WebSockets instead.
If you are scaling a site that needs multi-user editing, you will probably end up hooking into this new API. Here is a conceptual look at how a custom sync provider class might be defined in the upcoming release:
<?php
/**
* Conceptual Sync Provider for WordPress 7.0
*/
class bbioon_Custom_Sync_Provider {
public function __construct() {
// Initialize WebSocket or external sync logic
}
public function bbioon_broadcast_change( $data ) {
// Send data to other clients to prevent race conditions
$endpoint = 'https://api.bbioon-example.com/sync';
wp_remote_post( $endpoint, [ 'body' => json_encode( $data ) ] );
}
}
// Register the provider conceptually
add_filter( 'wp_sync_provider', function( $providers ) {
$providers['bbioon_socket'] = 'bbioon_Custom_Sync_Provider';
return $providers;
} );
Triage and good first bugs
With WordCamp Asia Contributor Day coming up, attention is on clearing the good-first-bugs list. Triaging those tickets matters as much as patching them, because plenty of the patches sitting on Trac have gone stale and need a refresh. There are around 8 tickets in the i18n component that are easy wins if you want something on the 7.0 milestone.
If you work on localizations, the Polyglots team is asking for string refinement so the translations in the final release hold up across locales. I wrote up more background on these shifts in my earlier post on branching delays and sign-offs.
If the WordPress 7.0 transition is eating your dev hours, I can take it on. I have been working with WordPress since the 4.x days.
What to do during the freeze
The trunk closure is not worth panicking over. It means the release lead is putting stability ahead of features, the same call the project made when the REST API and Gutenberg first landed. Use the freeze to audit your plugins against the latest Path Forward for 7.0 documentation, and check that your sync logic will not create bottlenecks once the RC arrives.
For the specific API changes, read the Official Sync Provider Dev Note, or go straight to the i18n Trac Tickets.
