Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | Field Guide | All Posts Tagged 5.7

WordPress 5.7 will be the first major release of 2021.

Matt Mullenweg is the Release leadRelease Lead The community member ultimately responsible for the Release., Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Ebonie Butler is the Release Coordinator, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Robert Anderson is the Editor Tech Lead, Sarah Ricker is 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, Tim Hengeveld is the Design Lead,  JB Audras is the Docs Lead, and Monika Rao the Test Lead.

All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community. There will not be a new bundled theme included in 5.7.

Release Schedule

17 November 2020Trunk is open for business.
15 December 2020Bug Scrub #1 (Slack archive) and #2 (Slack archive)
21 December 20205.7 Roundup Post
22 December 2020Bug Scrub #3 (Slack archive) and #4 (Slack archive)
23 December 20205.7 Kickoff chat
29 December 2020Bug Scrub #5 (Slack archive) and #6 (Slack archive)
6 January 2021Bug Scrub #7 (Slack archive) and #8 (Slack archive)
12 January 2021Bug Scrub #9 (Slack archive) and #10 (Slack archive)
21 January 2021Bug Scrub #11 and #12 (Slack archive)
27 January 2021Bug Scrub #13 (Slack archive) and #14 (Slack archive)
01 February 2021Bug Scrub #15 (Slack archive)
02 February 2021Beta 1, begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only 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. fixes, and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point and can be picked up for commit again at the start of the WordPress 5.8 development cycle.
04 February 2021Bug Scrub #16 (Slack archive)
08 February 2021Bug Scrub #17 (Slack archive)
09 February 2021Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
15 February 2021Bug Scrub #18 (Slack archive)
16 February 2021Beta 3, continue writing Dev Notes and About page, soft string freeze. (Slack archive, Zip download)
22 February 2021Bug Scrub #19
23 February 2021Release candidate 1, publish Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. with Dev Notes, commit About page, begin drafting release post, and hard string freeze. (Slack archive, Zip download)
25 February 2021Bug Scrub #20
01 March 2021Bug Scrub #21
02 March 2021Release candidate 2, update About page images and continue drafting release post. (Slack archive, Zip download)
8 March 2021Dry run for release of WordPress 5.7 and 24-hour code freeze
9 March 2021WordPress 5.7 general release date

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 5.7 ticket. Need help? Check out the Core Contributor Handbook.

Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticket Created for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever 😉

If you want to dive deeper into 5.7, join the weekly meetings in the #core 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, which occur next at Wednesday at 05:00 UTC and Wednesday at 20:00 UTC.

Wish us luck!