Title: WordPress 5.5 Planning Roundup Author: Josepha Published: May 13, 2020 --- [ ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/) 10:53 pm _on_ May 13, 2020   # WordPress 5.5 Planning Roundup There have been some scattered discussions about making some shifts to the way that we manage releases. I’m open to suggestions on the timeline below if I have misunderstood anything! As was suggested in the [WP5.3 debrief](https://make.wordpress.org/core/2020/01/08/5-3-release-cycle-post-mortem/), the cycle for WP5.5 has a longer alpha period (clocking in at ~126 days, one week less than WP5.3). As was discussed in the [core committer Slack channel ](https://wordpress.slack.com/archives/C18723MQ8/p1582278073006300) and subsequently [suggested by @francina](https://wordpress.slack.com/archives/C18723MQ8/p1582456770004200), this cycle also has a shorter 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/2020/05/13/wordpress-5-5-planning-roundup/?output_format=md#alpha-beta). period (clocked in at 14 day, two weeks shorter than WP5.3 but one week shorter than WP5.4). ## Proposed WordPress 5.5 Schedule These are my best guesses at the milestones, based on what I was able to find of the discussions: * **Alpha**: 3 March, 2020 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. is open for 5.5 alpha contributions * **Kickoff**: 13 May, 2020 (that’s this post!) * **Betas**: 7 July, 2020 (8 weeks from kickoff) * **Release Candidates**: 28 July, 2020 (3 weeks from 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) * **General Release**: 11 August, 2020 (2 weeks from 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/2020/05/13/wordpress-5-5-planning-roundup/?output_format=md#alpha-beta). 1) ## Proposed WordPress 5.5 Scope The main goal for 2020 is **full site editing via 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/)**. For WP5.5 the following features are in the [suggested roadmap](https://make.wordpress.org/updates/2020/03/06/update-progress-on-goals/): * Update WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to include current releases of the 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.. * Navigation menus 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. in Core. * Automatic updates for plugins and themes in Core. * Block directory in Core. * [XML Sitemaps](https://make.wordpress.org/core/2020/01/27/feature-plugin-xml-sitemaps/) * [Lazy Loading](https://make.wordpress.org/core/2020/01/29/lazy-loading-images-in-wordpress-core/) Also in that roadmap are a few hopeful items. Getting these into the Gutenberg plugin would be a great goal! * [Blocks in the widgets-editing areas](https://github.com/WordPress/gutenberg/issues/13204) * [Basic functionality for full site editing](https://github.com/WordPress/gutenberg/issues/13489) * Global styles There were also a collection of [hoped-for tickets raised on my earlier post](https://make.wordpress.org/core/2020/04/08/wordpress-5-5-call-for-tickets/) as well as a number from component maintainers. I ended up with some outstanding questions on those, but should have everything I need soon. ## Proposed WordPress 5.5 Leads _This area is intentionally incomplete. I’ve got some more confirmations/discussions I’m working through!_ * Editor Tech: * Editor Design: * Core Tech: * Docs coordinator: * Marketing/Release Comms: * Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM: * Release coordinator: [#5-5](https://make.wordpress.org/core/tag/5-5/) [#planning](https://make.wordpress.org/core/tag/planning/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2020/05/13/wordpress-5-5-planning-roundup/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2020/05/13/wordpress-5-5-planning-roundup/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2020/05/13/wordpress-5-5-planning-roundup/?share=bluesky) * [ X ](https://make.wordpress.org/core/2020/05/13/wordpress-5-5-planning-roundup/?share=x) * [ Facebook ](https://make.wordpress.org/core/2020/05/13/wordpress-5-5-planning-roundup/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2020/05/13/wordpress-5-5-planning-roundup/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/52525485c604c4ed417a11636a0884d89395675d139245024cb71ac3ebe88dcc? s=32&d=mm&r=g) 2. [Justin Ahinon](https://profiles.wordpress.org/justinahinon/) 8:51 am _on_ May 14, 2020 3. Hi [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) 👋. 4. I didn’t make it to the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. chat yesterday. But if there’s no new comers/volunteers for the Docs coordinator role already, I can help on that. 5. * ![](https://secure.gravatar.com/avatar/b98cc60e2f12d4573ab0dca7442b45137144bac0ffb28dac83fe6a72bd6ba007? s=32&d=mm&r=g) * [Josepha](https://profiles.wordpress.org/chanthaboune/) 2:59 pm _on_ May 14, 2020 * I will take you up on that! 6. ![](https://secure.gravatar.com/avatar/70c83ce0b076a495b73ee5823d0007c7b8e340fbc920c61286d2750deafa6a77? s=32&d=mm&r=g) 7. [Jake Spurlock](https://profiles.wordpress.org/whyisjake/) 6:14 pm _on_ May 14, 2020 8. I’d love to help more with this release. What’s the role of the release coordinator? I’m assuming this is similar to the role that I have filled on minor releases. 9. ![](https://secure.gravatar.com/avatar/6f505c6be9a951929a99becb6b413dcfa583a5ca3dd0f7320766fee1481f0f82? s=32&d=mm&r=g) 10. [Jb Audras](https://profiles.wordpress.org/audrasjb/) 6:38 pm _on_ May 14, 2020 11. As I said before, happy to serve as accessibilityAccessibility Accessibility ( commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( https://en.wikipedia.org/wiki/Accessibility) focus rep, since we have a quite large scope slated for 5.5. And I’d of course love to onboard the future WP 5.6 Accessibility focus lead at the same time 🙌 12. ![](https://secure.gravatar.com/avatar/a62d24bec2dbb1a6364198cf1e6afc062c91f6731838dcef908a5383ffd2bca8? s=32&d=mm&r=g) 13. [kiranrs](https://profiles.wordpress.org/kiranrs/) 4:30 pm _on_ August 7, 2020 14. Hi,I’m a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher developer. I wish to be in the development team. Please guide, how can I contribute to WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development? 15. Thanks Comments are closed. # Post navigation [← What’s new in Gutenberg? (13 May)](https://make.wordpress.org/core/2020/05/13/whats-new-in-gutenberg-13-may/) [Privacy Office Hours Minutes 14 May 2020 Plans for WCEU Contributor Day →](https://make.wordpress.org/core/2020/05/14/privacy-office-hours-minutes-14-may-2020-plans-for-wceu-contributor-day/)