Dev Chat Agenda – April 17, 2025

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

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

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 “Cecil” is now available! 🐣

WordPress 6.8 was released as scheduled and it was named after the legendary jazz pianist Cecil Taylor.

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

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.

WordPress 6.9

No ETA at the moment.

Highlighted posts ✨

Nothing, apart from the WordPress 6.8 “Cecil” announcement! 😃

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.

WordPress 6.8.1:
- Is there any 6.8 release leadRelease Lead The community member ultimately responsible for the Release. who want to help releasing 6.8.1? Any new person who want to be onboarded on this first post-6.8 release?
WordPress 6.8.x:
- @audrasjb suggests a discussion about how to handle tickets currently located in milestone 6.9 and how to dispatch them (when needed) in the next 6.8.x minor releases: should bug gardeners and component maintainers move them to minor releases related milestones? Should we have dedicated bug scrubs? Should we open 6.8.2 and 6.8.3 milestones right now?
- Given the 6.8.x cycle is going to be quite long, should we publish a call for release leads for the next coming months?
Handbook improvements:
- @jeffpaul proposal to improve the final part of the release process in the handbook. During the week following the release:
  - Publish a retrospective post if desired (help needed here)
  - Check in with the Support Team for any notable issues
  - Check in with the Community Team for any community feedback
  - Kick off the next cycle with the next lead
Minor topic: Time permitting, @audrasjb would like to start a discussion about how contributions are taken into account.

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.

Jeffrey Paul 1:16 am on April 16, 2025

FYI that my item(s) was not a handbook improvement item, but more so items from the release process that should be discussed for who can help close those items out (noting that @michelleames is working on a 6.8.x 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. leads nomination post which is the final bullet of the items I mentioned).
Jeffrey Paul 1:17 am on April 16, 2025

There’s also, as of now I believe, potentially an issue with generating 6.8 updates for DevHub that might need some triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors./resolution.
SirLouen 9:17 am on April 16, 2025

Since no one commented on this topic I raised last week:

https://make.wordpress.org/core/2025/04/09/summary-dev-chat-april-9-2025/#core-trac-workflow-keywords-issue

In: https://meta.trac.wordpress.org/ticket/7935

Taking an idea that @joemcgill gave:

https://wordpress.slack.com/archives/C02RQBWTW/p1744230798939769?thread_ts=1744214228.001519&cid=C02RQBWTW

I’ve been contemplating running a poll/survey to close this ticketticket Created for both bug reports and feature development on the bug tracker. in the next CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test meeting (23rd April), but I 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.