How MySQL’s New Innovation and LTS Versions Change Your Upgrade Strategy

1 Introduction

Oracle announces a new MySQL version model that adds Innovation (feature‑rich) and Long‑Term Support (LTS) tracks, giving users a choice between rapid feature delivery and a stable, low‑change release.

2 New MySQL Version Model

Transition to Innovation and LTS

MySQL 8.1.0 will be the first Innovation release; 8.0.34+ will be a pure error‑fix stream until the end of the 8.0 lifecycle (EOL April 2026). About a year later the 8.x line will become LTS, giving users ample time to migrate.

During the transition, use Innovation builds (e.g., 8.1.x, 8.2.x) for the latest features and fixes, or stay on 8.0.x (e.g., 8.0.35) for critical patches only. Quarterly Oracle Critical Patch Update (CPU) calendars are recommended for all versions.

MySQL HeatWave Service

HeatWave is fully managed by the MySQL team and receives the latest improvements and security patches. Users can choose Innovation (starting with 8.1.0) or error‑fix (starting with 8.0.34) streams, mixing versions per application needs.

Product Portfolio and Support Lifecycle

LTS versions follow Oracle’s lifetime‑support policy: five years of premier support plus three years of extended support. Innovation releases are supported until the next major/minor version.

MySQL Server, Shell, Router, NDB Cluster

MySQL Operator for Kubernetes (InnoDB ReplicaSet, Cluster, ClusterSet)

MySQL Connectors (latest version, GA, compatible with all supported servers)

MySQL Workbench (remains on 8.0.x, compatible with all supported servers)

Release Cadence

8.0.34+ – error‑fix only (red)

Innovation releases – roughly quarterly (gray)

New LTS version – approximately every two years (blue)

Future releases will follow the schematic shown below.

Note: this diagram is illustrative only and does not guarantee exact version numbers.

3 Innovation Versions

Innovation releases continue the MySQL 8.0 continuous‑development model (< 8.0.34) with bug fixes, security patches, and new features. They are supported only until the next minor version (Innovation or LTS) and are intended for production use, with quarterly releases expected.

Deprecations and Removals

Features deprecated in one version may be removed in a later major/minor version. A deprecated feature must remain for at least one year before removal, giving users time to adapt. LTS versions will not have deletions; only the first LTS release may add or remove features.

Note: LTS versions will never have deletions after the first LTS release.

Behavior Changes

Beyond new features, Innovation releases may include refactorings that align MySQL more closely with the SQL standard, leading to behavior changes that can affect syntax, reserved words, query execution, or performance, potentially requiring application adjustments.

Long‑Term Support (LTS) Versions

Approximately every two years a minor version becomes LTS, receiving five years of premier support and three years of extended support, similar to the model used for MySQL 5.7 and earlier.

Upgrade and Downgrade

The increased frequency of Innovation releases and biennial LTS releases give users more supported options, but adopting Innovation requires regular updates and a clear upgrade/downgrade strategy.

Upgrade/Downgrade Within LTS

Features and data formats remain unchanged within an LTS line, allowing in‑place upgrades and downgrades (unlike pre‑8.0.34 where downgrades were not possible). InnoDB CLONE supports both upgrade and downgrade within LTS.

Upgrade/Downgrade Between LTS Versions

Direct migration from one LTS to the next without intermediate Innovation upgrades.

Supported via in‑place upgrade, MySQL Shell export/import, or asynchronous replication.

Rollback can be performed using Shell export/import or replication.

Upgrade/Downgrade Between Innovation Versions

In‑place upgrade from one Innovation (or LTS) to a future Innovation until the next LTS.

Downgrade requires logical export/import, similar to pre‑8.0.34 behavior.

Asynchronous Replication Upgrade/Downgrade

In critical environments, upgrades are often performed via asynchronous replication, setting the new version as a replica to achieve near‑zero downtime. Replication can also be used to roll back to the previous version for rollback‑only scenarios.

Replicate to the next LTS version.

Replicate to any future Innovation version up to, but not beyond, the next LTS.

(✮) indicates rollback‑only support.

Supported Upgrade/Downgrade Methods

Upgrade

Supported paths include in‑place, clone (where applicable), asynchronous replication, and export/import, depending on the source and target versions (e.g., LTS 8.4 → LTS 9.7, Innovation 8.1 → 8.2, etc.).

Downgrade

Supported paths include in‑place, clone, asynchronous replication, and export/import for specific version pairs, with some paths limited to rollback scenarios only.

4 Summary

Community channels and the support team are available for feedback. Latest MySQL builds can be downloaded from mysql.com/downloads or the Oracle Software Delivery Cloud. Detailed release notes contain full information on new features, improvements, bug fixes, and breaking changes.