Jb Audras 11:37 pm on January 20, 2026
Tags: , , ,   

Dev Chat Agenda – January 21, 2026

The next WordPress Developers Chat will take place on Wednesday, January 21, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

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

The nomination process for Core Team Representatives for 2026 is now open. Please submit your nomination here.

Dropping support for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 7.2 and 7.3

Support for PHP 7.2 and 7.3 will be dropped in WordPress 7.0.

WordPress 6.9.1 Release Schedule

The WordPress 6.9.1 maintenance release is planned on February 3, 2026. See the release schedule announcement for more information.

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

#7-0, #agenda, #core, #dev-chat

Aaron Jorbin 9:28 pm on January 20, 2026
Tags: , 6-9-1, 6-9-x,   

WordPress 6.9.1 Release Schedule

Since WordPress 6.9 was released, contributors have kept a close eye on incoming reports to the 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/ Support Forums, TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., 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 GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/. The volume and severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. of tickets mean that the maintenance release should be prepared sagaciously.

This release will be co-led by @jorbin and @wildworks.

Schedule

Date/TimeEvent
Tuesday, January 20, 2026 at 22:00 UTCBug Scrub
Thursday, January 22, 2026 at 09:00 UTCBug Scrub
Thursday, January 22, 2026 at 16:00 UTCBug Scrub. WordPress 6.9.2 Milestone will be opened, and some tickets may be punted.
Tuesday, January 27, 2026 at 09:00 UTCBug Scrub
Tuesday, January 27, 2026 at 18:00 UTCBug Scrub.
Thursday, January 29, 2026 at TBA UTCWordPress 6.9.1 RC1
Tuesday, February 3, 2026WordPress 6.9.1 General Release

Specific times for 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). and General release will be announced in the 6.9 Release Leads room and will be based on availability of individuals helping with the release.

Targeted Fixes

WordPress 6.9.1 is intended as 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.-fix only maintenance release. Tickets will be included provided they are issues introduced during the 6.9 cycle or intentionally deferred at the end of the 6.9 cycle. You can follow trac report 4 or the 6.9.x editor tasks board for proposed fixes.

Some issues already have hotfixes available in plugin form if you are facing them on your site.

Get Involved with 6.9.1

Bug Scrubs will happen in the #core room during the times posted above. Each of the open tickets is going to require development work along with testing and review. You can also run your own scrubs to help ensure that all of the correct tickets are fixed in this release. Additionally, some locales have strings in 6.9 in need of translation.

General coordination for the release will happen in the #6-9-release-leads channel and decisions around code for the release will be made in the #core room.

Props to @wildworks, @dmsnell, @westonruter for assistance with this post.

#6-9, #6-9-1, #6-9-x, #minor-releases

Benjamin Zekavica 11:45 am on January 15, 2026
Tags: , ,   

Summary, Dev Chat, January 14, 2026

Start of the meeting 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/., facilitated by @desrosj 🔗 Agenda post.

Announcements 📢

WordPress 7.0 Call for Volunteers

If you are interested in volunteering for WordPress 7.0, please comment here by January 16.

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

The nomination process for Core Team Representatives for 2026 is now open. Please submit your nomination here.

Dropping support for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 7.2 and 7.3

Support for PHP 7.2 and 7.3 will be dropped in WordPress 7.0. Here you can find more information.

6.9 Release Retrospective

The 6.9 release retrospective is open to all contributors, not only release squad members.
Broader feedback helps improve future release processes. The form and comments will be open until January 15.

Discussions 💬

PHP Extensions List – filter

The topic was about the PHP filter extension and if it should be default. It was noted that the extension already exists on almost all PHP installs. The idea was to move it from optional to built-in (default), so no extra checks are needed. It was also noted that WordPress Core barely uses it, except in PHPMailer, and that filter functions, especially for email checks, are not very reliable.

#7-0, #core, #dev-chat

Aditya Dhade 5:54 pm on January 13, 2026
Tags: , , , ,   

