On May 26, 2026, at 13:31, Marc Mutz via Development <[email protected]> wrote:
* As for bug-fixes: they ought to be clearly communicated to users via [ChangeLog], so users know what will come with the next update instead of showing up as regressions in their projects. In the age of AI, there's no excuse for consumers of our products to not run the ChangeLog (or even the diff between releases) and their code past some AI to find potential regressions, it not outright fix the code, before upgrading. Well, at least Task-number/Fixes: QTBUG-xxxxxx. Nowadays every bug fix gets into release-note.md, as in https://github.com/qt/qtreleasenotes/blob/dev/qt/6.11.1/release-note.md (unfortunately that sounds a lot more negative than the hand-written ChangeLog messages though). So I think write a ChangeLog only if it’s an important behavior change, to avoid redundancy? OTOH it doesn’t look like the Qt Installer installs release-note.md. Also, CVEs are explicitly listed in release-note.md, it seems. So I think it’s important to put a CVE reference in the commit message, probably? Otherwise, how is it populated?
-- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
