Dev chat summary, January 26, 2022

@marybaum and @webcommsat led the meeting on this agenda.

The overall focus: celebrating WordPress 5.9, “Josephine,” which landed Tuesday, January 25, after months of hard work by more than 600 contributors and a release squad with @hellofromtonya at the helm.

Announcements

WordPress 5.9, ”Josephine,” is here!

Ahead of the 24-hour code freeze for 5.9, the squad released WordPress 5.9 RC4 on Monday, January 24, 2022. The freeze took effect immediately afterward.

Read the latest developer notes.

Blogblog (versus network, site) posts of note

What’s new in Gutenberg 12.4 (January 19, 2022)

A Week in Core (January 24, 2022)

Join the discussion on 2022 release planning (December 27, 2021 post by @chanthaboune). New document coming

New additions to the agenda:

Preliminary Roadmap 6.0 (January 26, 2022)

Let’s talk about WordPress 6.0 post and video hosted by @annezazu – Hallway Hangout in #fse-outreach-experiment (December 21, 2021)

After celebrations and discussion on the above, @desrosj added two more posts, both from @chanthaboune, to the list.

Our Three Big Ideas for 2022!

Big Picture Goals 2022

As @desrosj pointed out, these are really important for the year ahead. Please have a look and let @chanthaboune know if you have thoughts or questions.

An update

The day after dev chat on Thursday, @chanthaboune published Proposal: 2022 Major Release Timing. Take a look and add your thoughts there!

Major releases

@hellofromtonya congratulated everyone on the historic release and shared that after ten million downloads in the first 24 hours—ten million!—TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. showed a grand total of 17 issues, none of which raised any major issues or concerns. (Ed. note: If you speak the language of nines, where 99.9% uptime or other metric = three nines, the first 24 hours of Josephine showed nearly six nines of flawless performance.)

Looking ahead, Tonya addressed the timing of the first minor. There are patches and pull requests ready for 5.9.1 ready now, and the current thinking is for a quick release as soon as a couple of weeks from now.

She also said she was working on a 5.9 retrospective, planning to publish on Thursday, and it is out now. Please add your thoughts on the process in the comments!

Open Floor

WPDB got major love in Open Floor.

First, @craigfrancis shared ticketticket Created for both bug reports and feature development on the bug tracker. #52506, which updates `wpdp::prepare()` to escape identifiers safely. There were emoji equivalents to a bevy of oohs and ahs from the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers in the group, and @audrasjb marked the ticket Early for 6.0.

Second, @johnjamesjacoby proposed ticket #54877 to fix the occasional exception that a WPDP/MySQLi connection can throw. The group was equally appreciative of that.

With seven minutes to spare, the chat ended with several members running off in search of ice cream.

Want more details? Read the whole chat.

P.S. Want to start contributing to WordPress, and to Core in particular? Come to dev chat and volunteer to craft these summary posts! We refer to the activity as taking notes, but the whole chat is in text, so there aren’t really any notes to take. And how cool is it to be able to say you’re an author on make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/? Pretty cool, I say. — MB

#5-9, #dev-chat, #summary

Dev Chat Summary – January 19, 2022

Link to the start of the meeting in the WordPress Core Slack

Agenda

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @marybaum and @webcommsat led the meeting.

Announcements

WordPress 5.9 Release Candidate 3 is available.

Two key resources:
Help test WordPress 5.9 features
Read the 5.9 Field Guide.

Blogblog (versus network, site) posts of note

Update on the release

@hellofromtonya

5.9 final will land next week on 25 Jan 2022. RC3 yesterday was the last planned release before the final. If blockers or regressions are reported before 5.9 starts its 24 hour code freeze (which starts on 24 Jan), then another RCrelease 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). may happen. As of right now, there are not any reports that warrant another RC. But will keep on on it. 

@jeffpaul: You’re almost there @hellofromtonya, we’re all in support of you and the team, thanks again for everyone’s amazing work!

Release Process summary from @hellofromtonya

  • The release squad is discussing the start time for the release party on the 25th. Stay tuned.
  • The code freeze will start exactly 24 hours before that time.
  • Dry run will be on the 24th and end before that code freeze starts.
  • A post on Make Core will appear in advance to outline the release processes and how you can help.

Thank you to all contributors who made this happen! 

How can you help?

  • Test
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. any reports that come into TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. or 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/ to help teams figure out if a report needs immediate attention. Then come join the 5.9 Release Party to help prep and test the package and get it out into the world! Celebrate.
  • @webcommsat: please share the posts about the release and the RC3 post.

