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.
Using the weekly curated agenda post for live and asynchronous usage, this meeting will begin an experiment to dedicate time to current proposals in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. and to help specifically with progressing releases.
Through the summaries of the discussions and SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. links, those unable to join live, will continue to be able to read and contribute asynchronously.
The links in the various agenda sections below will not be shared in full in the meeting, but be available for pre and post-reading. Anything for particular discussion can still be highlighted.
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 post.
These are some of the current proposals in core for awareness and which may be suitable for further discussion in Dev Chats.
This focuses on considering how the team approaches the maintenance of the default themes to make them easier to maintain, and more future-compatible. With the release of Twenty Twenty-Four, there are now 14 default themes maintained by the project.
This proposal is focused on a workflow for merging 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/ into Core
This could be an ideal time to discuss to discuss and experiment based on 6.4 learnings for the benefit of 6.5.
As Dev Chat now has a combined input from the Gutenberg and Core meetings, there is opportunity for discussing this further during the meetings and for a deeper discussion on what could be done in 6.5.
Could you help curate a Call for Volunteers to review the open proposals on Make/Core and create a list of unresolved ones to discuss during Dev Chat meetings?
6.4.3 – next maintenance release – the post includes the planned schedule, the dates of the 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, and the final release date of 30 January 2024.
Highlighted posts for information
These will not be re-shared in full in the meeting itself to enable time for discussions in a new experimental approach to Dev Chat.
In 2023, the WordPress Core team shipped 2211 commits (2597 in 2022). 2751 tickets were opened, 2545 tickets were closed, and 365 were reopened.
Also, 1079 people contributed to WordPress source code using TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. (988 in 2022), and 472 people made their very first contribution to WordPress Core (398 in 2022).
The Feature Projects page has had an update and worth checking out for the latest statuses. Feature Projects are intended to concentrate a group of people together, to explore potential ideas for WordPress Core.
Font Library: biggest work for now is the Font Library: refactor REST API which needs feedback. Please help review if you have experience with the 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/..
Pattern overrides: work is ready to test starting with making paragraph blocks overrideable. Up next, headings, buttons and images are expected to be added soon as blocks that can have overrides.
Design tools: PR merged to add backgroundSize feature with implicit repeating backgrounds to add more functionality to the Group 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.’s background image support that was added in 6.4. Needs PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher backports.
Data Views: Templates is now stabilized with Pages, Patterns, and additional views in Templates added in as experimental. Questions around extensibility came up recently — extensibility is very much part of the plan with the focus currently being on stabilizing the base APIs.
Block bindings API: block bindings prototype is being split into smaller PRs to move work forward in smaller chunks with the PR that sets the basis for the API recently merged (this doesn’t add a UIUIUser interface to create the bindings).
January 23, 2024 at 12:00 UTC: Next Extensibility Issues TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. meeting (Project board) in #core-editor channel.
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.5
Please also view the updates relating to 6.5 related updates under the core-editor heading above.
A release squad announcement is expected shortly. Next milestone: BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is Feb 13, 2024.
Could you help with running a bug scrub around a particular area, component, or towards 6.5? More information on running scrubs. More dates for 6.5 bug scrubs will also be added once a squad is in place.
Next minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.4.3
As shared above in Highlighted Posts, the next maintenance release will be 6.4.3.
Milestone: RC1 January 25, 2024
Release slated for: January 30, 2024
Bug scrubs and more information is in the link above.