The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
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 ticketticketCreated 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.
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 and 6.8.3 will be announced soon.
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.
TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. Tickets
Create a list of reviewers with publishing privileges so an author knows who to contact to move things forward once the post has been peer-reviewed.
Create a list of volunteer authors who can help with drafts. For example: GutenbergGutenbergThe 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/ Release Manager could fulfil their responsibility by tagging those volunteers.
Create a GitHubGitHubGitHub 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 by the repository owner. https://github.com/ action from wordpress/gutenberg that triggers a Slack message to Core on Gutenberg release.
This solution can also automate a message about rc1 in Slack tagtagA directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) volunteers in #core-editor
@jorbin replied that there might be consent issues and it’s also hard to predict who is active on a day in/day out basis. Starting from a message in #core or #core-editor for someone with publish permissions to review and publish could be enough.
To be discussed 🙂
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.
WordCampWordCampWordCamps 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. Europe is today!
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 should be announced soon. Follow #6-8-release-leads for updates.
As a follow-up to this post, he asked the following to be discussed:
After a couple of weeks, I’m almost done on reviewing the Workflow Keywords sequence. I only need some extra info in the committing part as is the part I’m less knowledgeable, so I would need some committers to help me out on the review
[I] need committers to help with the revision of the Workflow Keywords (specially the committercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. and backportbackportA 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. part where I have more doubts). First I’m willing to publish an article explaining the new ideas with the first revision of the revised diagram and it could serve as an attention call for anyone willing to make an opinion or add anything else before the final proposal.
Some discussion happened in the Core Slack channel about this post/proposal.
To sum-up, some committers pointed out that:
@jorbin: This post seems to make the assumption that just because there is a patchpatchA 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. and the patch has no flaws, that it should be committed, but if something should be committed isn’t just a question of if there is a patch ready, it’s also things such as: Does this fit within the current priorities? Is this going to cause issues with future backwards compatibility? Are there alternative solutions that haven’t been considered that should be? How risky is this to commit? What other teams would be affected by this change? Have they been given a chance to chime in?
@desrosj: The crux of the post seems to suggest we can’t create a report for tickets that need a code review with the current keywords. Wouldn’t a report that shows tickets with has-testing and has-patch but does not have commit accomplish the same thing?
@sirlouen pointed out that the post is not completely assuming that every patch perfectly reviewed must be committed, but every patch perfectly reviewed should be considered by committers with more priority than patches from scratch.
The discussion then switched to patches that are reviewed and tested, and waiting for a committer review and commit:
@jorbin: Bringing those tickets up during bugbugA 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 can be a great way to get attention on them, [but] just because it fits [someone’s] definition of 100% baked doesn’t mean that a committer is going to agree.
@audrasjb: The best way to help these tickets is to ask to move them into the current milestone.
@jorbin: There are about 75 bug gardenersBug GardenerA contributor who has been given advanced privileges in Trac. who can modify milestones in addition to all of the committers. In addition, there is nothing that would prevent at the end of the bug scrub a post along the lines of: “After this scrub, we think that the following tickets should be included in 6.8.2 and the following ones in 6.9”. Once someone has demonstrated enough good judgement, they will likely be given bug gardenerBug GardenerA contributor who has been given advanced privileges in Trac. status so that they can do it themselves.
@justlevine wanted to bring attention to ticketticketCreated for both bug reports and feature development on the bug tracker.#61175: “Beyond the usual i could use a bit of help from people better skilled at WP CI/CD (PHPStan passes locally, but isn’t discovering certain symbols when run on CI)”. See the related GitHub PR.
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 ticketticketCreated 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.
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases. A release squad for 6.8.2 and 6.8.3 will be announced soon.
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.
Proposal concerning Core TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow keywords
He asked the following: “Need committers to help with the revision of the Workflow Keywords (specially the committercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. and backportbackportA 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. part where I have more doubts). First I’m willing to publish an article explaining the new ideas with the first revision of the revised diagram and it could serve as an attention call for anyone willing to make an opinion or add anything else before the final proposal.”
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.
WordCampWordCampWordCamps 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. Europe is one week away!
@benjamin_zekavica facilitated the organization of the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team tables. If you plan to attend, check the Core Team at WCEU 25 | Contributor Day article.
GutenbergGutenbergThe 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/ 20.9 is now available
The new version of the Gutenberg pluginPluginA 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. is now available in our plugin directory.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The Core Team is putting together a squad for future minor releases.
In preparation for the WordCamp Europe 2025 Contributor Day, @benjamin_zekavica called for important Core bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. tickets to be submitted for planning.
@realloc will lead the MultisitemultisiteUsed 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 table and is working with maintainers to identify good first bugs.
Core committers are encouraged to actively participate and make at least one commit — with @mamaduka offering remote support.
Where do bugs go if they are introduced in a point releaseMinor ReleaseA 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.?
There was a discussion about how to handle bugs found during a point release. Usually, these bugs should be included in the next point release, especially if there is a patchpatchA 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. or if it is a regressionregressionA 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..
Whether a fix is backported depends on factors such as the bug’s age, severityseverityThe 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., and the risk of the fix. Since clear guidelines are lacking, decisions are made case by case by release leads. More documentation on this process was recommended.
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 ticketticketCreated 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 📢
WordCampWordCampWordCamps 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. Europe is one week away 🤯 @benjamin_zekavica facilitated the organization of the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team tables. If you plan to attend (please do!), check the Core Team at WCEU 25 | Contributor Day article.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The Core Team is putting together a squad for future minor releases. And yes, more volunteers are welcome.
Next GutenbergGutenbergThe 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/ version: 20.9
Gutenberg 20.9 is scheduled for release on Wednesday, May 28, 2025. So it might be out by the time we start dev chat 💪
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.
@benjamin_zekavica posted about WordCamp Europe Contributor Day in Basel. Do you have ahigher-priority ticket dear to your heart? This is a great time to work on it and shepherd it to resolution. Please add them to the WCEU prep post as commentsso the table leads and supporters can prepare.
Where do bugs go if they are introduced in a point releaseMinor ReleaseA 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.?
@sirlouen asked: Should bugs introduced during a point release cycle be moved into the next point release or the next major releasemajor releaseA 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.? This item is not documented. Since we are moving to a different release cadence, it could use some clarity.
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.
There are no major announcements from the past week.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases.
Next GutenbergGutenbergThe 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/ version: 20.9
Gutenberg 20.9 is scheduled for release on Wednesday, May 28, 2025.
Discussion 💬
Refreshing Workflow Documentation
@SirLouen suggested updating the TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow keyword documentation, noting that some terms are outdated, misused, or conflicting. He plans to draft a revised version to provide clearer guidance for contributors and aims to publish it on the blogblog(versus network, site). The goal is to support future discussion and improve overall understanding of keyword use.
Improving the Local Development Environment
The current local development environment for WordPress is minimal and does not include all tools needed for comprehensive testing. Since different approaches are used, the documentation should be updated and improved to reflect the latest state.
Reducing Redundant Test Reports
@krupajnanda suggests limiting the number of test reports on simple tickets (e.g., UIUIUser interface/UXUXUser experience, accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)) to around 5 and adding a message to guide contributors to more important tickets, to reduce redundant testing. @jorbin and others agree but emphasize that this shouldn’t be automated, as a person needs to verify the validity of test reports.
Additionally, once enough test reports are received, the needs-testing label should be removed to focus efforts on tickets still requiring testing.
Open floor 🎙️
Review Needed: Unicode Email Addresses
@agulbra is requesting a review for ticketticketCreated for both bug reports and feature development on the bug tracker.#31992. The code was written last year, but it’s now ready to be merged since PHPMailer has released the required dependencies. @ironprogrammer has already reviewed it and suggested asking for further feedback here. It would be great if someone could take a look. Thanks!
Call for Core Bug Tickets for the WordCampWordCampWordCamps 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. Europe 2025 | Contributor DayContributor DayContributor 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://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/
@benjamin_zekavica mentioned that preparation for the WordCamp Europe Contributor Day in Basel should begin. To support this, suitable tickets need to be collected. If anyone finds higher-priority tickets that could be worked on during the event, they are encouraged to add them as comments in this article. This would help streamline the preparation process.
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 ticketticketCreated 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 📢
There are no major announcements from the past week.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team is putting together a squad for future minor releases.
Next GutenbergGutenbergThe 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/ version: 20.9
Gutenberg 20.9 is scheduled for release on Wednesday, May 28, 2025.
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.
Refreshing Workflow Documentation
@sirlouen suggests updating the workflow keyword documentation, as some terms are outdated, misused, or conflicting. He proposes drafting a clearer version to publish on the blogblog(versus network, site) for better contributor guidance.
Improving the Local Development Environment
The current WordPress development setup makes certain testing tasks (like email testing) harder than necessary. @sirlouen recommends adding helpful tools to make the environment more complete and testing more efficient.
Reducing Redundant Test Reports
@krupajnanda points out that some simple tickets, especially UIUIUser interface/UXUXUser experience and accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) ones, receive too many test reports, while more complex tickets are often ignored. She proposes setting a soft limit (e.g. 5 reports) and adding a message to guide contributors to other important tickets.
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.
A Month in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. – April 2025
In case you haven’t seen it yet, here’s a statistical report from the month of April published by the Core Team. You can find more details in the article.
GutenbergGutenbergThe 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/ 20.8 is now available
The new version of the Gutenberg pluginPluginA 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. is now available in our plugin directory.
AccessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Focused Bug Scrub
@jorbin is hosting an Accessibility-Focused Bug Scrub tomorrow at 15:30 UTC in #core to help move tickets forward. More detailed information you can find here.
Forthcoming releases 🚀
WordPress 6.8.2 and beyond
The Core Team need to set up a release squad, a plan/scope and a schedule for 6.8.2 (and beyond)
Discussion 💬
Call for Topics for the Dev Chat agenda
@sirlouen suggested to publish the “Call for Topics for the Dev Chat agenda” earlier to give contributors more time to suggest topics. @benjamin_zekavica, speaking for the Team Reps, noted that while it can be challenging due to time constraints, they will aim to publish the Call for agenda 1–2 days in advance and update it as needed.
He supports the idea of raising topics early and will discuss improvements with the other reps. Further updates on this will follow.
PHPCSPHP Code SnifferPHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. for Class FTPFTPFTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients files
In the discussion on ticketticketCreated for both bug reports and feature development on the bug tracker.#63436, it was agreed that PHPCS should not be applied to the FTP class files. These files come from an old external library, and applying coding standards would only make sense if WordPress fully adopts the code. There was also agreement on the need for clearer rules and improved documentation.
The CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team need to set up a release squad, a plan/scope and a schedule for 6.8.2 (and beyond)
@luminuu reported regressions in several third-party plugins caused by bugfixes introduced in WordPress 6.8 (PR #64770). Affected projects include Jetpack and WooCommerce. One key issue—buttons stretching full width—was tracked in Trac ticket #63373 and is scheduled to be fixed in version 6.8.2.
The group discussed how to prevent similar issues in the future. Suggestions included:
Introducing a Dev Notedev noteEach important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. format to track frontend CSS changes per release
Improving visibility of such changes before they ship
Investing in visual regressionregressionA 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. testing
Collecting and surfacing CSS-related changes in “What’s new in GutenbergGutenbergThe 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/?” posts
Better communication, testing, and transparency are needed to reduce the risk of regressions in future releases.
There are currently 7 tickets in the 6.8.2 milestone on Trac. Bugfixes currently located in milestone 6.9 can probably start to be moved to 6.8.x milestones, but 6.8.2 will most probably still be focused on remaining issues/regressions found on 6.8.
@sirlouen wanted to bring attention to this ticketticketCreated for both bug reports and feature development on the bug tracker.: #43936. He commented this ticket with a recap of everything that must be known if someone doesn’t want to read all the way through. @audrasjb pointed out that this ticket is a good candidate for a further 6.8.x release, as the patchpatchA 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. shouldn’t add any new file.
@sirlouen pointed out that publishing a call for dev chats topics should ideally be posted on the Make/CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Slack channel, ideally 2 days before each meeting to help gather topics for the agenda. @audrasjb proposed to post such a call on next Monday and to iterate on this process.
@sirlouen added another topic coming from the Core Test Team: “I’m writing a guide on creating Testing Use-Cases for core developers. The thing is that I’ve found over the period of ~100 ticket reviews, that most old stuck tickets with patches that have been pretty much abandoned, the main cause is that the patch creator did not provide enough information to test and help patch progress (even sometimes other reviewers asked for it). I’ve been ideating some examples and ideas, to help people build testing cases, and I’m going to publish this in the Test WP blogblog(versus network, site).” He is looking for people able and willing to review his proposal. @audrasjb volunteered.
@justlevine proposed to discuss the following ticket: #62622: Bump minimum PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version to 7.4. This ticket is on @johnbillion‘s radar. Everyone agreed that this ticket is a major goal for 6.9.
