We have released Qt 5.15.6 LTS for commercial license holders today. As a patch release, Qt 5.15.6 does not add any new functionality but provides bug fixes and other improvements.
You can add Qt 5.15.6 in the existing online installation by using the maintenance tool or do a clean installation by using the Qt Online Installer. Offline installers are available in the Qt Account download area.
Fixed Bugs and Important Changes
As always with our long-term supported releases, we have been targeting to include all the important bug fixes to the extent feasible. Looking back to the Qt 5.15.0 release the now released Qt 5.15.6 contains over 1170 bug fixes as well as numerous smaller improvements in the functionality - as well as multiple important security fixes. These bug fixes are also included in Qt 6.x releases and we recommend all active development projects to migrate either to the latest Qt 5.15.6 patch release or to Qt 6.
The list of fixes and the overview of all important changes in Qt 5.15.6 can be found from the release note. It is available via Qt Account: in Downloads, select Product: Qt and Version: 5.15.6.
Accessing Sources
If you want to access the source code repository, it can be done via the Codereview system. Just log in with a Qt Account that has a valid commercial license, and you will be able to access the LTS repositories. For more details, please check the instructions for accessing the commercial LTS repositories.
Building with Yocto
Qt for Device Creation images are also available for Qt 5.15.6 LTS. If you want to build yourself with yocto, set up Gerrit and use the meta-qt5 layer from the Qt repository. We have updated the yocto meta-qt5 layer of Qt 5.15.6 to point to the commercial LTS repositories. For more details, please check the instructions on using yocto with access to the commercial LTS repositories.
Support
If you have any problems with the commercial LTS releases, please contact Qt Support. You can also create bugs to https://bugreports.qt.io, but in addition it is recommended to notify the support team about it.
***
The next commercial-only LTS patch release Qt 5.15.7 will be released in October 2021.
Commenting for this post has ended.
I'd love to, but for the releases of my free software application I'm stuck on Qt 5.15.2 since Qt 6 would break compatibility with the operating systems for many users (Windows 7, Windows 8 and macOS 10.13 (which is the latest supported version on many Apple devices still in use)).
Does this help? https://community.kde.org/Qt5PatchCollection
Thanks, I wasn't aware of that effort! However, it would mean I need to build not only my application but also Qt itself for each of the supported platforms, which I'd really like to avoid.
I hope Qt can add Apple M1 support in the next release of 5.15.7(normally you don't need change the code of Qt, only add more parameters to build), so we will buy the license of Qt and don't need to face and immigrate to Qt6. Thanks!
It is strange that LTS is commercial, but I can not see changelog anywhere. The list of bugs is the reason to buy or not buy, but list of bugs is not available.
@Evgeniy Dushistov: Changelog is part of the Release note provided for customers via Qt Account.
That is exactly my point. They suggest to buy something, what is this something you can only know after you buy it, not before. Very strange politic.
Any chance of ever making Qt free again for open source academic projects? I am in charge of one such project and we are stuck with Qt 5.12.11 because... well, we can neither afford the license fee nor can we afford to use a non-LTS version of Qt.
I'm curious about the last point. Why does an academic project require an LTS version?
For the same reasons that a commercial project would also prefer to use an LTS version? I mean, my project is used by many people around the world. So, I need Qt to be as solid as possible and that means using an LTS version. I have, in the past, tried to stick to the bleeding edge version of Qt, but it has on occasions resulted in me being badly burnt. To use an LTS version is no guarantee of a bug free experience (as I have, once again, experienced recently), but at least it's safer.