5.9.1 early discussions

@jeffpaul: wait until we see how the forum responses come in post 5.9 since it sounds like nothing needing another RC as of now.

@marybaum shared she and @estelaris would be helping with the release-coordination for the minors, in in the interregnum before 6.0.

@hellofromtonya: I agree with @jeffpaul and points @desroj raised in the release leads channel. Though there are fixes ready for 5.9.1, good to give a week or so for reports to come in within the forums, Gutenberg GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, and Trac. Why? There may be things hadn’t yet surfaced that need priority attention.

@costdev: For reporting issues when testing RC, reproducing reported issues during/triage, and for when reports land in the forums and make their way to Trac, a test report template is available to help narrow down the steps and environments where issues may occur.

Open Floor

a) Request for core agenda to be published 24 hours ahead of a meeting to allow items and links o be more easily added for the discussion. It has not been published this far in advance in the last two weeks. Confirmed.

b) FSE
@annezazu: Join me for a hallway hangout on Thursday 20 January 2022 at 9:00pm UTC to talk about 5.9. It will be held in #fse-outreach-experiment and is meant to be a casual place to chat with other folks in the WordPress space. Bring your questions, pop in and out, etc. It will be recorded and recapped. Previous editions

c) Ticketticket Created for both bug reports and feature development on the bug tracker. #54859: New Welcome’s panel “Edit styles” link does not seem to work

@audrasjb: relating to 5.9: should we consider #54859 as a blockerblocker A bug which is so severe that it blocks a release.? any thought about this small (but annoying) issue? Can probably be skipped to a minor unless there is a RC4.

@hellofromtonya: That issue needs testing and more discussion to determine what should happen and if reproducible. But does not seem to be a blocker for the major releasemajor 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..

If it’s merely a bad link, that’s one thing and easily fixable. If it’s something else, then discussion needs to happen about resolution.

@audrasjb: The expected behavior would be to open the Global Styles panel.

For now, the two links in the welcome panel both lead to the same screen (*), which is, indeed, annoying.
(* on 5.9 + TT2)

ironprogrammer: The first time you open Styles, it has the nifty tutorial, so it’s a shame to miss that when you come here the first time…

@hellofromtonya: The question is: What should the link be to open the panel (this would be fixable in Core)? Or is the panel not wired to a link (this would be a Gutenberg issue)?

@audrasjb: I don’t think it’s a blocker. But I think it’s annoying and it’s not a super user experience when associated to the Welcome panel which is supposed to show all the amazing stuff we shipped in this release. What I try to say is that it’s more a “communication issue” than a technical one. @jeffpaul agreed not a blocker.

@hellofromtonya:

  • let’s get it fixed.
  • Then if there are other issues that pop, it can be bundled into a RC4.
  • I agree it has to be fixed upstream in Gutenberg and then packages released and backported to Core.

@hellofromtonya: Depends upon if the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is correct or not. If not correct, then it can be fixed in Core. Else, yes, I agree it has to be fixed upstream in Gutenberg and then packages released and backported to Core.

@audrasjb: I’m currently opening an issue upstream, and also, I’m searching for any Gutenberg behavior that would open the panel based on the URL hash.

@audrasjb: If so, we could fix this on Core side.

@desrosj: I think we should be worried about making the right decisions for our users and not to avoid publications writing unfavorable pieces about us.

@marybaum: A thing that seems like not-a-blocker to us can affect UXUX User experience profoundly, which in turn can damage perception.

@hellofromtonya: For now, it’s prioritized and in the 5.9 milestone. I’ll take ownership of this issue with priority to fix it. Once fixed, then a decision can be made as to whether to do another RC or release it in.

@hellofromtonya: There are known bugs that do impact UX that are in 5.9.1. Yes, the release seeks to ship a solid experience. And yes, it would be great to have a perfect UX across the board. In this case, the link does take the user to the Site Editor where the Styles can be opened with another click. The experience is not broken nor perfect. But I don’t see it as a major blocker to the final release. But let’s see if it can be fixed quickly and if other issues come in to warrant another RC. 

@audrasjb pinged the editor team
An issue has been reported that is a good to get fixed in case there’s a 5.9 RC4.
Clicking wp-admin/site-editor.php?styles=open in the Welcome panel is expected to automatically open the Styles panel in the Site Editor.  It is not. Is this the right link? Or is this a 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. that needs to be fixed? https://github.com/WordPress/gutenberg/issues/38090
https://core.trac.wordpress.org/ticket/54859Posted in core-editor 

