Re: Decommissioning Qt 5 CI

On 28/07/2026 12:52, Ben Cooksley wrote:
> Hi all,
>
> For some time now Qt 5 has been in extended maintenance=C2=A0/ support,=
=20
> which Iif my understanding is correct has now come to an end.
>
> Accordingly, given that all of our applications have now had a=20
> substantial amount of time to migrate, and plenty of notice that CI=20
> would be withdrawn eventually, i'd like to proceed with withdrawing CI=
=20
> support for Qt 5.
>
> This will free up valuable space=C2=A0on the CI nodes and allow us to=20
> remove an image that is under very minimal, if any, maintenance.
>
> Please let me know if there are any objections.

Hi,

for applications I agree to drop Qt5 CI. The few usages that are left=20
either already have Qt6 CI, or are more or less dead projects.

That said, we have a number of (Plasma) components that we still build=20
for Qt5 for (external) application compatibility (breeze,=20
plasma-integration, etc). So far we have not made a decision to stop=20
doing that, and I'd rather not lose CI for those. That doesn't mean we=20
need Qt5 CI in the current form. Could we use a distribution image with=20
Qt and the few necessary libraries/frameworks baked in? That would be a=20
much smaller image and easier to maintain than the current suse-qt515=20
image.

Cheers

Nico