Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is a WordPress Release Cycle? A Plain Explanation

Short answer

A WordPress release cycle is the planned run of work that turns new features and fixes into a public WordPress version. It usually lasts around 4 months and moves through planning, development, beta testing, release candidates, and launch. Major versions bring new features, while minor versions fix bugs and close security gaps.

Key takeaways

  • A WordPress release cycle usually lasts around 4 months, from scoping to launch, as of November 2026.
  • Beta testing starts a feature freeze, and release candidates start a string freeze for translators.
  • Major versions use two numbers, such as 7.1, while minor versions add a third number, such as 7.1.4.
  • WordPress 7.2 was scheduled for 8 December 2026, after Beta 1 on 20 October 2026 and RC1 on 17 November 2026.
  • Only the most recent WordPress version is actively supported, though security fixes are backported to older branches.
  • Minor and security releases install in the background by default, while major releases need a choice on most older sites.

What is a WordPress release cycle?

A WordPress release cycle is the planned run of work that turns a set of new features and fixes into a public WordPress version.

A cycle is not one event. It is a set of steps with dates, leads, and checks, and each step has a clear job.

The Make WordPress Core handbook says a release cycle usually lasts around 4 months, from the initial scoping meeting to the launch of the version. Planned future releases are listed on the Project Roadmap.

Each cycle has a release lead, who is the person in charge of that version. Focus leads run parts of the work, such as the editor, design, or docs. The team works in public, so anyone can follow the schedule and the open tickets.

How often does WordPress release a major version?

WordPress aims for about 3 major releases a year, or roughly one every 4 months, as of November 2026.

That pace is a goal, not a promise. Dates move when work slips or a feature needs more time.

The Make WordPress Project release schedules page says the goal is to return to 3 major releases in 2026, after 2025 saw just 2 major versions: 6.8 in April and 6.9 in December.

Recent history shows the shift. WordPress 7.0, code-named Armstrong, shipped on 20 May 2026, according to the WordPress.org news post for 7.0.

WordPress 7.1 shipped on 19 August 2026, according to the WordPress.org news post for 7.1.

WordPress 7.2 was scheduled for 8 December 2026, according to the 7.2 schedule on Make WordPress Core.

Minor releases fill the gaps. They ship when fixes are ready, often soon after a major release, and they do not wait for the next 4-month cycle.

What are the 5 phases of a release cycle?

A release cycle has 5 phases: planning, development, beta, release candidate, and launch.

The Make WordPress Core handbook lists the same 5 phases for each cycle. The table below gives a short view of each one.

PhaseWhat happensWhat it means for you
1. PlanningThe release lead picks focus leads and sets the scopeYou can see what the next version may hold
2. DevelopmentTeams build the planned featuresNew code lands in trunk, the main code line
3. BetaTesters report bugs and no new features are addedThis is the time to test on a staging site
4. Release CandidateOnly regressions are fixed and text is frozenThe version is close to final
5. LaunchThe version ships in the admin update screenYou can update, after a backup and a check

Planning

Planning starts the cycle. The release lead talks with contributors, picks the features for the next version, and names a focus lead for each one.

Development

Development is the build phase. Focus leads run teams, hold regular chats, and track tickets in Trac, the WordPress bug tracker.

The block editor moves on its own fast pace inside this phase. The Block Editor release process guide says Gutenberg releases happen about every 2 weeks, and the release closest to Beta 1 feeds into the major version.

What is the difference between a major, minor, and security release?

A major release adds new features, a minor release fixes bugs, and a security release closes security gaps.

The number tells you which type it is. A major version uses 2 numbers, such as 7.1. A minor version adds a third number, such as 7.1.4.

The Developer.WordPress.org guide on secure updates puts it in plain terms: major core updates include new WordPress features, while minor core updates often include maintenance releases, security fixes, and updates to translation files.

Release typeVersion exampleWhat changesHow urgent is it?
Major7.1New features, new tools, some changed behaviourPlan it, test first
Minor7.1.1Bug fixes from the last major releaseUpdate soon
Security7.1.4Fixes for security issuesUpdate right away

