WordPress 6.2.1 Planning

Coming after WordPress 6.2 “Dolphy”, a 6.2.1 release is planned for some items that came up near the end of the 6.2 release cycle or have been raised post-release.

If there is a critical bugfix that has a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing./PR ready, then please look to add those to the 6.2.1 milestone on Trac or the WordPress 6.2.1 Editor Tasks project board on GitHub.

Schedule

The following schedule is what’s currently planned for the release, any additional bugbug 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. scrubs, release candidates, or other items will be added here as they get scheduled.

Release Coordination

This release is led by @audrasjb and @mamaduka, with the help of @sergeybiryukov on mission control.

The #6-2-release-leads channel will continue to be used for all coordination and conversation related to the 6.2.x releases. This matches the pattern of communication that worked well for previous minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. cycles.

Thanks @mamaduka, @sergeybiryukov, @annezazu, @costdev and @jpantani for proofreading.

#6-2, #6-2-1, #minor-releases