Two years ago, efforts were made to provide more clarity in the Gutenberg GitHub repository to make it simpler to keep up to date with work underway at various levels. This post focuses on a piece of that effort: iteration issues and the growing role they can play to make it simpler to follow ongoing…

WordPressCore's platform is a central hub for WordPress developers and contributors, offering insights into WordPress core development, plugin development, and theme customization. Through articles, tutorials, and community forums, WordPressCore offers insights into WordPress architecture, development best practices, and contributing to the WordPress open-source project. Readers can learn about WordPress coding standards, security guidelines, and performance optimization techniques to build powerful and secure websites with WordPress.

Make WordPress Core

WordPress Core is formalizing expectations for Iteration issues in the Gutenberg GitHub repository to improve transparency and reduce fragmentation during release cycles. Key changes include opening a new iteration issue per release with the [Type] Iteration label, requiring monthly updates before beta and weekly updates during beta/RC periods, and closing issues when release work is complete. A new iteration issue template has been introduced to guide contributors. Good iteration issues should include assigned contributors, a scoped work plan, design input, open questions, and regular progress updates that go beyond simple changelogs to convey release readiness.

Defining expectations for Iteration issues

When should an iteration issue be opened?