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.
WordPress 6.8 | 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). 3 is now available 🥳
The Release Candidate 3 is now available! A heartfelt thank you to everyone who joined the Release Party. We appreciate your testing and feedback.
@jeffpaul reminds all CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers to read this article and follow the outlined process for the upcoming steps: WordPress 6.8 Release Candidate Phase
Help Test 6.8 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). version 🧪
The Test-Team has written two helpful guides for people interested in testing:
The general release of WordPress 6.8 will be available on Tuesday, April 15, 2025.
Ahead of it, there will be a Dry Run on Monday, April 14, 2025.
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.
The discussion concerns the release of version 6.8 as the last 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. for 2025. It was pointed out that the decision was not clearly communicated, and it was recommended to make a clear public announcement. Additionally, a formal proposal should be created in the future to better communicate such decisions and increase transparency.
Core TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. Workflow Keywords Issue
The discussion concerns an issue raised by @sirlouen on 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. about a 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. between the "needs-testing" and "needs-testing-info" keywords in search results on 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/ Meta Trac (TicketticketCreated for both bug reports and feature development on the bug tracker.7935). This problem makes reports, especially for the testing team, more difficult and leads to incorrect information. Two solutions were suggested: renaming one of the keywords or improving the search algorithm. The conversation continues in the Trac comments.
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 | 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). 3 is now available 🥳
@jeffpaul reminds all CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers to read this article and follow the outlined process for the upcoming steps: WordPress 6.8 Release Candidate Phase
Help Test 6.8 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). version 🧪
The Test-Team has written two helpful guides for people interested in testing:
The general release of WordPress 6.8 will be available on Tuesday, April 15, 2025.
Ahead of it, there will be a Dry Run on Monday, April 14, 2025.
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.
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 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.
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.
WordPress 6.8 | 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). 2 is now available 🥳
@jeffpaul reminds all CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers to read this article and follow the outlined process for the upcoming steps: WordPress 6.8 Release Candidate Phase
Help Test 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. version 🧪
The Test-Team has written two helpful guides for people interested in testing:
The Release Candidate 3 release of WordPress 6.8 will be available on Tuesday, April 8, 2025.
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 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.6
Gutenberg 20.6 is scheduled for release on Wednesday, April 2, 2025.
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
There were no significant topics that we would list in the summary.
Open Floor 💬
PHPDocs Improvements
@sirlouen is requesting a status update on TicketticketCreated for both bug reports and feature development on the bug tracker.#57299 on Core TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., which concerns the improvement of PHPDocs for arrays. The goal is to enhance code quality and developer-friendliness in WordPress.
Style Book Integration
@smrubenstein is asking for advice on handling tab color states. Currently, custom color attributes and slotfill are used for the color inspector, but there’s no clear way to define 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. states like hover or focus. He’s asking how to integrate these into the Style Book and Style Engine so users can set default values.
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 | 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). 2 is now available 🥳
@jeffpaul reminds all CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers to read this article and follow the outlined process for the upcoming steps: WordPress 6.8 Release Candidate Phase
Help Test 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. version 🧪
The Test-Team has written two helpful guides for people interested in testing:
The Release Candidate 3 release of WordPress 6.8 will be available on Tuesday, April 8, 2025.
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 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.6
Gutenberg 20.6 is scheduled for release on Wednesday, April 2, 2025.
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 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.
At the moment, there are no topics for 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.
WordPress 6.8 | 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 is now available 🥳
@jeffpaul reminds all CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers to read this article and follow the outlined process for the upcoming steps: WordPress 6.8 Release Candidate Phase
We are in the process of finalizing the development notes, after which the Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. will be released, followed by an email to 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 Authors containing the necessary information.
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/ 20.5 is now available
The new version of the Gutenberg plugin is now available in our plugin directory.
Help Test 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. version 🧪
The Test-Team has written two helpful guides for people interested in testing:
The Release Candidate 2 release of WordPress 6.8 will be available on Tuesday, April 1, 2025.
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 Gutenberg version: 20.6
Gutenberg 20.6 is scheduled for release on Wednesday, April 2, 2025.
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
@joemcgill created a follow-up ticketticketCreated for both bug reports and feature development on the bug tracker. (#63175) to update the tests and might need additional support.
@johnbillion explained that the fail() method is being called because the test environment doesn’t support Argon2. There have been discussions about whether this should cause the test to fail or be skipped. Skipping would be risky, as it’s harder to spot if, for example, the PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version in 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 suddenly stops supporting something the test depends on. @desrosj is currently investigating why the failures are happening in their setup.
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).-Testing and Bug TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.
@joemcgill reminded everyone to monitor the new tickets and forum feedback as RC testing begins. He emphasized flagging any bugs related to the 6.8 release, noting that a few tickets from yesterday still need triaging.
Open Floor 💬
There were no significant topics that we would list in the summary.
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 | 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 is now available 🥳
@jeffpaul reminds all CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers to read this article and follow the outlined process for the upcoming steps: WordPress 6.8 Release Candidate Phase
We are in the process of finalizing the development notes, after which the Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. will be released, followed by an email to 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 Authors containing the necessary information.
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/ 20.5 is now available
The new version of the Gutenberg plugin is now available in our plugin directory.
Help Test 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. version 🧪
The Test-Team has written two helpful guides for people interested in testing:
The Release Candidate 2 release of WordPress 6.8 will be available on Tuesday, April 1, 2025.
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 Gutenberg version: 20.6
Gutenberg 20.6 is scheduled for release on Wednesday, April 2, 2025.
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
You can keep up to date with the major Editor features with the weekly updates, now on the blogblog(versus network, site)! Editor Weekly Updates: March 10th – 23rd
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 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.
Hosting Issues Found During 6.8 RC1 Release Party
During the Release Party of 6.8 RC1, @desrosj observed errors occurring on several hosts. The most common issues involved three specific tests:
These tests resulted in failures on multiple hosts. We should discuss this issue further to identify the causes and potential solutions.
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.
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. 3 is now available 🥳
The Beta 3 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.
Help Test 6.8 Beta version 🧪
The Test-Team has written two helpful guides for people interested in testing:
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.5
Gutenberg 20.5 is scheduled for release on Wednesday, March 19th. This will be the first version of Gutenberg to be merged into WordPress 6.9.
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 of 6.8: March 25th
The Release Candidate 1 release of WordPress 6.8 will be available on Tuesday, March 25th.
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
To avoid listing the topics here twice, all the necessary links and information can be found in the agenda. This section now includes a few additions.
Release Support Needed
@jeffpaul provided an update: only a few dev notesdev noteEach important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. remain to be drafted and will be published this week. A Miscellaneous Dev Notedev noteEach important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. will be updated and released by 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). 1. The Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. draft will be shared later this week as more dev notes are completed. 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 Author email will likely go out next week due to current priorities.
Critical Issues Before RC 1
@joemcgill stated it’s the last week of beta and critical issues need prioritizing. @audrasjb mentioned 17 tickets are left before RC1, with no major issues, though #63122 is annoying. @joemcgill is tracking new tickets and ensuring regressions in 6.8 are added to the milestone. He also requested non-release prep tasks be resolved this week for a clean RC.
Open Floor 💬
There were no significant topics that we would list in the summary.
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. 3 is now available 🥳
The Beta 3 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.
Help Test 6.8 Beta version 🧪
The Test-Team has written two helpful guides for people interested in testing:
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.5
Gutenberg 20.5 is scheduled for release on Wednesday, March 19th. This will be the first version of Gutenberg to be merged into WordPress 6.9.
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 of 6.8: March 25th
The Release Candidate 1 release of WordPress 6.8 will be available on Tuesday, March 25th.
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.
Release Support Needed
Assistance with drafting, reviewing, and publishing developer notes Assistance is requested for the drafting, review, and final publication of the developer notes.
Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. draft coming Thursday, please be ready for review The Field Guide draft will be available on Thursday. Please be prepared to review it promptly.
Review of the “About” page and potential issues The “About” page should be reviewed to identify any potential issues in the text or content. See more here: #63025
Reminder of the string freeze next week before 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). 1 Please remember that the string freeze will take place next week before the release of RC 1.
Assistance with reviewing the email to 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 Authors about major changes Assistance is needed to review the email to be sent to Plugin Authors, informing them of the key changes.
Critical Issues Before RC 1
Discussion of critical issues before RC 1 It’s suggested to discuss any critical or new issues before the release of RC 1 to ensure all problems are addressed in time.
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.
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. 2 is now available 🥳
The Beta 2 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.
Help Test 6.8 Beta version 🧪
The Test-Team has written two helpful guides for people interested in testing:
Thanks @ankit-k-gupt and @krupajnanda for your contribution!
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.5
Gutenberg 20.5 is scheduled for release on Wednesday, March 19th. This will be the first version of Gutenberg to be merged into WordPress 6.9.
Next Beta 3 of 6.8: March 18th
The Beta 3 release of WordPress 6.8 will be available on Tuesday, March 18th.
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
We have only two weeks until 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). 1. Dev notes should be in progress. Please check @jeffpaul‘s message on Slack for details.
Editor Updates 🔄
Stay tuned for weekly updates to keep you informed about the latest in WordPress editor development. Whether you’re a developer, designer, or content creator, these updates will keep you in the 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. on all the key changes.
Don’t miss out — check out the weekly update and get ready for more!
Discussion 🤔
Finalizing the About Page for WordPress 6.8
Jeff Paul requested help reviewing and finalizing the About page text.
Deadline: March 25 (RC1), but earlier completion is preferred.
“Source of Truth” Document
@poena asked for updates on the “Source of Truth” document, which provides extenders with details about the WordPress 6.8 release. Currently, no one is actively working on it due to limited capacity. @joemcgill suggested prioritizing the Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. instead, as it serves a similar purpose and is officially published. Stevenlinx may have a draft of the Field Guide, and a request was made to share it for collaboration. If no one takes on the “Source of Truth” document, it will likely not be created for this release.
Unused Code in WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.
@zodiac1978 reported unused constants in WordPress Core and created TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker.#63017 to address the issue. He asked whether their deprecation had been officially documented. @joemcgill suggested verifying if their removal was intentional or if they are still needed. @desrosj pointed out that some plugins might still rely on these constants, making their removal risky. @joedolson agreed, emphasizing that plugins could use them in ways not immediately visible in Core. @zodiac1978 plans to investigate further 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 directory and update the ticket with his findings.
Open Floor 💬
There were no further topics to discuss today.
Thanks to @francinafor helping review this summary.
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. 2 is now available 🥳
The Beta 2 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.
Help Test 6.8 Beta version 🧪
The Test-Team has written two helpful guides for people interested in testing:
Thanks @ankit-k-gupt and @krupajnanda for your contribution!
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.5
Gutenberg 20.5 is scheduled for release on Wednesday, March 19th. This will be the first version of Gutenberg to be merged into WordPress 6.9.
Next Beta 3 of 6.8: March 18th
The Beta 3 release of WordPress 6.8 will be available on Tuesday, March 18th.
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
We have only two weeks until 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). 1. Dev notes should be in progress. Please check @jeffpaul‘s message on Slack for details.
Discussions 🤔
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.
Editor Updates 🔄
You can keep up to date with the major Editor features with the weekly updates, now on the blogblog(versus network, site)! Editor Weekly Updates: Mar 3 – Mar 7
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.