WordPress 5.0 Commit Management

Keeping our focus tight is key to ensuring WordPress 5.0 is released on time, so commit approval will be managed a little differently than usual. During this time, the 5.0 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". will be the working branch, rather than trunk, we can then port 5.0 commits to trunk after WordPress 5.0 is released.

And so, here is the current commit state of each branch:

Trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.

trunk is closed for all commits.

4.9 Branch

The 4.9 branch is closed for all commits.

If the WordPress 5.0 schedule slips until January, PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 7.3 fixes will be ported for a WordPress 4.9.9 release.

5.0 Branch

The 5.0 branch is current open for GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/-related commits.

The 5.0 branch has been created from the 4.9.8 tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.), not the 4.9 branch. Newer Gutenberg-related commits in the 4.9 branch will need to be ported to the 5.0 branch.

Prior to betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1, any Gutenberg-related commits can be added by any committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.. Commits not related to Gutenberg must be approved by me.

After Beta 1, commits must be approved by the relevant release leadRelease Lead The community member ultimately responsible for the Release., or me. After RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1, commits must be approved by the relevant release lead, and me.

All other branches are in their usual closed state, except for security releases, of course.

Thank you, my dear committers, for your cooperation here. We’ll be back to your regularly scheduled committing in short order. 🙂