Bug Scrub Schedule for WordPress 6.4

Following sessions are dedicated to move things forward and be ready in time according to 6.4 Release Schedule.

Everyone is welcome to join not only to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets but also to look for tickets you can contribute by creating patches, making code review and testing. Keep in mind that all features and enhancements should be in the 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. before 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 and most bugs and all strings need to be there before RC1. If you are working on a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., plan your contribution to have enough time for other contributors to make suggestions, review and test.

Alpha Bug Scrubs

Focus: features, enhancements and then bugs

Beta Bug Scrubs

Focus: rest of the bugs plus reported regressions

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). Bug Scrubs (if needed)

Focus: issues reported from the previous 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)..

  • TBD

Check this schedule often, as it will change to reflect the latest information.

Regular component scrubs and triage sessions

For your reference, here are some of the recurring sessions:

Have a regular component scrub or triage session?
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.” @audrasjb@oglekler or @marybaum 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/. to have it added to this page.

You can start your own triage sessions

  • Decide what you want to work on

6.4 triage session are our priority and moving forward tickets which already are scheduled for the release is most needed task. If you want to lead some of them, they can be added on this schedule.

But if you are interested in particular component or user focus, for example to take care about RTL-tickets, this will be most welcome too.

Especially interested can be the session to scrub old tickets. We are continuously closing new tickets with the same topic in favor of existing ones and because these tickets are looking complicated just because they’re age not, so many contributors are eager to work on them, but there are actual treasures hidden among very difficult or tricky topics.

  • Ping @oglekler or @marybaum on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Useful reports and information

  • Report 5 provides a list of all open 6.4 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 6.4 tickets ordered by workflow.

Need a refresher on 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. scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Thanks to @audrasjb, @mukesh27 and @marybaum for helping to put together this agenda and peer review.

#6-4, #bug-scrub, #core, #props

Performance Chat Summary: 26 September 2023

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

Announcements

  • Welcome to our new members of #core-performance
  • WordPress 6.4 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 is September 26, 2023 today
  • Early version of WordPress plugin checker launched

Priority Projects

Server Response Time

Link to roadmap projects

Contributors: @joemcgill @spacedmonkey @aristath @swissspidy @thekt12 @mukesh27

  • @spacedmonkey committed [56621], [56650], [56677], [56678], and [56683]
  • @thekt12 is working on #59314
  • @flixos90 committed [56681] and just opened a follow up bug fix PR that would be great to commit in the next hour if there is consensus (since committed in [56717])
  • @mukesh27 has been working on additional unit tests for #22192
  • @joemcgill posted some additional benchmarking for the two approaches in flight for #57789, and plans to do some more profiles to get more detailed info on both. He is still planning on tracking these PRs in 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/ repos but have punted to 6.5 for now to keep the release moving while this is getting worked out.

Database Optimization

Link to roadmap projects

Contributors: @spacedmonkey @mukesh27

  • @spacedmonkey committed [56656] and is currently reviewing a PR for #59442 which @thekt12 has been working on
  • @pbearne would like to start working/focus on the option auto-loading issue. now that there is the new 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. to allow easy shortcutting from [55256]
    • @flixos90: There are a few more existing ideas around, some of which are being worked on already, such as #42441
    • For any new ideas, a good next step would be to open issues. Depending on what you envision, you may either want to open a new TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. or a new module proposal in the 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
    • There’s also the autoloaded options Site Health check in Performance Lab, for which there are a few ideas to make it more helpful

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. & CSSCSS Cascading Style Sheets.

Link to roadmap project

