ApsaraDB RDS for MySQL follows MySQL community version lifecycles and extends support beyond community end-of-life (EOL) dates, giving you time to plan and complete major engine version upgrades.
Version lifecycle milestones
The following table lists the release and end-of-support dates for each major engine version.
Some dates are estimates and may change before the actual EOL or end-of-support date. Actual dates take precedence.
| Major engine version | Release date (MySQL community) | Release date (ApsaraDB RDS for MySQL) | EOL date (MySQL community) | End-of-support date (ApsaraDB RDS for MySQL) |
|---|---|---|---|---|
| MySQL 8.0 | April 19, 2018 | May 2019 | April 2026 (estimated) | / |
| MySQL 5.7 | October 21, 2015 | November 2016 | October 21, 2023 | October 21, 2028 (estimated) |
| MySQL 5.6 | February 5, 2013 | December 2014 | February 5, 2021 | February 5, 2028 (estimated) |
| MySQL 5.5 | December 8, 2010 | February 2012 | December 8, 2018 | December 8, 2021 |
What happens at community EOL
When a major engine version reaches its EOL date in the MySQL community, the MySQL community stops releasing updates for that version. ApsaraDB RDS for MySQL then enters an extended support period.
During the extended support period:
ApsaraDB RDS for MySQL continues to release updates that address severe security and stability issues.
Not all security issues can be fixed, because the MySQL community keeps some vulnerabilities confidential after EOL.
RDS instances running the EOL version remain available for purchase and use. For details, see Alibaba Cloud official announcements.
Plan your upgrade. The extended support period gives you time to upgrade without disruption. Upgrading the major engine version of your RDS instances is the recommended course of action. For upgrade instructions, see Upgrade the major engine version.