This has been a particularly busy month, with a number of interesting and ambitious proposals for the WordPress project along with active progress across the entire community. <\/p>\n\n\n\n
The upcoming minor release of WordPress, v5.2.3, is currently in the release candidate phase<\/a> and available for testing.<\/p>\n\n\n\n Following that, the next major release is v5.3 and the Core team has laid out a schedule and scope<\/a> for development. In addition, a bug scrub schedule<\/a> and an accessibility-focused schedule<\/a> have been set out to provide dedicated times for contributors to work on ironing out the bugs in the release.<\/p>\n\n\n\n Want to get involved in building WordPress Core? Follow the Core team blog<\/a>, and join the #core channel in the Making WordPress Slack group<\/a>.<\/p>\n\n\n\n The Core Privacy Team has proposed a feature plugin<\/a> to build a consent and logging mechanism for user privacy. This project will focus on improving the user privacy controls in WordPress Core in order to protect site owners and users alike.<\/p>\n\n\n\n The proposal includes some useful information about building effective controls for users, how other projects have worked on similar efforts, and what kind of time and resources the project will need in order to be developed.<\/p>\n\n\n\n Want to get involved in this feature project? Follow the Core team blog<\/a>, and join the #core-privacy channel in the Making WordPress Slack group<\/a> where there are open office hours every Wednesday at 19:00 UTC.<\/p>\n\n\n\n A proposal has been made<\/a> for a new feature project to build a robust notification system for WordPress Core. The aim of the project is to build a system to handle notifications for site owners that can be extended by plugin and theme developers.<\/p>\n\n\n\n This proposal comes on the back of a Trac ticket<\/a> opened 18 months ago. With weekly meetings to discuss the project, the team behind WP Notify are in the planning phase<\/a> while they establish exactly how to develop the feature. Want to get involved in this feature project? Follow the Core team blog<\/a>, and join the #core channel in the Making WordPress Slack group<\/a> – meetings for this project happen every Monday at 14:00 and 22:00 UTC.<\/p>\n\n\n\n Members of the Core Team have put together a local development environment for WordPress<\/a> that runs on Docker. This environment provides an easy way for developers to get involved with WordPress core development.\u00a0<\/p>\n\n\n\n The work on this was inspired by the environment used for local Gutenberg development, which has since been improved<\/a> based on the new work that has been done here.<\/p>\n\n\n\n The announcement post<\/a> explains how to use the Docker environment. If you have any feedback or bug reports, please comment on the post directly.<\/p>\n\n\n\n On July 30, the Security Team shared that security updates need to undergo the same testing and release process for every major version of WordPress. This means they have to provide long-term support for over fifteen major versions of WordPress. This requires a lot of time and effort, and the team has sought feedback on potential solutions for this challenge<\/a>.\u00a0<\/p>\n\n\n\n Following this discussion, a proposal was made to auto-update old versions of WordPress to v4.7<\/a>. This proposal garnered many responses and has since been updated to incorporate feedback from comments. The current recommendation is to secure the six latest versions and to eventually auto-update all older versions of WordPress to 4.7. Since this proposal was made, it has been discussed at Hosting Team meetings<\/a> and Dev Chat meetings<\/a>, and the conversation is still ongoing.<\/p>\n\n\n\n Want to provide feedback on this proposal? Comment on the original post<\/a> with your thoughts.<\/p>\n\n\n\nProposal for User Privacy Improvements<\/h2>\n\n\n\n
Core Notification System Proposal<\/h2>\n\n\n\n
<\/p>\n\n\n\nLocal WordPress Development Environment<\/h2>\n\n\n\n
Updates for Older Versions of WordPress<\/h2>\n\n\n\n
\n\n\n\nFurther Reading:<\/h2>\n\n\n\n