Skip to content

[MySQL] Extended Support Timeline update#353

Open
andtapia wants to merge 1 commit intoMicrosoftDocs:mainfrom
andtapia:patch-2
Open

[MySQL] Extended Support Timeline update#353
andtapia wants to merge 1 commit intoMicrosoftDocs:mainfrom
andtapia:patch-2

Conversation

@andtapia
Copy link
Contributor

Updated timelines

@prmerger-automator
Copy link
Contributor

@andtapia : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 9f2b84e:

✅ Validation status: passed

File Status Preview URL Details
articles/mysql/concepts-version-policy.md ✅Succeeded

For more details, please refer to the build report.

@v-regandowner
Copy link
Contributor

@xboxeer

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Feb 24, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Azure Database for MySQL major version retirement/support timeline table to reflect new Standard/Extended Support dates.

Changes:

  • Revised Standard Support end dates and Extended Support start/end dates for MySQL 5.7 and 8.0 in the retirement timeline table.
  • Adjusted timeline durations to align with the updated extended support plan.

Comment on lines +45 to +46
| [MySQL 5.7](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-31.html) | March 20, 2018 | October 31, 2023 | July 31, 2026 | August 1, 2026 | October 31, 2026 |
| [MySQL 8.0](https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-21.html) | December 11, 2019 | April 30, 2026 | Decembber 31, 2026 | January 1, 2027 | April 30, 2029 |
Copy link

Copilot AI Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The updated table shows Azure Extended Support starting on Aug 1, 2026 (MySQL 5.7) and Jan 1, 2027 (MySQL 8.0), but the next section says Extended Support is planned to begin in spring 2026. Please update the prose to match the revised timelines (or make it version-specific).

Copilot uses AI. Check for mistakes.
| [MySQL 5.7](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-31.html) | March 20, 2018 | October 31, 2023 | March 31, 2026 | April 1, 2026 | March 31, 2029 |
| [MySQL 8.0](https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-21.html) | December 11, 2019 | April 30, 2026 | May 31, 2026 | June 1, 2026 | May 31, 2029 |
| [MySQL 5.7](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-31.html) | March 20, 2018 | October 31, 2023 | July 31, 2026 | August 1, 2026 | October 31, 2026 |
| [MySQL 8.0](https://mysqlserverteam.com/whats-new-in-mysql-8-0-generally-available/) | [Features](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-21.html) | December 11, 2019 | April 30, 2026 | Decembber 31, 2026 | January 1, 2027 | April 30, 2029 |
Copy link

Copilot AI Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spelling typo in the date: "Decembber" should be "December".

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants