Summary, Dev Chat, Jan 22, 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 @joemcgill. 🔗 Agenda post.

Announcements

The Nominations for 2025’s Core Team Reps are now open! Please nominate people in the comments of that post. Self-nominations are welcome. The deadline is January 31, 2025.

Forthcoming releases

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.

Next maintenance release: 6.7.2

A release schedule for 6.7.2 was announced earlier today. Currently the release date is February 11. Review the next minor release milestone.

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. scrub was held just a few hours ago and all tickets on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. for the 6.7.2 release were reviewed. One area that I could use some help with is reviewing all the tickets on 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/https://github.com/orgs/WordPress/projects/232.

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/ release: 20.1

Gutenberg 20.1 was packaged earlier today, including the following issues. The team is currently addressing an issue that blocked the release from being published and the release will be delayed until tomorrow.

Discussion

Proposal: Moving Dev Chat starting next week, January 29, 2025 to 15:00 UTC – Based on conversation last week, and feedback from the release squad availability, it is proposed that we change the time of Dev Chat meetings for the 6.8 cycle to 15:00 UTC. Unless there are any new objections, this updated time will be reflected in the next Dev Chat agenda.

WordPress 6.8 Bug Scrubs – We have two bug scrubs each week scheduled in #core (on Mondays and Thursdays), and other ones in various channels like #accessibility#core-editor, etc. The next one will be held in #core tomorrow at 20:00 UTC. See the 6.8 bug scrub schedule blogpost for more info.

Anyone is welcome to run a scrub, just let @audrasjb know if you’re interested in running one (or more) and he’ll add it to the schedule.

WordPress 6.8 Release Roadmap update@krupaly2k is working on putting this together and had some follow-up questions.

  • There are some open iteration issues, are we planning to work on those for WordPress 6.8? @joemcgill asked @mamaduka to review and follow up.
  • There are two issues in the milestone related to PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher compatibility
    • #59231 – Prepare for PHP 8.3: @joemcgill and @desrosj will review and see if there are any follow-up tasks planned for this release.
    • #62061 – Prepare for PHP 8.4: @johnbillion is planning to split out remaining tasks and close this issue. No major work is planned.

Syncing Gutenberg updates to 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. – We’ve been discussing trying to do this sync earlier this cycle once GB 20.1 is released.

  • There are a number of PRs listed in this GB issue that need to be reviewed in order to help facilitate that process.
  • There’s a bug with the sync command, that needs to be addressed: #62839

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

Summary, Dev Chat, Jan 15, 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 @joemcgill. 🔗 Agenda post.

Announcements

The Nominations for 2025’s Core Team Reps are now open! Please nominate people in the comments of that post. Self-nominations are welcome. The deadline is January 31, 2025.

Forthcoming releases

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.

Next maintenance release: 6.7.2

There is currently no release date planned for WordPress 6.7.2 @jorbin is going to schedule a scrub for next week and is currently thinking of tentatively planning a release date in Feb. If you see a ticketticket Created for both bug reports and feature development on the bug tracker. that you think should be considered, please drop it in the #6-7-release-leads channel.

You can review the next minor release milestone.

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/ release: 20.1

The next Gutenberg release will be 20.1, scheduled for January 22. It will include the following issues.

Discussion

With the release squad having just been announced, we spent some time checking in on getting processes up and running for the release.

A few housekeeping items to share:

For tickets in the milestone marked early (🔗 Trac report):

  • While the handbook includes a definition for early, there is no standard deadline by when these tickets MUST be committed
  • @jorbin and @francina volunteered to update the description
  • @audrasjb and @joemcgill will review these tickets in a few weeks and determine whether the remaining ones need to be punted, or if they can have the keyword removed

We will attempt to do the first sync of Gutenberg releases to 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. earlier in this release. @mamaduka is planning to work on this.

