LTS vs Innovation Releases: Version Selection, Support Windows, and Compatibility

Learning outcomes

Suppose two developers say “we run modern MySQL.” One means 8.4 LTS because the company values a stable feature set and long maintenance window. Another means the newest Innovation release because the product team wants recently introduced features and already has automated compatibility tests. Both choices can be production-grade, but they create different upgrade and reproducibility obligations.

Why release track is an architecture choice

Database versions affect far more than the text printed by SELECT VERSION(). They can change available SQL syntax, reserved words, authentication behavior, optimizer decisions, defaults, upgrade paths, connector support, Shell/Router compatibility, and the operational runbooks used by replication or high availability.

Oracle divides current MySQL releases into LTS and Innovation tracks. LTS is designed for environments that want a stable feature set and longer support period; Innovation is designed for teams that want newer features and are prepared for a faster upgrade cadence. Both tracks receive bug and security fixes and are described by Oracle as production-grade. The tradeoff is change velocity and support horizon, not “production versus experimental.”

The release map in August 2026

The course deliberately does not chase the highest version number. Its published curriculum targets MySQL 8.4 LTS so all chapters can share one reproducible engine baseline. At the time of this lesson review, 8.4.11 is the latest 8.4 patch release. Oracle also documents MySQL 9.7 as an LTS series and the 26.7 calendar-versioned Innovation line.

Future readers may see newer numbers. That is expected. The durable rule is to identify the release track, exact patch, support status, and compatibility matrix at the time you deploy.

Server version, client version, Shell version: three separate facts

MySQL tools can be installed or upgraded independently. The command-line client on your workstation may not match the server on another machine. MySQL Shell is a separate product with its own version lifecycle. Connectors such as Connector/J or Connector/Python also have their own versions and compatibility ranges.

mysql --versionmysqlsh --version

SELECT VERSION() AS server_version,       @@version AS version_again,       @@version_comment AS version_comment,       @@version_compile_os AS compiled_for_os,       @@version_compile_machine AS compiled_for_architecture;

The client command tells you which client binary is on your path. The SQL query tells you which server accepted the session. Neither alone tells you the version of your application connector, Router, backup product, or operating-system package repository.

Release notes are part of the test plan

A version policy should force release-note review before deployment. Do not search only for new features. Look for fixed security issues, changed defaults, deprecated or removed functionality, replication or InnoDB notes, optimizer changes, authentication changes, packaging changes, and upgrade restrictions.

For a production application, pair documentation review with automated tests: schema migration tests, representative query tests, transaction/concurrency tests, connector tests, backup/restore tests, and—if relevant—replication or failover tests. “The server started” is not a compatibility test.

A wrong approach: let mysql --version choose your server baseline

Imagine a developer installs a new mysql client, runs mysql --version, sees a modern version, and records “database upgraded.” Nothing about that command proves the server changed. The client could still connect to an older or completely different server endpoint.

C:\> mysql --versionmysql  Ver ... for Win64 ...# This identifies the client binary only.

SELECT VERSION() AS server_version,       @@hostname AS server_hostname,       @@port AS server_port,       CONNECTION_ID() AS connection_id;

The repaired workflow verifies both ends and records the endpoint. This becomes especially important during staged upgrades where old and new servers run side by side.

Hands-on lab: write a version qualification record

Create environment.md in your disposable course workspace and add a “Version qualification” section. Capture the observations below, then answer what would have to be retested before switching release families.

SELECT NOW() AS observed_at,       VERSION() AS server_version,       @@version_comment AS version_comment,       @@default_storage_engine AS default_storage_engine,       @@sql_mode AS session_sql_mode,       @@character_set_server AS server_character_set,       @@collation_server AS server_collation;

Server track: MySQL 8.4 LTSServer patch: record SELECT VERSION()mysql client: record mysql --versionMySQL Shell: record mysqlsh --version, or "not installed"Deployment: native / VM / containerOS or image tag: record itApplication connector(s): record exact package versions when introducedRelease notes reviewed: link/dateRestore test status: not yet performed in Chapter 01

Production judgment: patch discipline still matters on LTS

“LTS” does not mean “install once and never update.” An LTS family receives necessary bug and security fixes. Your organization still needs a supported patch cadence, staging environment, release-note review, backups, recovery tests, and change windows appropriate to its risk profile.

Innovation users need an even stronger automation culture because the release cadence is faster and new behavior can arrive sooner. The correct track is the one your team can operate safely while meeting product requirements.

Summary and next lesson

Version selection is a policy, not a download-button accident. This course uses a current patched MySQL 8.4 LTS Community Server to keep 110 lessons reproducible, while explicitly acknowledging newer LTS and Innovation families. Always record the exact server and tool versions, read current release/upgrade notes, and retest real application behavior before changing families.

Next, you will install or locate the actual toolchain on Windows, Linux, or a disposable container and prove that the server—not merely the package installer—is working.

References

• MySQL 8.4 — Innovation and LTS releases
• MySQL 8.4 Release Notes
• MySQL 9.7 LTS Reference Manual
• MySQL 26.7 — current release model and calendar versioning
• MySQL 8.0 Release Notes and EOL notice