Performance Chat Summary: 20 May 2025

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 work on #61734 / PR #8815 adding fetchpriority support for Scripts and Script Modules.
  • @spacedmonkey shared a desire to see some eyes on #59592
    • @spacedmonkey says it seems to have a massive effect for those using object caching. The change has unit tests and has been been reviewed by a non committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.. Just needs another committers to give it the thumbs up.
    • @spacedmonkey would like to land this ASAP, to allow as much time as possible to test this change.
    • @rmccue confirmed support for the proposal but cannot review the code in the short term.
    • @westonruter asked whether there’s TTFB benchmarking data available for the 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..
      • @spacedmonkey noted there would’t be any noticeable difference there. This change would help high traffic site and helps database and object cache performance.
      • @tillkruess noted It will just reduce memory usage in the cache significantly, or make it easier to keep it low.
  • @spacedmonkey noted that #58001, #63021, and #57496 are still awaiting a second round of review.

Open Floor

  • @b1ink0 brought up some confusion around 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. scrub timing, asking if the schedule should be revisited to avoid conflicts. (Bug scrub schedule link)
    • @westonruter asked if the time had already been moved to avoid conflicting with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat.
    • @westonruter confirmed that, according to the Make Meetings page, it had not been adjusted.
    • @swissspidy suggested moving the bug scrub to Tuesdays on alternate weeks from office hours.
    • @westonruter and @flixos90 both supported the idea.
    • @swissspidy updated the Make Meetings page and Bug scrub schedule, then shared the schedule for the next meetings as follows:
      • May 27 – bug scrub (potentially led by @adamsilverstein)
      • June 3 – office hours (@swissspidy would probably cancel that one because of 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. Europe)
      • June 10 – bug scrub
      • June 17 – office hours

Our next chat will be held on Tuesday, June 3, 2025 at 15:00 UTC in the #core-performance channel in Slack.

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

Summary, Dev Chat, May 14, 2025

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 📢

A Month in CoreCore Core 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.

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/ 20.8 is now available

The new version of the Gutenberg 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 is now available in our plugin directory.

AccessibilityAccessibility Accessibility (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 Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. for Class FTPFTP FTP 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 ticketticket Created 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.

#6-8, #dev-chat, #summary

Summary, Dev Chat, May 7, 2025

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 @audrasjb. 🔗 Agenda post.

Announcements 📢

WordPress 6.8.2 and beyond

The CoreCore Core 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)

Forthcoming releases 🚀

Call for 6.8.x release leads

@michelleames and @jeffpaul published a Call for 6.8.x Release Managers. Anyone interested to lead a 6.8.x release can drop a comment in this P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post.

Discussion 💬

CSSCSS Cascading Style Sheets. Regressions in 6.8

@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 note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. format to track frontend CSS changes per release
  • Improving visibility of such changes before they ship
  • Investing in 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. testing
  • Collecting and surfacing CSS-related changes in “What’s new in 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/?” posts

Better communication, testing, and transparency are needed to reduce the risk of regressions in future releases.

Thanks to @audrasjb for proofreading this post.

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

