WordPress 6.8 Call for Volunteers

As a follow-up to the release calendar proposal for 2025, let’s gather interest in being part of the release squad for the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope., WordPress 6.8.

Proposed WordPress 6.8 tentative schedule

Based on that calendar proposal for next year, the WordPress 6.8 tentative schedule is as follows:

MilestoneDate
Alpha (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. open for 6.8 release)October 22, 2024
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. 1March 4 2025
Beta 2March 11, 2025
Beta 3March 18, 2025
Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1March 25, 2025
Release Candidate 2April 1, 2025
Release Candidate 3April 8, 2025
Dry RunApril 14, 2025
WordPress 6.8 General ReleaseApril 15, 2025

According to the schedule above and the 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 cadence, WordPress 6.8 would include up to Gutenberg 20.4 for a maximum of 11 releases, depending on the end-of-year Gutenberg release adjustments (according to an unaltered schedule, Gutenberg 20.0 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). and stable would land on December 25th and January 1st, respectively).

Release Leads call for volunteers

Following the release squad structure from the last release, except for the default theme role, as WordPress 6.8 won’t deliver a new default theme, these are the minimum roles that need filling:

  • Release Coordinator(s)
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead(s)
  • Editor Tech Lead(s)
  • Core Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead(s)
  • Editor Triage Lead(s)
  • Documentation Lead(s)
  • Test Lead(s)
  • Design Lead(s)
  • Performance Lead(s)

It’s worth noting that WordPress 6.7 experimented with not having an explicit Marketing Lead; depending on feedback from the last release, the 6.8 squad might add back that role or other missing ones. As usual, the Release LeadRelease Lead The community member ultimately responsible for the Release. role will be filled by project leadership. Check the Core Handbook to learn more about the release team’s roles and responsibilities.

All release decisions will ultimately be this release team’s to make and communicate, while gathering input from the community, including finalizing the release schedule.

If you are interested in participating in WordPress 6.8’s release squad as a lead, please show interest in the comments below, clearly specifying your desired role, by December 6th.


Thanks to @aaroncampbell and @jeffpaul for reviewing this post.

#planning #6-8

Proposal: Major releases for 2025

With WordPress 6.7 out the door, it’s time to plan for next year’s releases. The following dates try to account for flagship events and major international holidays:

  • 6.8 – BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 on March 4, stable release on April 15 (Beta 1 ten days after WC Asia)
  • 6.9 – Beta 1 on June 24, stable release on August 5 (WCEU in early June)
  • 7.0 – Beta 1 on  September 30, stable release on November 11 (no flagship events nearby)

The release cadence is similar to past years, with a longer initial release cycle, including the end-of-year festivities and ~4-month ones. Please leave your feedback below or through a 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/. DM by November 29.

Although the 6.8 dates aren’t final yet, they are close to final enough to let contributors know their availability around that time. If you want to participate in the WordPress 6.8 release, stay tuned for an upcoming post with the call for volunteers.

Props to @jeffpaul for reviewing the proposed dates and this post.

#planning

#6-8, #6-9, #7-0

Let’s reconsider adopting the WP Consent API

This post is a follow up to Feature Plugin Proposal: WP Consent API from 2020, which as part of the Core Privacy Roadmap, proposed a framework to allow extenders to coordinate user consent signals and help websites honor user privacy preferences.

Objective of this proposal

The legal and moral implications around respect for user consent and tracking have evolved steadily since the original proposal was published in 2020. Powering over 40% of the web, WordPress is in a position to lead by example and provide site operators built-in and extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. means to address these concerns. This proposal seeks to gather consensus around adopting the WP 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. for inclusion in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

A brief history of the API

In early 2020, the WP Consent API feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. was announced. It enables the setting and retrieval of user consent preferences, made accessible to plugins that register with the API. It was designed to be lean and unobtrusive, opt-in only, and with no UIUI User interface.

Rather than try to enforce cookie-setting compliance itself, the API lets opted-in plugins verify consent before placing cookies. It also allows consent categories to be defined and user choices set and stored by consent management providers (CMPs) and other extenders, where the technical and legal details around the various flavors of consent can be managed outside of WordPress.

In December 2020 the Consent API feature was swept up along with other features during a clean up of the features list, and marked as “Closed”. However, subsequent discussions in #core-privacy in following months were incognizant of the change, and there was confusion that it had been marked closed when attempts were made to move the 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 to the WordPress 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/ org.

