Databases 17 min read

Introducing MySQL Innovation and Long-Term Support (LTS) Versions

Oracle announces a new MySQL version model that separates Innovation releases, which deliver new features and frequent updates, from Long‑Term Support (LTS) releases that provide stable, minimal‑change versions with extended support, outlining upgrade paths, deprecation policies, and detailed release schedules.

Top Architect
Top Architect
Top Architect
Introducing MySQL Innovation and Long-Term Support (LTS) Versions

1 Introduction

Oracle continuously improves MySQL and is launching a new version model that includes Innovation (feature‑rich) and Long‑Term Support (LTS) editions, giving users a choice between rapid feature delivery and stable, long‑lasting releases.

2 New MySQL Version Model

Transition to Innovation and LTS

The upcoming model will debut with MySQL 8.1.0 as the first Innovation release; versions 8.0.34+ will contain only error fixes until the 8.0 end‑of‑life in April 2026. Approximately a year later, an 8.x version will become LTS, allowing ample migration time.

During the transition, users who need the latest features and fixes should adopt Innovation releases (e.g., 8.1.x, 8.2.x, 8.3.x). Users who only require critical patches should stay on the 8.0.x error‑only line.

MySQL HeatWave Service

HeatWave is fully managed by the MySQL team and receives the latest improvements, security patches, and features (OLTP, OLAP, machine learning, Lakehouse) from day 1. Users can select Innovation (8.1+) or error‑only (8.0.x) versions per database.

Product Portfolio and Support Lifecycle

LTS versions follow Oracle’s Lifetime Support policy (5 years primary, 3 years extended). Innovation releases are supported until the next major/minor version.

MySQL Server, Shell, Router, NDB Cluster will have both Innovation and LTS editions.

MySQL Operator for Kubernetes (InnoDB ReplicaSet, Cluster, ClusterSet) will have both editions.

MySQL Connectors will stay compatible with all supported server versions.

MySQL Workbench will remain on 8.0.x and stay compatible.

Version Release Rhythm

8.0.34+ – error‑only patches only (red).

Innovation releases – potentially quarterly (gray).

New LTS release – roughly every 2 years (blue).

Future years will see a timeline similar to the illustration in the original article.

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

Innovation Release Details

Innovation releases follow the continuous delivery model of MySQL 8.0 (< 8.0.34), delivering bug fixes, security patches, and new features. They are intended for fast‑moving development environments with automated testing and CI pipelines.

Each Innovation release may introduce new deprecations, removals, or behavior changes. Strategies and best practices will be provided to mitigate upgrade risk.

Deprecation and Removal

Features deprecated in a given version will not be removed for at least one year, giving users time to adapt.

LTS versions will not remove features; only the first LTS version may add or delete features.

Behavior Changes

Code refactoring or alignment with SQL standards may cause behavior changes, potentially affecting syntax, reserved words, execution plans, or performance, and may require application adjustments.

Long‑Term Support (LTS) Versions

Every ~2 years a minor version becomes LTS, receiving 5 years of primary support and 3 years of extended support, similar to MySQL 5.7 and earlier.

Upgrade and Downgrade Strategies

Frequent Innovation releases and biennial LTS releases give users multiple supported paths. Innovation adopters must upgrade regularly to stay current.

In‑place Upgrade/Downgrade within LTS

Features and data formats remain unchanged, allowing in‑place upgrades and downgrades, as well as InnoDB CLONE support.

Upgrade/Downgrade between LTS Versions

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

Rollback using MySQL Shell export/import or replication (for rollback only).

Upgrade/Downgrade between Innovation Versions

In‑place upgrade supported; clone not supported.

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

Using MySQL Asynchronous Replication

In production, upgrades often use asynchronous replication with the new version as a replica, enabling near‑zero‑downtime upgrades.

Can replicate to the next LTS version.

Can replicate to any future Innovation version up to the next LTS.

Supported Upgrade/Downgrade Methods

In‑place

Clone

Async Replication

Export/Import

LTS 8.4 → LTS 9.7

LTS 8.4.11 → LTS 8.4.20

Innovation 8.1 → 8.2

Innovation 8.1 → 8.3

Innovation 9.1 → LTS 9.7

LTS 8.4 → LTS 10.7

Downgrade Support

In‑place

Clone

Async Replication

Export/Import

LTS 8.4.20 → 8.4.11

LTS 9.7 → LTS 8.4

✓✮

✓✮

LTS 9.7 → Innovation 9.6

✓✮

✓✮

LTS 9.7 → Innovation 9.5

✓✮

✓✮

(✮) indicates support limited to rollback scenarios.

3 Summary

For more information, join the MySQL community channels or contact Oracle support. Downloads are available at mysql.com/downloads and edelivery.oracle.com . Detailed release notes contain feature lists, improvements, bug fixes, and major changes.

References

Life‑Time Support: https://www.oracle.com/support/lifetime-support/resources.html

Community Slack: http://mysqlcommunity.slack.com/

Oracle Support: https://support.oracle.com/

Downloads: https://www.mysql.com/downloads/

edelivery: http://edelivery.oracle.com/

Release Notes: https://dev.mysql.com/doc/

最近面试BAT,整理一份面试资料《Java面试BAT通关手册》,覆盖了Java核心技术、JVM、Java并发、SSM、微服务、数据库、数据结构等等。获取方式:点“在看”,关注公众号并回复 手册,领取,更多内容陆续奉上。

© Original article: https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions

DatabaseMySQLreleaseUpgradeinnovationVersioninglts
Top Architect
Written by

Top Architect

Top Architect focuses on sharing practical architecture knowledge, covering enterprise, system, website, large‑scale distributed, and high‑availability architectures, plus architecture adjustments using internet technologies. We welcome idea‑driven, sharing‑oriented architects to exchange and learn together.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.