Qt 5.15 Release: Difference between revisions
(Added Qt 5.15.17 release information.) |
(Added Qt 5.15.18 release information.) |
||
| Line 276: | Line 276: | ||
|October 2024 | |October 2024 | ||
| | | | ||
| | |31.10.2024 | ||
| | |https://www.qt.io/blog/commercial-lts-qt-5.15.18-released | ||
|- | |- | ||
|Qt 5.15.19 | |Qt 5.15.19 | ||
Latest revision as of 10:11, 31 October 2024
Qt 5.15 Standard Support Releases
Release blog post: https://www.qt.io/blog/qt-5.15-released
Announce: https://lists.qt-project.org/pipermail/announce/2020-May/000234.html
Contact Information
| Role | Name | irc | |
|---|---|---|---|
| Release Manager | Jani Heikkinen | jani.heikkinen@qt.io | jaheikki3 |
Qt 5.15 release plan
| Phase | Original plan | Updated plan | Realized |
|---|---|---|---|
| Feature Freeze | 31.01.2020 | 31.01.2020 | |
| Alpha Release | 04.02.2020 | 14.02.2020 | |
| Beta1 Release | 25.02.2020 | 28.02.2020 | |
| Beta2 Release | 12.03.2020 | 20.03.2020 | 23.03.2020 |
| Soft String Freeze | 25.03.2020 | 25.03.2020 | |
| String freeze | 01.04.2020 | 01.04.2020 | |
| Beta3 Release | 03.04.2020 | 06.04.2020 | |
| Branch 5.15.0 from 5.15 | 22.04.2020 | 23.04.2020 | |
| Beta4 release | 16.04.2020 | 20.04.2020 | |
| Release Candidate | 30.04.2020 | 06.05.2020 | |
| RC2 | 12.05.2020 | 12.05.2020 | |
| Final Release | 15.05.2020 | 26.05.2020 | 26.05.2020 |
| 5.15.1 | August 2020 | 08.09.2020 | 10.09.2020 |
| 5.15.2 | November 2020 | 19.11.2020 | 20.11.2020 |
Tools used when building & packaging Qt 5.15
Qt 5.15 release team meeting memos
03.12.2019 'Initial Qt 5.15.0 schedule'
31.03.2020
Qt 5.15 LTS Commercial Releases
Qt 5.15 LTS Commercial extended lifetime: https://www.qt.io/blog/qt-5.15-extended-support-for-subscription-license-holders
End of support: 26.5.2025
Contact information
| Role | Name | |
|---|---|---|
| Release Manager | Tarja Sundqvist | tarja.sundqvist@qt.io |
Release Plan
Release Notes
Release notes for the Qt 5.15 LTS Commercial release are available via Qt Account. In Qt Account, select Downloads - Product: Qt - Version: <Qt Version>.
Known Issues
Known issues for Qt 5.15 LTS Commercial releases are listed in the release notes.
Some additional highlights of known issues are listed below:
- Qt 5.15.4 LTS Commercial: See the Qt WebEngine known issues in Qt 5.15.4 Known Issues#QtWebEngine
- Qt 5.15.6 LTS Commercial: provides a fix for the security issue described in https://nvd.nist.gov/vuln/detail/CVE-2021-38593
- Qt 5.15.7 LTS Commercial: In Qt WebEngine, the CHROMIUM_VERSION file includes an incorrect version number 94.0.4606.61. The correct Chromium patch level version number is 94.0.4606.81.
Getting Source Codes
The Qt 5.15 LTS Commercial source codes are available in the tqtc shadow repositories and their lts branches.
Note! To be able to clone the LTS sources, you must have a commercial license. An evaluation license does not provide access to the LTS sources.
Qt sources
To clone the Qt sources, follow the instructions:
- Register to Gerrit as instructed in [1]. Some notes:
- If you just want to clone the sources, you need to follow the instructions in steps 1-3 and either set an SSH key (step 5) or an HTTP password (step 7).
- If you are going to contribute to the Qt Project, step 4 is mandatory.
- Login to Gerrit and follow the instructions in [2] to clone the LTS source codes.
Yocto environment
If you are using the Yocto environment, please see instructions in https://doc.qt.io/QtForDeviceCreation-5.15/qtee-meta-qt5.html#using-qt-5-15-lts-commercial-releases.
Troubleshooting
Here are some tips for the most common issues. Please note that as a commercial customer you can also contact our support team.
- Please check your license. The LTS branches require a commercial license. An evalution license does not provide access to the LTS sources.
- If you have used to work with the public Qt 5 repositories, please note that LTS sources are available via tqtc shadow repositories and a Gerrit account is needed for accessing them. Log in Gerrit and setup your account as instructed in [3].
- If you see the following error message at the end of cloning command, it might refer to the network issues (for example, too slow connection):
fatal: early EOF
Please wait a while and try again cloning sources.fatal: fetch-pack: invalid index-pack output