Performance Chat Summary: 6 May 2025

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 asked if any performance-related fixes were included in the WordPress 6.8.1 release.
    • @b1ink0 confirmed that the update focused primarily on general bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes across WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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. Editor, with no specific performance items.
  • @westonruter noted that he has some pending PRs to review and merge.

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)

  • @flixos90 has started work on the new View Transitions feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. (see issue #1997). The work is being tracked through a series of iterative PRs, starting with theme support and dynamic transition name handling. It builds on the experimental Core PR wordpress-develop#8370 and will include a UIUI User interface for customizing transitions.
    • @flixos90 plans to work on the next PRs later this week, with most work focused on porting the experimental code into plugin shape.
    • When asked if the plugin would be considered stable or experimental upon release by @mukesh27, @flixos90 noted that it depends on the final feature set and the team’s evaluation at that time.
  • @mukesh27 briefly noted progress on Accurate Sizes (part of the Auto Sizes plugin) and will share a more detailed update later this week.

Our next chat will be held on Tuesday, May 20, 2025 at 15:00 UTC in the #core-performance channel in Slack.

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

Summary, Dev Chat, Apr 30, 2025

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 @audrasjb. 🔗 Agenda post.

Announcements 📢

WordPress 6.8.1 is now available 🥳

WordPress 6.8.1 was released right after the dev chat. It is a maintenance release.

For now, 6.8 is identified as the last major release of the year.

Forthcoming releases 🚀

WordPress 6.8.2

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.

Call for 6.8.x release leads

@michelleames and @jeffpaul published a Call for 6.8.x Release Managers. Anyone interested to lead a 6.8.x release can drop a comment in this P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post.

Discussion 💬

@sirlouen wanted to bring attention to this ticketticket Created 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 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. shouldn’t add any new file.

@sirlouen pointed out that publishing a call for dev chats topics should ideally be posted on the Make/CoreCore Core 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 PHPPHP The 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.

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

Summary, Dev Chat, Apr 23, 2025

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 @francina. 🔗 Agenda post.

Announcements 📢

Forthcoming releases 🚀

WordPress 6.8.1

@jorbin is leading WP 6.8.1 which is scheduled for Wednesday April, 30, after the dev chat.

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/ 20.7

Gutenberg 20.7 was released on Tuesday April, 22.

Discussion 💬

@mamaduka and @karmatosed are planning to start working on the backlog management in the Gutenberg repository. The plan is to close non-actionable issues/tickets and stale PRs. This was mentioned during the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers call and they just trying to get things moving at this moment. They will try to publish a more detailed announcement once the path is clear.

@sirlouen reported that the conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. between the needs-testing and needs-testing-info keywords in search results on WordPress Core TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. (Ticketticket Created for both bug reports and feature development on the bug tracker. 7935) was about to be resolved by the next #core-test team meeting.

@justlevine is looking for discussion and assistance to move forward with the following tickets:

  • #49442: a parse_blocks 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., so we can stop dumping parsing functionality on render_blocks
  • #61175: Implementing PHPStan in core, which was recently discussed

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

Performance Chat Summary: 22 April 2025

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

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)

  • No immediate updates or blockers were reported for the Performance Lab plugin suite.
  • @flixos90 shared that work is beginning on a new View Transitions feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. (issue #1963). This plugin aims to provide a WordPress-specific 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. for enabling cross-document view transitions.
    • Development will start with a few experimental PRs, similar to the approach taken with the Web Worker Offloading plugin. A public release will only happen once an MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia is ready.
    • For those curious about the planned approach, @flixos90 pointed to an experimental PR opened against CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: wordpress-develop#8370, which will serve as the basis before being ported over to plugin form.

Open Floor

  • @flixos90 removed the milestone due dates from the performance plugin repo, following the team’s decision to move to an on-demand release schedule. Due dates will now be set only when a specific plugin release is planned.
  • @flixos90 shared an adapted 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/ Actions workflow originally created by @shyamgadde to bump the “Tested up to” version in readme.txt without triggering a full deployment. The updated version works for single-plugin repos and can be reused by most plugins on 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/. Example: bump-tested-up-to-dotorg.yml
    • @flixos90 is planning to write a blogblog (versus network, site) post to promote the workflow.

Our next chat will be held on Tuesday, May 6, 2025 at 15:00 UTC in the #core-performance channel in Slack.

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

Summary, Dev Chat, Apr 17, 2025

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 @audrasjb. 🔗 Agenda post.

Announcements 📢

Forthcoming releases 🚀

WordPress 6.8.1

@jorbin proposed to lead the next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. and to host a first 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 right after the devchat.

There has been discussion about the need for a WordPress 6.8 retrospective post. Several people have pointed out the lack of interest of this kind of initiative in recent releases. Members of the 6.8 release squad are still welcome to share their thoughts. @jeffpaul pointed out that the goal is to find ways to ensure the next release cycle is easier than the last: What should be stopped (because it doesn’t help); what should the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team start doing (because it would be helpful); what should be changed (because iterating would be better). Ideally the release squad could put together a Make/Core blogpost and invite people to comment to share their thoughts.

Discussion about the WordPress 6.8.x cycle

With no other 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. scheduled in 2025, 6.8.x is going to be a long cycle, comparable to cycle 4.9.x.

@jeffpaul and @michelleames published a Make/Core post to gather nominations for folks to help lead the 6.8.x minors.

@jeffpaul: “If folks find something and are not certain if it should be part of 6.8.1 (or any future minor release), then please drop a link in #6-8-release-leads […] to help further triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors..”

@audrasjb asked whether the Core team should open milestones 6.8.2 and 6.8.3 on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., but @jorbin pointed out that it’s better to avoid having multiple milestones open for minors except when the current one is on 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). step.

@joemcgill suggested that once any immediate issues that need to ship in a 6.8.1 release are addressed, the Core team could have a broader conversation about how they want to operate for the rest of the year, given that only minor releases are expected. His preference would be to identify a few volunteers to put together a proposal that we can get feedback on before finalizing the process, with a few things we need to consider: How does the ongoing development of JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. package in the GB 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 affect how the Core team plan minor release updates, etc. ; How much change do the Core team allow 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. during this period, given that large changes make it more difficult to 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. fixes to the 6.8 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". ; What types of tickets are “allowed” to be shipped in a minor over the rest of the year, since no more major releases is expected this year.

@jeffpaul pointed out that the Core team had a decent precedent (4.9.6, with privacy features) that expanded what can happen in minors. If there are ways to expand beyond that that won’t break things (e.g. updater), then let’s explore those but there may still be relatively hard constraints.

