MySQL 8.1 has been released, also announced that MySQL began to use a new version model.
By Kenny Gryp / Airton Lastori
MySQL product team.
Original: https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions
Primer
At Oracle, we are constantly looking for ways to improve our products to better meet your needs. We are pleased to introduce MySQL Innovation (Innovation) and Long-Term Support (LTS, Long-Term Support), which is an important improvement in the MySQL release model.
Patch releases for MySQL 5.7 and earlier were primarily dedicated to bug fixes and security patches. This changed in MySQL 8.0's continuous delivery model, and patch releases also include new features. This allows MySQL to release new features to users more frequently than just every few years. However, we understand that this approach may present challenges for projects and applications that require only critical patches and few behavior changes. We've listened to your feedback and observed industry trends, and we're now transitioning to a release model where you can choose between Innovation and Long Term Support (LTS).
Both Creative and LTS releases are production-grade in quality. If you crave access to the latest features and improvements, and like to stay abreast of the latest technologies, MySQL Innovation Edition might be right for you. This release is ideal for developers and DBAs working in a fast-paced development environment with a high level of automated testing and modern continuous integration techniques that allow for faster upgrade cycles. On the other hand, if your environment requires continued behavior that has been fixed, then an LTS release is for you. These releases contain only necessary fixes, thereby reducing the risk of changes in the behavior of database software.
With the new MySQL edition model, you have the flexibility to choose the option that suits your specific application and environment needs. Our goal is to ensure you have a great user experience in both the Innovation and LTS releases. You can learn more about the new version of the model and the transition process below.
New MySQL version model
Transition to Innovation and LTS releases
Our upcoming new release will transition to a new MySQL release model. MySQL 8.1.0 will be our first innovative release, and 8.0.34+ will be bugfix-only until 8.0 End of Life (EOL, scheduled for April 2026). In about a year, MySQL 8.x releases will finally become LTS, which will provide ample time for users to migrate from 8.0.x to 8.x LTS releases.
In practice, during this transition period, if you want the latest features, improvements, and all bug fixes of the MySQL database, use an innovative release (eg 8.1.x, 8.2.x, 8.3.x, etc.). If your MySQL only needs bug fixes, use an 8.0.x release (eg 8.0.35, 8.0.36, 8.0.37, etc.). In both cases, it is recommended that you update the MySQL database quarterly according to the Oracle Critical Patch Update (CPU) calendar. When 8.x becomes LTS, you can plan, test, and migrate from a fix release (such as 8.0.37) to an LTS release (such as 8.4.1).
MySQL HeatWave service
The MySQL HeatWave service is fully managed, developed and supported by Oracle's MySQL team. We deliver the latest improvements and security patches with the latest version of MySQL. MySQL HeatWave users get access to bug fixes from day 1, as well as the latest features including OLTP, OLAP, Machine Learning and Lakehouse.
MySQL HeatWave users can now choose between innovative releases, starting with 8.1.0, and bug-fix releases, starting with 8.0.34. The service provides the flexibility to choose a MySQL edition per database system, allowing users to mix and match editions based on application requirements. Users of 8.1+ innovative releases can take full advantage of the service's potential, accessing the latest features and bug fixes. On the other hand, those users who only need critical bug fixes and not the latest features can choose 8.0.x releases for their MySQL databases.
MySQL Product Portfolio and Support Lifecycle
LTS releases will follow Oracle's lifetime support policy , which includes 5 years of Prime Support and 3 years of Extended Support. Innovative releases will be supported until the next major and minor release.
Most products in the MySQL portfolio will have Innovation and LTS releases:
- MySQL Server, MySQL Shell, MySQL Router, MySQL NDB Cluster will have Innovation and LTS editions.
- MySQL Operator for Kubernetes with InnoDB ReplicaSet, Cluster, and ClusterSet will have Innovation and LTS releases.
- The MySQL connector will use the latest version, but will be considered generally available and compatible with all supported MySQL server versions.
- MySQL Workbench will remain at 8.0.x, generally available and compatible with all supported MySQL server versions.
MySQL version release cadence
- 8.0.34+ is only a bugfix release (red)
- Innovative releases (gray) may be released quarterly
- A new LTS version (blue) is released approximately every 2 years. The exception is the release of the 8.x LTS release, which will be well before the EOL of 8.0.
Over the next few years, MySQL releases will look similar to the diagram below:
NOTE: This is just an example, there is no promise that the version number will be exactly as presented.
innovative version
Innovative releases are similar to the MySQL 8.0 continuous development model (< 8.0.34), including bug fixes, security patches, and new features.
Support for innovative releases is limited to the next minor release (innovative or LTS). The current cycle goal is to release an innovative release every quarter, with incrementing minor version numbers (eg 8.2, 8.3, etc.). Patch releases within innovation releases are possible, but unlikely.
Innovation releases will also be generally available and recommended for production environments. Bug fixes and security patches are usually included in the next Innovation Release or LTS release, rather than as part of a patch release within that Innovation Release. When using innovative releases, regular upgrades to the latest innovative releases are necessary to keep up with the latest bug fixes and security patches.
In addition to bug fixes, security patches, and new features, innovative releases will introduce new deprecated features, removed features, and even behavior changes. To reduce the risk and complexity of escalating when these changes are introduced, policies and best practices will be developed to dictate when and how to proceed.
Deprecated and Removed Features
In previous versions of MySQL, a deprecated feature in one release (eg 5.7) meant that the feature might be removed in the next major/minor release (eg 8.0). As innovative releases are introduced, there will be more major/minor releases, so when deprecations and removals happen will change.
When a feature or behavior is deprecated in a release (eg 9.2 innovative release), that feature cannot be removed for at least one year (until 9.6 innovative release). This is to modify the database deployment time for users using the innovative version.
NOTE: There will not be any removals in the LTS release. Features can only be added and removed in the first LTS release (eg 8.4.0 LTS), and cannot be removed after that.
Expect to increase the number of deprecations and removals as we transition to the new model and move towards the first 8.x LTS release.
behavior change
In addition to new features in innovative releases, behavior changes are also expected as code is refactored or MySQL is modified to more conform to SQL standard behavior (which does not happen in LTS releases).
Behavior changes can have a big impact, especially when dealing with anything application-related, such as SQL syntax, new reserved words, query execution, and even query performance. Behavior changes may require application changes, which may require considerable effort for our users to migrate.
In addition to documenting every behavior change, it is important that our users have access to the necessary tools and configuration settings to facilitate upgrading and downgrading between versions. Depending on the type of behavior change, different methods will be used. More details will be provided as we introduce such changes.
Long Term Support Release
Approximately every 2 years, a minor release is designated as a long-term support release. This release will have 5 years of Prime Support and 3 years of Extended Support, the same as previously supported releases. This is similar to MySQL 5.7 and earlier.
The LTS will also be the last release of that major release. The next innovative release will increase the major version number. For example, if MySQL 8.4.0 is the 8.x LTS release, then MySQL 9.0 will be the next innovative release.
upgrade and downgrade
With the increased frequency of major and minor innovative releases, and LTS releases every 2 years, users will have more supported releases to choose from. Becoming an adopter of the innovative series will require frequent updates to keep up with bug fixes and security patches, which requires an upgrade and downgrade strategy.
Let's take a deeper look at the various supported upgrade and downgrade scenarios.
Upgrades and downgrades within LTS releases
Within the LTS release, the functionality remains the same and the data format does not change.
therefore:
- In-place upgrades and downgrades are possible. This is an improvement over MySQL 8.0.x releases (< 8.0.34), since downgrading is not possible, and skipping versions for upgrades is not recommended.
- InnoDB CLONE supports upgrade and downgrade in the LTS version.
It will take some work to fully transition to this point, which will be done in a release after 8.0.34.
Upgrades and downgrades between two LTS releases
- It is possible to migrate from one LTS release to the next without performing multiple intermediate innovation release upgrade steps.
- Upgrades are possible through in-place upgrades, MySQL Shell export and import, and MySQL asynchronous replication.
- Just to roll back an upgrade in progress, downgrades can be done via MySQL Shell export and import and MySQL replication, see below for details.
Upgrading and Downgrading Between Innovation Versions
- Supports in-place upgrades from one innovation release or LTS release to future innovation releases up to the next LTS release. Copy and export import are also possible.
- Downgrading will require a logical export and import. This is similar to MySQL 8.0.x (< 8.0.34).
Upgrading and Downgrading Using MySQL Asynchronous Replication
In business-critical environments, upgrades are typically done using MySQL asynchronous replication, where the new version environment is set as a slave for the current version. This allows for upgrades with near zero downtime.
Can copy asynchronously from LTS releases or innovation releases to:
- Next LTS release.
- Any future innovation releases until the next LTS release (LTS 8.4 → LTS 9.7, but not LTS 8.4 → LTS 10.7).
It is important to support going back to the previous version if any issues arise after promoting the new version. Therefore, MySQL asynchronous replication will be able to replicate to the previous version. This support is for rollback purposes only, where new features have not been used, and should not be considered part of continuous production deployments.
Upgrade and downgrade support
Here is an overview of the various supported upgrade and downgrade methods:
upgrade
| on the spot | clone | asynchronous 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
| on the spot | clone | asynchronous 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 that support is limited to rollback purposes only.
Summarize
You are welcome to engage with our community channels and support team as we transition to this new model .
You can download the latest MySQL release at mysql.com/downloads , or download the MySQL Enterprise Edition binaries from the Oracle Software Delivery Cloud at http://edelivery.oracle.com/ .
For details about each release, including new features, improvements, bug fixes, and possible breaking changes, see the MySQL Release Notes .
We're excited about the opportunities this new version of the model presents and eagerly look forward to your feedback. Let's work together to make MySQL better. For more technical articles, please visit: https://opensource.actionsky.com/
About SQLE
The SQLE of the Akson open source community is a SQL auditing tool for database users and managers, which supports multi-scenario auditing, supports standardized online processes, natively supports MySQL auditing, and has scalable database types.
SQLE get
| type | address |
|---|---|
| Repository | https://github.com/actiontech/sqle |
| document | https://actiontech.github.io/sqle-docs/ |
| release news | https://github.com/actiontech/sqle/releases |
| Data audit plug-in development documentation | https://actiontech.github.io/sqle-docs/docs/dev-manual/plugins/howtouse |