Performance Chat Summary: 13 January 2026

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter shared that an issue related to Modern Image Formats in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. had surfaced, pointing to #60480.
  • @westonruter shared the reports covering performance-related tickets for WordPress 6.9.1 and 7.0 specifically enhancements/features.
    • @westonruter highlighted #64066 as potentially the most impactful open ticketticket Created for both bug reports and feature development on the bug tracker., which proposes changing Speculative Loading’s default eagerness from conservative to moderate when caching is detected. @westonruter noted that no negative feedback has been received so far but acknowledged the change could be controversial and planned to ask for additional feedback in the #hosting channel.
  • @mukesh27 asked about the status of the Adminadmin (and super admin) View Transitions work. @westonruter replied that this is tracked in #64470, with an active PR #10699 opened by @flixos90.
    • @westonruter shared that the change looks close to being ready, but an unexpected E2E test failure still needs investigation. @mukesh27 shared that the implementation looks solid overall, and @westonruter mentioned he had merged the latest 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. changes and planned further debugging, including testing behavior with unminified scripts if the failure persists.

Performance Lab 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 (and other performance plugins)

  • @SarthakJaiswal shared that he has been working on PR #2321, plans to review feedback, and will implement required changes soon, while also asking whether there are additional polishing improvements worth considering.

Open Floor

  • @mukesh27 asked who would be attending WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia this year. @westonruter shared that he is looking forward to the Core Performance table at Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. and noted that, since the conference will correspond with WordPress 7.0, either team could land some very early things for WordPress 7.1 or focus on Performance Lab.

Our next chat will be held on Tuesday, January 27, 2025 at 16:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary

Benjamin Zekavica 11:20 am on January 13, 2026
Tags:   

Nominations for Core Team Reps: 2026 Edition

This post kicks off the formal election process with a call for nominations for the 2026 CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps. For 2025, Francesca Marano (@francina), Jb Audras (@audrasjb) and Benjamin Zekavica (@benjamin_zekavica) have served as the elected Core Team Reps.

The Role

In the WordPress open-source project, each team has on average one or two representatives, abbreviated as reps. For the historians out there, the role go way back to 2012.

Historically with the Core team, the 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. duration was around a year, though some reps stuck around longer if there was a specific need.

Anyone who serves as a team rep is responsible for communicating on behalf of the Core team to the other contributor groups via weekly updates, as well as occasional cross-team chats. Reps are also consulted on Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., where they help to find someone within the Core team who will be at an event who can lead a Core table. Full details on the Team Rep role can be found on the Team Update site.

It is not called team lead for a reason.  It’s an administrative role. While people elected as team reps will generally come from the pool of folks that people think of as experienced leaders, the team rep role is designed to change hands regularly.

This role has a time commitment of at least one or two hours a week.

The main tasks include:

  • Posting the weekly Dev Chat agenda, hosting the chats, and summarizing them (which can include writing and encouraging others to contribute to the summaries). More details on coordinating devchat are available in the Core handbook.
  • Keeping up with the current releases (mainly WordPress major and minors 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/ bi-weekly releases) and communicating updates.
  • Keeping a watch on the moving parts of the team to report for quarterly updates (example).

How the election works

Please nominate people in the comments of this post. Self-nominations are welcome. The deadline is January 31, 2026 at 23:59 UTC. If there are fewer than 2 nominees who have accepted their nominations, the deadline will be extended.

Once the nomination period expires, a poll will be opened for voting. It will stay open for two weeks. The new reps will start their role in February 2026.

Disclaimer: if you are nominated, please don’t feel like you have to agree to say yes. The election poll will only include the names of the people who have agreed to be nominated. So feel free to reply with a “Thank you, but no thank you”.

If you have any questions, please feel free to ask in the comments or speak to the current team reps. Finally, for reference, these are the 2020, 2021, 2022, 2023, 2024, 2025 nomination posts.

Thanks to @francina for reviewing this post.

#team-reps

Benjamin Zekavica 10:08 am on January 13, 2026
Tags: , , ,   

