Title: WordPress 5.9 Revised Release Schedule
Author: Tonya Mork
Published: November 22, 2021
Last modified: November 23, 2021

---

 [  ](https://profiles.wordpress.org/hellofromtonya/) [Tonya Mork](https://profiles.wordpress.org/hellofromtonya/)
11:02 pm _on_ November 22, 2021     
Tags: [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/)

# WordPress 5.9 Revised Release Schedule

A [revised release schedule](https://make.wordpress.org/core/5-9/) for WordPress
5.9 is available, with the final release planned for 25 January 2022.

## **Why the delay?**

Near the end of the original alpha release cycle, [issues arose](https://github.com/WordPress/gutenberg/issues/36556)
that related to multiple major features planned for the 5.9 release, including:

 * Full Site Editing (FSE), which is a collection of features, such as global styles
   interface, Navigation 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., block themes, template editors, and site
   editing flows.
 * The Twenty Twenty-Two (TT2) theme, which depends on these FSE features.

The 6.0 release isn’t due until April 2022—too long for the community to wait for
them. After processing this[ list of issues](http://github.com/WordPress/gutenberg/issues/36556),
CoreCore Core is the set of software required to run WordPress. The Core Development
Team builds WordPress. Editor team saw the features could ship in 5.9 with the revised
schedule. 

This decision, to delay the 5.9 release, was not made lightly. The following section
shares the decision-making process.

### **The decision-making process**

Careful, thoughtful, open discussions happened in the[ release squad channel](https://wordpress.slack.com/archives/C02JUSF02TT/p1637077431164600),
that considered  options and impacts:

 * Move the specific pieces needing fixing to 6.0.
 * Move the fixes to a 5.9 minor releaseMinor Release A set of releases or versions
   having the same minor version number may be collectively referred to as .x , 
   for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other
   versions in the 5.2 (five dot two) branch of that software. Minor Releases often
   make improvements to existing features and functionality..
 * Move the fixes to 6.0.
 * Move these major features to 6.0.
 * Delay 5.9 to include fixes.

As the FSE features are very closely intertwined, removing some of its pieces would
risk making the release unstable. To avoid delivering a sub-optimal experience, 
moving fixes to a 5.9 minor or 6.0 was ruled out.

It came down to a choice between:

 * Option 1: Remove these major features from 5.9 to target shipping in 6.0 in April
   2022.
 * Option 2: Delay the release to ship the promised major features in 5.9 in January
   2022.

After consulting with advisors from previous release squads and the Core Editor 
team, based on the current information available, the release squad determined shipping
these major features sooner rather than later would have more benefits and less 
impact.

The release squad respects that the community has expectations and plans for these
features. The extra time in the new schedule will help everyone involved deliver
the 5.9 features the community has been waiting for.

### **Seasonal considerations**

The 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. and 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)](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/?output_format=md#alpha-beta).
release cycles have two jobs: to get the community involved in testing and delivering
feedback, and to give contributors a block of time to fix identified issues before
the final release.

The third major releasemajor release A release, identified by the first two numbers(
3.6), which is the focus of a full release cycle and feature development. WordPress
uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are 
sequential and comparable in scope. of the year was originally scheduled for the
middle of December. Historically, fewer people are available the last two weeks 
of a year and the first week of a new year, because of various holidays, time off,
and end-of-year and annual planning. This means there would be fewer people to test,
give feedback, fix reported issues, and help package each release.

The revised schedule takes into account the realities of year-end and offers an 
optional Beta 4 if needed.

## **A schedule that delivers the full release **

5.9 is still in feature freeze. Work from here on is _strictly_ to address the changes
that get the release to a stable state.

The revised schedule also has a number of built-in safety measures:

 * More transparency. Constant communication between the release squad and Core 
   Editor team throughout each week, so everyone involved knows the status of relevant
   items and can surface (and meet!) needs as early as possible.
 * 🔺blockers merged by Beta 1. An agreement that blockers (identified as🔺[ in the list](https://github.com/WordPress/gutenberg/issues/36556))
   must be ready by Beta 1 or risk getting moved to 6.0. **(Update: these items 
   were merged last week and are no longer blockers.)**

## **How can you help?**

Above all, please [help test](https://make.wordpress.org/core/handbook/testing/beta-testing/)
everything.

 * Get involved in the FSE Program testing calls including [testing the site-editing experience](https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/).
   You can find a record of all the [FSE Outreach exercises](https://make.wordpress.org/test/tag/fse-testing-call/);
   feel free to go back and test any that interest you, but keep in mind that features
   have evolved.
 * [Spin up a test site](https://make.wordpress.org/core/handbook/tutorials/) that
   uses Twenty Twenty-Two. If you find issues, please report them by [opening a Trac ticket](https://login.wordpress.org/?redirect_to=https://core.trac.wordpress.org/newticket).
 * **Important: Try to break things to find things that may not work for your test
   sites.** 
 * If you’re available, come to the Beta and Release Candidaterelease 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)](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/?output_format=md#alpha-beta).(
   RC) release parties, and bring friends! Test the packages when they drop. The
   parties take place in the Core channel of the Make WordPress SlackSlack Slack
   is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
   The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).
 * Come to the Slack meetings for Core and the Core Editor, and keep reading the
   posts on the Make.WordPress.orgWordPress.org The community site where WordPress
   code is created and shared by the users. This is where you can download the source
   code for WordPress core, plugins and themes as well as the central location for
   community conversations and organization. [https://wordpress.org/](https://wordpress.org/)
   blogblog (versus network, site).
 * Share feedback! The teams need to know everything that breaks, and everything
   that works really well, too.
    - For issues with 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/](https://wordpress.org/gutenberg/),
      [create an issue](https://github.com/WordPress/gutenberg/issues/new/choose)
      on GitHubGitHub GitHub is a website that offers online implementation of git
      repositories that can easily be shared, copied and modified by other developers.
      Public repositories are free to host, private repositories require a paid 
      subscription. GitHub introduced the concept of the ‘pull request’ where code
      changes done in branches by contributors can be reviewed and discussed before
      being merged by the repository owner. [https://github.com/](https://github.com/).
    - For issues anywhere else, [start a ticket](https://login.wordpress.org/?redirect_to=https://core.trac.wordpress.org/newticket)
      on TracTrac An open source project by Edgewall Software that serves as a bug
      tracker and project management tool for WordPress..

Props [@marybaum](https://profiles.wordpress.org/marybaum/), [@annezazu](https://profiles.wordpress.org/annezazu/),
[@costdev](https://profiles.wordpress.org/costdev/), [@webcommsat](https://profiles.wordpress.org/webcommsat/),
[@cbringmann](https://profiles.wordpress.org/cbringmann/) for collaborating and 
proofreading this post.

[#5-9](https://make.wordpress.org/core/tag/5-9/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/?share=linkedin)

 1.  ![](https://secure.gravatar.com/avatar/a9d562e7120942d22426f454671157f1e47c3357016dc8bc4b08c2eaad78293f?
     s=32&d=mm&r=g)
 2.   [Evan Mullins](https://profiles.wordpress.org/circlecube/)  2:50 pm _on_ November
     23, 2021
 3.  Thank you for the clear update – and especially for including the decision process,
     a great idea to be transparent and open for the community today as well as for
     future reference. :community: :hero:
 4.  ![](https://secure.gravatar.com/avatar/df1cbc2af0312d83f46e5125afb2291cc87ad742d3eab0989a7bfaced1a042dd?
     s=32&d=mm&r=g)
 5.   [Aldo Ortiz](https://profiles.wordpress.org/arudope/)  5:39 am _on_ December 
     1, 2021
 6.  I’m looking for this new version :).
 7.  ![](https://secure.gravatar.com/avatar/0ff59e6c86f95d720d328fd8e2896fc661ac7557322b2fe01a60c2d469011349?
     s=32&d=mm&r=g)
 8.   [wallydavid](https://profiles.wordpress.org/wallydavid/)  3:35 pm _on_ December
     27, 2021
 9.  I work for an agency networknetwork (versus site, blog) and personally manage 
     over a hundred WordPress sites. 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 is so bad, I would never let
     my clients use it because it’s too complicated for the average end user. (WP’s
     biggest problem is an identity crisis, it can’t figure out if it’s for developers
     or end users). I just assume that many developers will just abandon WordPress 
     for alternatives after this release or leave older versions sitting on servers.
     The biggest issue is anyone doing e-commerce because WoCommerce is so integrated
     into these new releases now. It’s all a mess for anyone who does this for a living.
     Automatic doesn’t care or listen. But a guarantee they will double down on a bad
     idea.
 10.  * ![](https://secure.gravatar.com/avatar/737c2df3eecd59128718fa1f089e99f9463e664b51920f15bf781b2578015a2f?
        s=32&d=mm&r=g)
      *  [Colin Stewart](https://profiles.wordpress.org/costdev/)  4:40 pm _on_ December
        27, 2021
      * [@wallydavid](https://profiles.wordpress.org/wallydavid/) FWIW, I’m also a 
        developer with an agency as well as an unsponsored WordPress CoreCore Core 
        is the set of software required to run WordPress. The Core Development Team
        builds WordPress. contributor working in a range of areas across Core.
      * 5.9 doesn’t enforce Full Site Editing. If you don’t want to develop a 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.
        theme, you can still develop themes as you’re used to. If you don’t want to
        use the block editor, or block widgets, you can install the Classic Editor 
        and Classic Widgets plugins and continue as you were. Whether I use the Classic
        Editor, Block Editor or FSE will depend entirely on my clients’ operational
        needs, training needs and the scope of the project. I can tell you that from
        daily activity with other Core contributorsCore Contributors Core contributors
        are those who have worked on a release of WordPress, by creating the functions
        or finding and patching bugs. These contributions are done through Trac.
         [https://core.trac.wordpress.org](https://core.trac.wordpress.org)
        that there is no sign of FSE being forced. For those working on FSE, focus 
        is very much about outreach and feedback that can be used to improve FSE in
        both developer and non-developer contexts. While FSE is aimed towards being
        the new approach to theme development, the traditional approach is still fully
        supported. Core contributors have a strong ethos of maintaining backwards compatibility–
        and we go to great lengths to do so.
      * For both security and stability purposes, I strongly urge you and others not
        to leave old versions sitting on a server. Upgrade to 5.9 on a staging site
        and see that FSE does not activate unless you’re using a block theme. You can
        continue to get the benefits of the work we’ve done in Core without having 
        to use FSE/Blocks if you don’t want to.
      * I’m not quite sure what you mean about WooCommerce. I develop sites using WooCommerce
        too, and the only time the Block Editor and WooCommerce mix is if I’m inserting
        WooBlocks into the Block Editor, if I’m using the Block Editor for displaying
        products at all. Other than that, it’s the product editor and (for some workflows)
        editing the template files, or (for most workflows) using hooksHooks In WordPress
        theme and development, hooks are functions that can be applied to an action
        or a Filter in WordPress. Actions are functions performed when a certain event
        occurs in WordPress. Filters allow you to modify certain functions. Arguments
        used to hook both filters and actions look the same. for more stability.
      * For those working on FSE and the Block Editor, it would be great for them to
        get more specifics about what could make things simpler for your clients and
        what could make things cleaner for your workflow.
      * A note on the “identity crisis” – WordPress is about democratizing publishing.
        Its appeal has always been its ease of use and its ease of extension. We have
        an ethos – and a recognised obligation – to provide for both developers and
        non-developers. Everyone working in each area of WordPress aims to make things
        as accessible as we can, as soon as we can. We support the things that work
        and we fix the things that don’t work. The fact that FSE isn’t forced and that
        contributors have developed the “Classic” plugins to maintain traditional workflows
        should be a clear testament to this.
      * ![](https://secure.gravatar.com/avatar/050a3068cfbdd322f50361a572eadd95f5ac95ccfeedbe447bc5bc4d70e68973?
        s=32&d=mm&r=g)
      *  [Phil](https://profiles.wordpress.org/probablynotphil/)  1:35 pm _on_ December
        28, 2021
      * Just popping my two cents here too.
      * This is why I’ve migrated my ecommerce clients away from WP/WooCommerce over
        the past few years. The migrationMigration Moving the code, database and media
        files for a website site from one server to another. Most typically done when
        changing hosting companies. is a pain, but trust me, they will thank you for
        it when they start using something like Shopify instead.
      * That’s the joy of open sourceOpen Source Open Source denotes software for which
        the original source code is made freely available and may be redistributed 
        and modified. Open Source **must be** delivered via a licensing model, see 
        GPL. though. You can’t expect it to be perfect for you when there are so many
        cooks in the kitchen. I’m not going to complain about it, just move on and 
        find the system that works best for the project. I came to WP from Joomla in
        a similar way many years ago.
      * Now I just follow the development of WP out of interest from afar. Like watching
        a strange science experiment as it unfolds.
 11. ![](https://secure.gravatar.com/avatar/0ff59e6c86f95d720d328fd8e2896fc661ac7557322b2fe01a60c2d469011349?
     s=32&d=mm&r=g)
 12.  [wallydavid](https://profiles.wordpress.org/wallydavid/)  6:21 pm _on_ December
     28, 2021
 13. Yes, I understand all of this. I use the classic editor and the classic widgets
     and.. and.. and.. to make WordPress usable for my clients. (by usable, I mean 
     no 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). We feature locked many of our sites when the block editor
     was released. The short experiments with sites auto updating and frustrated clients
     who no longer knew how to edit them cost time, money and resources in retraining
     or rolling back WordPress versions. Thats a real world problem.
 14. Since the release of the block editor, more themes and plugins have been moving
     to the block editor layout or some version of it in the customizerCustomizer Tool
     built into WordPress core that hooks into most modern themes. You can use it to
     preview and modify many of your site’s appearance settings.. I end up having this
     mixed bag of third party visual classic editors and block type plugins. **To make
     matters worse for those of us who do not use the block editor, the classic plugins
     tend to be a few weeks behind main releases, so automatic updates aren’t even 
     possible because the classic editing features brake for my clients. We’re then
     at the mercy of a third parties developing fixes for “classic editing”**. That
     too is a real world problem.
 15. For an open sourceOpen Source Open Source denotes software for which the original
     source code is made freely available and may be redistributed and modified. Open
     Source **must be** delivered via a licensing model, see GPL. platform, my gripe
     with Automatic in requards WooCommerce is the integration of wordpress.comWordPress.
     com An online implementation of WordPress code that lets you immediately access
     a new WordPress environment to publish your content. WordPress.com is a private
     company owned by Automattic that hosts the largest multisite in the world. This
     is arguably the best place to start blogging if you have never touched WordPress
     before. [https://wordpress.com/](https://wordpress.com/)/woocommerce.com accounts
     and the requirements of the bloatware integration of JetPack. WooCommerce is Automatic,
     Automatic is WordPress, so more and more the requirements of the latest version
     of WordPress and the UIUI User interface of WooCommerce is becoming more dependent
     on the layout mechanincs of blocks. These all together give me no confidence in
     doing ecommerce on the WordPress platform. I end up with cobbled together sites
     that are trying to avoid all integration to to wordpress.com and woocommerce.com
     sites. **Yes, I can just not install JetPack, and yes, I can just not connect 
     to wordpress.com or woocommerce.com, but as a developer am I supposed to maintain
     30 different accounts for 30 different clients with 30 different emails to manage
     purchased plugins and jetpack settings?** That too is a real world problem of 
     using WordPress now.
 16. **This is also the part about identity crisis. Its hard to figure out who “WordPress.
     orgWordPress.org The community site where WordPress code is created and shared
     by the users. This is where you can download the source code for WordPress core,
     plugins and themes as well as the central location for community conversations
     and organization. [https://wordpress.org/](https://wordpress.org/)” the self installed
     platform is for. How can you be a develper at an agency, when simply installing
     JetPack makes you create a WordPress.com account? Am I supposed to do that for
     every client?** I dont have that many emails. I’ve built over 500 sites since 
     2010. Same with WooCommerce now. If my agency manages a site and is billing for
     support and managing updates and plugins, am I supposed to create a WooCommerce
     account for every client who’s doing ecommerce? Thats what I mean. Is the WordPress.
     org installer for developers or a single end user?
 17. It’s just frustrating. With the next release I’ll probably have to have another
     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/](https://wordpress.org/plugins/)
     or can be cost-based plugin from a third-party. installed called classic site 
     editing only… **The bigger feeling is that it’s just getting worse with the 6.0
     release and we’re going to end up with a few hundred sites and client that can’t
     be upgraded any further without using some form of the block editor putting the
     agency and our clients websites at risk.**
 18. I would love to have this discussion with WordPress devs, so would a lot of developers.
     But I think the point has been driven home by people in the forums who can write
     better than me.

Comments are closed.

# Post navigation

[← Editor Chat Agenda: 24 November 2021](https://make.wordpress.org/core/2021/11/22/editor-chat-agenda-24-november-2021/)

[A Week in Core – November 22, 2021 →](https://make.wordpress.org/core/2021/11/23/a-week-in-core-november-22-2021/)