Contributors: @mukesh27 @10upsimon @westonruter @spacedmonkey

  • @westonruter committed elimination of manual construction of script tags in WP_Scripts and of inline scripts on frontend/login screen in [56687] (see #58664). With this, Strict CSP can now be opted into on the frontend and wp-login screen. Followed up on prior ticket which sought to do the same for all of WP, and opened new ticket to complete effort in admin.
  • @westonruter also iterated on PR for #55491. In 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 yesterday, we agreed this ticket is actually a defect and not an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature., so it can still land after beta1 today

Images

Link to roadmap projects

Contributors: @flixos90 @thekt12 @adamsilverstein @joemcgill @pereirinha

  • @flixos90 committed [56651], [56690], and [56693]
  • @pereirinha could use some help to track the tickets that need help
    • @flixos90: One of the most flexible ways to search Trac with various filters is the https://core.trac.wordpress.org/query URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org
    • For example, this query shows all remaining 6.4 tickets with a performance focus; it looks like most tickets there are already assigned but please feel free to take a closer look and familiarize yourself with those issues to see if you’re interested in a particular ticket and/or have additional feedback

Measurement

Link to roadmap projects

Contributors: @adamsilverstein @joemcgill @mukesh27 @swissspidy @flixos90

Ecosystem Tools

Link to roadmap projects

Contributors: @mukesh27 @swissspidy @westonruter

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27 @10upsimon

  • @10upsimon pretty much finalized https://github.com/WordPress/performance/issues/651, has implemented necessary logic for redirection back to WPP Settings Screen following certain standalone plug-in actions, will outline in code review given that a few approaches needed to be tested before arriving at the working solution.
    • @flixos90 is looking forward to taking a closer look

Open Floor

  • @spacedmonkey raised #42441
    • The PR needs review and feedback
    • There was consensus that due to a lack of feedback this should be punted to the 6.5 milestone
    • Let’s continue discussing on the ticket so we can figure out a good approach for 6.5
  • @thekt12 has updated the PR for #59442 and would like additional feedback since he is not confident if this leads to any new issue as the new approach does change how cache key is generated for query

Our next chat will be held on Tuesday, October 3, 2023 at 15:00 UTC in the #core-performance channel in Slack.

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

Editor Chat Agenda: 27 September 2023

Facilitator and notetaker: @paaljoachim

This is the agenda for the weekly editor chat scheduled for Wednesday, September 27 2023, 03:00 PM GMT+1. This meeting is held in the #core-editor channel in the Making 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/..

  • Announcements
  • Project updates
  • Task Coordination
  • Open Floor – extended edition.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-core-editor-agenda, #meeting

Performance Chat Agenda: 26 September 2023

Here is the agenda for this week’s performance team meeting scheduled for Sep 26, 2023 at 15:00 UTC. 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

Editor chat summary: September 20th, 2023

This post summarizes the weekly editor chat meeting (agenda for September 20th meeting) held on Wednesday, September 20th 2023, 03:00 PM GMT+1 in Slack. Moderated by @fabiankaegy.

WordPress 6.4 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 will be released in less than a week on September 26th. The full development cycle for 6.4 can be found here: https://make.wordpress.org/core/6-4/

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/ 16.7 RC1 was released right before the meeting. It’s available to test through GitHub.

Gutenberg 16.6 was released last week and the full changelog was posted here in the Make blog.

Key project updates

Open Floor

@mamaduka asked for feedback/testing on a PR that fixes an issue relating to contentOnly locking.

@mdxfr shared several regressions related to the post excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. functionality in WordPress 6.3.

Just want to point out several issues related to Excerpt regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in WP6.3. Since it is a base feature, it is important to fix it soon.
The tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. issues are milestoned for 6.3.2 but would be nice to ship the fixes into next Gutenberg release (16.7/16.8) but also next WP6.4
https://github.com/WordPress/gutenberg/issues/53570
https://github.com/WordPress/gutenberg/issues/15117
https://core.trac.wordpress.org/ticket/59270 (flagged 6.3.2)
https://core.trac.wordpress.org/ticket/59043 (flagged 6.3.2)
It has impact for instance on
https://github.com/woocommerce/woocommerce-blocks/issues/10653
https://github.com/woocommerce/woocommerce/issues/39934

About Cover 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. align-top doesn’t work for awareness, the fix was merged into 16.7, thx (https://github.com/WordPress/gutenberg/pull/54050), maybe we can pick it into WP6.3.2 target list also…

@proxxim asked about any plans for adding a focal point picker to the cover block when it pulls in the featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. of a post. We moved the discussion to the relevant GitHub issue.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Dev Chat Summary, September 20, 2023

The notes from the weekly WordPress developers chat which took place on September 20, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Announcements

No announcements were made this week.

Highlighted Posts

Hallway Hangout: Performance Improvements for WordPress 6.4: Make plans to talk Performance at this hangouts session planned for October 19, 2023 at 15:00 UTC.

Analyzing the Core Web Vitals performance impact of WordPress 6.3 in the field: Read this thorough breakdown from @felixarntz of how 6.3 performance improvements have been reflected on production sites using WordPress at scale. Feedback in invited on the post.

Community Summit Discussion Notes: Increasing contributor recognition and celebration: Join the discussion on how contributor impact can be better identified and highlighted. The discussion at the summit considered the system of props, credit outside of a release, badges, encouragement of contribution.

Evolving the FSE Outreach Program: A reminder to provide feedback on the next phase for the #fse-outreach-experiment: Deadline for feedback: Friday, September 22, 2023

Additional Highlighted Post on Interoperability under Open Floor.

Release Updates

Next major WordPress release: 6.4

The last 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 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 will be on Monday, September 25, 2023 at 17:00 UTC.

More on 6.4 highlighted under Open Floor.

Beta 1 is scheduled for next Tuesday, September 26.

Stay in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. with 6.4 by following:

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/

Reminder: the revised release schedule for the next Gutenberg release is as follows:

  • Gutenberg 16.7 RC1: released September 20 (originally planned for September 13)
  • Gutenberg 16.7: September 27

Components & Tickets

Testing request following a recent bug scrub from @joedolson:

  • TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. #58912: Mobile: Adminadmin (and super admin) menu unexpectedly closes with Safari – after the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. is updated, this will be ready for testing
  • Trac ticket #58756: Media library improvements: UIUI User interface, Non-closing options, and Button select state issues in image editing – this is ready for testing
  • Trac ticket #40822: no longer requires further feedback and is ready for commit


From the tickets posted by @oglekler before dev chat, assistance is needed with the list of tickets left to tackle before Beta 1 (updated September 22, 2023):

  • Trac #55459: Change Login Label name
  • Trac #56886: Admin facing add site screen missing search engine visibility field
  • Trac #58703: wp-list-table: <label> is preceding <input> in the checkbox column – this ticket has a new patch, and further testing is requested
  • Trac #40762: Login: add canonical admin shorthand URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for login.php

Open Floor

  • Call for WordPress developer proposals: Update from @adamsilverstein regarding Interop 2024 was added to the Highlighted Posts list by @webcommsat.
    Seeking proposals for Interop 2024. WordPress developers are asked to contribute their proposals for 2024 as on GitHub or as a comment on the proposals post. Interop aims to improve interoperability across the three major web browser engines (Chromium, WebKit and Gecko) in important areas as identified by web developers.
  • Call for assistance with 6.3.2: @joemcgill highlighted @mikeschroder‘s message about next steps for getting another bugfix out for 6.3, and if there were any contributors available to help lead the release.
    • @ironprogrammer raised that there may be many busy with beta 1 next week, and more hands may be raised after this
    • @jeffpaul thought the concern before WCUS was that something(s) milestoned for 6.3.2 might be worth getting out before 6.4 lands. He asked if people had interest and availability, could they share this in the #6-3-release-leads Slack channel as it would be very helpful.
  • ** A number of contributors highlighted the final stretch to 6.4 Beta 1, and the calls to help deal with as many bugs as possible, clear triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. queues, and review available content.
    @cbringmann reminded the meeting that contributions are for all and not restricted to just the release squad and cohort. She thanked everyone who is lending a hand to the 6.4 release.

Next Meeting

The next meeting will be on Wednesday September 27, 2023, at 20:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel.

Props to @ironprogrammer for hosting the meeting,
@webcommsat and @zunaid321 for the notes,
and to @marybaum and @oglekler for reviews and updates on tickets.

#6-3, #6-4, #dev-chat, #meeting, #summary

X-post: Community Summit 2023: Your Role in What’s Next

X-comment from +make.wordpress.org/summit: Comment on Community Summit 2023: Your Role in What’s Next

Seeking proposals for Interop 2024

TL;DR

Once again it’s time to submit your proposals, as Interop 2024 is happening! WordPress developers, please contribute your proposals for 2024 as on GitHub or as a comment on this post.

What is Interop?

Developing for the web’s diverse browsers has historically been complicated by gaps in browser capabilities that developers had to work around. Interop is a multi-year, multi-browser effort to address that. 

Interop aims to improve interoperability across the three major web browser engines (Chromium, WebKit and Gecko) in important areas as identified by web developers. Interop provides a benchmark – agreed on by representatives of three major browsers and developed through a process of public nomination – and a scoring mechanism.  The overall goal is to make developers’ lives better by enabling a widely compatible “Baseline” of web platform features.

The scale of WordPress and the wide variety of use cases we support puts WordPress developers in a unique position to contribute to and benefit from this effort. In the past, WordPress has helped identify and adopt important features like `srcset` and native lazy loading, and Interop gives us an opportunity to contribute feedback directly to browser developers. 

The Interop 2023 work has already made great progress including on suggestions WordPress developers made on last year’s post like color-mix, inert, import-maps and some contentEditable areas. Now, the effort has begun to identify issues for Interop 2024

What browser interoperability issues continue to present problems for WordPress developers? You can make suggestions to the Interop 2024 project directly by opening a GitHub issue or leave a detailed comment below.

Suggestions can include features that have inconsistent behaviors across browsers or features that aren’t available in all browsers. When formulating proposals, keep in mind that the goal of the project is to improve interoperability between browsers rather than identify new features.

What potential features in WordPress are blocked by cross-browser compatibility issues? Help make browsers better by submitting issues!

#browser-support, #developer-experience, #standards

Default Theme Chat Agenda: September 20th, 2023

his is the agenda for the weekly Default Theme chat scheduled for 20th September 2023, 3pm UTC.

This meeting is held in the #core-themes channel in Making 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/..

  • Topics
    • Upcoming 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:
      • A11YAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issues
      • String translations
    • First build for Beta 1 at the end of the week
  • Open Floor

#6-4 #agenda #bundled-theme #core-themes #twenty-twenty-four

Dev Chat agenda, September 20, 2023

The next weekly WordPress developers chat will take place on Wednesday, September 20, 2023 at 20:00 UTC in the core channel of Make WordPress Slack. All are welcome.

More items will be added to this agenda as they come in.

Summary of Dev Chat, September 13, 2023 – thanks to @zunaid321 and @webcommsat

Welcome and housekeeping

Announcements

Highlighted posts


Analysing the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. web vitals performance impact of WordPress 6.3 in the field

Community summit: encouraging recognition for contributors discussion.

Reminder: The FSE Outreach Program is evolving.

  • The FSE Outreach Program will become a focused space for solving issues, creating resources, and facilitating conversations around Phase 2 adoption. You can contribute by commenting on this post.
  • After 6.4 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, the facilitated calls for FSE testing will be replaced by ad hoc calls for testing run by the Make Test team or contributors who need specific features tested.
  • Deadline: share feedback by September 22, 2023

Forthcoming release updates

Current major WordPress release: 6.3

Reminder: WordPress 6.3 developer notes.

Next major WordPress release: 6.4

WordPress 6.4 Beta 1 will be September 26, 2023.

Existing 6.4 useful links

Release parties schedule for 6.4

Roadmap to 6.4 – this release is scheduled for November 7, 2023.

Bug Scrub Schedule 6.4

6.4 Development Cycle

Project Board for Editor Tasks for WordPress 6.4 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/

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/

Reminder of revised schedule:

  • Gutenberg 16.7 RC1 on September 20, 2023 (originally planned on September 13)
  • Gutenberg 16.7 on September 27, 2023

Tickets or Components help requests

Please add any items for this part of the agenda to the comments. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

Request from the 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. scrubs from @joedolson to get some testing on the following tickets: #50846, and #58912

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

#6-4, #agenda, #dev-chat

Performance Chat Summary: 19 September 2023

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

Announcements

Priority Projects

Server Response Time

Link to roadmap projects

Contributors: @joemcgill @spacedmonkey @aristath @swissspidy @thekt12 @mukesh27

  • @spacedmonkey
  • @mukesh27 I’ve been working on issue #22192 and have received some feedback related to backward compatibility on the PR. I’m now in need of feedback from Joe and Felix
  • @thekt12 #58319 completed (about to be committed)
  • @thekt12 #58196 in progress, planning to give for initial review tomorrow
  • @joemcgill I made good progress on #57789 yesterday and could use a second set of eyes. It doesn’t full solve the issue of making Theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. data persistent, but is a step in that direction, which reduces unnecessary recalculation of that data during a page load. I’m going to work on a parallel PR to 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/ repo to get some testing of the strategy in 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 prior to making the change in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

Database Optimization

Link to roadmap projects

Contributors: @spacedmonkey @mukesh27

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. & CSSCSS Cascading Style Sheets.

Link to roadmap project

Contributors: @mukesh27 @10upsimon @westonruter @spacedmonkey

Images

Link to roadmap projects

Contributors: @flixos90 @thekt12 @joemcgill @pereirinha @spacedmonkey

Measurement

Link to roadmap projects

Contributors: @adamsilverstein @joemcgill @mukesh27 @swissspidy @flixos90

  • @flixos90 Last week I spent some time conducting field analyses to assess the performance impact of the WordPress 6.3 release. Primarily focusing on Web Vitals metric LCP which measures load time performance, and how it’s affected both in general, but also specifically by the two major enhancements that were projected to affect LCP:
    • the emoji loader script optimizations
    • the lazy-loading plus fetchpriority improvements
  • Sharing the most important highlights:
    • Overall, the Largest Contentful Paint (LCP) passing rate has improved by 5.6% for classic theme sites and by 2.7% for 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. theme sites :tada:
    • The Largest Contentful Paint (LCP) boost for classic theme sites using the emoji loader script is 3.4% to 7% higher than for those that don’t use it, and for block themes it’s 0.7% to 4.5% better as well :tada:
    • When looking at only the sites where that is the case and which were still lazy-loading the LCP image with WordPress 6.2, the LCP performance impact amounts to a massive 16% to 21% improvement for mobile viewports and 6% to 9% on desktop. :tada:
    • Lazy-loading accuracy has notably improved: In WordPress 6.3, only 9-10% of sites still lazy-load their LCP image for classic theme sites (down from 27-28% in 6.2) while for block theme sites it’s 5-8% (down from 17-29% in 6.2) :tada:
  • @flixos90 drafted and published the Analyzing the Core Web Vitals performance impact of WordPress 6.3 in the field post
  • @joemcgill Nothing new from me this week, but we expect to do an initial round of benchmarks against WP 6.4 beta1 after it’s released next week.

Ecosystem Tools

Link to roadmap projects

Contributors: @mukesh27 @swissspidy @westonruter

  • No updates this week

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27 @10upsimon

  • No updates this week

Open Floor

  • @joemcgill I wanted to mention that we should probably prepare some time after beta1 next week for some initial triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of any performance issues we see after the first round of code syncing from the Gutenberg project has occurred.
  • @spacedmonkey I would like to start a tracking ticket for dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. this team is going to work on
    • Created https://github.com/WordPress/performance/issues/840 for tracking 6.4 Trac tickets that require dev notes

Our next chat will be held on Tuesday, September 26, 2023 at 15:00 UTC in the #core-performance channel in Slack.

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