WordPress 7.0 has a new official release date set for May 20th, 2026, marking a significant milestone as contributors worldwide finalize architectural improvements and key features. The updated schedule outlines a series of release parties and testing phases designed to ensure the stability and performance of this major core update.
Key Takeaways
- The WordPress 7.0 general release is scheduled for May 20, 2026.
- Several release parties and pre-release milestones are planned, including beta and release candidate versions.
- RC3 will function as a beta in practice, emphasizing the importance of continued testing, especially by web hosts.
- Release parties happen live in the #core Slack channel, open to all contributors and interested participants.
- Last-minute schedule adjustments remain possible based on host feedback and final testing results.
WordPress 7.0 Release Cycle and Schedule Details
The WordPress 7.0 release cycle has been extended to accommodate crucial architectural enhancements aiming to improve stability and performance. Contributors have been actively addressing last-minute issues, with release parties serving as focused events for collaborative testing and bug fixing. The updated timeline reflects a structured cadence of beta releases and release candidates leading up to the general availability.
Pre-release versions have been rolling out since February 2026, with Beta 1 debuting on February 19 and the latest Release Candidate 2 on March 26. Notably, the upcoming RC3, scheduled for May 8, is designated to act as a new Beta 1 in practice, underscoring the need for continued rigorous testing.
Following RC3, a Release Candidate 4 is set for May 14, functioning as a new RC1. A dry run and 24-hour code freeze are planned for May 19 to ensure readiness before the general release on May 20.
| Date (UTC) | Milestone | Emcee / Release Lead | Committer | Security | Mission Control (Coordination) |
|---|---|---|---|---|---|
| February 19, 2026 at 15:00 UTC | Beta 1 | @amykamala | @ellatrix | @audrasjb | @sergeybiryukov |
| February 26, 2026 at 15:00 UTC | Beta 2 | @amykamala | @ellatrix | @audrasjb | @sergeybiryukov |
| March 5, 2026 at 14:00 UTC | Beta 3 | @amykamala | @audrasjb | Committing from WordCamp Nice Contributor Day! | @audrasjb, @sergeybiryukov |
| March 10, 2026 at 23:30 UTC | Unplanned Beta 4 following security releases | @desrosj | @sergeybiryukov | @sergeybiryukov | @sergeybiryukov |
| March 12, 2026 at 15:00 UTC | Beta 5 | @chaion07 | @ellatrix | @audrasjb | @sergeybiryukov |
| March 24, 2026 at 15:00 UTC | Release Candidate 1 | @amykamala | @ellatrix | @audrasjb | @sergeybiryukov |
| March 26, 2026 at 15:00 UTC | Release Candidate 2 | @4thhubbard | @ellatrix | @audrasjb | @sergeybiryukov |
| April 24, 2026 | Call for host testing | @desrosj | n/a | n/a | n/a |
| May 8, 2026 at 15:00 UTC | Release Candidate 3 (treated as Beta 1) | @amykamala | @ellatrix | @audrasjb | @sergeybiryukov |
| May 14, 2026 at 15:00 UTC | Release Candidate 4 (treated as new RC1) | @4thhubbard | @ellatrix | @audrasjb | @sergeybiryukov |
| May 19, 2026 at 15:00 UTC | Dry Run / 24-Hour Code Freeze | TBD | TBD | TBD | TBD |
| May 20, 2026 | General Release | TBD | TBD | TBD | TBD |
How to Participate in WordPress 7.0 Release Parties
All release parties take place in the #core channel on the official WordPress Slack workspace. These events welcome everyone, from first-time contributors to seasoned developers, as well as those simply curious about the release process. The parties focus on testing, bug reporting, and collaboration to help polish the release ahead of general availability.
Detailed participation instructions are available on the WordPress Core blog, making it accessible for contributors to join in regardless of their experience level. Active participation during these events is critical to catch last-minute bugs and compatibility issues, improving the overall quality of WordPress 7.0.
What This Means for WordPress Users
For most WordPress site operators and developers, the extended timeline and structured release parties mean a higher assurance of stability and performance from WordPress 7.0. This release focuses on foundational architectural improvements while delivering new features that have been eagerly anticipated.
In practice, the continued emphasis on host testing and community feedback during the RC3 and RC4 phases reflects lessons learned from previous major releases. It highlights the importance of real-world environment testing, especially given the diversity of hosting configurations in the WordPress ecosystem.
Agencies and plugin developers should plan to test their products early against the 7.0 beta and release candidate versions. This proactive approach helps identify compatibility issues before the final release, reducing risks for client sites. Hosting providers, in particular, are urged to participate in the call for testing to ensure their environments support the new core efficiently.
The release party format also reinforces the collaborative nature of WordPress development, inviting broad community involvement to maintain the platform’s reliability. We recommend subscribing to the #core Slack channel and monitoring official channels for updates as the release date approaches.
Frequently Asked Questions
What is the significance of treating RC3 as a beta in WordPress 7.0?
Treating RC3 as a beta allows the development team to incorporate feedback and fixes more flexibly before the final release. It encourages continued testing and helps catch issues that might not have appeared in earlier phases, improving overall stability.
How can I join the WordPress 7.0 release parties?
Release parties take place in the #core Slack channel on the official WordPress Slack workspace. Anyone interested can join by creating a Slack account and following the instructions posted on the WordPress Core blog.
What should plugin developers do to prepare for WordPress 7.0?
Plugin developers should test their plugins against the beta and release candidate versions of WordPress 7.0 to ensure compatibility. Early testing helps identify potential conflicts or deprecated features, allowing time to update before the official release.
Will there be any last-minute changes to the release schedule?
Yes, the release squad may adjust the schedule based on feedback from hosting providers and community testing. Updates will be communicated promptly via the #core Slack channel and official WordPress Core blog posts.
