Re: Re: Re: Re: Decommissioning Qt 5 CI
Ben Cooksley <[email protected]> Mon, 3 Aug 2026 22:09:44 +1200
| Newsgroups | gmane.comp.kde.devel.core,gmane.comp.kde.devel.general,gmane.comp.kde.devel.plasma |
|---|---|
| Message-ID | <CA+XidOFMw8rWMMuZveOjrDxEC+ZOVj+eGCTQxNdw3P3-mygSVQ@mail.gmail.com> |
--00000000000084368e065821bd62 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Aug 1, 2026 at 1:18=E2=80=AFAM David Redondo <[email protected]>= wrote: > Am Freitag, 31. Juli 2026, 11:34 schrieb Ben Cooksley: > > On Fri, Jul 31, 2026 at 9:15=E2=80=AFPM David Redondo <kde@david-redond= o.de> > 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-re= dondo.de> > > > wrote: > > > > > > > [Snip] > > > > > > > > So the Plasma developers want to keep supporting Qt 5 for essential= ly > > > > eternity and never drop support for it? > > > > > > > > At what point do you stop, or do you just keep continuing to mainta= in > > > > 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_t= ype=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. > > > > I've typed it up for breeze here: > https://invent.kde.org/plasma/breeze/-/merge_requests/630 > job is here: > https://invent.kde.org/plasma/breeze/-/jobs/4788674 > > Because of the inclusion of all our default rules, it runs only when > triggered manually > like all the other Plasma build jobs. That job will "get the job done" yes. If there is a significant amount of activity in the Breeze repository then we may need to look at something else, but hopefully this all becomes unnecessary and can be dropped in 6 months anyway. Cheers, Ben > > > > > > > > > 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 > works > > > > or not and risks silent bitrot taking place due to behaviour > differences > > > > between Qt 5 and Qt 6. > > > > > > > > > > > > > > > > > > Cheers, > > > > > David > > > > > > > > > > > > > > Regards, > > > > Ben > > > > > > > > > > Regards, > > Ben > > > > > > > --00000000000084368e065821bd62 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 Sat, Aug 1, 2026 at 1:18=E2=80=AFAM David Redondo <<a href=3D"mai= lto:[email protected]">[email protected]</a>> 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 Freitag, 31. Juli 2026, 11:34 schrieb Ben Cooksle= y:<br> > On Fri, Jul 31, 2026 at 9:15=E2=80=AFPM David Redondo <<a href=3D"m= ailto:[email protected]" target=3D"_blank">[email protected]</a>> = wrote:<br> > <br> > > Am Donnerstag, 30. Juli 2026, 20:53 schrieb Ben Cooksley:<br> > > > On Fri, Jul 31, 2026 at 3:47=E2=80=AFAM David Redondo <<a= href=3D"mailto:[email protected]" target=3D"_blank">[email protected]= e</a>><br> > > wrote:<br> > > ><br> > > [Snip]<br> > > ><br> > > > So the Plasma developers want to keep supporting Qt 5 for es= sentially<br> > > > eternity and never drop support for it?<br> > > ><br> > > > At what point do you stop, or do you just keep continuing to= maintain<br> > > > compatibility because one distribution doesn't want to d= rop<br> > > > $unmaintainedQt5App?<br> > ><br> > > (readding dropped lists)<br> > ><br> > > I dont't know the concrete point in time=C2=A0 but=C2=A0 give= n that there are some<br> > > big<br> > > applications on still on Qt5 I would say it's too early now.<= br> > ><br> > <br> > Please quantify that and list the applications you consider "big&= quot; that need<br> > to have ported before this can be abandoned.<br> > <br> > <br> > ><br> > > Btw Plasma 5 dropped support of Qt4 builds of breeze and oxygen= =C2=A0 in 2020<br> > > with<br> > > 5.18, see<br> > > <a href=3D"https://mail.kde.org/pipermail/plasma-devel/2020-Janua= ry/108585.html" rel=3D"noreferrer" target=3D"_blank">https://mail.kde.org/p= ipermail/plasma-devel/2020-January/108585.html</a><br> > <br> > <br> > ><br> > > I don't think we need an image provided by sysadmin and build= kf5 on our CI<br> > > infra. Couldn't we just download a image of $LTS distro like = okular does?<br> > ><br> > > <a href=3D"https://invent.kde.org/graphics/okular/-/blob/master/.= gitlab-ci.yml" rel=3D"noreferrer" target=3D"_blank">https://invent.kde.org/= graphics/okular/-/blob/master/.gitlab-ci.yml</a>?<br> > > ref_type=3Dheads#L24<br> > > <<a href=3D"https://invent.kde.org/graphics/okular/-/blob/mast= er/.gitlab-ci.yml?ref_type=3Dheads#L24" rel=3D"noreferrer" target=3D"_blank= ">https://invent.kde.org/graphics/okular/-/blob/master/.gitlab-ci.yml?ref_t= ype=3Dheads#L24</a>><br> > <br> > <br> > Depends on the number of times your job runs.<br> > Doing jobs that way is expensive because everytime the job runs it<br> > re-fetches every single dependency from distribution archives and inst= alls<br> > them in the container before it even starts building.<br> > <br> <br> I've typed it up for breeze here:<br> <a href=3D"https://invent.kde.org/plasma/breeze/-/merge_requests/630" rel= =3D"noreferrer" target=3D"_blank">https://invent.kde.org/plasma/breeze/-/me= rge_requests/630</a><br> job is here:<br> <a href=3D"https://invent.kde.org/plasma/breeze/-/jobs/4788674" rel=3D"nore= ferrer" target=3D"_blank">https://invent.kde.org/plasma/breeze/-/jobs/47886= 74</a><br> <br> Because of the inclusion of all our default rules, it runs only when trigge= red manually<br> like all the other Plasma build jobs.</blockquote><div><br></div><div>That = job will "get the job done" yes.</div><div><br></div><div>If ther= e is a significant amount of activity in the Breeze repository then we may = need to look at something else, but hopefully this all becomes unnecessary = and can be dropped in 6 months anyway.</div><div><br></div><div>Cheers,</di= v><div>Ben</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D= "margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le= ft:1ex"> <br> <br> > ><br> > > > Will Plasma developers keep Qt 5 installed on their local ma= chines and<br> > > > perform appropriate testing for that with the legacy, unport= ed<br> > > applications<br> > > > still using Qt 5?<br> > > > Just having CI compile something isn't a true test as to= whether it works<br> > > > or not and risks silent bitrot taking place due to behaviour= differences<br> > > > between Qt 5 and Qt 6.<br> > > ><br> > > ><br> > > > ><br> > > > > Cheers,<br> > > > > David<br> > > > ><br> > > > ><br> > > > Regards,<br> > > > Ben<br> > > ><br> > <br> > <br> > Regards,<br> > Ben<br> > <br> <br> <br> <br> <br> </blockquote></div></div> --00000000000084368e065821bd62--