Goals | Dev Chat Agendas | Dev Chat Summaries | Dev Notes | Field Guide | All Posts Tagged 5.1
WordPress 5.1 “Betty” was released on February 21, 2019.
WordPress 5.1 will be the first major 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, including PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher version upgrade notices, and block 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. editor improvements.
|December 19, 2018
|Trunk 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.0)
|January 10, 2019
|Beta 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 bug 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.2.
|January 21, 2019
|January 29, 2019
|Beta 3 and soft string freeze.
|February 7, 2019
|Release 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.
|February 20, 2019
|Dry run for release of WordPress 5.1 and 24 hour code freeze.
|February 21, 2019
|Target date for release of WordPress 5.1.
To get involved in WordPress core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development, head on over to Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and pick a 5.1 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 ticket 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.1, development is discussed at a weekly meeting in the #core Slack 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!