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.
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 below. 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.
Announcements 📢
WordPress 6.8 | 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 now available 🥳
The Beta 1 release of WordPress 6.8 is now available! A heartfelt thank you to everyone who joined the Release Party. We appreciate your testing and feedback.
At this point, we would like to express our sincere thanks to @krupajnanda for this wonderful article.
Forthcoming releases 🚀
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/ version: 20.4
Gutenberg 20.4 is scheduled for release on Wednesday, March 5th. This will be the final release to be merged into WordPress 6.8.
Next Beta 2 of 6.8: March 11th
The Beta 2 release of WordPress 6.8 will be available on Tuesday, March 11th.
A detailed overview of the release schedule for WordPress 6.8 can be found here. The article also includes information about the individuals assigned to each release party.
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.8
The discussion section of the agenda is to provide a place to discuss 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.
6.8 – Beta 1 | Current update issue with versions older than 5.1 ⚠️
Due to 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., older versions cannot be updated to Beta 1. The core team is actively working on a fix for this issue. We will provide more information as soon as it becomes available. In the meantime, you can refer to the detailed article for further reading and updates on the matter.
As mentioned above, an issue occurs with WordPress versions older than 5.1. In this round, we should discuss the current status of the situation. See more here: #63052
6.8 | Dev-Note Spreadsheet
@marybaum shared a Google spreadsheet for Dev-Notes, sourced from the needs-dev-noteTracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket. Anyone can edit, add their name as a Dev-Note author, and fill in relevant details as they draft, review, and publish. @jeffpaul also encouraged adding tickets 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/ issues as needed, noting the sheet may not be complete. See here.
6.8 | Preparing Documentation for the 6.8 Release
@estelaris has already started preparing the documentation for 6.8. The remaining gaps need to be filled in. It’s important to keep this in mind, and all Core Team members are asked to contribute so we are ready for the April release. A Google Doc has been created by @estelaris for this purpose. See here.
Last Call for “What’s New for Developers” Submissions
@marybaum reminded everyone to submit items for the March “What’s New for Developers” edition. The deadline is March 5. The article will be published during the week of March 10.
If you’d like to contribute to the Dev blogblog(versus network, site) or know someone who might, check out the Slack channel and join the editorial meeting this Thursday, March 6, at 15:00 UTC.
Call for the Security Role for the upcoming 6.8 release parties
@jeffpaul ask for assistance from the Core Team for the Security Role during the upcoming Release Parties. A detailed list of the dates can be found here: WordPress 6.8 Release Party Schedule. Should you be interested, please contact @jeffpaul.
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.
