Re: Re: Decommissioning Qt 5 CI

Am Dienstag, 28. Juli 2026, 23:36 schrieb Albert Astals Cid:
> El dimarts, 28 de juliol del 2026, a les 13:20:56 (Hora d=E2=80=99estiu d=
=E2=80=99Europa=20
> central), Nicolas Fella va escriure:
> > On 28/07/2026 12:52, Ben Cooksley wrote:
> > > Hi all,
> > >=20
> > > For some time now Qt 5 has been in extended maintenance / support,
> > > which Iif my understanding is correct has now come to an end.
> > >=20
> > > Accordingly, given that all of our applications have now had a
> > > substantial amount of time to migrate, and plenty of notice that CI
> > > would be withdrawn eventually, i'd like to proceed with withdrawing CI
> > > support for Qt 5.
> > >=20
> > > This will free up valuable space on the CI nodes and allow us to
> > > remove an image that is under very minimal, if any, maintenance.
> > >=20
> > > Please let me know if there are any objections.
> >=20
> > Hi,
> >=20
> > for applications I agree to drop Qt5 CI. The few usages that are left
> > either already have Qt6 CI, or are more or less dead projects.
> >=20
> > 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.
>=20
> Does the code of those repos change in qt5 related areas?
>=20
> 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?
>=20

breeze, oxygen and plasma-integration is
* new qt5 code builds on current distros
it changes as the qt6 code changes. The goal is that qt5 and qt6 applicatio=
ns
look and feel the same.
=46or breeze and oxygen the same code base is compiled twice, once with qt6=
 and once with qt5.
plasma-integration has copies of the code for qt5 and qt6 because the ifdef=
'ery became a bit too much.

Non changing qt5 code that I can think of is kwayland-integration which is =
an implementation detail of kf5/plasma5
but we provide in plasma6 to keep kf5 apps working.=20

Cheers, David

> Cheers,
>   Albert
>=20
> >=20
> > Cheers
> >=20
> > Nico
>=20
>=20
>=20
>=20
>=20