d) Dev notesdev 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 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.

@webcommsat and @courane01: For the work on Learn WordPress and social media, are there more dev notes on the release to come? Working on social media for LearnWP.
@marybaum: it looks like one more – https://github.com/orgs/WordPress/projects/11/views/8

Props: Meeting notes summary by: @webcommsat and light editing by @marybaum

#5-9, #dev-chat, #summary

Dev Chat summary: December 22, 2021

Dev Chat agenda.

The meeting was led by @webcommsat and @marybaum.

Start of the Dev Chat meeting in the Make WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/..

You can find last week’s notes in at Dev chat summary, December 15, 2021.

Announcements

Please join the discussion @chanthaboune has started on 2022 release planning.

WordPress 5.9 release updates

The WordPress 5.9 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. 4 has landed. Please download and test! Thanks to everyone who has been involved in the release so far and getting the Beta 4 out the door.

Beta 4 fixes 20 bugs that surfaced in Beta 3. Please test them and report your findings on the announcement post.

It does not look like a Beta 5 will be necessary at this stage. RC1 is scheduled for January 4, 2022. The revised 5.9 release schedule.

If there are no big issues, the release will continue to follow the plan from November 22, 2021 – more details on the 5.9 post.

Blogblog (versus network, site) posts to note

What’s new in Gutenberg 12.2? (December 22, 2021)

A Week in Core. Three new contributors to core this week – welcome to them all.
The next New Contributor Meeting for core is scheduled for 12 January 2022 at 19:00 UTC. If you have any questions on contributing to core before that, just bring them up here in #core any time outside of any ongoing meeting, or in the open floor section of the weekly dev chat, and someone should follow up.

Please continue to share the Help test WordPress 5.9 features. This replaces the ongoing call for FSE testing promotions until after 5.9 is released. Thanks @annezazu

WordPress 5.9 is now available for translation. The new theme with this release, Twenty Twenty-Two, can also be translated. Thanks to all the polyglots across the world who have started working on translating the next release.

The annual community survey closes next week on December 30, 2021. Still time to complete it.

Component Maintainers update

Build/Test Tools Component

Update via @sergeybiryukov: Some enhancements were made to the 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:

  • Reduce the use of unnecessary randomness in tests to increase the overall reliability of the tests. See ticketticket Created for both bug reports and feature development on the bug tracker. #37371 for more details.
  • Remove an assertion in filter_rest_url_for_leading_slash(). This assertion could mask the fact that some other tests don’t perform an assertion. See ticket #54661 for more details.

Thanks @johnbillion and @johnillo, a new contributor! 

Date/Time, General, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks

Update via @sergeybiryukov: No major news this week.

Quick/Bulk Edit component

Update from @nalininonstopnewsuk: For the Quick/ Bulk Edit component, we are continuing to work through and reading all the previous materials in the background while the primary focus is on 5.9. We want to run a 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. scrub on the tickets the week after 5.9 is out. 

About / Help page component

Update via @webcommsat: More updates have been done this week on the text and Figma. Will update the ticket today.

You can also join the collaborations cross-team on social media posts on the release features.

Open Floor

  1. Proposal for an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ticket. 

@maksimkuzmin  would like some comments on this message in Slack before Jan, 12?

Will raise a ticket and provide a UIUI User interface draft. Design input suggested.

Discussion suggested moving the ticket to 6.0.

2. Request to add thoughts on the Performance Team GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Issues and Projects. 

@Sergio Scabuzzo from the measurement group in the team encouraged contributors to look at the ideas. https://github.com/WordPress/performance/projects

3. A second enhancement proposal

@maksimkuzmin suggested: Most of the times bespoke themes built relying on page templates to set up specific page to the specific type of page. E.g. Search Page is bound to the page-search.php template in the code. The major lack of functionality is to have a function that will quickly retrieve page(s) by the given template name. Without building a WP Query, etc. Sort of get_page_by_template( $template_file ).

This enhancement will further be discussed and potentially reconsidered in a pre-existing ticket: #16264.

4. Bug report potentially related to 5.9

@afragen: FYI, posted bug report and PR for #54682, believed to be 5.9 related.

Next meeting

