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 our bug tracker.
We use Slack for real-time communication. Contributors live all over the world, so there are discussions happening at all hours of the day.
Our core development meetings are every Wednesday at 20:00 UTC in the #core channel on Slack. Anyone can join and participate or listen in!
WordPress 6.0 Development Cycle
Dev Chat Agendas | Dev Chat Summaries | Bug Scrubs Schedule | Dev Notes | Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. | All Posts Tagged 6.0 |
WordPress 6.0 will be the second major release of 2022 and is in the early planning stages. Check back in as more information is made available.
Release team
All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community.
A call to join the team will be announced at a later time.
Feature freeze/Bug Fixes period. During the following two weeks, there will be no commits for new enhancements or feature requests. 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 defect work (aka outstanding bugs).
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. 1. From this point on, core contributors will focus on testing and fixing bugs discovered during beta 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
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 (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).
Beta 2. Test the beta release, fix bugs discovered during beta testing, continue writing Dev Notes and the About page (Slack archive, ZIP download).
Beta 3. Test the beta release, fix bugs discovered during beta testing, continue writing Dev Notes and the About page, soft string freeze (Slack archive, ZIP download).
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).
Release candidate 2. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
Release candidate3. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
Dry run for release of WordPress 6.0 and 24-hour code freeze (Slack archive).
WordPress 6.0 is released (Slack archive, ZIP download)!
How to contribute
To get involved in WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. 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.0 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 deliver 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.0, join the weekly meetings in the #core Slack channel, which occur next at Wednesday at 20:00 UTC.
