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.
It’s time to get WordPress 7.0 ready for release, and help is needed to ensure it’s smooth and 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.-free. Whether you’re an experienced contributor or joining in for the first time, everyone is welcome! 🎉
Schedule Overview
Regular bug scrubs are being held twice a week with @audrasjb and @juanmaguitar leading them. As the release date approaches and activity ramps up, the number of scrubs may be increased. These efforts will help ensure everything is on track for a smooth launch. Participation is welcome at any of these sessions, so feel free to join. Bring questions, ideas, and let’s scrub some bugs together!
The full chat log is available beginning here on Slack.
WordPress Performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
@westonruter shared a Trac query covering performance-related tickets milestoned for WordPress 6.9.1 and 7.0.
@westonruter shared that for ticketticketCreated for both bug reports and feature development on the bug tracker.#61500, some work was done recently as part of the CodeMirror upgrade effort.
@westonruter explained that ideally there would be a declarative way to add script modules as dependencies for classic scripts, and noted that a workable approach is to register an empty script module that declares module dependencies, and then enqueue that module whenever the classic script is enqueued. @westonruter shared reference to example diffs demonstrating this workaround and mentioned being glad to find a quick solution.
@westonruter replied that the comment had been seen the night before and initially mentioned not having a patchpatchA special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. yet, then noted that a PR already existed and shared PR #10799. @westonruter reviewed the PR, said it looked good, and approved it.
@westonruter brought up #64066 and shared that @gilbertococchi is actively working on collecting data to support switching to moderate prefetch by default on sites with caching.
@westonruter referenced a Slack thread where LCP passing rates for conservative versus moderate prefetch were discussed and noted that additional data is being gathered by flipping a few CrUX-eligible sites from conservative to moderate to compare LCP passing rates and page hit increases over time.
@westonruter added that landing #64066 is related to #64370, noting that the latter needs to land to ensure reliable detection.
@westonruter replied that the PR had just been closed.
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)
@westonruter shared recent experience using 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/ Copilot together with Gemini CLICLICommand Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. locally, describing it as immensely useful both for review and implementation work. @westonruter described Copilot as significantly better than a traditional linter during reviews and noted that it can provide strong first-pass implementations. @westonruter shared PR #10778 as an example of using Gemini CLI during the CodeMirror upgrade and explained that a detailed historical and technical specification was provided to the tool.
@westonruter also shared that Copilot was used to draft a Performance Lab fix while on public transit using only a phone, referencing PR #2346.
@dmsnell cautioned that Copilot can sometimes reintroduce defects during PR reviews, sharing an anecdote where Copilot repeatedly flagged and reintroduced a PCRE-related 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. even after it had been fixed.
@justlevine added that this behavior can indicate ambiguities in code and suggested that improving self-documentation helps both humans and LLMs.
@dmsnell emphasized the need for extra care when LLMs introduce defects, as they can confidently repeat mistakes if the surrounding code does not change enough.
@westonruter agreed, noting that while hallucinations occur, the tools still provide good feedback most of the time and help shift focus away from minutiae like coding standards toward higher-level problem solving.
@dmsnell raised the topic of memoizing wp_normalize_path, noting observed performance improvements of roughly 1ms during WordPress startup in certain environments. @dmsnell explained that while this is a micro-optimization, it can have meaningful impact at scale and shared that @josephscott has been investigating early startup costs using production measurements. @dmsnell mentioned having tested earlier versions without caching and discussed trade-offs between caching and alternative approaches, including replacing PCRE calls and addressing what may be a latent bug.
@westonruter asked whether similar performance benefits were observed across different approaches.
@dmsnell replied that while direct testing had not yet been done for all variants, prior comparisons suggested the cache provided most of the benefit at a fraction of the cost, and that both approaches could potentially coexist.
@westonruter summarized this as a “both/and” situation rather than an either/or choice.
7.4 is currently at ~22% of all WP sites. So let’s find ways to work with Hosts and site owners to decrease that number.
WordPress 6.9.1 Release Schedule
The WordPress 6.9.1 maintenance release is planned on February 3, 2026. See the release schedule announcement for more information.
@jorbin shared this update: “Just a general note that here are multiple scrubs being held each week (see the 6.9.1 announcement). If you want to join for one of those or feel free to work on any of the tickets in tracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. or 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/ in your own time. You may see pings on those tickets, if you are able to help it would be appreciated as we work to resolutions on these. No concerns as of now, we seem to be in good shape for a release on 3 February.”
This post summarizes the feedback received from the WordPress 6.9 retrospective. Thank you to those who contributed their feedback via the retrospective survey and comments on the post!
For ease of reading, feedback has been synthesized. Full feedback is available for review in the anonymized form responses and comments to the original post.
Please remember that the following feedback are suggestions to bear in mind for future releases rather than action items for implementation.
What would you keep?
Having two triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. leads in different parts of the globe seemed to work well getting more contributors involved.
Clearer test instructions.
Long-term planning, regular check-ins, commit freeze, and a consistent cadence made the release feel stable and well-managed.
What would you add?
More automation for defined, common steps within the release cycle could help reduce stress.
Better documentation for the tasks required by the different release leads.
More community suggestions into CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
Earlier on boarding for release squad members.
What would you change, reduce, or remove?
Release Candidates should be tested more extensively.
Points of contact and ownership should be more clear, especially for new contributors.
Reduce manual work by increasing automation where possible.
What else would you like to express about any part of the release cycle or release squad?
The 6.9 release was well coordinated despite its size and complexity, reflecting significant effort from contributors and release leads.
There is a need for better communication with teams indirectly involved with the release, especially Documentation.
Releasing during a major event (SOTW in this case) was exciting but can limit who is able to take part due to various logistical factors (travel funds, VISAs, time differences, etc). Also requires planning further in advance.
The release squad was highly collaborative. Leads were trusted to complete the work required of their role.
Lots of contributors and committers were around and made themselves available to answer any questions the squad members had.
Tracking and guiding all release-related activity across TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and 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/ is a huge undertaking due to the volume of activity. This can place a lot of strain on the team.
Did you have an official role on the release squad during the 6.9 release?
This section describes if the survey participants are part of release squad or observer.
Did you contribute to the 6.9 release?
This section describes if the participants actually contributed to 6.9 release or not.
How did collaborating on this project feel?
This section included ways for one to indicate how much they agreed or disagreed with a statement around collaboration.
Would you like to be part of future release squads?
17.6%: I haven’t been part of a release squad and currently have no interest in it.
11.8%: I haven’t been part of a squad but I would like to try in the future.
5.9%: I have been part of a release squad but will not repeat in the near future.
67.4%: I have been part of a release squad and I will gladly repeat
What is your feedback on the current release squad size?
Takeaways and next steps
Find ways to assemble and onboard a squad for the next release earlier.
Review the Core Handbook for missing documentation.
Figure out how to make responsibilities for release-related tasks more clear.
Investigate how parts of the release process could possibly be automated.
Find new ways to encourage wider testing during the 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./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). period.
Make it more clear which contributors are knowledgeable and available to help for specific tasks or areas of the project.
Pairing up an experienced and inexperienced contributor in each role is a good way to “level up” those who are looking to participate in a release squad for the first time.
Props to @akshayar & @desrosj for compiling responses, authoring, and @jeffpaul, @jorbin for reviewing this post.
“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 covers typography, patterns, images, and responsive design. The Font Library now works with classic and hybrid themes. Pattern Overrides expanded to custom blocks. The Image 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. got focal point controls. And there’s an experimental feature for hiding blocks based on screen size.
Classic and Hybrid Theme Support for the Font Library
The Font Library and Global Styles now work with classic themes (#73971, #73876). Like the Media Library, you can access the Font Library as a modal or through a dedicated adminadmin(and super admin) section—regardless of your theme type.
Pattern Overrides: Custom Block Support
Custom blocks can now use Pattern Overrides. (#73889)
Since WordPress 6.5, Pattern Overrides let you create synced patterns where the layout stays consistent but specific content can change per instance. The catch? Only four coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks supported it: Heading, Paragraph, Button, and Image.
Not anymore. Any block attribute that supports Block Bindings now supports Pattern Overrides by default. Block authors can opt in through the server-side block_bindings_supported_attributesfilterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.. This closes a long-requested enhancement and opens up synced patterns to custom blocks.
Image Block: Focal Point Controls
The Image block now has focal point controls. (#73115) Set a focal point on any image to control which part stays visible when the image is cropped for different screen sizes or aspect ratios. The picker is built into the Image block settings, so you can adjust it without leaving the editor.
Block Visibility Based on Screen Size (Experimental)
A new experimental feature lets you hide or show blocks based on screen size. (#73949, #74249, #74379)
Site builders have been asking for this forever—control block visibility across devices without writing CSSCSSCascading Style Sheets.. The feature includes a viewport modal for setting visibility rules, backend support for generating CSS, and visual indicators showing which blocks are hidden at different screen sizes. It’s experimental for now and requires enabling the experiment flag.
Other Notable Highlights
A few more highlights worth mentioning:
Real-Time Collaboration is no longer experimental. (#74562) The code has moved out of experimental status ahead of planned inclusion in WordPress 7.0. Note that a default provider isn’t in place yet.
Verse and Quote blocks can now transform into each other. (#73068) Finally fixes the annoyance of similar blocks not being interchangeable.
Dimension presets for width and min-height. (#73811) Theme developers can define preset dimension values in 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. that appear when users set block widths or minimum heights.
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 can exclude terms. (#73790) Much easier than the old workaround of manually adding every term except the one you don’t want.
Paragraph block supports wide and full alignment. (#73958) Useful for theme developers working with wide and full alignment CSS in block layouts.
Notes appear even when template lock is enabled. (#74577) The Notes feature (added in WordPress 6.9) now shows up regardless of template lock mode.
Changelog
Features
Collaboration
Real-time collaboration: Move collaborative editing from experiments to default 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 experience. (74562)
Add autoComplete attribute to prevent browser autocomplete. (74595)
Add list view inspector tab for pattern editing. (74574)
Block Inspector: Update the design of the style variation to use ToolsPanel. (74224)
Block variation transformation: Change position and threshold. (74251)
ContentOnlyControls: Polish headerHeaderThe header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. style. (74260)
Enhance Notice actions to allow more props like disabled and onClick with URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org. (74094)
Preview drop down: Align preview editing widths with common breakpoints. (74339)
Block 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.
Annotations: Maintain active formats after applying. (73575)
Block Bindings: Remove caption from edit on EditWithGeneratedProps. (73552)
Command Palette: Fix in the font library page and site editor experiment. (74232)
Core Merge: Deduplicate Font Library page and routes. (74381)
Customize: Preserve CSS cascade for Additional CSS in classic themes. (74593)
DataForm: Fix panel field inaccessible when empty with labelPosition none or top. (74264)
Fix document title htmlHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. entities. (74027)
Fix punctuation and formatting in README.md. (74440)
Fix the dataviews experiment locked fields position on toggle. (74326)
Fix: Menu_order validation to allow zero and negative values. (74282)
Font Library: Allow the 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. to be scrolled in boot powered pages like fonts. (73960)
Image Cropper package: Add reactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. peer dependencies. (74402)
Preferences: Add TypeScript types to package.json exports. (73276)
Theme: Fix design-tokens.js entrypoint to specify types and CJS variants. (74129)
[create-block] Updates variant handling for missing directory files. (73986)
api-fetch: Add named export to fix TypeScript callable issues. (74576)
Editor: Remove extra comma from offline error notices. (73907)
Scroll to previous location in document with editor back button. (73737)
Block Library
Block Fields: Remove normalization code and tidy up. (74532)
Block Library: Fix discussion settings data selection. (74026)
Categories Block: Fix CSS collision with labels. (73862)
Comments Title Block: Fix double quotes in non-English locales. (74330)
Remove block selection clearer handling from 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.. (73753)
Replace default block on paste if it has no content. (73951)
Rich Text: Make inline toolbar more reactive for proper positioning. (73853)
WidgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Group: Remove parent outline. (74107)
Fix: Align Document Outline padding in List View sidebar to match surrounding panels (#73576). (73595)
Global Fonts: Convert relative font URLs to absolute theme URLs in font-face styles. (74115)
Global Fonts: Correctly convert relative font URLs to absolute theme URLs in font-face styles. (74137)
Site editor global styles settings: Ensure generated global styles are correct in canvas between views. (73952)
Site editor global styles settings: Preserve non-global styles in default site editor settings. (74088)
Theme_JSON_Resolver: Defensively cover against situations where the post is null. (74124)
Components
Add checkerboard pattern for background in featured imageFeatured imageA featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. preview. (74091)
Fix DateTimePicker timezone handling for non-string values. (73887)
Fix InputControl label overflow for long translations. (74301)
Improve memoization in the overrides panel. (74407)
Fix bindableAttributes only being returned for the selected block. (74061)
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
Update: Use 12px as minimum font size for warning on fit text. (74387)
@wordpress/keycodes: Add ariaKeyShortcut and shortcutFormats exports. (74205)
Stretchy Text: Accept very small font sizes, and show a warning. (73730)
Components
Validated form controls: Suppress native popover. (73471)
Performance
Block Library
Blocks: Cache URL root when registering assets. (74451)
Add experiment for hiding blocks based on screen size. (73949)
Block Visibility: Fix block position shift when toggling. (74535)
Block visibility: Incorrect argument passed to hasBlockSupport in isBlockHidden. (74151)
Block visibility based on screen size: Add backend block support. (73994)
Block visibility support: Use CSS range syntax for media queries. (74526)
Block visibility based on screen size: Add rules to hide on viewport size. (74379)
Block visibility: Add viewport modal and controls UI. (74249)
Block visibility: Add visibility notice for hidden blocks in the block inspector. (74180)
Block visibility based on screen size: Basic clientside state. (74025)
Block Library
PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher-only blocks: Generate inspector controls from attributes. (74102)
PHP-only blocks: Use HtmlRenderer to ensure fontend & editor consistency. (74261)
Refine overlay edit button UI: Move to link variant and add tooltip. (73957)
Render custom overlay template parts in Navigation block (behind experiment). (73967)
Update navigation-overlay-close block to be used as server side rendering. (74579)
Add Navigation Overlay close block (behind experiment). (73724)
Add create new overlay button to Navigation block. (73919)
Navigation Overlay: Fix area and icon name. (74520)
Real-time collaboration: Add type guard for rich-text attributes. (73946)
Real-time collaboration: Fix persisted document 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. and add tests. (73985)
Real-time collaboration: Improve type safety with YMapWrap. (73948)
Real-time collaboration: Use alternative diff in quill-delta, provide incremental text updates. (73699)
Real-time collaboration: Allow post-locked-modal to be overridden when collaborative-editing is enabled. (72326)
Create a reverse map for faster itemBlock lookups. (73930)
Site Editor
Add extensibleExtensibleThis is the ability to add additional functionality to the code. Plugins extend the WordPress core software. site editor experiment. (74123)
Extensible Site Editor: Design improvements and page rename. (73962)
Extensible Site Editor: Fix the dashboard link. (74231)
Extensible Site Editor: Lift template activation restriction. (74197)
Build: Rename extensible site editor page to avoid conflicts. (74221)
Extensible Site Editor: The Canvas should share the same ThemeProvider as all the surfaces. (74125)
Routing: Add title support to php generated pages. (73877)
Docs: Fix callout notices layout and clarify 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/ vs handbook links. (74252)
Enhance Block Bindings Documentation as per WP 6.9 updates: Customizing supported attributes an getFieldsList. (73763)
Fix documentation title for wordpress/build package. (74541)
Fix formatting in block bindings documentation: Corrected links to core sources by adding hyphens. (74414)
Fix 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. theme.json color value in Global Styles documentation. (73999)
Fix typo in Tutorial: Build your first block. (74050)
Update the copyright licensecopyright licenseCopyright holders may grant a license with various allowances including the ability to modify or distribute the copyrighted material. Also see GPL. to 2026. (74306)
Update the useCommandLoader example to fix the syntax error and add missing imports. (73660)
Validated form controls: Add stories for validation in popovers. (71282)
Code Quality
wordpress/theme: Update color ramp generation snapshots. (74281)
Fix: Use WP_Theme_JSON_Gutenberg instead of WP_Theme_JSON class. (74294)
Theme: Enable color ramp tests and update snapshots. (74403)
TypeScript: Convert notices package to TypeScript. (67670)
TypeScript: Migrate packages/jest-puppeteer-axe package to TypeScript. (70523)
TypeScript: Migrate 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. package to TS. (74522)
Block support: 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. anchor support changes in core. (74341)
Plugin
Bump minimum required WordPress version to 6.8. (74218)
Template Activation: Try fixing still flaky test. (74216)
Test: Update URLs in tests to use example.org/com instead of test.com. (74246)
Tests: Add unit tests for Button block __experimentalLabel functionality. (74186)
Theme: Ensure build artifacts are synced in 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.. (73894)
end-to-end tests: Restore removal of settings path in preload tests. (74375)
wordpress/theme: Disable color ramp unit tests. (74347)
Template Activation: Make template edit test less flaky again. (74066)
Template Activation: Make template edit test less flaky. (73975)
Data Layer
Cleanup the dependencies in the root package.json. (74212)
Update package version after an unfinished publish. (74413)
npm Packages
Packages: Add support for publishing stable release of pre-release package. (74332)
Packages: Avoid bumping the major version on prerelease packages. (74285)
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. 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 Make 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. A special thank you to the Docs team for already identifying that @sajib1223 and @milana_cap will be leading efforts from their perspective!
The number of volunteers far exceeded the available squad roles, so we selected folks whose experience and focus best aligned with the needs of the 7.0 release. If you weren’t selected this time, your contributions are still incredibly valuable, and there are plenty of ways to stay involved throughout the release cycle, including testing, 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, triage, documentation, and more. Every contribution helps move WordPress forward, and we’re grateful for your continued participation.
Big thanks to everyone who volunteered for the release squad, and heartfelt appreciation to everyone helping move WordPress 7.0 forward through testing, triage, documentation, bug scrubs, and more. Your efforts make this release possible, and there’s a lot to be excited about as WordPress 7.0 comes together!
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 📢
Nominations for CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps 2026
The nomination process for Core Team Representatives for 2026 is now open. Please submit your nomination here.
Dropping support for PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 7.2 and 7.3
The WordPress 6.9.1 maintenance release is planned on February 3, 2026. See the release schedule announcement for more information.
Discussions 💬
The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core 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.
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.
Since WordPress 6.9 was released, contributors have kept a close eye on incoming reports to the WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Support Forums, TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and the GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repository on GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. The volume and severityseverityThe seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. of tickets mean that the maintenance release should be prepared sagaciously.
Specific times for 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). and General release will be announced in the 6.9 Release Leads room and will be based on availability of individuals helping with the release.
Targeted Fixes
WordPress 6.9.1 is intended as 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.-fix only maintenance release. Tickets will be included provided they are issues introduced during the 6.9 cycle or intentionally deferred at the end of the 6.9 cycle. You can follow trac report 4 or the 6.9.x editor tasks board for proposed fixes.
Bug Scrubs will happen in the #core room during the times posted above. Each of the open tickets is going to require development work along with testing and review. You can also run your own scrubs to help ensure that all of the correct tickets are fixed in this release. Additionally, some locales have strings in 6.9 in need of translation.
General coordination for the release will happen in the #6-9-release-leads channel and decisions around code for the release will be made in the #core room.
You must be logged in to post a comment.