Dev Chat will take place next week, Wednesday 29 December 2021 at 20:00 UTC in the Make WordPress Core Slack for a quick check-in.

Props: Dev Chat summary by @webcommsat. Thanks to @marybaum and @sergey for proofing.

#5-9, #dev-chat, #summary

DevChat meeting summary, December 15, 2021

Agenda.
Meeting led by @marybaum, Notes by @webcommsat

Start of meeting on the Make WordPress 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/./ CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel

Announcements

The WordPress 5.9 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. 3 has landed, after a lot of very hard work by a lot of very dedicated contributors. Please download and test! Note: This beta focused on the bugs that showed …

WordPress 5.9 Beta 3 announcement 

Relevant posts

Since Beta 214 bugs have been reported by contributors and need testing. If you can help, please report your findings on the announcement post.
Editor chat summary: 15 December, 2021 highlights improvements made by the team.
What’s new in Gutenberg 12.1?
A Week in Core.
And remember that the release schedule has been revised.
WordPress 5.9 Beta 2
A Week in Core – December 13, 2021

5.9 release update

From @hellofromtonya:

  • There will be a 5.9 Beta 4 next week, Dec 21st.
  • 5.9 RC1 is on Jan 4th. That’s the code freeze. There are open issues both in Core TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and 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/’s Must-Have project board. The fixes for those issues will need a beta.
  • Appreciate folks testing, reporting issues, investigating, helping to fix, etc. Thank you! 
  • Beta 4 post – @marybaum, @estelaris, @webcommsat confirmed they would be available to work on the post.

Soft string freeze

A soft string freeze or “soft freeze” is announced when all the strings of an upcoming WordPress release are frozen, except for the strings of the About page

@sergeybiryukov: minimal string changes can still be allowed in “soft freeze” on a case-by-case basis if necessary, there’s an i18n-change keyword for that. 

@jeffpaul: RC1 is hard string freeze and not to interpret “code freeze” as no more changes so much as fixes for regressions found in Beta testing. @hellofortonya: And fixes can happen for regressions and bugs found during the RCrelease 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). cycle.The hope though is that all known bugs are fixed during beta before getting to RC.

@ryelle : #54489 also an exception to the soft string freeze? it has new strings, and still needs copy feedback (can come back to this during open floor if needed). It is an exception to the string freeze as it is connected to the About page area of work.
#54489: Update the Dashboard welcome banner for 5.9

@ryelle: Technically it’s not “the about page”, so I wasn’t sure if it all applied it just references the design. It’s a new iteration on the Welcome panel on the dashboard.

@hellofromtonya: I think folks intended for that Welcome panel to go past string freeze. or at least that was my understanding.

@marybaum: I don’t recall seeing art like this on a dashboard, other than as the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. art of the four pages About, Credits, Freedoms and Privacy.

@ryelle: On the dashboard (like basic /wp-admin/), there’s the Welcome panel – “Welcome to WordPress! We’ve assembled some links to get you started…” – this ticketticket Created for both bug reports and feature development on the bug tracker. totally redesigns it to introduce new art mirroring the About page, and updated copy and links.

About page 5.9 and associated resources/ marcomms:

  • @marybaum: estimated that layout, art and copy will be finalized for the About page by Monday, to allow time for @ryelle time to work on the code.
  • @webcommsat: we continue to request dev and extenders input into benefits they are expecting from 5.9 for social media messaging and to link in with training. More on this in last week’s devchat summary under the Component Maintainers/ About page heading.

Component maintainers updates

Components reports are being skipped until after 5.9.

Open Floor

@schlessera: raised two concerns that require workarounds with 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/ currently.

Trac Ticket 54634
We already had several similar bugs, where a check for wp_installing() was missing to wrap DB operations. I already provided an initial patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to fix this one. Without that patch, you get a fatal if you try to install a new 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).

I found it with a functional test that installed a new network using Behat. However, I think this is not as easy to test with the “unit”-tests of WP Core. I’m happy to add a test if someone can provide pointers into how this is typically done for Core.

@sergeybiryukov: Unit tests start by running the WordPress installation first in the bootstrap file, so wouldn’t be able to catch issues like this.

@schlessera: These tend to crop up from time to time due to the procedural nature of WP, where everything is sort of tied together based on order of executing. It only breaks on trunk, but not on current stable for me. Might be due to some other, seemingly unrelated change. In general, all DB operations like that should be safeguarded, as WP itself is being executed to prepare the DB for WP. Is this something we can still fix for 5.9? Seems like a simple bugfix. @sergeybiryukov agreed, as in line with similar fixes in the past.

