On Donnerstag, 2. Jänner 2025 12:37:47 Mitteleuropäische Normalzeit Ulrich 
Müller wrote:
> Can you provide a pointer to a Qt upstream page saying that Qt 5 is
> deprecated? Just for the case that the upstreams of my packages need
> further convincing.

Not sure I can, without accompanying explanations:
https://www.qt.io/blog/qt-offering-changes-2020

Qt5 upstream (Qt Company) OSS support ended on 2020-12-08. Since then, bugs 
are only fixed if reproduced in Qt6 first, then backported. Since then, public 
availability of commercial 5.15 LTS releases is delayed by 1 year, including 
repository access for cherry-picking - this is important, see below, and 
affects Gentoo first and foremost.

The last official LTS release will be this April/May:
https://www.qt.io/blog/qt-5.15-extended-support-for-subscription-license-holders
https://wiki.qt.io/Qt_5.15_Release#Release_Plan

Public availability of this release will be *1 year later*. Some may think 
now, fine, updates (3 in total) until 2026! However, if a dependency/toolchain 
upgrade down the stack breaks Qt5 between now and March/April, to be then 
fixed in their final release, you will be waiting until April/May 2026 for 
that to be available. If it breaks later than April 2025, you will be waiting 
forever. In either case, you rely on downstream volunteer patchwork.

KDE Qt5PatchCollection ultimately relies on Qt company's upstream commits as 
well, so don't expect any original work from there to get things fixed. In any 
case, there is no clear EOL date for these patches, but they *will* be drying 
up as there is no main KDE consumer left, I certainly know that my 
contributions come to an end.
https://community.kde.org/
Qt5PatchCollection#For_how_long_will_this_be_maintained?


Gentoo Qt Policy page:
https://wiki.gentoo.org/index.php?title=Project:Qt/
Policies#Handling_different_versions_of_Qt

Gentoo Qt migration notes:
https://wiki.gentoo.org/wiki/Project:Qt/Qt6_migration_notes

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to