@francina facilitated the chat on this agenda.
Meeting recap by @audrasjb and @marybaum.
Full meeting transcript on Slack
Just a few hours before the chat, the hardworking team behind the plugins and themes auto-updates feature committed it to Core! Congrats to all!
Check out this related ticket Created for both bug reports and feature development on the bug tracker. that adds Help Tabs text to
plugins WP-Admin (and super admin) screens: #50215
If you’d like to be part of the Full Site Editing outreach experiment, the sign-up deadline is now May 22. @chanthaboune noted that’s just to show interest, not a commitment yet.
The next 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 WordPress is in active development (Alpha cycle).
@francina noted the team is not quite complete, but it’s confirmed that @matt will return as release lead The community member ultimately responsible for the Release., @davidbaumwald as co-lead in the role of Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM and @sergeybiryukov as Core tech lead. The 5.5 team will also mentor the 5.6 team.
@audrasjb shared that there are 20 tickets in the milestone. Of those, 17 are closed as fixed.
@whyisjake leads this point release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality., and the group firmed plans for a 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). on June 3 and a final release June 10.
Components check-in and status updates
@whyisjake was exuberant that the core team was able to merge the auto-updates code today. This is going to do a great deal to help people stay on top of updates for a safer WordPress ecosystem.
The merge is just the latest significant step toward the master plan for 2020. Lazy-loading of images merged a few weeks ago, and XML sitemaps is making great progress as well.
On the accessibility 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) side, @audrasjb shared that most of the accessibility team’s main projects for 5.5 are moving forward. Alternate views for posts, users, and comments lists should be ready for review soon.
@johnbillion wanted to note that weekly meetings for Multisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site have restarted, on Tuesdays at 17:00 UTC in #core-multisite. Come join them!
In Site Health, @clorith pointed out that the Theme Review Team has implemented requirements for PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher headers in themes. That move should push users in the right direction for updates.
As well, the Site Health component team has had discussions with hosting about bumping the version for Servehappy dashboard nags.
@dlh wanted to highlight #48416. He recently encountered a use for it again. If you’re interested in the taxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. component, please give it a look.
@sippis reminded everyone to register for WCEU 2020 Online Contributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., which is Thursday, June 4, 2020 at 13:00 UTC. If you don’t register, you won’t get the emails you’ll need in advance, so don’t forget to register.