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.
With one month to the first WordPress 6.0 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., let’s review the WordPress 6.0 cycle status.
Live-streamed walkthrough and feature freeze
As an iteration over WordPress 5.8 and 5.9’s Go/No Go demo, WordPress 6.0 will offer a hosted walkthrough on April 5th. In this event, placed closer to Beta than past demos, WordPress leads will review the features ready for the next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. together with the community in a live, moderated stream.
As a result of this demo and to address contributor feedback received in the last two major release cycles, the effective feature freeze will happen with Beta 1 on April 12th.
This adjustment will give 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. two extra weeks over the original schedule. Together with the live demo, they will offer enough buffer time to identify and address any last-minute blockerblockerA bug which is so severe that it blocks a release. issues found during the walkthrough, reducing the amount of backports post- Beta 1.
5 April 2022
Live-streamed walkthrough
12 April 2022
Beta 1, effective Feature Freeze
19 April 2022
Beta 2
26 April 2022
Beta 3
3 May 2022
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
10 May 2022
Release candidate 2
17 May 2022
Release candidate 3
23 May 2022
Dry run
24 May 2022
WordPress 6.0 stable release
Release team
With the exception of the AccessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Lead, the release team is nearly complete. Thanks to all participating volunteers!
Release LeadRelease LeadThe community member ultimately responsible for the Release.:Matt Mullenweg
TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead:Ahmed Chaion and Colin Stewart.
All release decisions will ultimately be this release teams’ to make and communicate while gathering input from the community. Coordination between the whole squad primarily occurs in the public #6-0-release-leadsSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, and contributors are welcome to join the release team in this process.
How To Help
If you are still interested in being a part of 6.0’s release squad or shadowing a lead to participate in future releases, please show your interest in the comments below or the #6-0-release-leads Slack channel. If you want to dive deeper into 6.0, join the weekly meetings in the #core Slack channel, which occur every Wednesday at 20:00 UTC.