Summary of the Developer Blog editorial meeting on 9 January 2025

Summary of the WordPress Developer Blogblog (versus network, site) meeting, which took place in the  #core-dev-blog channel on the Make WordPress 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/.. Start of the meeting in Slack.

Attendees: @areziaal, @oglekler, @greenshady, @bcworkz (async) @cwhitmore (async) @annezazu (async) and @bph (facilitator).

Last meeting notes: Summary of the Developer Blog editorial meeting on 5 December 2024



Updates on the site

We started implementing a suggestion we received over the last few months for two more content post types: Snippets and Videos. You can see a list of available snippets here. They are shorter posts and solve one particular task/problem. There is also a separate async meeting format for Snippet approval between the monthly meeting

Video CPT only has one post for now: the recording of Developer Hours: Improve your workflows with WordPress development tools. There is the hope that over the following months, we can start a design process to integrate those two additional custom post types more prominently on the developer blog.

Newly published posts since last meeting

Huge thank you to the writer and reviewers! 🎉👏

Project status

The project board for Developer Blog content is 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/.

In review

In progress

On the to-do-list, assigned to writers

We have approved topics that still require a writer:

If you know someone who could tackle any of those topics, please comment on the particular issue

New topics approved

Open Floor

New leadership

@bph “After two years of leading the WordPress Developer Blog, it’s time for me to step back and let others take the reins! I’ve enjoyed creating and managing processes, running meetings, and working with all of you. However, due to other commitments, I need to pass the torch.

This is a fantastic opportunity for someone (or a few someones!) to take on a leadership role within the WordPress open-source project. Here are some of the responsibilities involved:

  • Facilitate monthly meetings (tentatively shifting to 15:00 UTC).
  • Manage the editorial calendar and content pipeline.
  • Onboard and support new contributors.
  • Guide reviewers and writers through the review process.
  • Oversee content publishing, ensuring quality and adherence to standards.

By taking on this role, you’ll gain valuable leadership experience, contribute to a vital resource for WordPress developers, and expand your networknetwork (versus site, blog) within the community.

I’ve already spoken with @marybaum, who is potentially interested in helping out. Announcement on the channel of January 10th, 2025:

I am happy to announce that @marybaum has agreed to take on the project WordPress Developer blog. She is a long-time WordPress contributor on the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team and a brilliant editor. I am very grateful to see the project in such good hands. Please support her as enthusiastically as you supported me in the project.

But, ideally, we’d have a few people sharing the responsibilities. If you’re interested, please contact me on WPSlack by January 23rd or leave a comment on the summary post of this meeting with a brief explanation of your relevant experience and why you’d be a good fit. (edited) 

What’s new for developers Round up post

@greenshady

“In other news, I’d love to have someone (or multiple someones) to volunteer for the What’s new for developers? monthly roundup.

The goal was to always rotate this through various writers so that it would be written from different viewpoints. I’m writing the January 2025 edition, and I’m happy to onboard anyone for February 2025 and set up the doc (we have a reasonably standard formula for it at this point).  I won’t be able to write this for February for sure and possibly afterward for a couple of months at least. Feel free to DM me, 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.” me here, or reply to the meeting summary post when it’s published if you’re interested in pitching in here

Upcoming meetings

  • Next Editorial Group meeting February 6th, 2025, at 15:00 UTC (!)📣
  • Next Async Snippet Approval meeting on January 22/23, 2025

Both happening in the #core-dev-blog channel

Props to @greenshady for review.

#dev-blog

#meeting, #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

Performance Chat Summary: 7 January 2025

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • Open floor discussion around this meeting format and changes in 2025
    • Agreed to move to a fortnightly performance meeting in a more “office hours” format from January 14 onwards
    • No agenda will be posted ahead of each meeting, instead the meeting host will follow the format suggested in this document, which is open for comments please
  • Bug scrub cadence was also discussed, but no conclusion reached – we will continue the discussion on the next meeting January 14

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

  • @joemcgill is planning to commit the fix for #62692 soon. His concern is that anyone on an older version of WP will still be affected by this 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.. Joe has reached out to all the affected caching plugins identified on the ticketticket Created for both bug reports and feature development on the bug tracker. and so far have seen mostly that those projects aren’t interested in supporting versions of WP that are impacted by the bug

Our next chat will be held on Tuesday, January 14, 2025 at 16:00 UTC in the #core-performance channel in Slack

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

Agenda, Dev Chat, Jan 8, 2025

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

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.

Next maintenance release: 6.7.2

