WordPress 5.2 “Jaco” was released on May 7, 2019.

Goals | Dev Chat Agendas | Dev Chat Summaries | Field Guide | Dev Notes | All Posts Tagged 5.2

WordPress 5.2 will be the second 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. of 2019, with plans to include Site Health Check, PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 error protection, the all new 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. directory, and update package signing.

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. Schedule

February 18, 2019 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 business. (Post-5.1)
March 21, 2019
March 22, 2019
March 27, 2019
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 and feature merge deadline

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 WordPress 5.3.

April 8, 2019 Beta 2
April 11, 2019 Beta 3 and soft string freeze.
April 17, 2019
April 25, 2019
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 and hard string freeze.
April 30, 2019
May 7, 2019
Target date for release of WordPress 5.2.

Contributing

To get involved in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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.2 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.2, development is discussed at a weekly meeting 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 and occurs next at Wednesday at 21:00 UTC. Wish us luck!