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.
Planning is underway for WordPress 7.0! This post outlines the proposed schedule along with a call for volunteers to support the release process.
Following the typical cadence and accounting for holidays later in the year, the proposed final release date for 7.0 is Thursday, April 9, 2026. This proposed timeline remains flexible for the resulting Release Squad and adjustments can be made if necessary as they determine what timeline works best for their schedule.
Proposed Schedule
Milestone
Date
Alpha Begins
Immediately (7.0-alpha began in trunk on November 12th with [61222])
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
Thursday, February 19
Beta 2
Thursday, February 26
Beta 3
Thursday, March 5
Beta 4
Thursday, March 12
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
Thursday, March 19
Release Candidate 2
Thursday, March 26
Release Candidate 3
Thursday, April 2
Dry Run
Wednesday, April 8
Final Release
Thursday, April 9
As always, all dates are subject to change based on development progress.
Call for Volunteers
Each WordPress release depends on contributors from across the project coming together to make it a success.
As with the 6.7, 6.8, and 6.9 release cycles, WordPress 7.0 will continue the approach of forming a smaller, focused Release Squad with making based on feedback received. This streamlined structure places more emphasis on collaboration with the various Make Team Reps, who are encouraged to help coordinate efforts from within their respective teams. The goals are to reduce the overhead on the Release Squad while still ensuring each team’s contributions and priorities are represented throughout the cycle, and to reduce overlap between a Make Team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. and that team’s Release Squad Leads. Noteworthy Contributors will be captured from Team Reps towards the end of the release cycle.
While the end goal is to publish the final release of WordPress 7.0 during Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia (which follows India Standard Time), traveling to or attending WordCamp Asia is not a requirement to serve on the release squad. All communication related to the release process will continue to take place in the #coreSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.
If you are interested in helping lead WordPress 7.0 in one of the following roles, please comment below or reach out in the #7-0-release-leads Slack channel:
Release LeadRelease LeadThe community member ultimately responsible for the Release. – Matt Mullenweg (@matt)
Release Coordination – helps manage timelines, cross-team collaboration, and status updates
Tech Leads – oversees coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development (including GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/), triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., and critical issues
Triage Lead – help monitor issues, shepherd patches, and guide contributors
Test Lead – coordinates testing efforts across the community and test reports
Whether you have led a release before or are looking to get involved for the first time, there are many ways to contribute. Volunteers of all backgrounds and experience levels are welcome!
If you are interested in volunteering, please leave a comment below noting your preferred area(s) by Friday, January 16th.@4thhubbard (or a designee), will review the nominations shortly after to confirm and announce the release squad as soon as possible.
Together we can make WordPress 7.0 the best one yet!