There is currently no release date planned for WordPress 6.7.2. 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 15. It will include the following issues.

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.

This will be the first Dev Chat of 2025, so we’ll use this time to discuss anything that needs to be addressed to prepare for the first releases of the year.

Highlighted Posts

Editor Updates

You can keep up to date with the major Editor features that are currently in progress by viewing these Iteration issues.

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 if you intend to be available during the meeting for discussion or if you will be async.

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

Performance Chat Agenda: 7 January 2025

Here is the agenda for this week’s performance team meeting scheduled for January 7, 2025 at 16:00 UTC.

  • Announcements
    • Welcome to our new members of #core-performance
    • Open floor discussion around this meeting format and changes in 2025
  • Priority items
    • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
    • Performance Lab pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins) including:
      • Enhanced Responsive Images
      • Embed Optimizer
      • Image Prioritizer
      • Image Placeholders
      • Modern Image Formats
      • Optimization Detective
      • Performant Translations
      • Speculative Loading
      • Web Worker Offloading
    • Active priority projects
  • Open floor

If you have any topics you’d like to add to this agenda, please add them in the comments below.


This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

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

Agenda, Dev Chat, Dec 18, 2024

The next WordPress Developers Chat will take place on Wednesday at 20:00 UTC in the core channel on Make WordPress Slack.

This will be the last Dev Chat of 2024 and we will resume the meetings again on January 8, 2025.

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

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

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.

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.

If you want 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.

Highlighted Posts

Editor Updates

Props to @annezazu for putting this list of updates together:

You can keep up to date with the major Editor features that are currently in progress by viewing these Iteration issues.

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 if you intend to be available during the meeting for discussion or if you will be async.

Thank you and props to @joemcgill and @annezazu for contributing to this agenda.

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

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

Performance Chat Summary: 10 December 2024

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • The Performance team have posted the WordPress 6.7 Performance Improvements results
  • The next Performance Lab release will be on December 16
  • Our performance chat time slot next week will be for our Hallway Hangout: Performance End of Year Review 2024 taking place December 17, 2024 at 16:00 UTC we welcome as many people there as possible!
  • The performance 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 on December 18, 2024 at 16:00 UTC will also be an end of year wrap up session
  • Upcoming Performance Weekly Chats in December
    • No meeting on Tuesday December 24
    • No meeting on Tuesday December 31
    • Meetings will resume again on Tuesday January 7, 2025

Priority Items

  • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
  • Performance Lab pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (and other performance plugins)
  • Active priority projects

WordPress Performance Trac Tickets

  • @spacedmonkey ticketticket Created for both bug reports and feature development on the bug tracker. #62658 is nearly ready to commit
  • @joemcgill we’ve got 5 marked for early that would be good to scrub later today if there’s time, since we skipped last week
  • @pbearne does not yet have a fix for #42743. The issue is that I can’t separate 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. widgets from the others the way it hackedhacked in is the problem
    • @joemcgill Has that challenge been documented anywhere? Happy to read up on it and try to give feedback, or perhaps there is someone else that is familiar with the issue that could help?
    • @pbearne The block widgets are load a single widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. as part of the option. Happy to have others look at this
  • @mukesh27 for #58001 suggested we can review the PR and iterate early in the 6.8 cycle
    • @spacedmonkey Not had time to look into this one again. I would love if someone else could pick this one up, as it most just needs unit tests now. IMO

Performance Lab Plugin (and other Performance Plugins)

Active Priority Projects

Improving the calculation of image size attributes

Enable Client Side Modern Image Generation

  • No updates this week

Open Floor

  • @spacedmonkey to discuss #57496
    • Has added tests to the above. I need code review. Can this be added to WP 6.8?
    • @joemcgill I don’t see any reason why it can’t be milestoned if it’s close. @pbearne you had self assigned ownership, but am wondering who needs to shepherd this into the release?
    • @pbearne the code is ready it just need a 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. to help
    • @spacedmonkey I am happy to commit this and action feedback. It doesn’t really need much more, I think it is basically done.

Our next chat will be held on Tuesday, December 10, 2024 at 16:00 UTC in the #core-performance channel in Slack in the form of our Hallway Hangout: Performance End of Year Review 2024

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

Agenda, Dev Chat, Dec 11, 2024

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

There are no major announcements from the past week.

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.

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.

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.

If you want 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.

Highlighted Posts

Editor Updates

You can keep up to date with the major Editor features that are currently in progress by viewing these Iteration issues.

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 if you intend to be available during the meeting for discussion or if you will be async.

Props to @joemcgill for contributing to this agenda.

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