@audrasjb led the chat on this agenda. You can also read the Slack logs.
Highlighted blog (versus network, site) posts
Bringing to your attention some interesting reads and some call for feedback and/or volunteers:
Worth mentioning:
Thanks to the 42 contributors of the past week, including 7 new contributors! Kudos to the 4 core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too.
A Week in Core – September 20, 2021
Upcoming releases updates
Next minor 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.(s)
@desrosj and @circlecube are still leading the 5.8.x releases.
They will publish a schedule for 5.8.2 and –if needed– 5.8.3 on September 23.
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.
Concerning the next major release —WordPress 5.9— a planning roundup was published a couple weeks ago.
Worth noting that @chanthaboune proposed a review of the upcoming 5.9 key features in the last issue of the WordPress.org podcast.
@audrasjb proposed to start to schedule 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. scrubs for the milestone. He will run the first scrub of 5.9 on Thursday September 23, 2019 at 20:00 UTC.
Reminder: everyone is welcome to run a bug scrub on 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. If you are interested, please read this handbook post: Leading bug scrubs. And yes, that’s a call for volunteers 🙂 Please add a comment below if you want to help.
For 5.9, @hellofromtonya pointed out that it would be nice to try to also plan some APAC-friendly bug scrubs when possible.
Component maintainers updates
Help/About – @marybaum
Build/Test Tools – @sergeybiryukov
- Some changes were implemented to make the PHPUnit Polyfills loading more flexible and improve the related messaging. See changesets 51810-51813 and ticket Created for both bug reports and feature development on the bug tracker. #46149 for more details.
- The PHPUnit Polyfills package and related test infrastructure changes are now backported to a few older branches (WP 5.8 to 5.2). This makes it easier for developers to continue testing on multiple versions of WordPress while adding tests for newer versions of PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher, which require more modern PHPUnit practices. See changesets 51838-51840, 51843-51846 and ticket #53911 for more details.
- Work is now complete on Modernizing to the Latest PHPUnit version. Dev 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, and 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. is being reviewed and plan is to publish on Monday.
- PHP 8.1: work is nearly complete, i.e. identified through tests. Will be shifting shortly into community feedback and open call for contributions to identify and help fix compatibility issues.
General – @sergeybiryukov and @hellofromtonya
Internationalization – @sergeybiryukov
- A translator comment was added to clarify the “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. HTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.” string in the Block widget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. settings form. This should reduce confusion for Polyglots translating the string.
Toolbar – @sabernhardt
- @sabernhardt shared a draft of a Toolbar component update post (it’s also available in a Google doc if you want to add comments that way)
Open Floor
From @hellofromtonya: If you want to contribute to the Testing Team, here’s this week’s edition of Week in Test which is a curated list of where testers (of any skillset) are needed this week.
#5-8-x, #5-9, #dev-chat, #summary