@schlessera: I noticed it during the tests of wp core install --network. These tests have been passing for all the previous stable versions of WP, and have started failing at some point with the latest trunk version, so I assume yes. The 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. was probably always there, but some re-ordering of something unrelated has created the conditions for it to be triggered.

The new default theme has hard dependencies on WP 5.9 code. This seems to make sense given it requires at least 5.9 to work. However, if that theme is active and you try to downgrade WP, you can get an immediate fatal error. What’s more, the theme states it requires WP 5.3, so this currently cannot even be detected.

@sergeybiryukov: I think historically bundled themes aim to be comparable with at least one or two previous major versions.

@schlessera: Can we have the theme be built in such a way that it doesn’t flat-out fatal when downgrading even to the very last version before an upgrade? @audrasjb thought this was feasible. @sergeybiryukov said core should have safeguards in place to check with an appropriate message, and there is some prior art in older themes. Looking at the inc/back-compat.php file in older themes might be helpful for reference, they have similar checks.
@schlessera: It doesn’t have to produce any meaningful output on the frontend, it can still produce errors, but it should do so gracefully without taking the entire server down. 

@schlessera: I haven’t created a ticket yet, as I wanted to first check what the consensus is about this.

More on this discussion can be found on the core slack at this timestamp.

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

Dev Chat Summary for November 24, 2021

@hellofromTonya led the weekly meeting at 20:00 UTC. Here is the meeting agenda.

Link to this <devchat> in #core on Making WordPress 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/..

Notable News and blogblog (versus network, site) posts

Team Reps

  • @marybaum will be a new Core Team Rep for 2022.
  • Thanks to @francina for serving in this role!
  • @audrasjb will continue in this role until another team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. is found.

Interested in being a Core Team Rep? Reach out to @audrasjb.

WordPress 5.9

  • @jeffpaul asked if there are any 5.9 blockers that are in specific need of help and asked what type of help they need (engineering, design, testing, etc).
  • @hellofromTonya posted an update on 5.9 blockers and scheduling. Design help is needed for Global styles & Design tools.
  • There is an open Call for Testing for Safari.
  • Everyone is invited to help wherever possible.
  • The release squad is keeping a daily close eye on progress, needs, and any blockers that might surface. Discussions and updates are centralized in the #5-9-release-leads channel on Slack.

Component Team Updates

Build/Test Tools

@sergeybiryukov gave an update:

  • Dependabot scanning is now configured for GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Actions. This eliminates the need to manually check all GitHub Actions used within workflow files for updates. See ticketticket Created for both bug reports and feature development on the bug tracker. #54503 for more details.
  • NodeJS is pinned to the 14.x version in the .nvmrc file to ensure contributors are able to contribute without issue until compatibility with version 16.x can be confirmed in both trunktrunk 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. and the 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/ repository on GitHub. See ticket #54502 for more details.
  • Some PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher warnings from stdClass::__invoke() callback mocks were fixed in REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. tests. See ticket #53844 for more details.
  • The timeout for GitHub Actions jobs was lowered so runaway or stalled processes don’t risk running for the default timeout duration of six hours. See ticket #53363 for more details.

@sergeybiryukov shared: No major news this week

Open Floor

  • @afragen asked for feedback on the Plugin Dependencies project for WordPress 6.0. Reach out to @peterwilsoncc if you wish to have editing access.
  • @jeffpaul asked how we are progressing on the Pre Beta 1 tasks and asked if there are any items that need help.
  • @hellofromTonya replied that there are some Dev notesdev 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 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. that need to be compiled and published.
  • @audrasjb has been marking tickets that need Dev notes.
  • @mkaz noted that documentation for WordPress 5.9 could use some help and posted a link to the requirements. Contributors are invited to reach out to @mkaz with any questions.
  • @jeffpaul is working on the WordPress 5.9 HelpHub page.
  • @abhanonstopnewsuk noted that the latest checks for the About and Help page were carried out on Monday November 22, 2021. The next check is on Monday November 29, 2021 at 20:30 UTC.
  • @audrasjb will be leading a 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. scrub on November 25, 2021 at 21:00 UTC. See the 5.9 Bug Scrub schedule.
  • With Thanksgiving taking place in the US on November 25, 2021, @hellofromTonya thanked the community for all contributions.

