Re: Re: Re: Decommissioning Qt 5 CI

--00000000000079ab940657e4e589
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 31, 2026 at 9:15=E2=80=AFPM David Redondo <[email protected]=
> wrote:

> Am Donnerstag, 30. Juli 2026, 20:53 schrieb Ben Cooksley:
> > On Fri, Jul 31, 2026 at 3:47=E2=80=AFAM David Redondo <kde@david-redond=
o.de>
> wrote:
> >
> [Snip]
> >
> > So the Plasma developers want to keep supporting Qt 5 for essentially
> > eternity and never drop support for it?
> >
> > At what point do you stop, or do you just keep continuing to maintain
> > compatibility because one distribution doesn't want to drop
> > $unmaintainedQt5App?
>
> (readding dropped lists)
>
> I dont't know the concrete point in time  but  given that there are some
> big
> applications on still on Qt5 I would say it's too early now.
>

Please quantify that and list the applications you consider "big" that need
to have ported before this can be abandoned.


>
> Btw Plasma 5 dropped support of Qt4 builds of breeze and oxygen  in 2020
> with
> 5.18, see
> https://mail.kde.org/pipermail/plasma-devel/2020-January/108585.html


>
> I don't think we need an image provided by sysadmin and build kf5 on our =
CI
> infra. Couldn't we just download a image of $LTS distro like okular does?
>
> https://invent.kde.org/graphics/okular/-/blob/master/.gitlab-ci.yml?
> ref_type=3Dheads#L24
> <https://invent.kde.org/graphics/okular/-/blob/master/.gitlab-ci.yml?ref_=
type=3Dheads#L24>


Depends on the number of times your job runs.
Doing jobs that way is expensive because everytime the job runs it
re-fetches every single dependency from distribution archives and installs
them in the container before it even starts building.


>
>
> > Will Plasma developers keep Qt 5 installed on their local machines and
> > perform appropriate testing for that with the legacy, unported
> applications
> > still using Qt 5?
> > Just having CI compile something isn't a true test as to whether it wor=
ks
> > or not and risks silent bitrot taking place due to behaviour difference=
s
> > between Qt 5 and Qt 6.
> >
> >
> > >
> > > Cheers,
> > > David
> > >
> > >
> > Regards,
> > Ben
> >


Regards,
Ben

--00000000000079ab940657e4e589
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><span style=3D"background-color:transpare=
nt">On Fri, Jul 31, 2026 at 9:15=E2=80=AFPM David Redondo &lt;<a href=3D"ma=
ilto:[email protected]">[email protected]</a>&gt; wrote:</span></div>=
<div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">Am Donnerstag, 30. Juli 2026, 20:53 schrieb Ben Coo=
ksley:<br>
&gt; On Fri, Jul 31, 2026 at 3:47=E2=80=AFAM David Redondo &lt;<a href=3D"m=
ailto:[email protected]" target=3D"_blank">[email protected]</a>&gt; =
wrote:<br>
&gt; <br>[Snip]<br>
&gt; <br>
&gt; So the Plasma developers want to keep supporting Qt 5 for essentially<=
br>
&gt; eternity and never drop support for it?<br>
&gt; <br>
&gt; At what point do you stop, or do you just keep continuing to maintain<=
br>
&gt; compatibility because one distribution doesn&#39;t want to drop<br>
&gt; $unmaintainedQt5App?<br>
<br>
(readding dropped lists)<br>
<br>
I dont&#39;t know the concrete point in time=C2=A0 but=C2=A0 given that the=
re are some big <br>
applications on still on Qt5 I would say it&#39;s too early now.<br></block=
quote><div><br></div><div>Please quantify that and list the applications yo=
u consider &quot;big&quot; that need to have ported before this can be aban=
doned.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">
<br>
Btw Plasma 5 dropped support of Qt4 builds of breeze and oxygen=C2=A0 in 20=
20 with <br>
5.18, see<br>
<a href=3D"https://mail.kde.org/pipermail/plasma-devel/2020-January/108585.=
html" rel=3D"noreferrer" target=3D"_blank">https://mail.kde.org/pipermail/p=
lasma-devel/2020-January/108585.html</a></blockquote><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><br>
<br>
I don&#39;t think we need an image provided by sysadmin and build kf5 on ou=
r CI<br>
infra. Couldn&#39;t we just download a image of $LTS distro like okular doe=
s?<br>
<br>
<a href=3D"https://invent.kde.org/graphics/okular/-/blob/master/.gitlab-ci.=
yml?ref_type=3Dheads#L24" rel=3D"noreferrer" target=3D"_blank">https://inve=
nt.kde.org/graphics/okular/-/blob/master/.gitlab-ci.yml?<br>
ref_type=3Dheads#L24</a></blockquote><div><br></div><div>Depends on the num=
ber of times your job runs.=C2=A0</div><div>Doing jobs that way is expensiv=
e because everytime the job runs it re-fetches every single dependency from=
 distribution archives and installs them in the container before it even st=
arts building.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><br>
<br>
&gt; Will Plasma developers keep Qt 5 installed on their local machines and=
<br>
&gt; perform appropriate testing for that with the legacy, unported applica=
tions<br>
&gt; still using Qt 5?<br>
&gt; Just having CI compile something isn&#39;t a true test as to whether i=
t works<br>
&gt; or not and risks silent bitrot taking place due to behaviour differenc=
es<br>
&gt; between Qt 5 and Qt 6.<br>
&gt; <br>
&gt; <br>
&gt; &gt;<br>
&gt; &gt; Cheers,<br>
&gt; &gt; David<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; Regards,<br>
&gt; Ben<br>
&gt;</blockquote><div><br></div><div>Regards,</div><div>Ben</div></div></di=
v>

--00000000000079ab940657e4e589--