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

WordPress 5.4 will be the first major release of 2020 and aims create a 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. for navigation menus 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 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. version as we continue to focus in 2020 on full site editing via Gutenberg. Matt Mullenweg is the Release LeadRelease Lead The community member ultimately responsible for the Release., Francesca Marano is the Release Coordinator, David Baumwald is the Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM, Tammie Lister is the Design Lead, Sergey Biryukov is the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead, Mark Uraine is the Editor Design Lead, Jorge Costa is the Editor Tech Lead, and JB Audras is the Documentation Lead. All release decisions will ultimately be theirs to 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). and communicate while gathering input from the community. There will NOT be a new bundled theme included in 5.4.

Release Schedule

25 October 2019 Trunk is open for business. (Post-5.3)
15 January 2020 5.4 Kickoff meeting
21 January 2020 Bug Scrub #1 (Slack Archive)
29 January 2020 Bug Scrub #2 (Slack Archive)
7 February 2020 Bug Scrub #3 (Slack Archive)
10 February 2020 Bug Scrub #4 (Slack Archive)
11 February 2020
(+3w 6d)
Beta 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.5 development cycle.
18 February 2020
(+1w)
Beta 2 and continue writing Dev Notes and About page. (Slack archive) (Zip download)
24 February 2020 Bug Scrub #5 (Slack Archive)
25 February 2020
(+1w)
Beta 3, continue writing Dev Notes and About page, and soft string freeze. (Slack archive) (Zip download)
27 February 2020 Bug Scrub #6 (Slack Archive)
3 March 2020
(+1w)
Release 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)
10 March 2020
(+1w)
Release candidate 2, update About page images, and continue drafting release post. (Slack archive) (Zip download)
17 March 2020
(+1w)
Release candidate 3, update About page images, and continue drafting release post. (Slack archive) (Zip download)
24 March 2020
(+1w)
Release candidate 4. (Slack archive) (Zip download)
27 March 2020 Release Candidate 5 (Slack archive) (Zip download)
30 March 2020
(+6d)
Dry run for release of WordPress 5.4 and 24 hour code freeze. (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)
31 March 2020
(+1d)
Target date for release of WordPress 5.4. 🎉

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.4 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.4, development is discussed at a weekly meeting in the #core Slack channel and occurs next at Wednesday at 21:00 UTC. Wish us luck!