Dev Chat Agenda – January 14, 2026

The next WordPress Developers Chat will take place on Wednesday, January 14, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

WordPress 7.0 Call for Volunteers

If you are interested in volunteering for WordPress 7.0, please comment here by January 16.

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

The nomination process for Core Team Representatives for 2026 is now open. Please submit your nomination here.

Dropping support for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 7.2 and 7.3

Support for PHP 7.2 and 7.3 will be dropped in WordPress 7.0. Here you can find more information.

6.9 Release Retrospective

The 6.9 release retrospective is open to all contributors, not only release squad members.
Broader feedback helps improve future release processes. The form and comments will be open until January 15.

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

PHP Extensions List – filter

@sirlouen raised a question about setting the filter PHP extension as default. See the Hosting Team Handbook.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

#7-0, #agenda, #core, #dev-chat

John Blackbourn 9:24 pm on January 9, 2026
Tags: , ,   

Dropping support for PHP 7.2 and 7.3

Support for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 7.2 and 7.3 will be dropped in WordPress 7.0, currently scheduled for release in April 2026. The minimum recommended version of PHP will remain at 8.3, but the new minimum supported version of PHP will be 7.4.0.

The minimum supported version of PHP was last raised in July 2024 to 7.2.24. Since then usage of PHP 7.2 and 7.3 has dropped below 4% of monitored WordPress installations.

Historically, the project has used 5% as the baseline usage percentage that a PHP version must fall below before it can be considered for a well-earned retirement. Now that usage of PHP 7.2 and 7.3 combined has fallen well below that, the process to increase the minimum supported PHP version can proceed.

The goal of increasing the minimum supported version of PHP is to ensure the long-term maintainability of WordPress. The benefits to increasing the minimum supported PHP version manifest over time across multiple areas, including 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 and theme ecosystem, tooling and libraries for AI, the long-term perception of the WordPress project, developer relations, and eventually within the WordPress codebase itself, including its developer tooling and automated testing infrastructure.

Discussion around this minimum version bump can be found here on the Trac ticket.

What about PHP 8 and higher?

WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is fully compatible with PHP 8.0 to 8.3 and is beta compatible with PHP 8.4 and 8.5.

A full breakdown of which PHP versions are compatible with each version of WordPress can be found in the WordPress Core Handbook..

What about security support?

Sites that are running PHP 7.2 or 7.3 will remain on the 6.9 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". of WordPress once 7.0 is released. While only one branch officially receives security updates, fixes are backported down to WordPress 4.7 as a courtesy when possible.

What about 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/ plugin?

The minimum supported version of PHP will also be increased to 7.4 in the Gutenberg plugin.

Going forward

There are no plans to bump the minimum supported PHP version on a set schedule. The Core team will continue to monitor PHP version usage and work with the Hosting team to encourage users and hosting companies to upgrade their versions of PHP as swiftly as possible. The 5% usage threshold will continue to be used as the standard for the foreseeable future.

At the time of publishing, the PHP version usage is as follows:

  • 8.5: 0.23%
  • 8.4: 4.90%
  • 8.3: 16.74%
  • 8.2: 27.29%
  • 8.1: 15.39%
  • 8.0: 5.69%
  • 7.4: 22.20%
  • 7.3: 2.04%
  • 7.2: 1.81%

Update PHP today

If you need more information about PHP or how to update it, check out this support article that explains more, guides you through the process, and provides instructions for contacting your web hosting provider for assistance.

Props to all those that have contributed to this discussion recently. Thanks to @desrosj, @westonruter, and @jorbin for feedback and proof-reading this post.

#7-0, #dev-notes, #php

Jonathan Desrosiers 1:19 am on January 9, 2026
Tags:   

WordPress 7.0 Call for Volunteers

Planning is underway for WordPress 7.0! This post outlines the proposed schedule along with a call for volunteers to support the release process.

Following the typical cadence and accounting for holidays later in the year, the proposed final release date for 7.0 is Thursday, April 9, 2026. This proposed timeline remains flexible for the resulting Release Squad and adjustments can be made if necessary as they determine what timeline works best for their schedule.

