WordPress 6.5.3: An upcoming maintenance release

WordPress 6.5.3 is scheduled to be the next maintenance release for the 6.5 version. Its release will follow the following preliminary schedule:

  • 2 May 2024 – Release Candidaterelease candidate 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). made available and announced here on the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. site.
  • 7 May 2024 – Final release made available.

Specific times will be decided in advance and adjustments to the schedule may be made. All adjustments will be noted in this post.

Minor or Maintenance releases of WordPress are intended as 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.-fix releases. If you have a tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. that you think should be considered, please put it in the 6.5.3 milestone. If you have a githubGitHub 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/ issue, please add it to the 6.5.x Editor Tasks board. If you lack bug gardening capabilities and have a ticket or issue you wish to highlight for 6.5.3, please add a comment here.

Note: except in extreme situations, only bug fixes will be considered and generally only bugs that have been introduced during the 6.5 cycle.

Get involved with 6.5.3

Bug Scrubs will happen in the #core room during the following times:

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, while the intent is for no new translated strings in this release, some locales have strings in 6.5 in need of translation.

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

This 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. will be led by @grantmkin and myself (@jorbin).

Thank you to @grantmkin for pre-publication review.

#6-5, #6-5-x

What Happened to WordPress 6.5.1?

Observant folks will notice that the first 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. for WordPress 6.5 is 6.5.2 instead of 6.5.1. This is due to an error with the initial package. When the tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) for 6.5.1 was created on the WordPress build server, it was created from a previous revision of the 6.5 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".. As tags are treated as immutable, this meant that WordPress 6.5.1 could not be released.

As a follow-up, the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team will work with the WordPress.orgWordPress.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/ Systems team and update respective documentation as needed to ensure that everything is done to prevent similar situations.

Thanks to @audrasjb, @davidbaumwald, and @jeffpaul for pre-publication review.

#6-5, #6-5-x

Initial Bug Scrub for 6.5.1

There is no specific target date for WordPress 6.5.1 yet. However, we can start ensuring that all the correct bugs are targeted for it and that work progresses towards fixing them.

To assist with preparation for 6.5.1, an initial scrub will be held at Thursday, April 4, 2024 at 18:00 UTC in the #core slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.

Thanks to @desrosj and @hellofromtonya for pre-publication review.

#6-5, #6-5-x, #bug-scrub