Dev Chat Agenda – June 18, 2025

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

Forthcoming releases 🚀

WordPress 6.8.2 and beyond

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.

  • The following tickets were mentioned by Will Garcia on Slack. They asked whether these tickets are likely to be fixed, since the related dependencies are frequently pointed out as outdated by security compliance audits:
  • Mentioned by @justlevine:
    • Concerning  #61175 (Integrate PHPStan into the core development workflow): “We still to have a serious look at what PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Static Analysis errors we want to ignore (e.g. bc they 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. with WPCSWordPress Community Support A public benefit corporation and a subsidiary of the WordPress Foundation, established in 2016., should be handled in a follow-up after the tool is merged, etc) vs baselined (enforced on new code, but not justifiable enough on it’s own to the required criteria for a code refactor).”
      For more info on this topic, see this thread in the #core-coding-standards channel.
    • Also they pointed out that “there’s some PHPStan Level 0 +1 errors that I need help remediating (if we dont baseline/ignore them in the previous bullet) […] If anyone else is interested in lending a hand here, please chime in on the ticket, in chat, or via DM”.
  • @sirlouen mentioned: as per Monday’s 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 there are two tickets that need to discussed about errors in Direct Execution of Files. See tickets #62722 and #63316. The discussion should go around if this kind of issues should be covered or is not something of priority for WP.
  • Finally, @krupajnanda proposed the following: “I’d love to discuss some pointers shared in the recent WCEU Core Committers notes, especially around improving the quality and timing of testing, reviving structured user testing, and making better use of tools like the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 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. Looking forward to some guidance and input on how test team can align better with the Core team’s needs.”

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, #6-8-2-2, #agenda, #dev-chat, #wceu-25

Dev Chat Agenda – June 11, 2025

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

Forthcoming releases 🚀

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

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

Misc Topics

Bottlenecks when publishing posts. Mentioned by @justlevine 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/.. Proposed solutions:

  • 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: 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/ Release Manager could fulfil their responsibility by tagging those volunteers.
  • Create a 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/ 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 tagtag A 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.

#6-8, #6-8-3, #agenda, #dev-chat, #trac, #wceu-25

Dev Chat Agenda – June 4, 2025

The next WordPress Developers Chat will take place on Wednesday June 4, 2025 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 📢

Forthcoming releases 🚀

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 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 TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow keywords

@sirlouen posted a blogpost in the Make/Test team 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.: The Code Review Flaw in the Workflow.

He asked the following: “Need committers to help with the revision of the Workflow Keywords (specially the 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. and 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. 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.

#6-8, #6-8-2-2, #6-8-3, #agenda, #dev-chat, #trac, #wceu-25

Dev Chat Agenda – May 28, 2025

The next WordPress Developers Chat will take place on Wednesday May 28, 2025 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 📢

  • 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 is one week away 🤯 @benjamin_zekavica facilitated the organization of the CoreCore Core 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 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/ version: 20.9

Gutenberg 20.9 is scheduled for release on WednesdayMay 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.

Call for Core Bug Tickets for the WordCamp Europe 2025 | 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/.

@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 comments so the table leads and supporters can prepare.

Where do bugs go if they are introduced in a point 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.?

@sirlouen asked: Should bugs introduced during a point release cycle be moved into the next point release or the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.? 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.

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

Dev Chat Agenda – May 21, 2025

The next WordPress Developers Chat will take place on Wednesday May 21, 2025 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 📢

  • There are no major announcements from the past week.

Forthcoming releases 🚀

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 is putting together a squad for future minor releases.

Next 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/ version: 20.9

Gutenberg 20.9 is scheduled for release on WednesdayMay 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 UIUI User interface/UXUX User experience and 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) 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.

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

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

Agenda, Dev Chat, Apr 2, 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). 2 is now available 🥳

The Release Candidate 2 release of WordPress 6.8 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 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. version 🧪

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

Forthcoming releases 🚀

Release Candidate 3: April 8, 2025

The Release Candidate 3 release of WordPress 6.8 will be available on Tuesday, April 8, 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.

Next 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/ version: 20.6

Gutenberg 20.6 is scheduled for release on Wednesday, April 2, 2025.

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8

We are currently in the WordPress 6.8 release cycle. Read more about the release squad, timeline and focus for this release.

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.