Security releases can also reach older branches. WordPress 7.1.4 shipped on 28 October 2026, and the WordPress.org news post says its fixes were backported to all branches that still get security fixes, currently through 4.7.

That backport is a courtesy, not full support. The same post says only the most recent version of WordPress is actively supported.

What happens during beta testing?

Beta testing is the phase when new features stop and bug hunting starts.

The Make WordPress Core handbook says no more commits for new enhancements or feature requests are allowed for the rest of the release once beta starts. Testers are asked to report bugs.

For WordPress 7.2, Beta 1 landed on 20 October 2026, and the 7.2 schedule lists 5 betas in total: Beta 1 on 20 October, Beta 2 on 27 October, Beta 3 on 28 October, Beta 4 on 3 November, and Beta 5 on 10 November 2026.

Each beta fixes bugs found in the last one. The count can change, so a cycle may have more or fewer betas than 7.2 did.

Beta code is not final. Do not run it on a live site.

Use a staging copy, and check the plugins and theme you rely on. If you need a way to spot plugins that have gone quiet, read our guide on how to find abandoned WordPress plugins.

What happens during the release candidate phase?

The release candidate phase is the last check before launch, when only regressions are fixed.

A regression is a bug that broke something that worked before. The Make WordPress Core handbook says work in this phase is targeted on regressions introduced during the current cycle only.

A string freeze also starts at this point. That means the text in WordPress stops changing, so translators can finish their work without chasing new words.

For WordPress 7.2, RC1 arrived on 17 November 2026. The WordPress.org news post for 7.2 RC1 says the scheduled final release date was 8 December 2026, and it warns readers not to install, run, or test the RC on production or mission-critical websites.

The 7.2 schedule lists 4 release candidates: RC1 on 17 November, RC2 on 18 November, RC3 on 24 November, and RC4 on 1 December 2026, with a dry run on 7 December. A dry run is a practice run of the release steps, held the day before launch.

How do you know which version your site runs?

You can see your WordPress version in the admin dashboard, under Dashboard, then Updates.

That screen shows the version you run and the version offered to you. It also shows plugin and theme updates on the same page.

Another quick check is Tools, then Site Health, then Info. That page lists your WordPress version, your PHP version, and your database version in one place.

Check the PHP version too, because a new WordPress version may need a newer PHP version. WordPress.org's Requirements page recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, and HTTPS support, as of November 2026.

The same page notes a legacy floor: WordPress also works with PHP 7.4 and MySQL 5.5.5, but those versions have reached official End Of Life and may expose a site to security risks. PHP 8.3 gets security fixes until 31 December 2027, according to php.net.

How do automatic updates fit into the release cycle?

Minor and security releases install in the background by default, while major releases need your choice on many sites.

Automatic background updates for minor core releases have been the default since WordPress 3.7. That is why a security release such as 7.1.4 can reach many sites without an admin clicking anything.

The Developer.WordPress.org hook reference says new installs on WordPress 5.6 or higher also auto-update major versions by default. Older sites keep the earlier behaviour, with minor releases only, until an admin opts in.

You can change the setting in code with the WP_AUTO_UPDATE_CORE constant. The Developer.WordPress.org wp-config.php guide lists 3 values: true for all core updates, minor for minor releases only, and false to turn all core updates off.

If you run many sites, keep the rule the same on each one. Our guide on how to manage multiple WordPress sites covers a shared routine for updates, backups, and checks.

What changed in the 2026 release cycle?

The 2026 cycle brought 3 major releases, with 7.0 in May, 7.1 in August, and 7.2 scheduled for December.

WordPress 7.0, code-named Armstrong, shipped on 20 May 2026. WordPress 7.1, code-named Mary Lou, shipped on 19 August 2026 and honours jazz pianist Mary Lou Williams.

