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.
Scheduled 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. scrubs are completed 😊 Thanks to everyone! Please continue testing 6.6 💪
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). Bug Scrubs will be conducted if needed.
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 RC3 was released on July 9. We are in a hard string freeze. Note that the dev-feedback and dev-reviewed workflow is required prior to committing to 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". (handbook reference).
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
We are currently in the WordPress 6.6 release cycle. The WordPress 6.6 is scheduled for Tuesday, July 16. There will be a dry run of the release on Monday, July 15 which starts a 24-hour code freeze of the 6.6 branch.
Next maintenance release
No maintenance releases are currently being planned. We will take time to discuss any important tickets that may require a maintenance 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: 18.8
Gutenberg 18.8 is scheduled for July 17 and will include these issues. This version will NOT be included in the WordPress 6.6 release and will be included with 6.7.
Discussions
As we’re at the end 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 on several key features related to this release.
Review status of any outstanding issues (if applicable)
You can keep up to date with the major Editor features that are currently in progress by viewing these Iteration issues.
Props to @annezazu for putting together these updates each week.
Canonical blocks: there’s a latest update from some folks working to explore the idea. TLDR: work on a few requested blocks but put these blocks behind an opt-in feature flag in the GB 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 to allow for quickly iterating and experimenting.
The propotype for the DataFormAPIAPIAn 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. has landed in the plugin. It renders the Duplicate action modal for pages and follow-up work includes replacing other action modals until the pieces are in place to create a details panel for a post type.
Font Library: a PR is underway to group fonts by source to better distinguish what might be installed by a theme vs a user and a new PR building on a prior effort is in process to add a font size preset UIUIUser interface to allow users to edit the font size presets using the editor.
Inserter: A PR landed to Remove the dialog behaviour, meaning the Inserter now remains open to match how all the other panels work.
Interactivity API: new iteration issue has been shared Interactivity API iteration for WordPress 6.7. TLDR: work will begin on the Gallery 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. lightbox and the Query block’s Instant Search along with internal improvements to ensure that the Interactivity API’s code is as simple and stable as possible.
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.
This hallway hangout seeks to be another snapshot of what’s being worked on in 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/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 to provide broader awareness to more WordPress contributors and get feedback. In line with the first edition, the hope is to come together early to talk about different features, flush out concerns sooner, help more folks get involved, and find ways to work better together.
Important note: this hallway hangout will likely last for 90 minutes instead of the usual 60 minutes to allow for ample time to demo and discuss.
How to join
If you’re interested in joining, the Hallway Hangout will happen on 2024-08-15 15:00 . A Zoom link will be shared in the #coreSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel before starting and all are welcome to join, whether to listen or participate, for as long or as little as you’d like. This will be recorded and recapped. Note that the time for these hallway hangouts are intentionally rotated to allow for different folks to participate in different ones.
If you’re unable to make it but have something to comment on or share, I welcome you to leave feedback in the comments of this post or dive straight into the 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 be the repository owner. https://github.com/ issues linked below. This isn’t meant to replace any particular way to get involved but is meant to streamline and offer a more high bandwidth way to connect.
Agenda
At a high level, the following items are currently on the list to go through but more might be added depending on how work shapes up in the coming weeks. We’ll get through as many of these as we can in the order as shown below, with either demos to go through from figma, from a PR, or via the Gutenberg plugin.
Next up for the Data views efforts and its relationship to the Adminadmin(and super admin) Redesign. This includes adding data views to Posts and the Media Library as experiments.
Gallery block lightbox and the Query block’s Instant Search powered by the 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..
Zoomed out view and the experience coming together to focus on patterns rather than granular 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. editing, including Advancing contentOnly editing.
In an effort to focus on some of the larger, more relevant work, let’s start here. If you’d like to present something, just comment below too! Hope to see you there.
WordPress 6.6 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). 3 happening today, ahead of the main release scheduled for Tue Jul 16
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 (WP 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)
@joemcgill We already have a good number of performance focus tickets on the 6.7 milestone—most of which are roll-overs from 6.6. I know that I need to review and clean up the ones that I’m responsible for, but I would encourage us all to do so.
Performance Lab Plugin (and other Performance Plugins)
This includes fundamental enhancements to Optimization Detective to make it much more powerful to be able to make optimizations to a document (e.g. what Embed Optimizer requires)
PR #1329 – Merge feature 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". to trunktrunkA 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.
@joemcgill there’s also a proposed name change for the Auto-Sizes plugin
Active Priority Projects
Improving the calculation of image size attributes
Discussed above
Improved template loading
@joemcgill The template loading work is mainly wrapped up in 6.6. There are a few minor follow-up issues that I think we’ll continue to track but I’ll work on summarizing next steps and closing up those GH issues.
The two things that are on my mind in the short term are:
Supporting the Plugin Check project as the Plugin Review team are working to get it integrated into their systems.
Improving our performance metrics for both CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. and GB.
Plugin Check
@joemcgill For Plugin Check, I’d like to get more eyes on this conversation., which may end up being a requirement for them to do the integration
Open Floor
@mukesh27 Do we have any open issue for Improving our performance metrics for both Core and GB
I do think it would serve us well to put some focus on this early in the 6.7 cycle so we can more easily pinpoint which commits have server timing performance implications. That’s been a big challenge the past 2 releases. (In the GB repo specifically)
@pbearne I am thinking of suggesting that WP has an infrastructure release where we update/re-organize the PHPUnit tests etc. as without core committers actively making the changes it will never get done. The performance testing could be part of this
@joemcgill I would suggest proposing the infrastructure changes you have in mind and whether those become a release focus or not, could be secondary.
WordPress 6.6 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). 3 happening today, ahead of the main release scheduled for Tue Jul 16
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
Image Prioritizer
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 most recent default theme, Twenty Twenty-Four, has been praised for its design and flexibility. It is time to start thinking about Twenty Twenty-Five, which will be released with WordPress 6.7 in November 2024. Twenty Twenty-Five will be a block theme showcasing new Site Editing features introduced this year.
Share your ideas
What types of sites do you want to create with the theme?
What problems do you need the theme to solve to be able to create these sites?
Is there an existing feature that you want the theme to support?
Please add your comments below. Feedback and ideas will be collected continuously. You are also welcome to participate in the discussions on the GitHub repository and in the #core-themes channel on 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/..
Note: Ideas won’t necessarily guarantee inclusion in Twenty Twenty-Five but might be considered when creating other community themes.
More information will be provided later for those who would like to contribute to the theme with design, code, testing, or documentation.
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.
We now have 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 be the repository owner. https://github.com/ team set up for Developer Blog Contributors. Every writer and reviewer will be part of it. That way, contributors can label issues, move them forward on the Project board and check off items from a Checklist, like the publishing checklist. We roll this out gradually, one contributor at a time.
The design team is also working on creating Figma templates for featured images for the blog, which will help standardize and simplify the process of creating featured images.
Newly published post since the last meeting:
Since the last meeting, we published four articles.
Since the last meeting, we published the following articles
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 proposal to introduce video content was also discussed in more depth.
The production process is slightly different from the blog post process, as outlined in the proposal. That is also to make sure that an author doesn’t go through the production of a video and then have it not approved. The danger can be minimized by a multistep approval process of scrip and storyboard before production begins. A new creator could be asked to record a short section for review before going into full production, with opportunity to provide further feedback.
We won’t be able to provide video editing services, but other teams have some great guidelines and tips for creating videos, we can share with future video bloggers.
The proposal also outlines the need for branded assets for thumbnails, lower thirds and outro. We certainly collaborate with the design team, once there is bandwidth available.
The next step is that Ryan will submit an overview of all directives of the 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. and provide an example of the first video. It will also be the test drive of the suggested process from which we can iterate afterward.
To summarize: Video content is approved in principle, the details need to be ironed out. Thank you to Ryan for the great work on the proposal and volunteering to be the first video blogger.
Next meeting: August 1, 2024, at 13:00 UTC in the #core-dev-blog channel
Please leave your feedback about the schedule and release squad size in the comments by July 19th.
If you are interested in participating in WordPress 6.7’s release squad as a lead, please show interest in the comments below, clearly specifying the role.
With WordPress 6.6 almost ready, it’s time to start planning WordPress 6.7 so that the release leads can participate from the start of the release cycle.
The timeline for the third release of 2024 takes into consideration 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. US in mid-September. To avoid having major milestones (Beta1, RC1) conflictconflictA conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with flagship events, this proposal suggests having WordPress 6.7 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 after WordCamp US with a small buffer in between.
According to the schedule proposed below 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/ release cadence, WordPress 6.7 would include up to Gutenberg 19.3 for a total of 8 Gutenberg releases.
Proposed WordPress 6.7 Schedule
Milestone
Date
Alpha (trunktrunkA 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.7 release)
June 25, 2024
Beta 1
October 1, 2024
Beta 2
October 8, 2024
Beta 3
October 15, 2024
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). 1
October 22, 2024
Release Candidate 2
October 29, 2024
Release Candidate 3
November 5, 2024
Dry Run
November 11, 2024
WordPress 6.7 General Release
November 12, 2024
Please leave your feedback about the schedule in the comments by July 19th.
Release Leads call for volunteers
With the recent switch to using the microsite as the base for the About page, some of the Marcomms lead’s responsibilities increasingly overlap with the Design Lead. Considering recurring feedback about the excessive number of release roles, we propose experimenting with combining the Marcomms and Release Coordination roles. This new consolidated role would absorb the duties of the Marcomms lead, streamline communication, and enhance collaboration, addressing the feedback on role complexity and redundancy while improving overall efficiency.
Leads in the squad should have proven experience and availability during the release cycle. Less experienced folks and newcomers are still welcome to followalong the process in preparation for future releases.
Some roles have already been filled by volunteers from the previous call, while others remain open. The TBDs in the list below indicate the number of spots that still need to be filled.
Release LeadRelease LeadThe community member ultimately responsible for the Release.: Matt Mullenweg
Release Coordination and Communications: TBD
CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Leads: Peter Wilson, Kira Schroder
TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads: TBD
Documentation Leads: TBD
Test Lead: TBD
Design Lead: TBD
Performance Lead: TBD
Default Themes Lead: TBD
All release decisions will ultimately be this release team’s to make and communicate while gathering input from the community.
As a reminder, if you are interested in participating in WordPress 6.7’s release squad as a lead or as a cohort, please show interest in the comments below, specifying the desired role and level of involvement (lead/cohort).
WordPress 6.6 RC2 was released yesterday, on July 2. We are still in a hard string freeze. Note that the dev-feedback and dev-reviewed workflow is required prior to committing to 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". (handbook reference).
A big thank you to everyone who is working on these releases!
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
We are currently in the WordPress 6.6 release cycle. See the Roadmap Post for more information about what is planned for this release. The 6.6 RC3 is scheduled for Tuesday, July 9.
Next maintenance release
No maintenance releases are currently being planned. @mikachan noted that based on the latest messages in the #6-5-release-leads channel, all seems good!
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.8
No discussion was had about the next Gutenberg release during this meeting.
Discussion
Nobody proposed any discussion topics for this week, so @mikachan addressed some follow-up tasks from our last meeting.
Can we extend the hard string freeze date to 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). 3 for major releases?
@audrasjb did not have any further updates from last week.
@marybaum suggested that maybe RC 2 would be a possible milestone for string freeze
@mikachan asked if we need to update any handbook docs and suggested being more specific about this in the Release Candidate section, and note which 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). triggers the hard string freeze.
Do we have further information on who can help progress a PR in the WordPress Importer repo?
@mikachan shared an update from @joemcgill that he’s reached out to some folks familiar with the WP Importer 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 to clarify next steps for maintaining that plugin and is awaiting some feedback. We hope to have an update by next week.
Open Floor
Imdad suggested that we update the documentation about the Future Release milestone in TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., but wasn’t around to clarify what would be helpful.
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.
“What’s new in 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/…” 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.
A total of 115 PRs were merged in Gutenberg 18.7, with 7 first-time contributors! With WordPress 6.6 rapidly approaching, many contributors are focusing on 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. However, this release still includes some great features and enhancements, including the manual mode for the grid interactivity experiment!
In order to allow more precise manipulation of the grid, all grid items are now fixed in place when using manual mode. Grid items can then be moved around with drag and drop, 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. movers (in any direction), or by changing the values of column and row in the Dimensions sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. This new feature is a part of Grid interactivity and is available behind an experimental flag. (#61025)
Content panel for template parts
Template parts now show the content panel in the editor settings. (#62034)
Other Notable Highlights
Text orientation controls have been added to more blocks (site-title, site-tagline, verse, and button block.) (#62727)
The sticky toggle for posts can be found in its new home, the “Status and visibility” popover. (#62782)
The document bar is now displayed when viewing the Style book and Style 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. (#62669)
Rename yieldToMain to splitTask and export from wordpress/interactivity. (62665)
Update: Check assignable properties on the duplicate action. (62590)
Update: Followups to the template and template_lock rest apiREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. addition. (62696)
Update: Reverse backportbackportA port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. changes on post type REST API changes. (62751)
Display the DocumentBar for Style Book and Style Revisions. (62669)
fetchLinkSuggestions: Allow for partial matching. (62570)
DataViews: Support passing the registry to actions callbacks. (62505)
Add tooltip on hover of color and typography presets. (62201)
Revert change that removes the social link block when pressing backspace in the URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org Popover. (61344)
Bug Fixes
Add context in post actions 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.. (62443)
Add html to reset styles for the .editor-styles-wrapper container. (62350)
Cherry pick script: Make authenticated requests. (62473)
Editor: Fix blocked Post Publish Panel buttons on mobile. (62736)
Fix rawHandling, pasteHandling for mixed content with blocks and classic. (62545)
Fix: Active template is not highlighted properly in list view. (62811)
Fix: Check Capability to create pages on DataViews add new page button. (62592)
Fix: Check ability to create patterns on the add new pattern modal. (62633)
Fix: Check create capability on duplicate post action. (62620)
Fix: Check permissions on duplicate pattern and template part actions. (62757)
Fix: Comments and Pingbacks get cleared out when a pattern is edited. (62507)
Fix: DataViews: Active page is not highlighted properly in list view. (62378)
Fix: Include permission management on permanently delete, rename, and restore. (62754)
Fix: List view renders an empty menu when no actions are eligible. (62786)
Fix: Post_type template is not used when creating a page in site editor. (62488)
Fix: Resetting template part causes notification saying it’s been delete. (62521)
Fix: The trashTrashTrash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. post action doesn’t take into account user capabilities. (62589)
Inspector: Improve handling of long words in post titles. (62691)
Revert “Revert test data for WithSlug variation (#62579)”. (62587)
Add letter spacing inheritance for the navigation block. (62745)
Caption utility component: Allow the main CSSCSSCascading Style Sheets. Class Name to be excluded from the markup. (62485)
Fix: Empty style attribute issue in navigation block. (62600)
Image Block: Fix Aspect Ratio button position. (62776)
Media & text: Update the image replacement logic. (62030)
Post Date Block: Fix PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher warning error. (62783)
Template Part: Improve how the tagtagA 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.) name attribute is handled. (62785)
fix: Update block categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. to design and build documentation. (61905)
Global Styles
Allow children of alignfull flow layouts to have root padding. (62670)
Section Styles: Switch away from using init for variation registration. (62640)
Skip registration of variation styles when unsupported. (62529)
Styles: Lower specificity of figcaption style to allow theme.jsonJSONJSON, 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. override. (62689)
Components
CustomSelectControl V2: Fix setting initial value and reacting to external controlled updates. (62733)
CustomSelectControlV2: Handle long strings in selected value. (62198)
Block Editor
Raw handling: Fix too aggressive indented list removal. (62622)
Writing flow: Split heading into default block. (61891)
AccessibilityAccessibilityAccessibility (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)
Fix: Remove inexistent link from the documentation. (62624)
Interactivity API docs: Add wp-async directives doc. (62663)
Query LoopLoopThe 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. block: Clarify explanation around query loop variation example. (62605)
Small Typo correction in block-library.md file. (62765)
Update link to API section in block-editor README.md. (62671)
Update old links in wordpress/babel-preset-default. (62616)
Updates the reference links in wordpress/compose documentation. (62593)
Autoformat e2e-tests package JavaScriptJavaScriptJavaScript 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/.. (62572)
Edit site: Do not autoformat edit-site/lib. (62573)
Remove changelog checks for branches other than trunktrunkA 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.. (62645)
Skip test: Create a new page, edit template and toggle page template preview. (62799)
Tests: Simplify test set up in WP_Block_Supports_Block_Style_Variations_Test. (62637)
Theme JSON resolver: Read theme.json files from the styles/ folder only once. (62638)
Build Tooling
Generic name for previous version of WP tests. (62853)
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 be the repository owner. https://github.com/ PHP changes workflow: Remove it. (62609)
Various
Update Private API opt-in string for WP 6.6. (62635)
Update caniuse-lite dependency to latest version. (62611)
First-time contributors
The following PRs were merged by first-time contributors:
@aatanasovdev: Caption utility component: Allow the main CSS Class Name to be excluded from the markup. (62485)
@dilipbheda: Correct documentation for WP_Block_Parser_Frame class. (62598)
@graylaurenm: Add letter spacing inheritance for the navigation block. (62745)
@ivan-ottinger: Editor: Fix blocked Post Publish Panel buttons on mobile. (62736)
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 RC2 was released on July 2. We are in a hard string freeze. Note that the dev-feedback and dev-reviewed workflow is required prior to committing to 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". (handbook reference).
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
We are currently in the WordPress 6.6 release cycle. The WordPress 6.6 RC3 is scheduled for Tuesday, July 9.
Next maintenance release
No maintenance releases are currently being planned. We will take time to discuss any important tickets that may require a maintenance 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: 18.7
Gutenberg 18.7 is scheduled for July 3 and will include these issues. This version will NOT be included in the WordPress 6.6 release and will be included with 6.7.
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 on several key features related to this release.
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 each week.
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.: open question started around Should the bindings logic be moved to core functions instead of using a hook? and recent request for new designs for the ability to add/remove bindings in attributes panel.
Twenty Twenty-Five is open for business with a fresh 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 be the repository owner. https://github.com/ repo: https://github.com/WordPress/twentytwentyfive
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.
Follow-ups from last week
There were a couple of points raised in last week’s dev chat that would be good to check in with:
Can we extend the hard string freeze date to 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). 3 for major releases?
Do we have further information on who can help progress a PR in the WordPress Importer repo?
You must be logged in to post a comment.