Props to @costdev for writing the devchat summary.

#5-9, #dev-chat, #summary

Dev Chat Summary for November 17, 2021

@marybaum and @webcommsat led the weekly meeting at 20:00 UTC. Here is the meeting agenda.

Link to this <dev-chat> in #core on Making WordPress 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/..

Please note that depending on your timezone, the time may have changed with the end of daylight saving time.

Blogblog (versus network, site) Post Highlights and announcements

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

Components check-in and status updates

Build/Test Tools

  • The results of PHP_CodeSniffer across workflow runs are now cached. This allows for rescanning only changed files, making subsequent scans significantly faster. See ticketticket Created for both bug reports and feature development on the bug tracker. #49783 for more details,
  • Plugins and non-bundled themes are now excluded from PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher compatibility scans. This allows the scans to run only on files included in the final WordPress package. See ticket #54425 for more details.
  • Some remote HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. requests in REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. tests are now mocked to address timeout failures. I think this could use some more discussion though to verify the intent of the tests, and whether they were created specifically to test the WP.org 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. response. See ticket #54420 for more details.
  • The default GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ 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". was changed from master to trunk. See ticket #54399 and the post on make/core for more details.
  • No major news this week 

Help/About component

  • @marybaum and @webcommsat have been running 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 weekly, and will continue to have checks-in every Monday for the next few weeks, but at a new time of 20:30 UTC.
  • This week they spent time exploring the About Page and centralizing images which can be used for multi-purposes.

Toolbar

  • The anchor link bug fix (#46371) is committed toward the 5.9 release (thanks!), and the new “Edit site” link still needs to be adjusted for narrower screens (#54441).

Site Health

  • An issue in trunktrunk 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. for 5.9 could do with some input on the best route forward to solving https://core.trac.wordpress.org/ticket/54351 . The issue touches on the WP Filesystem handlers as well, and how they may need more sanity checks.

Quick Bulk Edit component 

@marybaum@Nalini and @webcommsat are starting to review tickets for future releases.

Other components

There are some components without maintainers if you find one that would be interested to help move forward. 

Open Floor

PHP 8.1 by @sergeybiryukov

  • PHP 8.1 is scheduled for release next week, on November 25, and I would like to discuss the state of PHP 8.1 support in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • After commiting #51968, there are still more than 60 errors when running the PHPUnit test suite on PHP 8.1
  • Shall we continue adding ad-hoc fixes or shall we pause PHP 8.1 fixes and start a more structural discussion about input validation?
  • The “errors” in the test suite are PHP 8.1 deprecation notices that will not affect users. WordPress is not PHP 8.1 compatible. It’s also not 8.0 compatible. There are larger architectural discussions needed to figure out how to become compatible as stated by @hellofromtonya.

FSE Outreach Program call for testing

There are two weeks left for testing these two versions

Bug scrubs continue; check out the timetable.

#5-9#core#dev-chat#summary

#5-9, #dev-chat, #summary

Dev Chat Summary: November 3, 2021

@francina led the weekly meeting at 20:00 UTC. Here is the meeting agenda.

Link to this <dev-chat> in #core on Making WordPress 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/..

Notable news and blogblog (versus network, site) posts

Component Team Updates

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

  • PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 compatibility fixes #53635
  • PHP Coding Standards fixes for 5.9 #53359
  • Removed role="navigation" from Core & Bundled Themes #54054
  • Permalinks: sanitize non-visible characters. #47912

@francina and @audrasjb highlighted the call for new Core Team reps for the next calendar year, emphasized reps do not need to be experienced contributors or developers to fill the role and outlined some of the main tasks.

Also, contributors are still needed for the WordPress 5.9 Release Squad (details on the responsibilities).

Build/Test Tools

  • Preliminary work on visual regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. tests in Core. #49606
  • Continuing work on end-to-end (e2e) tests in Core. #49507
  • Add missing @covers to PHPUnit tests. #39265
  • Improving Slack Notifications via GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Actions. #53363

Date/Time

  • Improved inline documentation #53399

About/Help

  • Next 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. scrub is Monday, November 8 at 19:00 UTC, following three prior scrubs for 5.9.

Editor

  • 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/ 11.9 (the last release going into WordPress 5.9) has an RC cutoff of November 5.

Open Floor

  • @hellofromtonya called out the WordPress 5.9 Feature Freeze is November 9. Work then shifts to defect tickets until the 5.9 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. 1 target date of November 16.
  • @francina brought up a Gutenberg PR (36168) to remove the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. menu item when 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. Themes are active. @johnbillion raised #54370 in relation to this change. If you build 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 extends the Customizer, please test with this change!

Watch For

  • WordPress 5.8.2 is currently in RC’s. 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. expected on November 10.
  • WordPress 5.9 Feature Freeze is November 9.
  • Our next Weekly Developer Chat is Wednesday, November 10 at 20:00 UTC

#5-8-2, #5-9, #dev-chat, #summary

Dev chat summary – October 27, 2021

@audrasjb led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

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

After 1.5 year, @francina and @audrasjb decided to pass the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Representative baton for 2022. Everyone can nominate the people they think are best suited to be our new Core team reps, just comment in the above post.

Upcoming releases updates

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.: WP 5.8.2

@desrosj confirmed WP 5.8.2 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). is still planned for Tuesday November 2, with a few tickets including #54207 which has been quite a pain for many, so fixing it sooner rather than later is best.