Each major release is named after a jazz musician. The WordPress.org news post for 7.1 says 7.1 reflects the work of more than 800 contributors from all over the world.

Security work ran between the majors. WordPress 7.1.4 shipped on 28 October 2026 as a short-cycle security release, and the WordPress.org news post says the next major release, 7.2, was planned for 8 December.

A new default theme was also set to ship with 7.2, according to the 7.2 schedule on Make WordPress Core. A default theme is the free theme that ships with a fresh WordPress install.

How should you prepare for a new major release?

Prepare in 3 steps: back up, test on staging, then update.

Start with a full backup of files and the database. Read our guide on how to back up WordPress before you touch the update button.

Next, test the new version on a staging copy. Check your main pages, your forms, and your checkout if you sell online. Look for plugin notices and PHP errors.

Then update the live site from Dashboard, then Updates, then Update Now. The Developer.WordPress.org upgrading guide describes the same one-click update path, and it warns against jumping across more than 2 major releases at once.

If a plugin breaks, check its WordPress.org page for a closure notice or a missing update. Our guide on what happens when a plugin is closed on WordPress.org explains what a closure means and what to do next.

What mistakes should you avoid?

Avoid 4 common mistakes: updating without a backup, testing a beta on a live site, ignoring security releases, and staying on an old branch.

  • Update a live site with no backup. A backup is the only fast way back if the update breaks a plugin or a theme.
  • Test a beta or a release candidate on a live site. Beta and RC builds are for staging only, and WordPress.org says so in each RC post.
  • Put off a security release. A security release such as 7.1.4 is urgent, and the WordPress.org post says to update sites right away.
  • Stay on an old branch and assume it is fine. Only the most recent version is actively supported, even when older branches get backported fixes.
  • Skip the PHP check. A new major version may raise the PHP floor, so check Tools, then Site Health, then Info before you update.

Frequently asked questions

How long does a WordPress release cycle take?

A release cycle usually lasts around 4 months, from the initial scoping meeting to launch. That covers planning, development, beta testing, release candidates, and the launch itself. Dates can move, so check the current schedule on Make WordPress Core for the exact dates of the release you follow.

Does WordPress release a new major version every month?

No. WordPress aims for about 3 major releases a year, or roughly one every 4 months, as of November 2026. In 2025 it shipped only 2 major versions, and in 2026 it planned 3: 7.0 in May, 7.1 in August, and 7.2 in December. Minor and security releases ship between majors, when fixes are ready.

Should I install a beta or release candidate on my live site?

No. Beta and release candidate builds are for testing on a staging site or a local copy, not for a live site. They can still change, and a bug in a beta could break pages, forms, or checkout. Test the beta on staging, report bugs you find, and wait for the final release before you update the live site.

What is the difference between WordPress 7.1 and 7.1.4?

WordPress 7.1 is a major release, with new features, while 7.1.4 is a minor security release on the same branch. The third number marks a minor release. Version 7.1.4 shipped on 28 October 2026 with security fixes, and its fixes were also backported to older branches, through 4.7.

Do minor WordPress updates install on their own?

Yes, in most cases. Minor and security core releases have installed in the background by default since WordPress 3.7, if the site can run one-click updates. Major releases auto-install by default only on new installs from WordPress 5.6 onward. You can check or change the setting under Dashboard, then Updates.

How do I know when the next WordPress release is coming?

Check the release schedule on Make WordPress Core, which lists the dates for beta releases, release candidates, and the final launch. The WordPress.org news blog also posts each beta, release candidate, and final release. For example, the 7.2 schedule listed Beta 1 on 20 October 2026 and the final release on 8 December 2026.

Sources

  1. How the Release Cycle Works Make WordPress Core
  2. WordPress 7.2 Make WordPress Core
  3. WordPress 7.1.4 WordPress.org News
  4. WordPress 7.1 Mary Lou WordPress.org News
  5. Requirements WordPress.org
  6. WordPress 7.2 Release Candidate 1 WordPress.org News
  7. Supported Versions PHP.net

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test