Tag Archives: dev chat

Amy Kamala 3:04 am on September 16, 2026
Tags: , , , , dev chat   

Dev Chat Agenda – September 16, 2026

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

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

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

Announcements 📢

7.2

General

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.

Open floor  🎙️

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

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

#7-1, #7-2, #agenda, #core, #dev-chat

Jb Audras 8:22 pm on September 10, 2026
Tags: , , , dev chat   

Dev Chat summary: September 9, 2026

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, facilitated by @amykamala 🔗 See the agenda post.

Announcements 📢

7.1

7.1.1

  • WordPress 7.1.1 RC1 is planned on September 10.

7.2

General

Discussion 💬

@drivingralle is asking for feedback on 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/ issue 79082 / PR 79146.

@n8finch is requesting feedback on two Gutenberg PRs: 82367 and 81944.

Background (apart from what’s in the Issue and PRs): these are two features that are available in 7.1, but are incomplete:

  • Icons: being able to use keywords in the search is invaluable
  • Placeholder: would be great for this to work outside the Site Editor, in 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

@n8finch‘s team is pretty jazzed about these features, and would like to be able to use them. These PRs push the features over the finish line.

@oglekler proposed to move the new contributor meeting a bit earlier at 1 pm UTC so that it will be more convenient for people from Asia, but of course another shift in timing is something that people will need to get used to. She added that people from Asia are mostly who are attending, even if time isn’t ideal for them. Ideally we need to 2 meeting to cover all the globe.

@joefusco shared that tracking RTC’s polling cost and the Gutenberg & Presence 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. overlap in presence-api#444, for anyone following that space. Originating from this thread.

@ericmann shared that for those who didn’t see the comments on his make/core post about the Secrets API proposal, he have an initial working draft of a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins live at https://github.com/ericmann/secrets-api and would love feedback on this. His hope is this also addresses some of the feedback we’ve gotten from hosts/providers about how they can integrate with their own platforms as well.

More chances to come as it develops and we work on interop with other systems, but feedback is absolutely welcome and encouraged

#7-1-1, #7-2, #core, #dev-chat

Amy Kamala 2:38 am on September 9, 2026
Tags: , , , , dev chat   

Dev Chat Agenda – September 9, 2026

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

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

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

Announcements 📢

7.2

7.1

General

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.

Open floor  🎙️

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

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

#7-1, #7-2, #agenda, #core, #dev-chat

Jb Audras 7:29 pm on September 2, 2026
Tags: , , , dev chat   

Dev Chat summary: September 2, 2026

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, facilitated by @audrasjb 🔗 See the agenda post.

Announcements 📢

7.2

7.1.1

General

Discussion 💬

From @jeffpaul

Jeff resurfaced this heads up from @annezazu, for anyone who’s working on something for 7.2 to ensure they flag that to Anne for the roadmap post:

Howdy! I’m starting to work on a roadmap for WordPress 7.2 since we’re less than 2 months from betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1. I wanted to check in to see what might be coming up across the project that folks are dedicated to working on. As a reminder, roadmaps aren’t meant to be completely comprehensive but are meant to reflect the priority work slated for the release. As a result, I won’t include every little detail and instead focus on getting the broad strokes in place. As always, I’ll share drafts as I go but just want to flush out anything early as I have a long list already!

@annezazu – link to the Slack thread

@audrasjb: “On my side, I’d say this feature (ticket #65910) may be a huge thing for support teams (on dotorg as well as for plugins/themes support teams if we make it an 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.). Design welcome but I think we can probably make a POC with the existing dashicons and basic styling.”

From @pbearne

Paul would love to see some of his patches that add tests get merged.

#7-1-1, #7-2, #core, #dev-chat

Amy Kamala 12:54 pm on September 2, 2026
Tags: , , , , dev chat   

Dev Chat Agenda – September 2, 2026

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

Dev chat is back on Wednesdays again!

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 📢

7.2

7.1.1

General

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.

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 @audrasjb for collaborating on this agenda.

#7-1, #7-2, #agenda, #core, #dev-chat

Jb Audras 5:13 am on August 25, 2026
Tags: , , , , dev chat   

Dev Chat Agenda – August 26, 2026

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

Yes, the dev chat is switching back to Wednesdays starting this week!

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 📢

Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

7.1

7.2

General

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.

Open floor  🎙️

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

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

#7-1, #7-2, #agenda, #core, #dev-chat

Jb Audras 3:49 pm on August 18, 2026
Tags: , , , dev chat   

Dev Chat summary: August 18, 2026

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, facilitated by @audrasjb 🔗 See the agenda post.

Announcements 📢

7.1

  • 7.1 RC3 was released on August 12th.
  • The Accessibility Improvements 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. was published.
  • 7.1 RC4 was released on August 17th.
  • WordPress 7.1 Field Guide
  • As of Aug 10th, 7.1 is branched. Committers: 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. is open for 7.2 and the 7.1 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". requires double sign off.
  • Learn more about WordPress 7.1 Release Day Process.

@amykamala mentioned that commit freeze is currently in effect until Wednesday post-release.

From @joedolson: “Nothing else to share from the release squad. At the moment, everything is looking like it’s in good shape for the release.” 🚀

7.2

General

Discussion 💬

From @amykamala

“Dev chat scheduling! Back to Wednesdays next week?”

ℹ️ We will indeed move back to the regular schedule starting next week: Wednesdays at 15:00 UTC.

From @jeffpaul

More a 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. thing than coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., but it sounds like https://meta.trac.wordpress.org/ticket/1181 had some folks at WCUS discussing it this week.  So if anyone has interest or experience there, commenting with feedback on the ticketticket Created for both bug reports and feature development on the bug tracker. would be helpful.

#7-1, #7-2, #core, #dev-chat

Jb Audras 9:10 pm on August 17, 2026
Tags: , , , , dev chat   

Dev Chat Agenda – August 18, 2026

The next WordPress Developers Chat will take place on Tuesday, August 18, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

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

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

Announcements 📢

Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

7.1

  • 7.1 RC3 was released on August 12th.
  • The Accessibility Improvements 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. was published.
  • 7.1 RC4 was released on August 17th.
  • WordPress 7.1 Field Guide
  • As of Aug 10th, 7.1 is branched. Committers: 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. is open for 7.2 and the 7.1 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". requires double sign off.
  • Learn more about WordPress 7.1 Release Day Process.

7.2

General

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.

Open floor  🎙️

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

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

#7-1, #7-2, #agenda, #core, #dev-chat

Amy Kamala 4:23 am on August 11, 2026
Tags: , , , dev chat   

Dev Chat Agenda – August 11, 2026

The next WordPress Developers Chat will take place on Tuesday, August 11, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

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

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

Announcements 📢

Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

7.1

  • 7.1 RC1 was released Wed August 5th.
  • A silent RC2 security release was released on August 6th.
  • RC3 scheduled for Wednesday, August 12th.
  • WordPress 7.1 Field Guide
  • 7.1 Release Candidate phase
  • As of Aug 10th, 7.1 is branched. Committers: 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. is open for 7.2 and the 7.1 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". requires double sign off.

    General

    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.

    Open floor  🎙️

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

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

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

    Amy Kamala 3:34 am on August 4, 2026
    Tags: , , , dev chat   

    Dev Chat Agenda – August 4, 2026

    The next WordPress Developers Chat will take place on Tuesday, August 4, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

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

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

    Announcements 📢

    Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

    7.1

    General

    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.

    Open floor  🎙️

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

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

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