WordPress 5.7 plan summary-WP Webmaster

WordPress 5.6 was successfully released on December 8. This article summarizes the plans for WordPress 5.7 so far. Published by Francesca Marano .

Directory   hiding 

Proposed WordPress 5.7 plan timeline

Recommended WordPress 5.7 range

Suggested WordPress 5.7 clues

Post specific leads

Proposed WordPress 5.7 plan timeline

The time range of this cycle is similar to 5.6:

Alpha, 78 days-84 days
Beta for WordPress 5.6 , 21 days-same as 5.6
RC, 14 days-same as 5.6

Based on the tentative timetable and experimentation of the past twelve months, this is the recommended timetable for the first of the four planned releases in 2021:

Alpha: The trunk on November 17, 2020 will be available for 5.7 Alpha contributors.
Start: December 15, 2020 The first bug cleanup of the new cycle.
Plan summary: December 21, 2020 (this information!)
Beta version : February 2, 2021 (11 weeks from the main branch, seven weeks from the start)
Release candidate: February 23, 2021 (three weeks from Beta 1)
Normal release: March 9, 2021 ( Two weeks before release candidate 1)

Recommended WordPress 5.7 range

The main goal for 2021 is to use Gutenberg for site-wide editing .

You can read the status report, join the FSE Outreach program, check the progress of the GitHub issue used to outline progress, and start contributing to it from there!

For WP5.7, the following are some features that may work:

Update WordPress Core to include the current version of the Gutenberg plugin.

Gutenberg: Publish other blocks, optimize the UI, add themes and design tools, and then continue the work of widgetizing the screen.

Continue to work on the automatic update function and jQuery.

The WordPress developer team may add more content in the next few weeks and reconfirm the proposed list after the year-end holiday.

As with each version, all component maintainers and teams should prioritize its 5.7 bug fixes and enhancements. Find the 5.7 report in Trac, see what milestones there are, and help the project complete these work orders!

In addition, all components and teams are invited to continue to improve the current interaction and make the UI more user-friendly.

JB and I are collecting all the suggestions from the open ticket: we will submit them to the relevant component maintainers so that they can evaluate whether they have sufficient resources to resolve these issues and update their status during this release cycle. If so, they will reach the 5.7 milestone, so if they are not already open, please open the notification.

Please keep in mind that if the ticket is still awaiting review, there is no patch or no owner, the ticket may not be implemented (not impossible) in 5.7. This shouldn't stop you from continuing to work hard, gather feedback, and finally improve it so that it can be used in future versions. Taking care of work orders is as important as submitting patches.

Suggested WordPress 5.7 clues

This field is not complete yet. JB, Josepha and I are reaching out to people who are interested in becoming 5.7.

You can learn about each role in our brochure. If you are interested, please comment on this information and we will also contact you.

Release leader: Matt
Release coordinator: To be confirmed
Triage PM: Tonya Mork
Core technology: To be confirmed
Technology editor: Robert Anderson
Design: To be confirmed
Document: To be confirmed
Accessibility: Sarah Ricker
Test: Monica Rao

Post specific leads

If needed, we will have more clues.

Guess you like

Origin blog.csdn.net/lilihuigz/article/details/111602969