Until early this year, adoption of the plugin was minimal, but has been steadily maintained by @rogierlankhorst, @szepeviktor, @xkon, @aurooba, @mujuonly, @phpgeekdk, @paapst, @aahulsebos, @pputzer, and @markwolters.

Why does this matter now?

In March 2024, enforcement of the European Union’s Digital Markets Act (DMA) began, and adoption of the plugin has since grown from under 1,000 to over 100,000 active installations. Uptake of the plugin can largely be attributed to consent-requiring plugins such as Google Site Kit, WooCommerce, and WP Statistics, which use the API to support site analytics, advertising, marketing, and 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.) management.


Beyond the DMA, there are numerous other privacy-focused regulations around the world that over the past few years have come into effect, or will soon. User consent is a key theme to achieving many of these protections, and WordPress can provide the foundation on which consent plugins interact.

Considerations for Core adoption

The API has remained largely unchanged since its introduction, so would likely require refreshing to meet today’s Core merge expectations. There may also be features that need to be revisited, such as how non-consent-related plugins appear in Site Health recommendations.

Along with the API, Core could implement a default cookie “popup” or 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. that could be activated similar to the built-in Privacy Policy feature. This would give site owners a simple mechanism to request and track consent (cookie-based), and be customizable without requiring an additional plugin.

A sample use would be to request “statistics” consent through the popup, styled through a theme, and wrap client-side tracking code inside a wp_has_consent() check. Extenders can take things further by expanding the default categories and storage mechanism for more advanced integrations, as current adopters of the API do today.

Canonical plugin alternative

If adding this feature to Core is not viable at this time, then another option would be to make it canonical. While originally developed under @rogierlankhorst‘s personal repo, it has since been migrated to that of a specific plugin developer and vendor in the CMP space.

Considering the original intent that this feature be merged to Core, agreement from Rogier that it remain available to the community, and the API’s adoption by other vendors, officially bringing the plugin into the WordPress org would send a clear signal to site owners and extenders that this is a community-built and supported standard.

Where to find more info

Share your thoughts

What do you think about WordPress paving the way for easier integration of consent-based privacy controls? Please comment below, especially if you have dealt with implementing consent management in WordPress.

Special thanks to @rogierlankhorst and @azaozz for review and feedback on this post.

#consent-api #core-privacy #feature-plugins #privacy #privacy-roadmap

What’s new in Gutenberg 19.8? (04 December)

“What’s new in 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/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor.



Gutenberg 19.8. has been released and is available for download!

The latest release of the Gutenberg 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 entails a myriad of user experience improvements for selecting section styles, image manipulation and font handling. The DataViews layouts also received important improvements. 

Table of Contents

Section styles selector in toolbar 

