Dev Chat Agenda for August 4, 2021

Here is the agenda for this week’s developer meeting to occur at August 4, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

Bringing to your attention some interesting reads and some call for feedback and/or volunteers

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #core, #dev-chat

A Week in Core – August 2, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between July 26 and August 26, 2021.

  • 24 commits
  • 24 contributors
  • 85 tickets created
  • 7 tickets reopened
  • 58 tickets closed

Pending the appointment of the WordPress 5.9 team, a number of tickets have been fixed, waiting for the next minor releaseMinor 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). No release date is yet available for 5.8.1, but it should arrive in a couple of weeks.

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Build/Test Tools

  • Post a message to #core in 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/. when a workflow fails – #52644
  • Remove the check for changes to version-controlled files in the Test Old Branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". workflow – #53799
  • Revert the test and coding standards changes in [51511]#52644
  • Split packages and blocks to their webpack configs – #53690

Bundled Themes

  • Remove extra trailing spaces from translatable strings in 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. patterns – #53774

Coding Standards

  • Apply some alignment fixes from composer format#53729
  • Coding Standards: Fix typo in the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. function name for handling the password reset button – #53359
  • Code Modernization: Silence the deprecation warning for missing return type in JsonSerializable_Object#53635
  • Add missing documentation for the minute parameter of WP_Query#53399

Documentation

  • Clarify the @return value for WP_Filesystem_Base::getnumchmodfromh()#53399
  • Correct @return type for WP_Filesystem_Base::getnumchmodfromh()#53793
  • Correct the documented allowed range for the minute and second parameters of WP_Query#53399
  • Document the $wpdb global in WP_Debug_Data::get_mysql_var()#53845
  • Fix typo in the WP_Upgrader::install_package() description – #53399
  • Replace $this in hook param docs with more appropriate names – #53457

Networks and Sites

  • Replace two remaining occurrences of “blogblog (versus network, site)” with “site” in user-facing strings – #53775

Site Health

  • Add some more MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. information to the Site Health Info screen – #53845

Site Health

  • Standardise site health check status message punctuation – #53594

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

  • Pass correct default value for $post_id to wp_terms_checklist() in the posts list table – #43639

Themes

  • Add “Template Editing” to the list of WordPress theme features – #53556, #meta5802
  • Make sure get_theme_mods() always returns an array – #51423

Upgrade/Install

  • Add files for 5.8 to the $_old_files list that were missed – #53702
  • Avoid creating nonce during installation – #53830
  • Skip any node_modules directories when removing Genericons example.html files on update – #52765
  • Store correct result when bulk updating plugins or themes – #53002

Props

Thanks to the 24 people who contributed to WordPress Core on Trac last week: @SergeyBiryukov (3), @desrosj (3), @audrasjb (3), @jrf (2), @johnbillion (2), @donmhico (2), @mukesh27 (2), @afragen (2), @pbiron (1), @ocean90 (1), @WFMattR (1), @aristath (1), @youknowriad (1), @poena (1), @pwtyler (1), @tareiking (1), @bobbingwide (1), @zodiac1978 (1), @xknown (1), @hellofromTonya (1), @sanketchodavadiya (1), @swissspidy (1), @schlessera (1), and @ankitmaru (1).

Congrats and welcome to our 2 new contributors of the week! @pwtyler and @tareiking ♥️

Core committers: @sergeybiryukov (15), @desrosj (5) and @johnbillion (4).

#5-8, #meta5802, #week-in-core

Devchat summary, July 28, 2021

A week after the release of WordPress 5.8, @desrosj led a well attended but quick chat on this agenda.

Highlighted blogblog (versus network, site) posts

Jonathan drew the group’s attention to these posts:

He also added a late post of his own:

If you’d like to help with 5.8.xx minor releases, leave a comment on that post.

To-do items on 5.8

Moving on, @desrosj opened one last review of the 5.8 release and asked the group for retrospective comments and other feedback.

In reply, @chanthaboune said she’d likely have her retrospective up later in the day. And she said @matveb will shortly have some thoughts about features to target for 5.9.

Remember, also, that trunk is open now, so if you’re a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component., keep committing whatever you feel is ready! (Ed. note: Plus, we’re also in alpha for 5.9, so whether you’re a committer or not, if you’re passionate about bringing a new feature into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., now is the time to do what it takes to land it.)

Component maintainers

@sergeybiryukov checked in with news on Build/Test, where ticketticket Created for both bug reports and feature development on the bug tracker. #53363 has details on some 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 updated naming to follow established conventions.

