Jadwal Rilis WordPress 6.9.1

Since WordPress 6.9 was released, contributors have kept a close eye on incoming reports to the WordPress.org The 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, Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and the Gutenberg The 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 GitHub GitHub 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/. The volume and severity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. of tickets mean that the maintenance release should be prepared sagaciously.

This release will be co-led by @jorbin and @wildworks.

Schedule

Specific times for RC One 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). and General release will be announced in the 6.9 Release Leads room and will be based on availability of individuals helping with the release.

Targeted Fixes

WordPress 6.9.1 is intended as a 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.-fix only maintenance release. Tickets will be included provided they are issues introduced during the 6.9 cycle or intentionally deferred at the end of the 6.9 cycle. You can follow trac report 4 or the 6.9.x editor tasks board for proposed fixes.

Some issues already have hotfixes available in plugin form if you are facing them on your site.

Get Involved with 6.9.1

Bug Scrubs will happen in the #core room during the times posted above. Each of the open tickets is going to require development work along with testing and review. You can also run your own scrubs to help ensure that all of the correct tickets are fixed in this release. Additionally, some locales have strings in 6.9 in need of translation.

General coordination for the release will happen in the #6-9-release-leads channel and decisions around code for the release will be made in the #core room.

Props to @wildworks, @dmsnell, @westonruter for assistance with this post.

#6-9, #6-9-1, #6-9-x, #minor-releases