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.
Alpha Begins.TrunktrunkA directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. is open for business.
13 February 2024
Beta 1. From this point on, core contributorsCore ContributorsCore contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. will focus on testing and fixing bugs discovered during betaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. testing. Begin writing Dev Notesdev noteEach important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and the About page (Slack archive, ZIP download).
Beta 3. Test the beta release, fix bugs discovered during beta testing, and continue writing Dev Notes and the About page (SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. archive, ZIP download).
5 March 2024
Release candidaterelease candidateOne 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). 1. Publish the Field Guide with Dev Notes, commit the About page, begin drafting the release post, hard string freeze, and branchbranchA 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". for the release. (Slack archive, ZIP download).
12 March 2024
Release candidate 2. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
19 March 2024
Release candidate3. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
25 March 2024
Dry run for release of WordPress 6.5 and 24-hour code freeze (Slack archive).
26 March 2024
WordPress 6.5 is released (Slack archive, ZIP download)!
Take a more granular look at key roles for each release party, and volunteer for a role, on this post. Note that these roles require specific access.
How to contribute
To get involved in WordPress core development, head over to TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and pick a 6.5 ticket. Need help? Check out the Core Contributor Handbook.
Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticketCreated for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above so that we can all focus on squashing bugs and delivering the most 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.-free WordPress ever 😉.
If you want to dive deeper into 6.5, join the weekly meetings in the #core Slack channel, which occur every Wednesday at 20:00 UTC.