The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
This post summarises the weekly dev chat meeting from February 27th (agenda, Slack archive).
WordPress 5.1.1 Updates
To allow a little extra time, WordPress 5.1.1 will now be released on March 12. To make the most of the available time, two bugbugA 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. scrubs have been scheduled. You can read more about them on the WordPress 5.1.1 schedule update post.
The are currently 18 tickets milestoned for 5.1.1.
BetaBetaA 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: 21 March, 2019
Release Candidaterelease candidateOne 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).: 17 April, 2019
General Release: 30 April, 2019
The WordPress 5.2 scope and schedule proposal included a suggestion for “feature release leads” to help keep the release running on time. If you’re interested in volunteering, please comment on that post, and mention @chanthaboune.
Updates from focus leads and component maintainers
There have been quite a few ongoing discussions around release cadences, @desrosj has kindly summarised the situation into a post. If you have thoughts or feelings on this topic, please comment on this post:
There are several tickets for pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-partyPHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher compatibility with patches that need testing, feedback, and committing. If you’re able to do one or more of these, please lend a hand! 🙂
The work on reverting the recent bulk ticket close will be kicking off soon. If you’re a component maintainer who does not want to have tickets in your component re-opened, please pingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.”@desrosj know.
General Announcements and Open Floor
@joyously asked about determining if there are test cases for everything, which lead to a discussion about setting up a code coverage tracker. #46373 now exists for researching options, and setting this up.