While this release is focused mainly on “polish”, we will still include any new enhancements that are ready in time. A few that were mentioned in the meeting included:

  • #62503: Add speculative loading support
  • #21022: Use bcrypt for password hashing; updating old hashes
  • #30465: Dashboard alert if a 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/theme was removed from WordPress repo (may be stalled)

@karmatosed asked that folks please label and raise issues that need help from the design team.

We are looking at moving Dev Chat times during this release to an earlier time. Currently thinking that these will be some time between 15–18:00 UTC. Once confirmed, and update will be posted to the team blog.

Open Floor

  • @nikunj8866 asked about ticket #40477. It looks like it was previously tested but needs to be reviewed for code quality/approach.
  • @mamaduka is looking for feedback on this GB issue proposing a change to the post editor.
  • @justlevine asked for feedback on the following:
    • #49442: Request: 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. for parse_blocks() result
    • #61175: Integrate PHPStan into the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development workflow

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

Summary, Dev Chat, Jan 8, 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 @joemcgill. 🔗 Agenda post.

Announcements

The Nominations for 2025’s Core Team Reps are now open! Please nominate people in the comments of that post. Self-nominations are welcome. The deadline is January 31, 2025.

Forthcoming releases

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

The WordPress 6.8 call for volunteers closed on Dec 6. There will be more information about the release squad to follow soon based on these volunteers.

Next maintenance release: 6.7.2

There is currently no release date planned for WordPress 6.7.2 but @desrosj is planning to review the state of the release this week. You can review the next minor release milestone.

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/ release: 20.1 20.0

The agenda post incorrectly identified the next release as 20.1 with a release date of January 15 due to a shift in the schedule for the holidays. Instead, Gutenberg 20.0 was released on January 9 and Gutenberg 20.1 is expected on January 22.

Discussion

Update on the formation of the 6.8 release squad

The call for volunteers date is closed and @priethor had previously been working on providing an announcement. Following the meeting, he shared that he had handed over responsibility to @jeffpaul and @desrosj, who are working to finalize the squad for the 6.8 release.

To prepare for the release, anyone can volunteer to lead a bug scrub of the 6.8 milestone. Looking at tickets marked early would be a good place to start.

@jorbin suggested the PR for a reliable sync protocol for collaborative editing could use more eyes.

Open Floor

@joemcgill highlighted out this initiative to improve CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s end-to-end (E2E) tests that is looking for support. @jorbin agreed do an initial review.

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

Summary, Dev Chat, December 18, 2024

This meeting was the final Dev Chat for 2024.

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

Announcements

The Nominations for 2025’s Core Team Reps are now open! Please nominate people in the comments of that post. Self-nominations are welcome. The deadline is January 31, 2025.

Also, 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/ 19.9 was released prior to the start of the meeting. See, What’s new in Gutenberg 19.9?

Forthcoming releases

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

The WordPress 6.8 call for volunteers closed on Dec 6. There will be more information about the release squad to follow soon based on these volunteers.

Next maintenance release: 6.7.2

There is currently no release date planned for WordPress 6.7.2. You can review the next minor release milestone. The 6.7.2 milestone was scrubbed during the week and the Gutenberg board is scrubbed with only a few PRs that need to be merged.

Discussion

There were no discussion topics for this meeting.

Open Floor

@luminuu raised the following on the agenda post:

how much work would it be to allow pseudo-styles on 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. style variations, for example on buttons? Talking about this issue: https://github.com/WordPress/gutenberg/issues/55359

@mikachan noted a similar issue being worked on for the stylebook: https://github.com/WordPress/gutenberg/issues/38277.

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

Summary, Dev Chat, December 11, 2024

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

Announcements

There were no announcements today, but @mikachan posted a reminder that WordCamp Asia 2025 is looking for volunteers for 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/., especially to lead CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./Core Editor/Core Performance tables. Please reach out to @Jhimross if you’d like to volunteer.

Forthcoming releases

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. The call for volunteers for the 6.8 release squad closed on Dec 6 and the release squad will be put together soon based on these volunteers.

Next maintenance release: 6.7.2

