WordPress 5.5: Call for Tickets

With 5.4 released, let’s officially kick-off 5.5! As we do with each 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., we want to fix bugs, add new tools and makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). WordPress the best user experience. 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 full sitesite (versus network, blog) editing) are still at the top of the WordPress goals list, but what other tickets do you think need some attention in this release cycle?

Share Your Feedback!

  • What do you want to see included in 5.5?
  • What are current UXUX User experience pain points?
  • What features can we add or iterate on?
  • Component Maintainers: what tickets of yours do you think will be ready to ship in 5.5 and need some review/feedback/approval/etc?

Note: Adding your ticketticket Created for both bug reports and feature development on the bug tracker. here won’t necessarily guarantee inclusion. But no one can fix things they can’t see, so bravely share your thoughts!

Deadline April 30, 2020