Author | JiekeXu
Source|Public Account JiekeXu DBA Road (ID: JiekeXu_IT)
If you need to reprint, please contact for authorization | (Personal WeChat ID: JiekeXu_DBA)
Hello everyone, I am JiekeXu. I am very glad to meet you again. Today, I will translate an article about Oracle's new MySQL innovation and long-term support (LTS) version. Welcome to click on the blue word "JiekeXu DBA Road" to follow My official account, star or top, more dry goods will arrive as soon as possible!
Table of ContentsTransitioning
to Innovative and LTS ReleasesMySQL
HeatWave Database ServicesMySQL
Portfolio and Support LifecycleMySQL
Release
CadenceInnovative
ReleasesDeprecations and RemovalsFeature Behavior
ChangesLong
Term Supported VersionsUpgrade
and DowngradeUpgrade and Downgrade
in an LTS ReleaseUpgrade and Downgrade
from an LTS Release Downgrading to Another LTS
Upgrading and Downgrading Between Releases Upgrading and Downgrading Using MySQL Asynchronous Replication
Upgrading and
Downgrading Support Matrix Upgrading and
Downgrading Conclusion
原文链接：https://blogs.oracle.com/mysql/post/introducing-mysql-innovation-and-longterm-support-lts-versions
原文作者：Kenny Gryp: MySQL Product Management Director
Airton Lastori: MySQL Product ManagerTranslator's Note: On the evening of July 18, 2023, the MySQL official website released the download and update instructions for MySQL 8.1.0 and 8.0.34. The following is the download address: https://dev.mysql.com/downloads/mysql/ Or reply [MySQL8.1] in the backstage of this public account to get the installation package for installation experience) At the same time, MySQL 5.7.43 version, 5.7 and 8.0 is already a version we are familiar with, but an 8.1.0 Innovation version has been released . What version is this? The word Innovation means innovation, indicating that 8.1.0 is an innovative version, unlike 8.0, which is an LTS long-term version, so let's take a look at how the official introduction is, the following is the original translation:
At Oracle, we are constantly looking for ways to improve our products to better meet your needs. We are pleased to introduce MySQL Innovation and Long Term Support Releases, an important improvement in the MySQL versioning model.
Patch releases for MySQL 5.7 and previous versions focus on bug fixes and security patches. That changed in MySQL 8.0, and the continuous delivery model in patch releases also includes new features. This allows MySQL to release new features to users more frequently than every few years. However, we know this approach can pose challenges for projects and applications that only require critical patches and have infrequent behavior changes. We've listened to your feedback and observed industry trends, and we're now transitioning to a version control model where you can choose between innovative and long-term support (LTS) releases.
Both Innovation and LTS are production-grade quality. If you want access to the latest features and improvements and enjoy staying on top of the latest technologies, MySQL Innovation Edition might be right for you. These releases are ideal for developers and DBAs working in fast-paced development environments with high levels of automated testing and modern continuous integration techniques for faster upgrade cycles. On the other hand, if your environment requires established behavior, then the LTS release is the one for you. These releases contain only necessary fixes, so they reduce the risks associated with changes in the behavior of database software.
With the new MySQL versioning 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 innovative and LTS releases. Below you can find additional information about the new versioned model and the conversion process.
Transition to innovation and LTS releases
We are transitioning to the new MySQL versioning model with an upcoming release. MySQL Database version 8.1.0 will be our first innovative release, and 8.0.34+ will transition to bug fixes only until 8.0's End of Life (EOL) is scheduled to stop in April 2026. In about a year, MySQL version 8.x will finally become LTS, which will give users ample time to migrate from 8.0 to 8.x LTS releases.
In fact, during this transition period, if you want MySQL Database to get the latest features, improvements, and all bug fixes, use the innovation release track (eg, 8.1.x, 8.2.x, 8.3.x, etc.). If you only need to fix errors in the MySQL database, use the 8.0.x versions (eg 8.0.35, 8.0.36, 8.0.37, etc.). In both cases, you should plan to update your MySQL database quarterly according to the (Oracle Critical Patch Update (CPU))[https://www.oracle.com/security-alerts] calendar. When 8.x becomes LTS, you can plan, test, and migrate from the 8.0.x bug fix track to the LTS release track ( for example, from 8.0.37 to 8.4.1 ).
MySQL HeatWave database service
The MySQL HeatWave database service is fully managed, developed and supported by Oracle's MySQL team. We deliver the latest improvements and security patches with the latest MySQL database releases. MySQL HeatWave customers have access to bug fixes and the latest features including OLTP, OLAP, Machine Learning and Lakehouse from day one.
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 offers the flexibility to choose a MySQL edition for each database system, enabling users to mix and match editions based on application requirements. Those on the 8.1+ innovation release can take full advantage of the service's potential, getting the latest features and bug fixes. Alternatively, those who only need critical bug fixes and do not need the latest features can choose the 8.0.x releases for their MySQL database system.
MySQL Product Portfolio and Support Lifecycle
LTS releases will follow Oracle's lifetime support policy, which includes 5 years of Premier 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 both innovative and LTS releases:
MySQL Server, MySQL Shell, MySQL Router, MySQL NDB Cluster will have innovative and LTS versions.
MySQL Operator for Kubernetes, InnoDB ReplicaSet, Cluster and ClusterSet will have innovation and LTS releases.
The MySQL connector will use the latest version used, but will be considered generally released and will remain compatible with all supported MySQL server versions.
MySQL Workbench will remain on 8.0.x, which is generally released, and will remain compatible with all supported MySQL server versions.
MySQL version release cadence
MySQL 8.0.34+ will be bug fix only releases (red)
innovative releases (gray) may be released quarterly and
a new long term support release (blue) approximately every 2 years. One exception is the 8.x LTS releases, which will occur in
the next few years before the EOL of 8.0, MySQL versioning will look like the example diagram below:
Note that this is an example and there is no promise that the version number will be exactly the same as the presented version.
Innovation release
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 Innovation is limited to the next minor release (Innovation or LTS). The current cadence targets quarterly releases of innovative, increasing minor version numbers (eg 8.2, 8.3, etc.). A patch release in an innovative version is possible, but unlikely to happen.
The innovative version will also be officially released and it is recommended to use it in a production environment. Bug fixes and security patches are usually included in the next innovation or LTS release, rather than as part of a patch release within that innovation release. When using innovative releases, it is necessary to regularly upgrade to the latest innovative releases 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 deprecations, feature removals, and even behavior changes. To reduce the risk and complexity of upgrading when such changes are introduced, strategies and best practices for when and how to implement them need to be developed.
Deprecated and removed features
In previous versions of MySQL, a deprecation in one release (eg 5.7) meant that the feature could 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 are allowed will change.
When a feature or behavior is deprecated in a release (for example, the 9.2 innovation), that functionality cannot be removed for at least one year (until the 9.6 innovation). This is to give users time to modify the database deployment while running an innovative version.
Note that there are no deletions in the LTS release. Features can only be removed (and added) in the first LTS release (such as 8.4.0 LTS), not later.
Expect deprecations and removals to increase 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 as code is refactored or when MySQL is modified to be more SQL-compliant (this 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 migration effort for our users.
In addition to documenting every behavior change, it's important to provide our users with the necessary tools and configuration settings to be able to easily upgrade and downgrade 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 supported version
Approximately every 2 years, minor releases are designated as Long Term Support releases. This release will provide 5 years of pre-qualification and 3 years of extended support, the same as previously supported releases. This is similar to MySQL 5.7 and prior versions.
LTS will also be the last release of a major release. The next (innovative) release will increase its major release. 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 an increased cadence of major and minor innovative releases and LTS releases every 2 years, users will have more supported versions to choose from. As an adopter of the innovative series, frequent updates are required to follow bug fixes and security patches, which requires an upgrade and downgrade strategy.
Let's take a deeper look at the various upgrade and downgrade scenarios that will be supported.
Upgrading and Downgrading in LTS Releases
In the LTS release, the functionality remains the same and the data format does not change.
Hence:
in-place upgrades and downgrades are possible. This is an improvement compared to MySQL 8.0.x versions (<8.0.34), MySQL <>.<>.x versions cannot be downgraded, nor is it recommended to upgrade by skipping versions.
InnoDB clones will be supported in LTS releases for upgrades and downgrades.
More work is needed to fully transition to this and will be released after 8.0.34.
Upgrading and downgrading from one LTS to another
It is possible to migrate from one LTS release to the next without performing the several intermediate steps of upgrading an innovative release.
Upgrades can be accomplished with in-place upgrades, MySQL Shell Dump and Load, and MySQL Asynchronous Replication.
Downgrades can be achieved via MySQL Shell Dump&Load and MySQL Replication with the sole purpose of rolling back an upgrade in progress, see below for details.
Upgrading and Downgrading Between Innovation Versions
In-place upgrades from one innovation or LTS release to future innovation releases will be supported until the next LTS release. Copy and dump and load will also work.
Downgrading will require a logical dump and load. This is similar to MySQL 8.0.x (< 8.0.34).
Upgrading and Downgrading Using MySQL Asynchronous Replication
Upgrades for business-critical environments are typically done using MySQL asynchronous replication, where the new version environment is set as a replica of the current version. This allows for upgrades with almost zero downtime.
Can be copied from LTS or innovation releases to
Next LTS version
Any future innovation release before the next LTS release (LTS 8.4 → LTS 9.7, but not LTS 8.4 → LTS 10.7)
It is important to support copying back to the previous version if any issues arise after upgrading to the new version. Therefore, MySQL asynchronous replication will be able to replicate to previous versions. This support is for rollback purposes only, where new features have not been used, and should not be considered part of regular continuous production deployments.
Upgrade and Downgrade Support Matrix
Below is an overview of the various supported upgrade and downgrade methods
upgrade
downgrade
(✮) indicates that support is limited to rollback purposes only.
in conclusion
We welcome your engagement on 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 you can download MySQL Enterprise binaries using Oracle Software Delivery Cloud at http://edelivery.oracle.com/.
For details about each release, including new features, improvements, bug fixes, and possible breaking changes, check out the MySQL Release Notes.
In addition to 8.0, MySQL HeatWave Database Service now offers the latest innovative release of MySQL 8.1. This includes the latest capabilities including OLTP, OLAP, Machine Learning and Lakehouse. For a free trial account, visit oracle.com/mysql/free.
We're very excited about the opportunities this new versioning model will bring, and eagerly look forward to your feedback. Together we can continue to make MySQL better.
The full text is finished, I hope it can help you who are reading, if you think this article is helpful to you, you can share it with your friends, colleagues, whoever you care about, and share it with whoever you care about, let's learn together and make progress~~~
Welcome to follow my official account [JiekeXu DBA Road], and learn new knowledge together as soon as possible! You can find me at the following three addresses. The other addresses belong to pirated copyright infringement crawling my articles, and the code format, pictures, etc. are disordered, which is inconvenient to read. Welcome to my official account or Motianlun address to follow me, and get the latest updates as soon as possible information.
Welcome to follow my official account [JiekeXu DBA Road], and learn new knowledge together as soon as possible!
————————————————————————————————
Public account: JiekeXu DBA Road
CSDN: https://blog.csdn.net/JiekeXu
Motian Wheel: https://www.modb.pro/u/4347
———————————————————————————————
Share several database backup scripts
Oracle table fragmentation check and defragmentation scheme
OGG|Oracle GoldenGate 基础2022 年公众号历史文章合集整理Several problems encountered by Oracle 19c RAC
OGG|Oracle 数据迁移后比对一致性OGG|Oracle GoldenGate Microservice Architecture
Oracle query table space usage is extremely slow
Domestic database|TiDB 5.4 stand-alone quick installation first experience
Oracle ADG standby database shutdown maintenance process and incremental recovery
Linux environment to build MySQL8.0.28 master-slave synchronization environment
