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.
Summary of the WordPress Developer Blogblog(versus network, site) meeting, which took place in the #core-dev-blog channel on the Make WordPress SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. Start of the meeting in Slack.
The site has passed the first 1,000 subscribers Don’t want to miss the next blog post? Subscribe. And please share the links with your networknetwork(versus site, blog) as well. @webcommsat volunteered to submit an amplification request to the WordPress marketing team to celebrate the milestone with the community.
Newly published post since the last meeting:
Since the last meeting, we published four articles.
The project board for Developer Blog content is 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/.
If you are interested in taking on a topic from this list or know someone who would be a good person to write about them, comment on the Issue or pingPingThe 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 in slack either in the #core-dev-blog channel or in a DM.
The WordPress Developer Survey – A regular survey could give “the whole project a lot of useful data” There were concerns about logistical challenges and needs further discussion with coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., the marketing team in its new media focus, and with Learn WP. The next step as identified as “to define the purpose of the survey, and what questions would be included/not included.” The discussion continues on GitHub
Open Floor
@webcommsat Inquired about topics schedule around the WordPress 6.6 release. There are a few posts already on the list or were just approved. As almost all topics are assigned to writers. Contributor’s bandwidth will determine the publishing timeline.
@colorful-tones has slightly changed the topic of his post he has been working on. It was originally thought to be an Interactivity APIAPIAn 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. tutorial, but as you can read in the issue he went a different route. It was concluded that “it’s still a valuable post for the Dev Blog”, “the new focus is still really useful” and “the underlying method doesn’t need to be the same as the originally proposed method”
Next meeting: July 4, 2024, at 13:00 UTC in the #core-dev-blog channel
WordPress 6.5.4 was released on June 5 and is now available for download. Thanks to all the contributors who worked on this release too! @jorbin noted that there is now a 6.5.5 milestone in tracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., but suggests that we enter a holding pattern for ~2 weeks before deciding if it’s necessary.
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/ 18.5 was scheduled for release on June 5 (completed after the meeting). This is the final release going into WordPress 6.6, and from this point only 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 will be cherry-picked into the 6.6 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"..
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.6
As we’re in the middle of the 6.6 cycle, we used the discussion time to check in on priority items for this release. Noting that an early look of the 6.6 source of truth has been published recently by @annezazu. This is usually particularly helpful for marketing, training, and docs at this stage. Feedback, questions, comments welcomed! Expect a finalized version in line with 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). 2 on July 2nd.
@colorful-tones raised concern about whether pattern shuffling is suitable for 6.6 and identified a few items that came up right after 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. 1 that are on the WordPress 6.6 Editor Tasks board:
@joemcgill advised that if these are bugs, it is fine to fix during the beta period, but that they will need to be prioritized:
“…folks basically have the next 3 weeks do decide if these bugs should be fixed, if the feature should be removed, or if these are minor issues that don’t need to make the release. But punting the bugs is essentially committing to shipping the feature with known issues, so I would try to avoid punting them without discussion with folks closest to the features.”
@joemcgill also raised concern about the fact that we only have 3 weeks until RC1, which overlaps time that many contributors will be traveling and attending WCEU.
@marybaum requested that if we drop a feature, it would be fabulous to know that a week or so before RC 1 in order to update the About page prior to the RC 1 string freeze.
Open Floor
@apedog asked for someone to review #58932, which @joemcgill followed up on after the meeting.
@kkmuffme requested more attention to the following issues:
@joemcgill had reviewed these ahead of the meeting and mentioned that several were already too late to make this release. Specifically, the enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. tickets and one marked early. @hellofromtonya noticed that at least one needs deeper review because of a potential back-compat break.
Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.
WordPress 6.6 will ship with version 18.3 of the React library, which is identical to 18.2 but adds warnings for deprecations and other changes to help developers prepare for the ReactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces.
https://reactjs.org 19 upgrade once it becomes stable.
It’s recommended to stop using the deprecated features to ensure better compatibility with React 19 when it ships with WordPress. Keeping deprecations unchecked may lead to bugs or unintended behavior in your plugins. Addressing them is important to ensure smooth and reliable functionality.
Removed: defaultProps for function components
When searching the 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 theme repo for the use of deprecations in React 19, this one was found to be common.
React 19 will remove defaultProps for function components in favor of ES6 default parameters. This change can cause unexpected side effects when a component relies on default values provided by defaultProps.
// Before.
function Welcome( { text } ) {
return <p>{ text }</p>;
}
Welcome.defaultProps = {
text: 'Howdy!',
};
// After.
function Welcome( { text = 'Howdy!' } ) {
return <p>{ text }</p>;
}
Please refer to the official React 19 upgrade guide for a full list of deprecations and changes.
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2024 is just around the corner and Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ is on June 13! Here is a quick summary if you’re interested in joining the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. team on the day.
The Core table is focused on both WordPress Core and the Editor, and we welcome anyone who would like to contribute by writing new code, updating existing code, or even fixing bugs.
WordPress 6.6 introduces the possibility for developers to use the new React JSX transform that was first released in ReactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces.
https://reactjs.org 17.
How to use the new JSX in WordPress 6.6
Your build scripts need to apply the following changes in the built files:
Add the react-jsx-runtime to your script dependencies.
Use ReactJSXRuntime.jsx global as the output of your JSX calls.
In general, this is not something you do manually in your code base. Instead, you’ll use a build tool. The @wordpress/scripts, @wordpress/babel-preset-default and @wordpress/dependency-extraction-webpack-plugin npm packages have been upgraded to apply these transformations automatically.
Build Tools Compatibility and upgrade path
If you’re using the JSX syntax in your code base, and as long as you don’t update your dev dependencies (including @wordpress/scripts, @wordpress/babel-preset-default or @wordpress/dependency-extraction-webpack-plugin), you will continue to use the old JSX transform. This will allow your 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 built files to be compatible with WordPress 6.5, earlier versions and WordPress 6.6 as well.
When you’re ready to make WordPress 6.6 the minimum supported version of your plugin, you can update the following dependencies to use the new JSX transform.
@wordpress/scripts from version 28.
@wordpress/babel-preset-default from version 8.
@wordpress/dependency-extraction-webpack-plugin from version 6.
Going forward
The new JSX transform comes with performance improvements and optimization.
Note that the React team will deprecate the old JSX transform in the upcoming React v19 release (currently in RC).
During and after the Hallway Hangout on using the Site editor for client projects the question on how to handle version controlversion controlA version control system keeps track of the source code and revisions to the source code. WordPress uses Subversion (SVN) for version control, with Git mirrors for most repositories. workflows for blockBlockBlock 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 development surfaced. You are invited to join Core contributorsCore ContributorsCore contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac.
https://core.trac.wordpress.org and theme builders at Automattic, discussing and sharing a workflow that combines open-source WordPress tools: Create Block ThemepluginPluginA 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 WordPress Playground. Playground allows them to connect their work to a 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/ repository for managing their themes’ version control.
In this session, theme developers will demonstrate the design, development, and preview approach for Automattic’s process. You will learn how to make all the connections work seamlessly from Playground to GitHub and back again, and how to work with the features of the Create Block Theme plugin. An extensive time for Q & A allows for plenty of questions answered.
The event will take place on June 19 at 11:00 UTC. The Zoom link will be posted into the #outreach channel on the day of the meeting. There will be a recording provided for those who can’t make it.
WordPress 6.6 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. 1 is today
Performance lab 3.2.0 release scheduled for June 6
Priority Items
Structure:
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Current release (WP 6.6)
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)
#61276 was just re-opened but the enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. is committed
@joemcgill I committed the caching improvements that we’ve been working on and left a review on your PR, @spacedmonkey I think we could still consider making your proposed change, but the impact will be much smaller and should most likely start with a GB PR
@spacedmonkey I think that #53167 & #59871 are ready for commit IMO but we missed the cut off there
@joemcgill The main one that I want a 2nd opinion on is #55996 and specifically this PR, which fixes 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. that the .org team ran into when trying to apply filters to blockBlockBlock 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. content at the template level instead of the block level.
Performance Lab Plugin (and other Performance Plugins)
Otherwise, for Performance Lab itself (and metaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. items for the repo as a whole) there are currently 8 open issues/PRs: https://github.com/WordPress/performance/milestone/47
@westonruter For 3.2.0 we’ll at least have the Upgrade Notice – I think we should discuss more what should be done there, whether we bring back the adminadmin(and super admin) pointer whenever there is a big new feature or if something else less obtrusive is warranted
@joemcgill states 1136 the main one that we need to try to get wrapped up
@stellastopfer Yes, we should get the last icon and the export today EOD
Active discussion on the ticketticketCreated for both bug reports and feature development on the bug tracker. regarding the assets and agreed to go with just the “P” for now as we are short on time
Agreed to puntpuntContributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) the onboarding experience issue https://github.com/WordPress/performance/issues/1032
@westonruter I submitted the Image Prioritizer plugin for review with the plugin review team. This includes the fetchpriority=high for the LCP image, including when there are different LCP image elements for different breakpoints. It also now includes applying correct lazy-loading so that images that appear in the initial viewport in any breakpoint never get lazy-loading whereas images outside the initial viewport in any breakpoint always get lazy-loading.
Active Priority Projects
Improving the calculation of image size attributes
@mukesh27 has been working on improved image sizes algorithm
PR that ready for review:
PR #1250 – Initial implementation of improved image sizes algorithm
@joemcgill now that we’ve included the Site Health check, I think we can update the dev notedev noteEach 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. draft and then close out that project. I’ve been waiting on the doc release leads to get a process setup that we can add our dev note to.
WordPress 6.6 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. 1 is today
Performance lab 3.2.0 release scheduled for June 6
Priority items
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.6)
Future release
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:
Auto-Sizes for Lazy-Loaded Images
Embed Optimizer
Fetchpriority
Image Placeholders
Modern Image Formats
Optimization Detective
Performant Translations
Speculative Loading
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.
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, as below. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.
Announcements
WordPress 6.6 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. 1 is scheduled for June 4. Contributors will now be focused on testing and fixing bugs discovered during beta testing.
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.6
The 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). for 6.5.4 is now available for testing. The full release is scheduled for June 5.
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: 18.5
Gutenberg 18.5 is scheduled for June 5 and will include these issues. This is the last version of Gutenberg to be included in WordPress 6.6.
Discussions
As we’re in the middle of the 6.6 release cycle, we’ll prioritize any items for this release. Please review the Editor Updates section of this agenda for a list of updates of several key features related to this release.
Editor updates
You can keep up to date with the major Editor features that are currently in progress for 6.6 by viewing these Iteration issues.
Props to @annezazu for putting together these updates.
Synced Patterns now allow for overrides and they are connected with the BlockBlockBlock 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. Bindings APIAPIAn 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. – If you are interested on how this works @santosguillamot just published an Update for the Beta phase – with short videos and a list of how things work and what will have to wait for 6.7
Inserter: a PR landed to show all blocks when searching for blocks while a block is selected. The prior experience showed either a limited set or no blocks depending on allowed blocks.
Unified publish flows: an issue is open to consider returning revisionsRevisionsThe WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. to a higher level of prominence, another great area to share feedback and your perspective.
Outside of the above, @annezazu has published the 6.6 source of truth early look. It’s expected things might shift during the beta period but hopefully this helps folks prepare for the release and help educate others on what’s to come.
Tickets for assistance
Tickets for 6.6 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 if there are any questions or you will be async.