In zoom-out mode, users can now apply different sections styles and designs directly from the toolbar, cycling through them and inspecting them in the context of the rest of the page. This enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. streamlines the decision-making and production process. (#67140)

Font family preview in dropdown

Another user experience improvement can be found in the list of fonts: Each font family is now previewed in the font picker dropdown and gives users a better indication as to what the font will look like. (67118)

The outcome of the Image manipulation methods are now better communicated 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. The success notices are now displayed at the bottom of the editor. The notices also come with a handy Undo link to revert to the original if necessary. (67314)(67312)

Other Notable Highlights

DataViews improvements

This release also contains some Data View improvements. For instance,  the table layout received density options: A user can modify the amount of whitespace that is displayed per row on three levels: comfortable, balanced and compact.  (67170)  Developers working with the Dataviews can now make use of a new 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. to programmatically  register and unregister fields for the various display methods. (67175). 

Block supports from experimental to stable.

📣 Plugin authors and Theme builders might appreciate the stabilization of certain block support settings and functions. A separate make blogblog (versus network, site) post will explain the ins and outs. For now, you can read about it in two 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/ PRs:  (67018) (66918).

Continue reading

#gutenberg, #gutenberg-new

Performance Chat Summary: 3 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
  • Next Performance Lab release has been moved from December 2 to December 16
  • 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
  • End of year Performance Hallway Hangout

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

  • @joemcgill While it’s not a performance ticketticket Created for both bug reports and feature development on the bug tracker.. #62046 is the one that I’ve been looking at most recently, as it could have implications on how we approach improving sizes attribute calculation.

Performance Lab Plugin (and other Performance Plugins)

  • @pbearne aiming to do one more update to Image Placeholders
    • To the media modal https://github.com/WordPress/performance/issues/354#issuecomment-2506494681 if this hack is OK
    • @joemcgill my question would be whether working on adding dominant color backgrounds in the media modal to the plugin has any real performance benefit that would lead this to be a priority at this point?
    • @pbearne it is not a priority but it would nice to finish it now i have worked out how to add it to media model. Adding ThumbHash should be left to @swissspidy client side image code
    • @joemcgill yes, as long as the plugin is still a part of the performance lab repo, I think it’s free for contribution if there is something you’ve already got going.
    • @pbearne will add some cleaner code. But would like someone better at JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. to look at the replace
    • @joemcgill Sure. I’ll respond to the issue and am happy to review a PR once you’ve got something together
  • @mukesh27 The PR 1683 for Bump minimum required WordPress version to 6.6 is ready for review. I will work on issue 1557 in the coming week it’s quick one.

Active Priority Projects

Improving the calculation of image size attributes

  • @joemcgill This week, I plan on continuing iteration on https://github.com/WordPress/performance/pull/1701
  • @mukesh27 I’m exploring how we can pass the context for Column 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. as it’s more complex then other parent blocks

Enable Client Side Modern Image Generation

  • No updates this week

    Open Floor

    • @joemcgill discuss having an end of year Hallway Hangout for the Performance team in the next couple of weeks
      • We could even possibly just use this current meeting slot, but should confirm with @flixos90 what will work for him. I suspect he wants to put together some end of year data, similar to last year, that could be shared on the call.
      • To be picked up async on 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/. once @flixos90 is back

      Our next chat will be held on Tuesday, December 10, 2024 at 16:00 UTC in the #core-performance channel in Slack.

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

      Performance Chat Agenda: 3 December 2024

      Here is the agenda for this week’s performance team meeting scheduled for December 3, 2024 at 16:00 UTC.

      • Announcements
        • Welcome to our new members of #core-performance
        • Next Performance Lab release has been moved from December 2 to December 16
        • 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
        • End of year Performance Hallway Hangout
      • 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

      Agenda, Dev Chat, Dec 4, 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 is open until Dec 6. There is also a proposal open for the major releases for 2025.

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

      The next Gutenberg release will be 19.8, scheduled for December 4. 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.

      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 and @annezazu for contributing to this agenda.

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

      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

      Agenda, Dev Chat, Nov 27, 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

      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.
      The call for volunteers for the 6.8 release squad is open until Dec 6.

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

      The next Gutenberg release will be 19.8, scheduled for December 4. 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 @annezazu for contributing to this agenda.

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

      Performance Chat Summary: 26 November 2024

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

      Announcements

      • Welcome to our new members of #core-performance
      • Last week (Nov 20) saw the release of Performance Lab 3.6.1

      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

      Performance Lab Plugin (and other Performance Plugins)

      • @westonruter For Image Prioritizer I have a new PR which is preloading LCP background images which are defined in external CSSCSS Cascading Style Sheets. files or in stylesheets in STYLE tags. Up until now, it would only preload background images which were defined inline with style attributes. This was a big limitation since from what I’ve seen page builders very frequently use non-inline styles, for example to be able to do viewport-specific images on mobile and desktop. My finding is that this can improve LCP by 20% on an Elementor-built page! https://github.com/WordPress/performance/pull/1697 
        • This also improves LCP for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. themes like Twenty Thirteen that have a CSS background image for the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.. I measured a ~9% improvement. The PR is ready for review, but I still need to add tests.

      Active Priority Projects

      Improving the calculation of image size attributes

      Enable Client Side Modern Image Generation

      • No updates this week

      Enhance Onboarding Experience of Performance Lab Plugin

      Open Floor

      • Agreed for the December 16 release to be skipped and a smaller special release scheduled for Dec 2
        • The next release will be scheduled for January 20, 2025
      • This meeting will not take place on:
        • Tuesday December 24
        • Tuesday December 31
        • It will resume again on Tuesday January 7, 2025

      Our next chat will be held on Tuesday, December 3, 2024 at 16:00 UTC in the #core-performance channel in Slack.

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

      Performance Chat Agenda: 26 November 2024

      Here is the agenda for this week’s performance team meeting scheduled for November 26, 2024 at 16:00 UTC.

      • Announcements
        • Welcome to our new members of #core-performance
        • Yesterday (Nov 25) saw the release of Performance Lab 3.6.1
      • 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, 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