On U[grade/Install, Sergey added a second plug for his feedback request on the updater proof of concept highlighted above.

Open Floor

Above, in highlighted posts, you probably noticed that @desrosj asked for comments on his minor-releases post if you want to help with the 5.8.x minors. He actually added that suggestion in Open Floor.

#5-8, #core, #dev-chat, #summary

Dev Chat Agenda for July 28, 2021

Here is the agenda for this week’s developer meeting to occur at July 28, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Review

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-8, #agenda, #core, #dev-chat

Dev Chat Agenda for July 21, 2021

Here is the agenda for this week’s developer meeting to occur at July 21, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Schedule Review

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-8, #agenda, #core, #dev-chat

WordPress 5.8 Release Day Process

We’re less than 24 hours away from WordPress 5.8! If you would like to help with the final steps of the release, here is how you can join in.

The current plan is to start the release process at Tuesday, July 20, 2021 1500 UTC 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.

The major version release process can take a bit more time than the Betas or Release Candidates do, particularly if we run into any last minute issues that need to be addressed.

The Release Process

We will be working through the Major Version Release process for anyone who wants to follow along. Earlier today the pre-final release dry run was coordinated in #core (Slack archive).

How You Can Help

A key part of the release process is checking that the ZIP packages work on all the different server configurations available. If you have some of the less commonly used servers available for testing (IIS, in particular), that would be super helpful. Servers running older versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher and MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. will also need testing.

There are two ways to help test the package:

  • Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ to test: wp core update https://wordpress.org/wordpress-5.8.zip
  • Directly download the 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./RC version (e.g., https://wordpress.org/wordpress-5.8.zip)

In particular, testing the following types of installs and updates would be much appreciated:

  • Does a new WordPress install work correctly? This includes running through the manual install process, as well as WP-CLI or one-click installers.
  • Test upgrading from 4.0.33, 4.9.18, 5.7.2, and 5.8 RC 4 as well as any other versions possible
  • Remove wp-config.php file and test fresh install
  • Test single site and multisitemultisite 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/networknetwork (versus site, blog) (both subdirectory and subdomain) installs
  • Does it upgrade correctly? Are the files listed in $_old_files removed when you upgrade?
  • Does Multisite upgrade properly?

Finally the following user flows, on desktop and mobile, would be great to validate work as expected:

  • Publish a post, including a variety of different blocks.
  • Comment on the post.
  • Install a new pluginPlugin A 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-party/theme, or upgrade an existing one.
  • Change the site language.
  • If you’re a plugin developer, or if there are complex plugins you depend upon, test that they’re working correctly.

You can even start this early, by running the WordPress 5.8 RC4 packages, which are built using the same method as the final packages.

#5-8, #release-process

Dev chat summary: July 14, 2021

Well now! We have less than a week left in the 5.8 release cycle, and this was its final devchat.

@francina welcomed several new attendees and opened the chat with this agenda (props @jeffpaul!).

Notable blogblog (versus network, site) posts

5.8 RC 3 is here. Please test the release and report any last-minute issues!

A Week in Core for last week highlights 44 contributors, two of them new and 14 active committers. Props @audrasjb!

Ever wondered why we use chat instead of video? So did Arnold Wright KITI, and here’s the discussion that followed.

Three items of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ news:

  • Gutenberg reached 11.0 with a basketful of enhancements.
  • Check out the latest Editor chat summary, here.
  • And there’s a late-breaking dev note that pertains to the editor APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways..

If JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. is your jam, the Core JS team is changing its office hours.

And, the mobile teams would really like you to test their respective 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. releases, for iOS here and for Android here.

Upcoming release: 5.8

A final schedule reminder: we’re in the RC period, with a hard string freeze. RC 4 is slated for Thursday, July 15 at 16:00 UTC (Ed. note: basically now, at this writing) and final release in FIVE DAYS on Tuesday, July 20.

@desrosj gave a detailed report on what still needs to happen before Tuesday. He also covered what’s going in the RC 4 release. Please check out his review and pitch in if you can!

If you’re interested in the process of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development, you’ll want to see the discussion that followed, about the tickets involved and how they arose. The team is following a new, more traditional process that @francina championed for this release and has also had strong public advocates in @azaozz, @audrasjb, and others.

@chanthaboune raised this Polyglots/WP-CLI ticket and asked for some quick eyeballs.

Component maintainers

@sergeybiryukov reported in for Build/Test Tools: they’re working hard to modernize the WordPress unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. suite with tickets #53363 and #53491.

Open floor

@francina used the last ten minutes of the chat to go back to @Arnold W. K.’s questions and give more context about how the Core team does things.

She also asked first-time attendees how they happened to find their way to the channel.

You can catch the discussion verbatim here.

(Ed. note: Updated Friday, July 16) @webcommsat reminded the group of two things:

Marketing is still accepting ideas for social-media posts on this Social Sharing Google Doc. Questions? Ask her, @marybaum or @meher.

Marketing also still wants to know: what’s your favorite feature? Add your nomination, and why it’s your favorite, to this Google Doc.

#core, #dev-chat, #summary

Dev Chat Agenda for July 14, 2021

Here is the agenda for this week’s developer meeting to occur at July 14, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Schedule Review

  • RC 2 released last week and RC 3 yesterday, now under hard string freeze
  • Email to pluginPlugin A 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-party/theme authors on Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. went out last week
  • No further 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. scrubs scheduled, so please highlight issues of concern directly in #core
  • 5.8 release in SIX days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-8, #agenda, #dev-chat

Dev Chat summary, July 7, 2021

With just two weeks left in the 5.8 release cycle, @jeffpaul led the devchat on this agenda.

Announcements

RC 2 has landed! And it needs you, to help test it in as many ways as possible and chase down any last-minute bugs. For details, check out the RC 2 release post here.

As it happens, @desrosj reported in and said the release is in great shape:

The milestone only has three 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. tickets remaining that may require changes (excluding release related task tickets and two tickets needing only to be backported). We are in great shape heading into RC3 and final release. 

@desrosj

Blogblog (versus network, site) Post Highlights

In the afternoon chat, @jeffpaul led off with the RC 2 release post above, and it is indeed worth a second read, if you’re so inclined.

Other posts of note:

The 5.8 Field Guide is out. Docs lead @milana_cap has done a masterful job of pulling it all together. So if you’re getting a theme or a pluginPlugin A 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-party ready for 5.8, the Guide is your most reliable source of timely, topical information on the changes that will affect your products and the processes you use to get them out the door.

Catch up on the latest feedback the Full Site Editing crew has received with this post from @annezazu. And while we’re at it, here’s the FSE team’s latest chat summary.

And @audrasjb is back with another Week in Core, celebrating 52 contributors (five who are brand-new!) and nine committers who got things going this week.

@jeffpaul thanked the authors and everyone who commented or otherwise helped share news or knowledge this past week and shared this reminder:

We are now in the RC period. That means we’re in a hard string freeze, and the final planned 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)., RC 3, is now just FIVE days away, on July 13. The 5.8 release is TWELVE days away, on July 20.

(Ed. note: Where has the year gone?)

With no seemingly urgent business connected to the release (see @desrosj on the state of the milestone, above) @jeffpaul referred the group to a post from @mapk on care and influence in the WordPress community.

Components check-in

@sergeybiryukov reported in on Build/Test Tools. Referring the community to this ticket on PHPUnit 8.x, he described the challenges that come with adding support for PHPUnit 8.x and 9.x, since they’re not compatible with versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher older than 7.1.

@marybaum commented that Help/About is looking good and then took a minute to thank all the people involved with the About page.

Open Floor

Pivoting from @sergeybiryukov‘s discussion of PHPUnit 8.x and 9.x, @azaozz opened a discussion of when WordPress might stop supporting PHP versions earlier than 7.1. The upshot, according to @sergeybiryukov: WordPress ends support for a PHP version when it’s running fewer than 5% of sites. At the moment, 8.83% of WordPress sites run PHP 5.6, and 5.23% are running on PHP 7.0.

Marketing Rep and Help/About co-maintainer @webcommsat would like to know what your favorite 5.8 feature is, so the Marketing team can write some social-media posts about it. You can share your favorites with her or @marybaum directly or in threads on this week’s marketing meeting, which run asynchronously through Friday.

@webcommsat would also like some more posts on key features in the release. To add one or more, use the commenting feature in this Google Doc.

#5-8, #core, #dev-chat, #summary

Dev Chat Agenda for July 7, 2021

Here is the agenda for this week’s developer meetings to occur at July 7, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Schedule Review

  • RC 1 released last week and RC 2 yesterday, now under hard string freeze
  • Working on Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. email to pluginPlugin A 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-party/theme authors
  • No further 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. scrubs scheduled, so please highlight issues of concern directly in #core
  • RC 3 in 6 days on Tuesday, July 13th
  • 5.8 release in 13 days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-8, #agenda, #dev-chat