Decommissioning Qt 5 CI

[Ingo Klöcker]

On Dienstag, 28. Juli 2026 23:36:20 Mitteleuropäische Sommerzeit Albert Astals 
Cid wrote:
> El dimarts, 28 de juliol del 2026, a les 13:20:56 (Hora d’estiu d’Europa
> central), Nicolas Fella va escriure:
> > That said, we have a number of (Plasma) components that we still build
> > for Qt5 for (external) application compatibility (breeze,
> > plasma-integration, etc). So far we have not made a decision to stop
> > doing that, and I'd rather not lose CI for those. That doesn't mean we
> > need Qt5 CI in the current form. Could we use a distribution image with
> > Qt and the few necessary libraries/frameworks baked in? That would be a
> > much smaller image and easier to maintain than the current suse-qt515
> > image.
> 
> Does the code of those repos change in qt5 related areas?
> 
> Trying to understand what we want CI for here:
>  * Potentially new qt5 code builds with old qt5/gcc distros?
>  * Non changing qt5 code builds new gcc/stuff from distros?

Additionally to Albert's questions I don't understand why distros that still 
need Qt 5 builds of breeze and plasma-integration cannot simply build the 
latest released versions that support(ed) Qt 5. Why do they need the latest 
and greatest breeze and plasma-integration for the remaining Qt 5 apps which 
probably haven't seen a release in years? Does plasma-integration need to 
match the version of Plasma?

Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 265 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20260730/180dc32c/attachment.sig>