A minor release is intended for bugfixes and enhancements that do not add new deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. files and are at the discretion of the release leadRelease Lead The community member ultimately responsible for the Release. with suggestions/input from component maintainers and committers.

Source: Releasing Minor Versions in the Core Handbook

@joedolson suggested the team should consider that the first couple point releases could be reserved to new issues only, the same as most minor releases, and once those are settled, the scope of minors can start to be expanded. But the drift between trunk and minors could be difficult to manage, especially if the scope of what can go into a minor is too restrictive. @audrasjb confirmed that it’s exactly what was done during cycle 4.9.x: the cycle started with bug fixes introduced in version 4.9, the the Core team started to introduce enhancements with 4.9.5 and all along the rest of the cycle.

For now, there is a hard rule, though: No new file can be introduced in a minor release.

@jorbin encouraged Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. to publish their own ideas on their own blogs so then all the ideas can be shared and the Core team could come up with a plan.

@joemcgill volunteered to to coordinate a proposal for Make/Core, unless more guidance is given. He would welcome ideas that folks want to share (please feel free to reach out with him).

Open Floor 💬

Core Trac Workflow Keywords Issue

The discussion concerns an issue raised by @sirlouen on MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. about a conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. between the "needs-testing" and "needs-testing-info" keywords in search results on 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/ Meta Trac (Ticketticket Created for both bug reports and feature development on the bug tracker. 7935). This problem makes reports, especially for the testing team, more difficult and leads to incorrect information. Two solutions were suggested: renaming one of the keywords or improving the search algorithm. The conversation continues in the Trac comments.

@sirlouen wanted to run a poll/survey to close this ticket in the next Core Test meeting (23rd April), but he would like to have the consensus (and the awareness) from the core team that this is going to happen, and It’s going to bring a change in core. This item is scheduled for discussion during the next dev chat.

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

Summary, Dev Chat, Apr 9, 2025

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 @francina. 🔗 Agenda post.

Announcements 📢

WordPress 6.8 | 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). 3 is now available 🥳

The Release Candidate 3 is now available! A heartfelt thank you to everyone who joined the Release Party. We appreciate your testing and feedback.

@jeffpaul reminds all CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers to read this article and follow the outlined process for the upcoming steps: WordPress 6.8 Release Candidate Phase

Help Test 6.8 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). version 🧪

The Test-Team has written two helpful guides for people interested in testing:

Forthcoming releases 🚀

General Release: April 15, 2025

The general release of WordPress 6.8 will be available on Tuesday, April 15, 2025.

Ahead of it, there will be a Dry Run on Monday, April 14, 2025.

A detailed overview of the release schedule for WordPress 6.8 can be found here. The article also includes information about the individuals assigned to each release party.

Highlighted posts ✨

Discussion 🤔

Dotorg Core Committers Check In

The discussion concerns the release of version 6.8 as the last 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. for 2025. It was pointed out that the decision was not clearly communicated, and it was recommended to make a clear public announcement. Additionally, a formal proposal should be created in the future to better communicate such decisions and increase transparency.

Open Floor 💬

Core TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. Workflow Keywords Issue

The discussion concerns an issue raised by @sirlouen on MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. about a conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. between the "needs-testing" and "needs-testing-info" keywords in search results on 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/ Meta Trac (Ticketticket Created for both bug reports and feature development on the bug tracker. 7935). This problem makes reports, especially for the testing team, more difficult and leads to incorrect information. Two solutions were suggested: renaming one of the keywords or improving the search algorithm. The conversation continues in the Trac comments.

Thanks @francina for the review

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

Agenda, Dev Chat, Apr 9, 2025

The next WordPress Developers Chat will take place on Wednesday 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.

Additional items will be referred to in the various curated agenda sections below. 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.

Announcements 📢

WordPress 6.8 | 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). 3 is now available 🥳

The https://wordpress.org/news/2025/04/wordpress-6-8-release-candidate-3/ is now available! A heartfelt thank you to everyone who joined the Release Party. We appreciate your testing and feedback.

@jeffpaul reminds all CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers to read this article and follow the outlined process for the upcoming steps: WordPress 6.8 Release Candidate Phase

Help Test 6.8 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). version 🧪

The Test-Team has written two helpful guides for people interested in testing:

Forthcoming releases 🚀

General Release: April 15, 2025

The general release of WordPress 6.8 will be available on Tuesday, April 15, 2025.

Ahead of it, there will be a Dry Run on Monday, April 14, 2025.

A detailed overview of the release schedule for WordPress 6.8 can be found here. The article also includes information about the individuals assigned to each release party.

Highlighted posts ✨

Discussions 🤔

The discussion section of the agenda is to provide a place to discuss 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.

#6-8, #agenda, #dev-chat