Proposed Schedule

MilestoneDate
Alpha BeginsImmediately (7.0-alpha began in trunk on November 12th with [61222])
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. 1Thursday, February 19
Beta 2Thursday, February 26
Beta 3Thursday, March 5
Beta 4Thursday, March 12
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). 1Thursday, March 19
Release Candidate 2Thursday, March 26
Release Candidate 3Thursday, April 2
Dry RunWednesday, April 8
Final ReleaseThursday, April 9

As always, all dates are subject to change based on development progress.

Call for Volunteers

Each WordPress release depends on contributors from across the project coming together to make it a success. 

As with the 6.7, 6.8, and 6.9 release cycles, WordPress 7.0 will continue the approach of forming a smaller, focused Release Squad with making based on feedback received. This streamlined structure places more emphasis on collaboration with the various Make Team Reps, who are encouraged to help coordinate efforts from within their respective teams. The goals are to reduce the overhead on the Release Squad while still ensuring each team’s contributions and priorities are represented throughout the cycle, and to reduce overlap between a Make 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. and that team’s Release Squad Leads. Noteworthy Contributors will be captured from Team Reps towards the end of the release cycle.

While the end goal is to publish the final release of WordPress 7.0 during Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia (which follows India Standard Time), traveling to or attending WordCamp Asia is not a requirement to serve on the release squad. All communication related to the release process will continue to take place 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.

If you are interested in helping lead WordPress 7.0 in one of the following roles, please comment below or reach out in the #7-0-release-leads Slack channel:

  • Release LeadRelease Lead The community member ultimately responsible for the Release. – Matt Mullenweg (@matt)
  • Release Coordination – helps manage timelines, cross-team collaboration, and status updates
  • Tech Leads – oversees coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development (including 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/), triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., and critical issues
  • Triage Lead – help monitor issues, shepherd patches, and guide contributors
  • Test Lead – coordinates testing efforts across the community and test reports

Whether you have led a release before or are looking to get involved for the first time, there are many ways to contribute. Volunteers of all backgrounds and experience levels are welcome!

If you are interested in volunteering, please leave a comment below noting your preferred area(s) by Friday, January 16th. @4thhubbard (or a designee), will review the nominations shortly after to confirm and announce the release squad as soon as possible.

Together we can make WordPress 7.0 the best one yet!

Props to @jeffpaul, @jorbin, and @4thhubbard for reviewing this post.

#7-0

Benjamin Zekavica 4:38 pm on January 7, 2026
Tags: , ,   

Summary, Dev Chat, January 7, 2026

Start of the meeting 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/., facilitated by @benjamin_zekavica 🔗 Agenda post.

Announcements 📢

6.9 Release Retrospective

The 6.9 release retrospective is open to all contributors, not only release squad members.
Broader feedback helps improve future release processes.

Discussions 💬

PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Extensions List – filter

The discussion covered whether the PHP filter extension is set as default. See the Hosting Team Handbook. @dmsnell asked about the impact on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., how similar changes were handled before, and mentioned concerns about using functions like FILTER_VALIDATE_EMAIL. @realloc noted that Core uses filter only in a few places, mainly in PHPMailer, and suggested removing those usages instead of requiring the extension. The topic will be discussed again next week.

#7-0, #core, #dev-chat

Benjamin Zekavica 7:07 pm on January 6, 2026
Tags: , , ,   

Dev Chat Agenda – January 7, 2026

The next WordPress Developers Chat will take place on Wednesday, January 7, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

Happy New Year!

The first Dev Chat meeting of the year will take place on January 7 at the usual time.

6.9 Release Retrospective

The 6.9 release retrospective is open to all contributors, not only release squad members.
Broader feedback helps improve future release processes.

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Extensions List – filter

@sirlouen raised a question about setting the filter PHP extension as default. See the Hosting Team Handbook.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

#7-0, #agenda, #core, #dev-chat