At the moment, there are no topics for 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

Agenda, Dev Chat, Mar 26, 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). 1 is now available 🥳

The Release Candidate 1 release of WordPress 6.8 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

We are in the process of finalizing the development notes, after which the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. will be released, followed by an email to PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Authors containing the necessary information.

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.5 is now available

The new version of the Gutenberg plugin is now available in our plugin directory.

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

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

Forthcoming releases 🚀

Release Candidate 2 of 6.8: April 1st

The Release Candidate 2 release of WordPress 6.8 will be available on Tuesday, April 1, 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.

Next Gutenberg version: 20.6

Gutenberg 20.6 is scheduled for release on Wednesday, April 2, 2025.

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8

We are currently in the WordPress 6.8 release cycle. Read more about the release squad, timeline and focus for this release.

Editor Updates 🔄

You can keep up to date with the major Editor features with the weekly updates, now on the blogblog (versus network, site)!
Editor Weekly Updates: March 10th – 23rd

Props to @krupaly2k for this wonderful overview.

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.

Hosting Issues Found During 6.8 RC1 Release Party

During the Release Party of 6.8 RC1, @desrosj observed errors occurring on several hosts. The most common issues involved three specific tests:

  • WP_Test_REST_Users_Controller::test_get_items_only_fetches_ids_for_head_requests() | Error Log
  • test_wp_check_password_supports_argon2i_hash() | Error Log
  • test_wp_unique_id_from_values() | Error Log

These tests resulted in failures on multiple hosts.
We should discuss this issue further to identify the causes and potential solutions.

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.

Props to @jeffpaul for reviewing the agenda.

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

Agenda, Dev Chat, Mar 19, 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 | BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3 is now available 🥳

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

Help Test 6.8 Beta version 🧪

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

Forthcoming releases 🚀

Next 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/ version: 20.5

Gutenberg 20.5 is scheduled for release on Wednesday, March 19th.
This will be the first version of Gutenberg to be merged into WordPress 6.9.

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). 1 of 6.8: March 25th

The Release Candidate 1 release of WordPress 6.8 will be available on Tuesday, March 25th.

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.

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8

We are currently in the WordPress 6.8 release cycle. Read more about the release squad, timeline and focus for this release.

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

Release Support Needed

  • Assistance with drafting, reviewing, and publishing developer notes
    Assistance is requested for the drafting, review, and final publication of the developer notes.
  • Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. draft coming Thursday, please be ready for review
    The Field Guide draft will be available on Thursday. Please be prepared to review it promptly.
  • Review of the “About” page and potential issues
    The “About” page should be reviewed to identify any potential issues in the text or content. See more here: #63025
  • Reminder of the string freeze next week before 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). 1
    Please remember that the string freeze will take place next week before the release of RC 1.
  • Assistance with reviewing the email to PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Authors about major changes
    Assistance is needed to review the email to be sent to Plugin Authors, informing them of the key changes.

Critical Issues Before RC 1

  • Discussion of critical issues before RC 1
    It’s suggested to discuss any critical or new issues before the release of RC 1 to ensure all problems are addressed in time.

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

Agenda, Dev Chat, Mar 12, 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 | 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. 2 is now available 🥳

The Beta 2 release of WordPress 6.8 is now available! A heartfelt thank you to everyone who joined the Release Party. We appreciate your testing and feedback.

Help Test 6.8 Beta version 🧪

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

Thanks @ankit-k-gupt and @krupajnanda for your contribution!

Forthcoming releases 🚀

Next 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/ version: 20.5

Gutenberg 20.5 is scheduled for release on Wednesday, March 19th.
This will be the first version of Gutenberg to be merged into WordPress 6.9.

Next Beta 3 of 6.8: March 18th

The Beta 3 release of WordPress 6.8 will be available on Tuesday, March 18th.

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.

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.8

We are currently in the WordPress 6.8 release cycle. Read more about the release squad, timeline and focus for this release.

Reminder

We have only two weeks until 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). 1. Dev notes should be in progress. Please check @jeffpaul‘s message on Slack for details.

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

Editor Updates 🔄

You can keep up to date with the major Editor features with the weekly updates, now on the blogblog (versus network, site)!
Editor Weekly Updates: Mar 3 – Mar 7

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.

Props to @benjamin_zekavica for reviewing the agenda.

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