Dev Chat Agendas | Dev Chat Summaries | Wishlist | Dev Notes | 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. | All Posts Tagged 5.6

WordPress 5.6 will be the third and final major release of 2020 and aims to include nav menu 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., automatic updates for major coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. releases, widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. editing and 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 in core, PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 support, and update 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/ to the latest release version as we continue to focus in 2020 on full site editing via Gutenberg. Josepha Haden is the Release LeadRelease Lead The community member ultimately responsible for the Release., Dee Teal is the Release Coordinator, Tonya Mork is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Helen Hou-Sandì is the Core Tech Lead, Isabel Brison is the Editor Tech Lead, Ellen Bauer and Tammie Lister are the Design Leads, Shital Marakana is the Design 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, Yvette Sonneveld is the Marketing Lead, the Documentation Wrangler is Shawntelle Coker, Michele Butcher-Jones is the Documentation Review Lead, Mel Choyce-Dwan is the Default Theme Design Lead, Carolina Nymark is the Default Theme Development Lead, Jessica Lyschik is the Default Theme Wrangler, Monika Rao is the Test Lead, and Bet Hannon is the Support Lead. This group of release leads is supported by various cohort groups. All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community. There will be a new bundled theme included in 5.6.

Release Schedule

28 July 2020Trunk is open for business. (Post-5.5)
19 August 2020
(+3w 1d)
5.6 Kickoff meeting. (Slack archive)
4 September 2020Bug Scrub #1 (Slack archive)
10 September 2020Bug Scrub #2 (Slack archive)
15 September 2020Bug Scrub #3 (Slack archive)
24 September 2020Bug Scrub #4 (Slack archive)
1 October 2020Bug Scrub #5 (Slack archive)
7 October 2020Bug Scrub #6 (Slack archive)
15 October 2020Bug Scrub #7 (Slack archive)
19 October 2020Bug Scrub #8 (Slack archive)
20 October 2020
(+8w 6d)
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, 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. (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/. 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.7 development cycle.
26 October 2020Bug Scrub #9 (Slack archive)
27 October
3 November 2020
(+2w)
Beta 2, continue writing Dev Notes and About page. (Slack archive, Zip download)
Note the additional week here allows for not releasing Beta 2 during WordCamp US.
29 October 2020Bug Scrub #10 (Slack archive)
4 November 2020Bug Scrub #11 (Slack archive)
10 2 November 2020
(+1w)
Beta 3, continue writing Dev Notes and About page. (Slack archive, Zip download)
9 November 2020Bug Scrub #12 (Slack archive)
10 November 2020Beta 4, continue writing Dev Notes and About page, soft string freeze. (Slack archive, Zip download)
16 November 2020Bug Scrub #13 (Slack archive)
17 November 2020
(+1w)
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, publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze. (Slack archive, Zip download)
1 December 2020
(+2w)
Release candidate 2, update About page images, and continue drafting release post. (Slack archive, Zip download)
Note the additional week here allows for not releasing RC2 during US Thanksgiving week when some of the release lead team may be offline.
7 December 2020
(+6d)
Dry run for release of WordPress 5.6 and 24 hour code freeze. (Slack archive)
8 December 2020
(+1d)
Target date for release of WordPress 5.6. 🎉

To get involved in WordPress core development, head on 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.6 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.6, development is discussed at a weekly meeting in the #core Slack channel and occurs next at Wednesday at 20:00 UTC. Wish us luck!