Announcements 📢
WordPress 6.9 Roadmap
The roadmap for 6.9 has been published. Please take a look to see
what’s actively being worked on for release later in the year.
WordPress 6.9 Planning Proposal and Call for Volunteers
The planning phase for 6.9 wrapped up on July 25.
More information will be announced about the release team in the coming weeks.
Forthcoming releases 🚀
WordPress 6.9
WordPress 6.9 is scheduled for Tuesday, December 2, 2025.
Discussion 💬
Contributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They’re one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US
@jorbin shared plans for the Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. table, including a live bug A 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. scrub, a live demo from a committer A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers – a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. showing the final review process, and activities aimed at helping contributors become more active. @karmatosed suggested using the day to also update the handbook with any improvements discovered.
Mail Component – New Maintainer Proposal + Discussion about the role and expectations
@SirLouen put forward his interest in becoming the maintainer for the Mail component, highlighting several months of consistent triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., reviews, and fixes. With many components currently without maintainers, the proposal received strong support. @desrosj suggested assigning the role now, reviewing progress after three months, and refining the maintainer role description in the handbook. He noted that the recent, more relaxed approach to assigning maintainer roles has had mixed results. He is preparing an updated, clearer role description for the handbook, based on established open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. practices.
Updating seems_utf8()
@dmsnell proposed updating seems_utf8() to comply with RFC 3629 (#38044). This function is used for validating titles, filenames, and exports. The group discussed deprecating the current implementation and replacing it with proper validation. @agulbra and @jorbin offered to review the changes further.
Props to @francina for review.
Leave a Reply