There is currently no release date planned for WordPress 6.7.2. Review the next minor release milestone. @joemcgill agreed to follow up about another 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 before the end of the year.

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/ release: 19.9

The next Gutenberg release will be 19.9, scheduled for December 18. It will include the following issues.

Discussion

There were two topics for discussion today

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

@joemcgill noted that we’ve already gotten a lot of good feedback and asked @ironprogrammer how long we should leave the proposal open for comment.

@ironprogrammer:

“Given the coming holiday season, would it make sense to leave it open through the end of the year? The feedback has been really positive, but additional feedback from orgs/plugins working with consent would be valuable.”

@joemcgill:

If the consensus is that this should be a core feature, then ensuring the team who is going to shepherd this into a future release is properly supported would be key. Either way, I think there is value in considering the other question in the proposal—which is whether this should become a canonical 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 that is officially supported by the community. I think we can follow up with @4thhubbard about how we want to handle these kinds of requests as there really hasn’t been an established policy that I’m aware of.

@mikachan:

Through the end of the year sounds fine to me. We can make sure we follow-up (including in dev chats) towards the start of next year

WordPress and Typescript

@mikachan:

We adopted TypeScript in WordPress more than 3 years ago and our usage has evolved over time. It’s time to update our approach/guidelines. @youknowriad has opened a discussion to gather thoughts before publishing a 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..

Next steps are to continue collecting feedback and revisiting in a future Dev Chat, if needed.

Open Floor

  • @mamaduka asked for more eyes on #59425, which was recently reported in Gutenberg as well.
  • @jonsurrell shared this call for feedback on this PR for adding CSSCSS Cascading Style Sheets. selector-based 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.) navigation to HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. and Tag Processors (#62653)
    • All feedback is welcome, but specifically, he’s looking for high-level feedback, especially from WordPress veterans. Does the implementation feel appropriate for WordPress? Are there things that are discouraged in Core?
  • @joemcgill raised the need to prepare for nominations for Core Team Reps for 2025 and suggested publishing a call for nominations in the next week with the hopes of collecting responses in Jan and being able to do a transition by Feb. @mikachan and @joemcgill will take responsibility for following up on this.

Props to @mikachan for reviewing.

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

Summary, Dev Chat, December 4, 2024

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

As mentioned at the top of today’s agenda, the weekly Dev Chat times have gone back to 20:00 UTC.

Announcements

The WordPress 6.8 call for volunteers is open until December 6. You can find out more and volunteer for any of the roles here.

Also, 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/ 19.8 was released earlier today 🎉. What’s new in Gutenberg 19.8?

Forthcoming releases

There is a proposal open for the 2025 major releases. The date for feedback has now passed, but comments will remain open until the official announcement is made. @priethor is waiting for the 6.8 call for volunteers to end before publishing an announcement with the 6.8 calendar.

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. You can review the next major release milestone.
The call for volunteers for the 6.8 release squad is open until Dec 6. The most pressing needs are still for Editor Tech Lead and Documentation.

Next maintenance release: 6.7.2

There is currently no release date planned for WordPress 6.7.2. You can review the next minor release milestone. @desrosj suggested that mid to late January is a good ballpark at the moment, as there are no urgent issues after 6.7.1.

Next Gutenberg release: 19.8

Gutenberg 19.8 was released prior to this meeting. See, What’s new in Gutenberg 19.8?, for details.

Discussion

@azaozz expressed his hope that every Gutenberg release can be merged to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. during alpha. Would probably reduce the final pressure during 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. and 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)..

@joemcgill agreed, stating, “It is currently not ideal that nightly WordPress releases aren’t really available to test features that are ready until after the first sync of the cycle”.

@priethor asked, “What’s preventing us from doing that from the core side?”

Consensus from those in attendance was that there wasn’t any specific blockers to doing this, so it may be worth giving this a try in 6.8 once a release squad is identified.

