What is the main goal of syncing Gutenberg and wordpress-develop?

The goal is to reduce friction by making it easier to merge new features and fixes from the Gutenberg plugin into the stable wordpress-develop repository, improving release cadence and stability.

Why is communication so important among WordPress maintainers?

Clear and early communication prevents breaking workflows, aligns contributor expectations, and increases the quality and quantity of feedback, which is crucial for maintaining Core stability.

How would a Canary-style development model change WordPress releases?

It would introduce an early-release channel with experimental features enabled, allowing faster iteration and feedback but requiring new infrastructure for feature management, testing, and user segmentation.

Is it safe to enable experimental features on live WordPress sites?

Generally, no. Without rollback mechanisms and thorough testing, experimental features can cause instability. Use dedicated staging sites and backups before enabling such features.

What can I do to help improve WordPress Core testing?

Participate in beta and release candidate testing by using tools like the Beta Tester plugin, reporting bugs, and providing feedback to the Core team. Advocating for merging beta testing into Core may increase participation.

Beta Testing

Core

Core Committers Convene at WordCamp Europe 2026: Key Discussions and Future Directions

At WordCamp Europe 2026, WordPress Core committers gathered to discuss syncing challenges between Core and Gutenberg code bases, communication improvements, a proposal for Canary-style development, and strategies to boost beta testing participation. These discussions reveal deep operational issues impacting WordPress release velocity and stability, with implications for developers, agencies, hosts, and site operators.

Jun 16, 2026 · 6 min read