Next major releasemajor 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.: WP 5.9

First the Release Squad for WordPress 5.9 was published. If anyone is interested in volunteering for one of the roles needing more help, please comment on that post. If anyone has any questions about the release squad roles, some answers are available in the Core team handbook.

@audrasjb and @chaion07 published the 5.9 Bug scrub schedule.

Next scrubs are scheduled on Thursday October 28, 2021 at 20:00 UTC and on Friday October 29, 2021 at 06:00 UTC.

Please note that anyone can run a 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. scrub. Checkout the Leading Bug Scrubs section in the Core handbook.

Also, a WordPress 5.9 Editor Update (26 October) was published.

Component maintainers updates

Build/Test Tools – @sergeybiryukov

The 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/. Notifications workflow was modified to be a reusable one. See changeset [51921] and some follow-up changes on ticketticket Created for both bug reports and feature development on the bug tracker. #53363.

General – @sergeybiryukov

Work has continued on various coding standards fixes in core. See tickets #53359, #54177, #54279, #54295 for more details.

Help/About – @marybaum

Two tickets are getting closer to commit but not completely there. Copy reviews are done, the component maintainers have new patches. Should be able to commit both by next Monday’s component scrub.

Open Floor

@craigfrancis wanted to discuss #54042, as I’d like to make the IN() operator easier/safer, and likewise with quoting table/field identifiers. Given the amount of information shared in the PR, @audrasjb moved this ticket to 5.9, but it will need a deep review as soon as possible to be committed ahead of the feature freeze which is the target for such enhancements.

@marybaum asked if there is still feature freeze a week or so ahead of 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. 1. Feature freeze is scheduled on November 9th, and Beta 1 is on the 16th.

@afragen shared a message of @peterwilsoncc from the #core-auto-updates Slack channel. The Upgrade/Install team will meet in this channel on next Tuesday to discuss a proposal concerning the 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 Dependencies feature.

#5-8-x, #5-9, #dev-chat, #summary

Dev chat summary – October 20, 2021

@audrasjb led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

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

Worth mentioning:

Thanks to the 30 contributors of the past week, including 7 new contributors! Kudos to the 5 coreCore 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 – October 18, 2021

Upcoming releases updates

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)

Please note that 5.8.2 was deferred due to the lack of ready-to-ship tickets. WP 5.8.2 RCrelease 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). is scheduled on Tuesday November 2, 2021. With a final release on Wednesday, November 10, 2021.

Reminder: @desrosj and @circlecube are co-leading the 5.8.x releases. The 5.8.x point releases are coordinated in the #5-8-release-leads 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. This channel is public and will be archived once 5.9 is released.

From @desrosj: If there is anything you’d like to see released prior to 5.9, please make sure to flag it and help bring the ticketticket Created for both bug reports and feature development on the bug tracker. to a resolution!

Next major releasemajor 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.

First announcement, it’s a GO for the main 5.9 features: WordPress 5.9 Feature Go/No-Go | October 14, 2021 🎉

@audrasjb and @chaion07 published the 5.9 Bug scrub schedule.
Please note that anyone can run a 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. scrub. Checkout Leading Bug Scrubs in the core handbook.

@chanthaboune added that a Release Squad will be announced soon.

Twenty Twenty-Two was introduced a couple week ago. As usual, there is a public repository on GitHub so feel free to help testing the theme, and to contribute to this project.

Component maintainers updates

Build/Test Tools – @sergeybiryukov