@mikachan asked if we could automate a lot of the process, perhaps open a wordpress-develop PR from a GH action when a new Gutenberg release is out, and then the majority of the work would be testing and committing.

@johnbillion identified a couple of tickets on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. for automation that could use help moving forward: #60967 and #60966.

Open Floor

@annezazu shared the following update prior to the meeting:

It would be awesome to have more contributors working on exposing the Font Library for classic themes, especially as work continues around adding a stylebook screen for classic themes. In this way, we can work towards landing a cohesive “Design” section for classic themes complete with patterns, Style Book, and the Font Library.

@ironprogrammer shared an updated proposal to reconsider adopting the WP Consent API.

Props to @mikachan for reviewing.

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

Summary, Dev Chat, November 27, 2024

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

As mentioned at the top of today’s agenda, from today forward, the weekly Dev Chat times will be back to 20:00 UTC.

Announcements

WordPress 6.7.1 was released on November 21, 2024.

Forthcoming releases

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. You can review the next major release milestone.
The call for volunteers for the 6.8 release squad is open until Dec 6. A call for volunteers for the release squad has been published here.

Next maintenance release: 6.7.2

There is currently no release date planned for WordPress 6.7.2. You can review the next minor release milestone. @desrosj suggested that mid to late January is a good ballpark at the moment, as there are no urgent issues after 6.7.1.

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/ release: 19.8

The next Gutenberg release will be 19.8, scheduled for December 4. It will include the following issues. Reading the release posts, like What’s new in Gutenberg 19.7 is a great way to see what is being worked on for the next major release.

Discussion

There were no topics proposed for this week. As a reminder, anyone can propose discussion topics for these meetings by commenting on the agenda posts each week or reach out to @mikachan or @joemcgill (the current CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps) directly.

Open Floor

@azaozz mentioned ticketticket Created for both bug reports and feature development on the bug tracker. #62504, which seems somewhat common judging by the number of duplicate tickets.

Was wondering if having just a hotfix 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 will be sufficient until 6.7.2 considering it would probably be released next year.

A current workaround for folks is to update the Classic Editor plugin. The same issue affects any plugins that still use the old Edit Posts screen to edit custom post types, and we recommended that these plugins apply the hotfix to work around the issue until the fix is backported to 6.7.2.

Props to @joemcgill for reviewing.

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

Summary, Dev Chat, November 20, 2024

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

As mentioned at the top of today’s agenda, from today forward, the weekly Dev Chat times will be back to 20:00 UTC.

Announcements

WordPress 6.7.1 is now available! Thanks so much to everyone who helped prepare this release.

Forthcoming releases

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. You can review and give feedback on the proposed release schedule for 2025 on this post. A call for volunteers for the release squad has been published here.

Next maintenance release: 6.7.1

We discussed the plan to release WP 6.7.1 on Thursday, November 21, at 13:30 UTC, according to this schedule.

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/ release: 19.8

The next Gutenberg release will be 19.8, scheduled for December 4.

Discussion

@johnbillion mentioned doing some analysis of how often tickets are bumped from one major release to the next, as there are currently >200 tickets in the 6.8 milestone on Trac. @joemcgill suggested doing a scrub of the existing tickets and moving any that have been bumped more than one release to “Future Release”. We also discussed keeping an eye on how often tickets are bumped during the 6.8 cycle.

Open Floor

We started with a call for volunteers that @bph shared:

From the Developer Blogblog (versus network, site) content board we identified six approved topics that are looking for writers. Check out the issues and if you want to tackle a topic, comment on it.
For questions, join us in the #core-dev-blog channel or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @bph (me) .

@remy mentioned ticketticket Created for both bug reports and feature development on the bug tracker. #51525, which proposes adding two new functions, apply_filters_single_type() and apply_filters_ref_array_single_type():

we have a separate repo where we are doing the changes and testing them live in our plugins, but we were waiting for feedbacks before merging the changes up to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

We discussed that it would be good to look at this soon and consider it for the 6.8 release.

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