Description:
In recent MySQL release notes (such as MySQL 9.7.2 and 8.4.11 releases), the bug fix summaries have become overly generic. Many entries now read simply as:
"Fixed an issue related to <topic> (Bug #XXXXX)"
or
"Fixed several issues relating to validations."
While we understand that release notes are now streamlined or generated using HeatWave AI / automated tools, removing the functional details makes it difficult for developers, and architects to assess the impact of a release.
Historically, release notes provided 1–2 clear sentences explaining what the issue was, under what conditions it occurred. This detail is crucial for evaluating whether an upgrade fixes a specific problem affecting a production environment.
How to repeat:
Examples
MySQL 9.7.2 Release Notes:
https://dev.mysql.com/doc/relnotes/mysql/9.7/en/news-9-7-2.html
Entries lack context regarding the trigger conditions or symptom of the bug.
MySQL 8.4.11 Release Notes:
https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-11.html
Grouping fixes under generic phrasing like "Fixed several issues relating to validations" leaves no actionable information for DBAs.
Suggested fix:
Could the prompt or generation pipeline for the AI tool be updated to include a brief 1–2 line summary for each bug fix?
Ideally, a release note entry should answer:
What was the observed symptom or unexpected behavior?
Under what specific feature/command/condition did it occur?
Example of desired format:
"Fixed an issue where a high volume of concurrent DDL statements could cause temporary tables to leak memory. (Bug #XXXXX)"
Restoring this level of clarity would restore immense value to the official MySQL release documentation for the community.
© 2026, Oracle Corporation and/or its affiliates