A readme file for end-to-end (e2e) tests was added to WordPress core. It provides instructions of how to run the tests locally and links to documentation. This should hopefully result in more contributors writing e2e tests. See ticket #53550 for more details.

General – @sergeybiryukov

Work has continued on various coding standards fixes in core. See tickets #54177, #54277, #54278, #54284 for more details. Thanks to @sabbirshouvo, a new contributor, for improving escaping in various parts of core!

Internationalization (i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.) – @sergeybiryukov

Some Media Library filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. strings now have a context for better translations. See ticket #54238 for more details.

Help/About – @marybaum

Scrubs continue weekly, hosted by @marybaum and @webcommsat. Three tickets will wind up contributing to big changes long-term; a couple of tickets are minor markup changes, so they should be good to go this week.

This component will have another scrub scheduled on Monday October 25, 2021 at 19:00 UTC, focused on tickets slated for 5.9.

Open Floor

@audrasjb asked for an update concerning the new Performance team proposal. @chanthaboune: “There are a few questions that I’m synthesizing into a comment. Performance is, of course, an important thing for the WordPress project as a whole. There were some questions on implementation, though.”

@janthiel asked for a review of #53450. @audrasjb moved it for 5.9 consideration. This ticket will need dev-feedback and a technical review.

@costdev is working on the changes from assertEquals() to assertSame() in the test suite for 5.9 and the “Stage 1” pull request is ready for review: #53364.

@tobifjellner asked for a review of #54300. @audrasjb moved it for 5.9 consideration and added a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. proposal.

#5-8-x, #5-9, #dev-chat, #summary, #twenty-twenty-two

Dev chat summary – October 13, 2021

@audrasjb led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

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

The proposal for a new Make/Performance team was well received by the meeting participants. Encouraging! Please add your feedback in the post comments.

Worth mentioning:

Thanks to the 30 contributors of the past week, including 3 new contributors! Kudos to the 5 coreCore 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 – October 11, 2021

Upcoming releases updates

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)

Please note that 5.8.2 was deferred due to the lack of ready-to-ship tickets.

Reminder: @desrosj and @circlecube are co-leading the 5.8.x releases. The 5.8.x point releases are coordinated in the #5-8-release-leads 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. This channel is public and will be archived once 5.9 is released.

@sergeybiryukov proposed to also backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. changeset [51883] (which is milestoned to 5.8.2) to older branches.

Next major releasemajor 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 some weeks ago.

@kjellr introduced the new bundled theme on Make/Core last week. The first Twenty Twenty-Two meeting was hosted on October 11, in the #core-themes Slack channel.

As usual, there is a public repository on GitHub so feel free to help testing the theme, and to contribute to this project.

The go/no go date for the main WP 5.9 features is October 14.

@audrasjb will run another 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. scrub on Thursday October 14, 2021 at 20:00 UTC.

Reminder: everyone is welcome to run a bug scrub on the #core Slack channel. If you are interested, please read this handbook post: Leading bug scrubs and get in touch with @audrasjb or @francina for details.

Component maintainers updates

Upgrade/Install – @sergeybiryukov @afragen

Work has continued on addressing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher timeouts or missing files during large 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 or theme updates. A couple of solutions were implemented so far, but it looks like the issue might not be fully resolved yet. Any testing and feedback welcome! See ticketticket Created for both bug reports and feature development on the bug tracker. #54166 for more details.

Also, @afragen made a few updates to the new move_dir() function based on @sergeybiryukov’s comments.

Help/About – @marybaum

Help/About: the component had a scrub Monday and is following up with another on @audrasjb will run another bug scrub on Monday October 18, 2021 at 19:00 UTC. So far two tickets are ready for commit action.

The #core-auto-updates team is still looking on getting a consensus on which approach to proceed with for #22316. Two competing PRs are proposed (1547 and 1724), there is a need to decide what is the best approach.

Open Floor

@johnjamesjacoby raised ticket #38231 and asked for another pair of eyes. @costdev pointed out some possible enhancements in the unit tests provided by the ticket.

@webcommsat shared that the Marketing Team is exploring how to help the Test Team reach extenders with the message to update their test suites to bring them in line with the latest WordPress Core PHP Test Suites.Everyone is welcome to join the collaboration in this document, and they are looking specifically for items to be filled in on the table on page 4 to 6.

#5-8-x, #5-9, #dev-chat, #summary, #twenty-twenty-two