WordPress 6.1 Planning Roundup

WordPress 6.1 will be the third major release of 2022. Following WordPress 6.0 Arturo, 6.1 will aim to refine those experiences found in Arturo and in 5.9 Joséphine [ref]. In preparation, this post includes target dates, features, and a call for the release’s squad.

This release cadence will consist of a long alpha and two short 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. periods before the 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). phase. According to the schedule proposed below and 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/ release cadence, WordPress 6.1 would include up to Gutenberg 14.1 for a total of 11 Gutenberg releases, the same amount as WordPress 6.0 included.

Proposed WordPress 6.1 Schedule

MilestoneDate
Alpha (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. open for 6.1 release)May 3, 2022
Beta 1 & Feature FreezeSeptember 20, 2022
Beta 2September 27, 2022
Release Candidate 1October 4, 2022
Release Candidate 2October 11, 2022
Release Candidate 3October 18, 2022
Dry RunOctober 24, 2022
WordPress 6.1 General releaseOctober 25, 2022

Proposed WordPress 6.1 Release Leads

Release LeadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg
Release Coordinator: TBD
CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead: TBD
Editor Tech Lead:  TBD
Core Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead: TBD
Editor Triage Lead: TBD
Documentation Lead: TBD
Marketing & Communications Lead: TBD
Test Lead: TBD
Design Lead: TBD

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community.

Join The Squad!

If you are interested in being a part of 6.1’s release squad, please show your interest in the comments below. Roles can be shared among more than one person!

#6-1, #planning

WordPress 6.0 planning update

With one month to the first WordPress 6.0 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., let’s review the WordPress 6.0 cycle status.

Live-streamed walkthrough and feature freeze

As an iteration over WordPress 5.8 and 5.9’s Go/No Go demo, WordPress 6.0 will offer a hosted  walkthrough on April 5th. In this event, placed closer to Beta than past demos, WordPress leads will review the features ready for the next 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. together with the community in a live, moderated stream.

As a result of this demo and to address contributor feedback received in the last two major release cycles, the effective feature freeze will happen with Beta 1 on April 12th.

This adjustment will give 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. two extra weeks over the original schedule. Together with the live demo, they will offer enough buffer time to identify and address any last-minute blockerblocker A bug which is so severe that it blocks a release. issues found during the walkthrough, reducing the amount of backports post- Beta 1.

5 April 2022Live-streamed walkthrough
12 April 2022Beta 1, effective Feature Freeze
19 April 2022Beta 2
26 April 2022Beta 3
3 May 2022Release 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). 1
10 May 2022Release candidate 2
17 May 2022Release candidate 3
23 May 2022Dry run
24 May 2022WordPress 6.0 stable release

Release team

With the exception of the 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) Lead, the release team is nearly complete. Thanks to all participating volunteers!

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community. Coordination between the whole squad primarily occurs in the public #6-0-release-leads SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, and contributors are welcome to join the release team in this process.

How To Help

If you are still interested in being a part of 6.0’s release squad or shadowing a lead to participate in future releases, please show your interest in the comments below or the #6-0-release-leads Slack channel. If you want to dive deeper into 6.0, join the weekly meetings in the #core Slack channel, which occur every Wednesday at 20:00 UTC.

#6.0, #planning

#6-0

WordPress 6.0 Planning Roundup

WordPress 6.0 will be the second major release of 2022. Following WordPress 5.9 Joséphine, 6.0 will aim to refine and iterate on the customization tools introduced earlier this year. In preparation, this post includes target dates, features, and squads.

This release will follow the same cadence as 5.9, with a long alpha and short 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. periods before the 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). phase.

Proposed WordPress 6.0 Schedule

MilestoneDate
Alpha (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. open for 6.0 release)January 4, 2022
Feature freeze/Bug FixesMarch 29, 2022
Beta 1April 12, 2022
Beta 2April 19, 2022
Beta 3April 26, 2022
Release Candidate 1May 3, 2022
Release Candidate 2May 10, 2022
Release Candidate 3May 17, 2022
Dry RunMay 23, 2022
WordPress 6.0 General releaseMay 24, 2022

Proposed WordPress 6.0 Scope

Take a look at the 6.0 preliminary roadmap, which includes Editor refinement, Pattern expansion, 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. refinement, block exploration, and design tooling.

Proposed WordPress 6.0 Release Leads

  • Release LeadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg
  • Release Coordinator: Héctor Prieto
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech: Peter Wilson
  • Editor Tech: 
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead: 
  • Documentation Lead: Birgit Pauli-Haack
  • Marketing & Communications Lead: Dan Soschin
  • Test Lead: 
  • Design Lead:
  • 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) Lead:

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community.

How To Help!

If you are interested in being a part of 6.0’s release squad, please show your interest in the comments below. In particular, open roles that need volunteer support include:

  1. Editor Tech
  2. Triage Lead
  3. Test Lead
  4. Any additional support on existing squad roles

#6.0, #planning

Proposal: 2022 Major Release Timing

After our initial discussion about potential release timing for the year, I would like to suggest two additional 2022 releases:

  • 6.0 – Late May
  • 6.1 – Mid October

I believe that the relationship between WP5.9 and WP6.0 will be similar to the relationship between WP5.0 and WP5.1 in that there will be copious user feedback to process so that we can extend, refine, and in some cases even rework the user experience with the vast new feature set introduced in 5.9. By aiming to release WP6.0 in late May, we can let WP5.9 breathe a little, work through the rest of the Phase 2 roadmap, and prioritize WordPress-wide needs as we encounter them.

Given the complexity of our last pair of similar releases, I would love to see some Five for the Future sponsored project manager-ish people* join @jeffpaul and @priethor in addition to our usual release squad. If you’re interested in participating in a squad and want to know more, you can pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @chanthaboune, @jeffpaul, @priethor or any former release squad member you know!

*So as not to startle anyone or overpromise anything—I’m not suggesting that we need a bunch of people to show up and boss around all of our brave and generous contributors. I’m suggesting that a 19-year-old project can no longer be fully tracked by a person or two and the people who are tracking all of our moving parts could use some support.

#planning

WordPress 5.9 Planning Roundup

Happy September no matter where you are in the world! Since we’re halfway through the alpha period for the next big release of WordPress, it’s time to gather all the pieces of planning into one place. This post will include all the best guesses and targets for dates, features, and squads.

This release will follow the same general cadence as the other releases this year, with a long alpha period (132 days) and a short 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. period (14 days) before the 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). phase.

Proposed WordPress 5.9 Schedule

These are my best guesses at the milestones:

MilestoneDateDays from
Alpha (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. open for 5.9 release)June 30, 2021
Go/no go DateOctober 12, 2021
October 14, 2021
104 days after Alpha
Feature freeze/Bug FixesNovember 9, 202142 days after go/no go
Beta 1November 16, 20217 days after Feature Freeze
Release Candidate 1November 30, 202114 days after Beta 1
General releaseDecember 14, 202114 days after RC1
WP5.9 Schedule

This schedule puts Beta 1 the week of a major US holiday and a few major commerce dates worldwide. It does avoid putting RC1 during that week.

Proposed WordPress 5.9 Scope

The main goal for 2021 is getting full site editing to all WordPress users. For WP5.9 the following features are in the suggested roadmap:

  • Blocks + intrinsic web design
  • Navigation menus
  • Interface for theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.
  • Refining editing flows for 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. themes
  • New default theme
  • Additional design tools

There are also a few roadmap hopefuls out there.

  • Pattern insertion + creation
  • Unzip/Rollback Failsafes
  • PHPUnit Tests
  • Improved compatibility with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.0 and 8.1

Proposed WordPress 5.9 Leads

  • Release LeadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg
  • Release Coordinators:
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead:
  • Editor Tech:
  • Editor Design:
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech:
  • Theme Lead:
  • Technical Writer: Jonathan Bossenger
  • Docs Lead:
  • Marketing & Comms: Josepha Haden
  • 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) Lead:
  • Test Lead:

How to help!

I think we will need a slightly larger release squad for this final release of the year, so I’m opening calls for volunteers. As we approach the go/no go date and get a better idea of what features will really land in the release, we’ll get more squad leads assigned.

However, there are a couple of roles we really could use some volunteers for right now:

  1. Triage Lead
  2. Release Coordinators

If you’re interested in lending a hand, please share your interest in the comments!

Props to @francina for early versions of this post, and @jeffpaul + @desrosj for wrestling calendars with me.

#5-9, #planning

WordPress 5.8: What’s on your to-do list?

With the 5.8 release scheduled for 20 July 2021, I’d like to understand what work folks have planned for the release so that @desrosj and I can help track that overall scope and work to resolve blockers anyone has in achieving those goals (noting that our primary focus will be on Full Site Editing).

Historically within the major release cycle this is the time in which a “wish list” post would be published. However, given the nature of the 5.8 release and it’s primary focus on the release of Full Site Editing there won’t be the normal availability to review a lengthy wish list and attend to getting that work to commit within the release. We hope to return to that approach in a future release.

This post is specifically targeted at:

  • Core Component Maintainers to understand what their intended focus is for 5.8
  • Feature plugin authors to understand what they hope to propose for merge in 5.8
  • 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/ team (via @youknowriad as 5.8 Editor Tech Lead) to understand what WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. changes are desired to support Full Site Editing (alongside the already-defined “next steps”)

