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.
Since WordPress 6.7 was released last week, contributors have kept a close eye on incoming reports to the 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/ Support Forums, TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and the 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/ repository on 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/. Though volume has not been meaningfully higher than normal after a 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., most reports are describing a small set of issues that should be addressed expeditiously.
Schedule
WordPress 6.7.1 will be targeted for release on Thursday, November 21, 2024 with a very specific focus of only fixing bugs there were introduced in the 6.7 release. The goal is to deliver a small handful of high-impact 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. fixes for added stability prior to the busy online commerce holiday week consisting of Black Friday, Cyber Monday, and Giving Tuesday.
Continued triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., testing, and committing/backporting fixes.
Wednesday, November 20, 2024 at 13:00PM UTC
Gutenberg package updates released/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 update released (if necessary).
Wednesday, November 20, 2024 at 17:00PM UTC
WordPress 6.7.1 RC1
Thursday, November 21, 2024 at 13:30PM UTC
WordPress 6.7.1 General Release
Targeted Fixes
The following are the high priority items that cumulatively make a fast-follow release necessary:
sizes=auto causing images to show smaller than they should (#62413)
Patterns without categories break the editor when browsing uncategorized patterns (GB-66944/GB-66888)
Zoom in doesn’t focus on the right area of the screen based on selected item (a few PRs issues for this)
Zoom out button goes missing when plugins register toolbar items (GB-66884)
The following are bugs that should be included if ready, but as understood now are not affecting as many people or are less problematic:
Using the Upload button in image-based blocks in Safari unexpectedly converts images to HEIC with a temporary file name (#62447)
CategoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. management in the Classic Editor is broken (#62440)
CSSCSSCascading Style Sheets. targets changed on the login screen affecting custom logos (#62410)
Finally, the following are minor bug fixes introduced in 6.7 that should also be considered:
Horizontal scroll bar in the CustomizerCustomizerTool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. (#62313)
There is currently only one ticketticketCreated for both bug reports and feature development on the bug tracker. that does not represent a bug introduced during 6.7 being considered: #62331. This is a pretty significant performance problem for sites using GD for image editing that should be considered. It was only discovered 2 weeks ago, too late to be considered for 6.7.