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.
Support for PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 7.2 and 7.3 will be dropped in WordPress 7.0, currently scheduled for release in April 2026. The minimum recommended version of PHP will remain at 8.3, but the new minimum supported version of PHP will be 7.4.0.
Historically, the project has used 5% as the baseline usage percentage that a PHP version must fall below before it can be considered for a well-earned retirement. Now that usage of PHP 7.2 and 7.3 combined has fallen well below that, the process to increase the minimum supported PHP version can proceed.
The goal of increasing the minimum supported version of PHP is to ensure the long-term maintainability of WordPress. The benefits to increasing the minimum supported PHP version manifest over time across multiple areas, including 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 ecosystem, tooling and libraries for AI, the long-term perception of the WordPress project, developer relations, and eventually within the WordPress codebase itself, including its developer tooling and automated testing infrastructure.
WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. is fully compatible with PHP 8.0 to 8.3 and is beta compatible with PHP 8.4 and 8.5.
Sites that are running PHP 7.2 or 7.3 will remain on the 6.9 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". of WordPress once 7.0 is released. While only one branch officially receives security updates, fixes are backported down to WordPress 4.7 as a courtesy when possible.
What about 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/ plugin?
There are no plans to bump the minimum supported PHP version on a set schedule. The Core team will continue to monitor PHP version usage and work with the Hosting team to encourage users and hosting companies to upgrade their versions of PHP as swiftly as possible. The 5% usage threshold will continue to be used as the standard for the foreseeable future.
Props to all those that have contributed to this discussion recently. Thanks to @desrosj, @westonruter, and @jorbin for feedback and proof-reading this post.
Planning is underway for WordPress 7.0! This post outlines the proposed schedule along with a call for volunteers to support the release process.
Following the typical cadence and accounting for holidays later in the year, the proposed final release date for 7.0 is Thursday, April 9, 2026. This proposed timeline remains flexible for the resulting Release Squad and adjustments can be made if necessary as they determine what timeline works best for their schedule.
Proposed Schedule
Milestone
Date
Alpha Begins
Immediately (7.0-alpha began in trunk on November 12th with [61222])
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
Thursday, February 19
Beta 2
Thursday, February 26
Beta 3
Thursday, March 5
Beta 4
Thursday, March 12
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
Thursday, March 19
Release Candidate 2
Thursday, March 26
Release Candidate 3
Thursday, April 2
Dry Run
Wednesday, April 8
Final Release
Thursday, April 9
As always, all dates are subject to change based on development progress.
Call for Volunteers
Each WordPress release depends on contributors from across the project coming together to make it a success.
As with the 6.7, 6.8, and 6.9 release cycles, WordPress 7.0 will continue the approach of forming a smaller, focused Release Squad with making based on feedback received. This streamlined structure places more emphasis on collaboration with the various Make Team Reps, who are encouraged to help coordinate efforts from within their respective teams. The goals are to reduce the overhead on the Release Squad while still ensuring each team’s contributions and priorities are represented throughout the cycle, and to reduce overlap between a Make Team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. and that team’s Release Squad Leads. Noteworthy Contributors will be captured from Team Reps towards the end of the release cycle.
While the end goal is to publish the final release of WordPress 7.0 during 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/. at 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. Asia (which follows India Standard Time), traveling to or attending WordCamp Asia is not a requirement to serve on the release squad. All communication related to the release process will continue to take place 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.
If you are interested in helping lead WordPress 7.0 in one of the following roles, please comment below or reach out in the #7-0-release-leads Slack channel:
Release LeadRelease LeadThe community member ultimately responsible for the Release. – Matt Mullenweg (@matt)
Release Coordination – helps manage timelines, cross-team collaboration, and status updates
Tech Leads – oversees coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development (including 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/), triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., and critical issues
Triage Lead – help monitor issues, shepherd patches, and guide contributors
Test Lead – coordinates testing efforts across the community and test reports
Whether you have led a release before or are looking to get involved for the first time, there are many ways to contribute. Volunteers of all backgrounds and experience levels are welcome!
If you are interested in volunteering, please leave a comment below noting your preferred area(s) by Friday, January 16th.@4thhubbard (or a designee), will review the nominations shortly after to confirm and announce the release squad as soon as possible.
Together we can make WordPress 7.0 the best one yet!
The 6.9 release retrospective is open to all contributors, not only release squad members. Broader feedback helps improve future release processes.
Discussions 💬
PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Extensions List – filter
The discussion covered whether the PHP filter extension is set as default. See the Hosting Team Handbook. @dmsnell asked about the impact on CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., how similar changes were handled before, and mentioned concerns about using functions like FILTER_VALIDATE_EMAIL. @realloc noted that Core uses filter only in a few places, mainly in PHPMailer, and suggested removing those usages instead of requiring the extension. The topic will be discussed again next week.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
The various curated agenda sections below refer to additional items. 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 or bring them up during the dev chat.
Announcements 📢
Happy New Year!
The first Dev Chat meeting of the year will take place on January 7 at the usual time.
6.9 Release Retrospective
The 6.9 release retrospective is open to all contributors, not only release squad members. Broader feedback helps improve future release processes.
Discussions 💬
The discussion section of the agenda is for discussing 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. 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.
PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher Extensions List – filter
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 indicate whether you intend to be available during the meeting for discussion or will be async.
The full chat log is available beginning here on Slack.
View Transitions to CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.
@westonruter kicked off the discussion by referencing plans to graduate the View Transitions plugin into core for WordPress 7.0, noting it pairs well with the adminadmin(and super admin) refresh and introduces theme support for configuration.
@mikewpbullet raised concerns about potential clashes with plugins or custom code and suggested a UIUIUser interface checkbox or update splash screen guidance, while @schmitzoide proposed a general “Activate Advanced Features” checkbox.
@westonruter clarified that sites could opt out via code toggles like filters or theme support, aligning with WordPress philosophy of decisions over options.
@westonruter highlighted ticketticketCreated for both bug reports and feature development on the bug tracker.#64066 to shift default eagerness from conservative to moderate when caching is detected, aiding View Transitions by reducing link click delays.
@mikewpbullet raised concerns about page caching rarely helping admin performance and noted that server-side caching via nginxNGINXNGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. or Varnish often runs without WordPress plugins that Site Health could detect.
@westonruter explained that core’s Site Health test already accounts for proxy caches beyond just plugins and remains extensibleExtensibleThis is the ability to add additional functionality to the code. Plugins extend the WordPress core software. for improvement.
@adamsilverstein acknowledged that comprehensive coverage is impossible but emphasized WordPress’s advantage in rendering detection rules dynamically.
@schmitzoide asked whether Site Health could diagnose performance issues.
@westonruter added that Performance Lab includes additional tests for excessive blocking scripts and styles.
@westonruter responded to @mikewpbullet‘s earlier admin concerns with two ideas: enabling bfcache in the admin for smooth back/forward transitions #63636, and considering speculative loading for admin menu items on sites with object caching enabled.
@mikewpbullet raised concerns that users may not want cached admin pages when hitting back, and that object caching is unlikely to help with page load times in admin where slowness comes from 3rd party background requests.
Admin and Dashboard Performance
@adamsilverstein shared that tackling the Dashboard landing page is a priority for the new year and mentioned an existing performance ticket. @westonruter later identified ticket #55344 and suggested the Dashboard could leverage preload links for commonly-used resources like the edit post screen assets.
@westonruter connected this to ticket #57548 about retiring script and style concatenation in wp-admin, explaining the benefit would be effective preloading but noting that concatenation might still offer better performance without a primed cache, which requires benchmarking. This discussion led to exploring Compression Dictionaries, a newer capabilitycapabilityA capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). that @westonruter explained allows browsers to reuse intersecting portions of different concatenated bundles.
@mikewpbullet questioned the need given server-side Brotli compression already exists.
@westonruter clarified this isn’t about PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher-based gzip but about the new compression dictionary transport standard that enables reusing cached bundle portions across different pages, particularly beneficial 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. themes enqueue block styles on-demand based on page content, and in WordPress 6.9 this also applies to classic themes, so compression dictionaries would allow concatenating these varying bundles while enabling browsers to cache and reuse individual styles across pages with different bundles, significantly reducing CSSCSSCascading Style Sheets. downloads for both logged-in and logged-out users.
Roadmap and Future Planning
@schmitzoide asked about the team’s roadmap. @westonruter linked to the 2024 roadmap and explained this meeting serves to shape 2026 priorities, noting they’ll likely use milestoned TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets rather than a full roadmap post given fewer active contributors currently.
@schmitzoide asked about graduating additional Performance Lab features and shared plans to propose ideas from block theme optimization work via repository tickets. @adamsilverstein encouraged opening issues for any PerfNow conference ideas worth experimenting with in 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.
@sirlouen asked about integrating performance testing activities similar to 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/’s approach, including 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/ Actions tagging and handbook expansion. @westonruter welcomed aligning testing strategies with other core teams in the new year.
Congratulations to all who helped make WordPress 6.9 possible!
Now that the release cycle is complete, you’re invited to reflect and share your thoughts on the release cycle, release processes, release squad, or whatever else is on your mind. Feedback loops are critical to learning what works and what doesn’t so that the teams involved can iterate on the processes to improve for future releases.
Everyone is welcome to submit feedback about the release using this form, even contributors who did not contribute directly to the release itself.
A member of the community that casually observes a release cycle will have very different thoughts and opinions than someone who was heavily involved on a weekly or daily basis. The more viewpoints and backgrounds represented within this feedback 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. the better. So please take a moment to complete the form or leave public feedback in the comments below.
Please note: the survey is not anonymous, but anything submitted will be anonymized before being shared in a post summarizing the results. Your 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/ username is required just case the person processing the responses needs to reach out to you for further clarification.
The form and comments will be open until January 15, 2026. A follow-up post with the collected, anonymized results will be published shortly after.
Again, thank you for your contributions to 6.9 “Gene,” and for taking the time to provide valuable feedback to help make future releases even better!
Props to @amykamala, @desrosj for the peer review.
“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-newtagtagA 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.)) 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.
This release brings a dedicated Fonts page for easier typography management, responsive Grid layouts, continued progress on the Site Editor’s routing infrastructure, and improvements to the image editing experience.
Dedicated Fonts page for easier typography management
A dedicated Fonts page is now available under the Appearance menu 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. themes. Until now, font management has lived deep inside Global Styles, requiring navigation through several panels to install or preview a font. This new standalone page lets block theme users browse, install, and manage their typography collection in one dedicated space. Support for non-block themes will come next.
Under the hood, this page is built on a new routing infrastructure for the Site Editor, designed to improve navigation and support new top-level pages in wp-adminadmin(and super admin). View transitions are now wired into this routing layer, providing early zoom/slide animations when navigating between pages.
Image editing improvements
The in-editor image cropper has been rebuilt on a new foundation. While the workflow remains familiar, you’ll notice improvements: aspect ratios and zoom levels now persist when rotating images, fixing a long-standing frustration. This refactor also lays the groundwork for future image-editing enhancements. (#72414, #73277)
Responsive Grid block
The Grid block now adapts to different screen sizes when columns are set. Layouts will adjust naturally across devices, providing a more consistent experience for visitors on mobile and desktop alike.
wordpress/data: Migrate index.js to index.ts. (73597)
DataViews
Add min/max validation support to DataForm inputs. (73465)
Field 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.: Display formats for number and integer types. (73644)
Try using 24px padding for consistency across different uses. (73334)
Update operator labels and deprecate the isNotAll. (73671)
Internationalization
Fields: Update “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.” translationtranslationThe process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. to provide verb context. (73704)
Layout
Enable grid block to be responsive when columns are set. (73662)
Try removing top and left grid drag handles in stable (auto) mode. (73864)
Media
Add media-specific fields for use with Attachment post types and DataViews/DataForm. (73071)
Pattern insertion: Drag chip when multiple blocks of the same type in a pattern are dragged. (73681)
Block Library
Accordion Heading: Add default style for classic themes. (73608)
Add i18ni18nInternationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. support for math block error messages. (73643)
Breadcrumbs: Improve home page and front page handling. (73487)
Classic Block: Restore HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. editing option. (73865)
Fix Page List block HTML rendering in editor. (73614)
Fix Page List block button HTML rendering to escape at output. (73641)
Fix align right issue on avatarAvatarAn avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. component. (67494)
Post Title: Add fallback no title in edit mode when is readOnly. (73750)
Post Title: Fix empty heading element when post_title is empty but get_the_title returns markup V2. (73841)
Prevent flipping the border style when creating RTL stylesheets. (44170)
Verse Block: Prevent text overflow off-screen when the previous block has float. (45221)
Block Transforms
Gallery: Fix missing captions shortcodeShortcodeA shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. transform. (73748)
Command Palette
Commands: Restrict editor UIUIUser interface commands to entity-edit context. (73717)
Fix button background and focus outline styles. (73722)
Global Styles
Fix: Default color variations not showing in global styles. (73742)
Global Styles UI: Remove unnecessary padding for Navigatior component. (73810)
Global Styles UI: Restore borders for preview items. (73741)
Global Styles UI: Revert some of the padding / markup changes from #73334. (73834)
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: Override coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. classic theme styles. (73580)
Notes: Avoid incrementing comment_count when notes are resolved or reopened. (73689)
Notes: Ensure notes never show on the comments page. (73640)
Paste
Raw Handling: Fix grok markdown pasting issues. (73019)
Patterns
contentOnly patterns: Mark patterns as contentOnly by adding metadata.patternName to the root block. (73477)
Templates API
Template Activation: Update template ID format test. (73629)
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)
Block Editor
Fix block toolbar icon CSSCSSCascading Style Sheets. when using show icon label preference. (73674)
Performance
Block Editor
Block Styles: Avoid re-rendering when typing. (73701)
Theme
Theme: Better max chroma detection for taperChroma. (73625)
Experiments
Block API
PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher-only blocks: Pass all metadata from PHP registration to the client. (73556)
Collaboration
Real-time collaboration: Add UndoManager support for collaborative editing. (72407)
Real-time collaboration: Disable syncing for “synthetic” template posts. (73526)
UI: Add Stack component leveraging gap spacing design tokens. (73308)
UI: Update Stack component to support only gap tokens. (73852)
Documentation
Block API
Block 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. schema: Add visibility key to supports definition. (73612)
Docs: Add “Migrating Blocks for iframeiframeiFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. Editor Compatibility” page. (73778)
Docs: Add missing periods to example descriptions in block-attributes.md. (73666)
Linting: Disable the wordpress dependency group lint rule. (73616)
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.: Add Carlos Bravo to mailmap. (73840)
Meta: Introduce .mailmap for transforming author names. (72412)
Scripts: Update license checker to ignore invalidinvalidA resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. package entries. (73528)
Storybook: Skip transpilation of build-modules files. (73780)
wp-build: Fix invalid package references for peer dependencies. (73676)
wp-ui: Add legacy export fields to package.json. (73850)
Remove custom import resolvers and package subpath syntax rules. (72978)
Tests: Emulate form blocks experiments in integration tests. (73705)
Tests: Update assertion for ‘Global styles 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.’ end-to-end test. (73685)
Note: This was the final Dev Chat of 2025. The next Dev Chat will take place on January 7, 2026. Bug scrub meetings may still take place in the meantime. Thanks everyone, and see you in the new year.
Announcements 📢
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/ 22.3 has been released!
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. Asia 2026 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/.: Call for table leads
Contributors interested in helping with the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team during the WordCamp Asia 2026 Contributor Day can contact @krupajnanda.
WordPress 6.9 Hotfixes
Since the WordPress 6.9 release, several issues have been reported, temporary workarounds are available as plugins and will be included in a maintenance release planned for January 2026 at the earliest, with full details in the linked post.
Planning for WordPress 7.0
With 6.9 released, attention is already shifting toward WordPress 7.0, including early ideas, focus areas, and ways to contribute, all outlined in the follow-up post.
Real-time collaboration: Early user feedback
Real-time collaboration for WordPress 7.0 has been in WordPress VIP 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. testing since October 2025, with early feedback covered in this post.
Discussions 💬
Dev Chats Over the Holidays
During today’s meeting, it was decided to skip the next two Dev Chat meetings, making today’s meeting the final Dev Chat of the year. Bug scrub meetings may still take place during this time. The next Dev Chat is scheduled for January 7, 2026.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
The various curated agenda sections below refer to additional items. 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 or bring them up during the dev chat.
Announcements 📢
WordPress 6.9 Hotfixes
Since the WordPress 6.9 release, several issues have been reported, temporary workarounds are available as plugins and will be included in a maintenance release planned for January 2026 at the earliest, with full details in the linked post.
Planning for WordPress 7.0
With 6.9 released, attention is already shifting toward WordPress 7.0, including early ideas, focus areas, and ways to contribute, all outlined in the follow-up post.
Real-time collaboration: Early user feedback
Real-time collaboration for WordPress 7.0 has been in WordPress VIP 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. testing since October 2025, with early feedback covered in this post.
Discussions 💬
The discussion section of the agenda is for discussing 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. 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.
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. Asia 2026 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/.: Call for table leads
@krupajnanda asked whether contributors would be available to volunteer as table leads for the WordCamp Asia 2026 Contributor Day.
No further topics have been submitted for this discussion round yet. If you have something in mind, feel free to leave a comment below this post.
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 indicate whether you intend to be available during the meeting for discussion or will be async.
You must be logged in to post a comment.