So if you consider yourself a part of one of these three groups, please share what your intended focus is for the 5.8 release so that @desrosj and I can help track the overall 5.8 release scope.

Deadline for response: 14 May 2021 (10 days from now, 11 days from then until Feature Freeze).

Props @desrosj for peer review.

#5-8, #planning, #scope

WP5.8 Squad Call for Volunteers

Edit: 4/23/2021 @ 19:10 UTC – changed the references to contributors in the last paragraph to 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/ usernames to help to make the connection. – @desrosj

With the schedule finalized and parts of 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/ phase 2 getting ready to merge, it’s time to put together a squad of focus leads for WordPress 5.8.

You can read more about the different roles in the handbook.

Here are the squad roles available:

The roles of release leadRelease Lead The community member ultimately responsible for the Release. and marketing/communications lead will be filled by @matt and @chanthaboune, respectively.

Expectations

Focus leads should be available for at least 5-6 hours a week to perform their tasks, with more time as milestones like Betas, Release Candidates, and General release approach. On the days of those milestones, you might need to dedicate 4-6 hours to WordPress on one day.

There are no limitations to where you come from. We are a global community, open 24/7 so you will schedule scrubs, if needed, according to your availability and potentially find a deputy to cover other timezones.

Because 5.8 is going to be a busy release, the squad won’t have mentorship or ride-along opportunities, like it did in the past, but as Josepha mentioned there is a public channel for the team to coordinate so that others can learn through observation.

This doesn’t mean you need to have all the answers to volunteer. 🙂 There will be a bunch of people available to help and support (the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team representatives, long-time contributors, etc…).

Are you interested?

Please leave your name in the comments with the role you are interested in or reach out to me (@francina), @audrasjb or @chanthaboune if you have any questions before raising your hand.

Thanks!

#5-8, #planning

5.8 Pre-planning

Following Josepha’s early thoughts on 5.8 planning, I am kicking off the pre-planning phase of WordPress version 5.8.

Full site editing in 5.8

The plan for WordPress 5.8 is to merge and release the minimum viable product (MVP) of full site editing (FSE). This makes this release particularly complex to handle. It’s a new, exciting change, and it needs the appropriate time to marinate in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for contributors with enough time to work on it.

Schedule

I would like to propose the following schedule.

MilestoneDateDays from
AlphaFebruary 23, 2021
First FSE go/no go dateApril 13, 2021
Second FSE go/no go dateApril 27, 2021
(If go) FSE MergeTo be determined, but as soon as possible after being greenlighted
Feature freeze/Bug FixesMay 25, 202191 days after Alpha
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. 1June 8, 202114 days after Feature Freeze
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). 1June 29, 202121 days after Beta 1
General releaseJuly 20, 202121 days after RC1

What’s this “Feature Freeze” step?

As previously discussed (first post, second post), mixing defect work and beta testing is not great for a number of reasons:

  • As a project, we want to respect the beta testers efforts by not introducing new bugs (defect work fixes) in areas they’ve already tested.
  • A mature software project has a beta period during which the focus is on testing changes made during alpha period to ensure its stability.
  • Having a separate deadline for enhancements/features and bugs is beneficial to allow developers to switch focus after the first deadline to address a slew of outstanding bugs.

Enter the “Feature Freeze” step: two weeks where contributors and committers can take care of the thousands of defect tickets in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

This process should allow time to dedicate appropriate attention to those tickets, without taking attention and resources away from beta testing, which needs to be a priority, especially in this release.

Squad

With such a complex release, Core needs a group of experienced contributors leading the release. For this release, the ride-along/mentorship will pause so that the leads, with previous experience in releases, can focus on the process.

Pre WP5.8 Squad – Skeleton Crew

The period leading to the go/no go step, will need a minimal squad that will focus on:

  • 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. hunting for WP5.7.x minor releases
  • triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and group tickets into future milestones
  • test Core and FSE tickets and PRs

We are kicking off with a minimal squad of three roles:

Full Squad

Once we’re past the go/no go dates the skeleton crew, together with the project leadership, will determine which skills are needed to successfully complete the cycle.

What about scope?

The focus of the release is full site editing. As suggested in the recent FSE FAQ, the specific scope is to merge the interface that allows for template interaction outside of content, as well as 20+ new blocks, and design tools. This part of the FSE merge will not be offered to users by default, but instead will be geared toward our extender community (theme authors, 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 developers, agencies, builders, etc) so that they can experiment with their users in mind.

As with other releases, it is possible to include more features, provided someone can spearhead them.

I will start a round of check-ins with component maintainers as soon as the timeline is confirmed.

#5-8, #planning

WordPress 5.7 Planning Roundup

