WordPress 5.0 Schedule Updates

Gutenberg 4.2 (release candidate) has just been released, and we’d like to have a WordPress 5.0 Beta including those updates. Additionally, there are a few more known bugs and tasks to complete in WordPress 5.0, before we can tag a Release Candidate. With that in mind, we feel it’d be prudent to allow for some extra beta time in the WordPress 5.0 schedule.

Beta 2: October 29, 2018

  • Beta 2 included fixes to bugs discovered in Beta 1, an update to the latest version of the block editor, and the Twenty Nineteen theme.
  • Gutenberg 4.2 (RC) was released today, October 30.

Beta 3: November 2, 2018

  • Beta 3 will include updates to the block editor from Gutenberg 4.2, as well as required bug fixes.
  • All Core enhancement tickets must be fixed by this date.
  • This will also be the new soft string freeze date.

Beta 4: November 5, 2018

  • Beta 4 will include bug fixes that come up following Gutenberg 4.2, as well as additional fixes from Gutenberg’s WordPress 5.0 milestone.
  • Assess need for additional beta releases prior to Release Candidate 1.

Release Candidate 1: November 12, 2018

  • All Core bug reports should be fixed by RC1. Release-related task tickets can remain open.
  • The WordPress 5.0 milestone should have low impact or low priority issues remaining, which may be moved to WordPress 5.0.1.
  • This will continue to be the hard string freeze date.
  • There will be additional Release Candidate releases, if needed.

WordPress 5.0: November 19, 2018

  • Final release of WordPress 5.0 will include Gutenberg and all necessary bug fixes.

To answer a few immediate questions:

  • Why the shortened RC period? The block editor has been available for over a year. It’s already had a longer testing period, with 30 times the number of sites using it, than any previous WordPress release. The primary purpose of the beta and release candidate periods is to ensure that it’s been correctly merged into Core.
  • Why so many betas? By adding extra betas we can fix and test iteratively, which will result in a well-polished final release. It also lets the faster cadence of Gutenberg releases continue.
  • What will happen to the Gutenberg releases? Over the past six months, there has been a release every two weeks. We’ll plan to continue that over the first few WordPress 5.0.x releases, to ensure that bug fixes are available as quickly as possible.
  • How soon should we expect WordPress 5.0.1? Approximately two weeks after WordPress 5.0, unless we see bug reports that indicate a need for a faster release.