The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?Create a ticket in the bug tracker.
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Current release (6.7 released last week)
Future releases
Performance Lab pluginPluginA 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)
@joemcgill It’s not really clear what that release schedule will be yet, but we can already start planning our priorities
@mukesh27 Tomorrow we have bugbugA 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 so we can take a look tickets in 6.8 milestone
Performance Lab Plugin (and other Performance Plugins)
@westonruter The most recent Optimization Detective release from yesterday has a key change that addresses an under-collection of URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org Metrics from site visits. However, this change might result in collecting too much (or at least too many attempting to be submitted). So especially for high traffic sites, I’ve opened this issue along with @flixos90 to investigate further: https://github.com/WordPress/performance/issues/1655 Something to monitor this month
@westonruter For Image Prioritizer, I’ve had this issue on my radar for awhile which tackles a big missing piece for optimizing the LCP element’s background image when it is not defined inline (as is very commonly the case, like in Elementor, Divi, and even older coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. themes’ headerHeaderThe 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. images): https://github.com/WordPress/performance/issues/1584
@adamsilverstein There are probably some other opportunities to optimize fonts as well, so maybe “Font Optimizer“. Thinking about web fallbacks to reduce CLS for example. eg. some of the optimizations from https://github.com/unjs/fontaine look like they could apply in WordPress
@shyamgadde Yesterday, after new versions of some plugins were released, I tried to activate and install them from the Performance Lab settings page. However, the old versions were being installed instead. The issue seems to be that the plugin data, including the version number and download link, were stored in a transient, causing older versions to be downloaded. This behavior doesn’t seem correct. Perhaps when installing or activating a plugin, we should consider bypassing or refreshing the transient to ensure the latest version is used.
@mukesh27 requested to open an issue in the performance repo
@westonruter The transient shouldn’t be related to the version being installed
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Performance Lab pluginPluginA 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:
Since WordPress 6.7 was released last week, contributors have kept a close eye on incoming reports to the WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Support Forums, TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and the GutenbergGutenbergThe 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/ repository on GitHubGitHubGitHub 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 by the repository owner. https://github.com/. Though volume has not been meaningfully higher than normal after a major releasemajor releaseA 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., most reports are describing a small set of issues that should be addressed expeditiously.
Schedule
WordPress 6.7.1 will be targeted for release on Thursday, November 21, 2024 with a very specific focus of only fixing bugs there were introduced in the 6.7 release. The goal is to deliver a small handful of high-impact bugbugA 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. fixes for added stability prior to the busy online commerce holiday week consisting of Black Friday, Cyber Monday, and Giving Tuesday.
Continued triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., testing, and committing/backporting fixes.
Wednesday, November 20, 2024 at 13:00PM UTC
Gutenberg package updates released/pluginPluginA 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. update released (if necessary).
Wednesday, November 20, 2024 at 17:00PM UTC
WordPress 6.7.1 RC1
Thursday, November 21, 2024 at 13:30PM UTC
WordPress 6.7.1 General Release
Targeted Fixes
The following are the high priority items that cumulatively make a fast-follow release necessary:
sizes=auto causing images to show smaller than they should (#62413)
Patterns without categories break the editor when browsing uncategorized patterns (GB-66944/GB-66888)
Zoom in doesn’t focus on the right area of the screen based on selected item (a few PRs issues for this)
Zoom out button goes missing when plugins register toolbar items (GB-66884)
The following are bugs that should be included if ready, but as understood now are not affecting as many people or are less problematic:
Using the Upload button in image-based blocks in Safari unexpectedly converts images to HEIC with a temporary file name (#62447)
CategoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. management in the Classic Editor is broken (#62440)
CSSCSSCascading Style Sheets. targets changed on the login screen affecting custom logos (#62410)
Finally, the following are minor bug fixes introduced in 6.7 that should also be considered:
Horizontal scroll bar in the CustomizerCustomizerTool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. (#62313)
There is currently only one ticketticketCreated for both bug reports and feature development on the bug tracker. that does not represent a bug introduced during 6.7 being considered: #62331. This is a pretty significant performance problem for sites using GD for image editing that should be considered. It was only discovered 2 weeks ago, too late to be considered for 6.7.
Notice: This week the Dev Chat time will be changing back to 20:00 UTC.
The next WordPress Developers Chat will take place on Wednesday at 20:00 UTC in the core channel on Make WordPress Slack. Please note that this has changed to the original time which is later than the previous Dev Chats during the 6.7 release.
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 ticketticketCreated 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 “Rollins” was released on November 12, 2024. Thank you and congratulations to everyone who participated in this release!
Forthcoming releases
Next major releasemajor releaseA 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.1
We are discussing releasing 6.7.1 for this week, with @desrosj offering to lead the release.
Next GutenbergGutenbergThe 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.7
The next Gutenberg release will be 19.7, scheduled for November 20. 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 CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team.
This week, we can discuss the 6.7.1 maintenance release, including which issues should be included (trac milestone, Editor board) and who is available to help as part of the release squad. It’s worth noting that GB 19.6.3 was released on Nov 18, which may or may not mitigate #62413 (see thread)
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.
Block Themes and site editor: Refactoring templates: new overview issue that seeks to “adapt our mental model regarding these theme-provided entities” to solve some long standing problems, like mix and matching templates from different sources.
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.
WordPress 6.7 “Rollins” was released on November 12, 2024. A big thank you to everyone who contributed to this release!
To quote the release post:
WordPress 6.7 reflects the tireless efforts and passion of more than 780 contributors in countries all over the world. This release also welcomed over 230 first-time contributors!
Forthcoming releases
Next major releasemajor releaseA 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
There are no maintenance releases planned at this time.
Next GutenbergGutenbergThe 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.7
The next Gutenberg release will be 19.7, scheduled for November 20.
Discussion
There were two main topics today:
Immediate issues that need to be addressed following the release
Confirming volunteers to coordinate upcoming maintenance releases following 6.7
There are currently no immediate issues requiring a quick minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality., so the first minor will likely be released in around 30 days.
@azaozz mentioned #62401 as something that may need addressing soon, but it is from 6.6 rather than 6.7.
@oglekler also raised #62413 for potential inclusion in the next minor release.
We also discussed the need to start to identify volunteers who are willing to help with minor releases as they are ready. We already have a list of 21 issues (1 fixed) set to the 6.7.1 release milestone. @joemcgill suggested we do a call for volunteers if needed next week.
Notice: This abbreviated Dev Chat agenda is will be entirely focused on coordinating follow-up from yesterday’s major releasemajor releaseA 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. of WordPress 6.7.
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 ticketticketCreated 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.
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 CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team.
Topics for this week will include:
Immediate issues that need to be addressed following the release
Confirming volunteers to coordinate upcoming maintenance releases following 6.7
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.
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.
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Current release
Future releases
Performance Lab pluginPluginA 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)
@joemcgill Nothing specific for WP 6.7 at this point. I expect will produce a final set of benchmarks for the release and write up a performance review post, as has been our tradition for the last several releases.
Performance Lab Plugin (and other Performance Plugins)
@westonruter we’ll only be releasing new plugin versions for Performance Lab, Optimization Detective, and Modern Image Formats. The milestone for Speculative Loading is mostly just for the readme along with some PHPStan changes that don’t warrant a release.
@joemcgill are there outstanding PRs from any of those that you need additional support to get landed this week?
@joemcgill highlighted that @flixos90 asked for additional feedback on the expected outcome of that ticketticketCreated for both bug reports and feature development on the bug tracker.here
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Performance Lab pluginPluginA 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:
A mandatory 24-hour code freeze is now in effect for the 6.7 branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..
What does this mean?
No source code for 6.7.0 (i.e., in the 6.7 branch) can be changed during these 24 hours.
What happens if a critical bugbugA 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. is reported during this period?
The release squad will meet with committers and maintainers to determine if the issue is a blockerblockerA bug which is so severe that it blocks a release..
If yes, another RCrelease candidateOne 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). release happens, and the release process restarts (meaning the dry run is repeated, and then the 24-hour code freeze clock restarts).
Please note releasing a major version requires more time than releasing a betaBetaA 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. or release candidaterelease candidateOne 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).. There are more steps in the process. If any last-minute issues need addressing, more time will be needed.
How You Can Help
A key part of the release process is checking that the ZIP packages work on all the available server configurations. If you have some of the less commonly used servers available for testing (IIS, in particular), that would be super helpful. Servers running older versions of PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher and MySQLMySQLMySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com will also need testing.
You can start this early by running the WordPress 6.7 RC5 packages, which are built using the same method as the final packages.
During the release party, options will be provided on how to help test the release package.
Tips on What to Test
In particular, testing the following types of installs and updates would be much appreciated:
Does a new WordPress install work correctly? This includes running through the manual install process, as well as WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/ or one-click installers.
Test upgrading from various versions.
Remove the wp-config.php file and test a fresh install.
Test single site and multisitemultisiteUsed to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site/networknetwork(versus site, blog) (both subdirectory and subdomain) installations.
Testing the following user flows on both desktop and mobile would be great to validate each function as expected:
Publish a post, including a variety of different blocks.
Comment on the post.
Install a new pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party./theme, or upgrade an existing one.
Change the site language.
If you’re a plugin developer, or if there are complex plugins you depend upon, test that they’re working correctly.