The article has been edited on January 27, 2021, to confirm the schedule and the features included in the release.

After a successful WordPress 5.6 release, this post aims to provide a round-up of planning done so far for WordPress 5.7.

WordPress 5.7 Schedule

This cycle will have a similar timeframe than 5.6:

  • Alpha, 78 days – 5.6 had 84 days
  • 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., 21 days – same as 5.6
  • 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)., 14 days – same as 5.6

Based on the tentative schedule and experiments from the past twelve months, this is the proposed schedule for the first of the four planned releases for 2021:

  • Alpha: 17 November 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.7 alpha contributions
  • Kickoff: 15 December 2020 first 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. scrub of the new cycle
  • Planning roundup: 21 December 2020 (that’s this post!)
  • Betas: 2 February 2021 (eleven weeks from branching off trunk, seven weeks from kickoff)
  • Release Candidates: 23 February 2021 (three weeks from beta 1)
  • General Release: 9 March 2021 (two 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). 1)

WordPress 5.7 Scope

The main goal for 2021 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/ (edited for clarity: this is not THE scope for 5.7 but an ongoing effort 😊).
You can read the status report, join the FSE Outreach program, check the progress on the GitHub issue used to overview to progress, and dive into contributing to it from there!

For WP5.7, these are some of the features that will be likely worked on:

As with every release, all component maintainers and teams are invited to prioritize their bug-fixes and enhancements for 5.7. Look out for the 5.7 report in Trac to see what is getting milestoned and help the project gets those tickets to the end line!”

In addition, all components and teams are invited to continue polishing current interactions and making the UIs more user-friendly.

JB and I are collecting all the proposals from the open call for tickets: we will submit them to the relevant component maintainers so they can evaluate if there are enough resources to address them during this release cycle and update their status. If they are, they will be milestoned for 5.7, so turn on your notifications if you haven’t already.

Please bear in mind, if a ticketticket Created for both bug reports and feature development on the bug tracker. is still waiting for review, has no patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., or no owner, it is unlikely (not impossible) that it will land in 5.7. This shouldn’t stop you from continuing to work on it, gather feedback, and ultimately polish it enough to have it in a future release. Shepherding tickets is as vital as submitting patches.

WordPress 5.7 Leads

This area is intentionally incomplete. JB, Josepha, and I are reaching out to people that have expressed interest in being part of 5.7. 

You can read about each role in our handbook. If you are interested, leave a comment on this post, and we will reach out to you too.

  • Release LeadRelease Lead The community member ultimately responsible for the Release.: Matt
  • Release Co-ordinator: Ebonie Butler
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM: Tonya Mork
  • Core Tech: Sergey Biryukov
  • Editor Tech: Robert Anderson
  • Design: Tim Hengeveld 
  • Docs: JB Audras
  • 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): Sarah Ricker
  • Test: Monika Rao

Release specific leads

Once we have final confirmation of scope, we will annouce additional focus leads, if needed.

Thanks @chanthaboune and @audrasjb for the help with the post.
Edited for clarity about scope (FSE is not THE scope, it’s an ongoing effort) and tickets in milestone (unlikely to happen vs. impossible to happen)

#5-7, #planning

Update | WordPress 5.6 Release Progress

The planned date for 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 is just about two weeks away on October 20, 2020. The release squad has been keeping me up to date on our collective progress, and I want to update our list of expected features!

Note: This update doesn’t include a number of cross-team initiatives, that could happen around the time of release, but may ship outside of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. itself. Progress on those will be shared in our quarterly updates on 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//updates.

Planned for Beta 1

  • Automatic updates for major WordPress Core releases (opt-in)
  • New features from 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 upgrades
  • Widgets editing support in Core
  • Twenty Twenty-One theme
  • PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support
  • oEmbed updates

Not Planned for Beta 1

  • Twenty Twenty-One block-based/FSE-first – this will be available in the theme repo once completed.
  • Navigation menus block and screen – work will continue on the feature after 5.6. Find out more here.
  • 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. support – work will continue on this feature, but it won’t be ready for Beta 1. Find out more here.
  • Full Site Editing – Full site editing (FSE) will be added to 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 once available.
  • Drop support for PHP 5.6 – On hold until a decision is made on when to stop support for older versions. Find out more here.

Uncertain for Beta 1

There are a few proposals that are still settling, and it’s not clear whether they will resolve in time for beta. I’ve listed them below for better tracking and transparency.

I also enlisted the generous help of some Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors./TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress./Core folks to get a priority list of tickets that could be ready with a little more help. If you’ve got some spare time left in your contribution budget, head on over and see if any of those tickets call to you. 🙂

Thank you to the release squad for their help compiling and reviewing this post. Thank you to everyone who has contributed their time thus far!

#5-6, #planning, #update