Proposed WordPress 5.0 Scope and Schedule

WordPress 5.0 will be focussed on merging the 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/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party into 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.. In addition, there are two related areas of new development:

  • Updating the default themes to work well with the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor, and creating the new Twenty Nineteen theme.
  • Creating an upgrade experience to remove the Gutenberg plugin and offer the Classic Editor plugin.

Given the scope of this change, there won’t be any extra feature focusses. In order to ensure that we can keep the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. schedule, minor changes, and bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes will only be included on a case-by-case basis.

Here is the proposed release schedule for WordPress 5.0:

WordPress 5.0 Kickoff meeting: October 3, 2018 (Today! Now!)

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: October 19, 2018

RC 1: October 30, 2018

Release: November 19, 2018

We know there is a chance that 5.0 will need additional time, so these dates can slip by up to 8 days if needed. If additional time beyond that is required, we will instead aim for the following dates:

Secondary RC 1: January 8, 2019

Secondary Release: January 22, 2019

Should we need to switch to the secondary dates, this will be communicated as soon as we’re aware. It’s also important to note that we have some updates for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 7.3 compatibility that must be released in 2018 regardless, and we would have a short 4.9.9 release cycle for them if needed.

I expect the WordPress 5.1 release will be available around March 2019, allowing features outside of the block editor to be launched then.

#5-0