[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-release-team
Subject: Re: CI moved to Qt 6.7 for Linux builds
From: Michael Reeves <reeves.87 () gmail ! com>
Date: 2024-04-21 16:23:38
Message-ID: 4dc8dd5f-df79-4fbc-93d4-0ab66c09460e () gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
[Attachment #4 (text/plain)]
kdiff3 will make one or two releases but needs only frameworks. This support will end in three \
months. master is qt6 only now.
Apr 20, 2024 8:35:40 PM Ben Cooksley <bcooksley@kde.org>:
> Hi all,
>
> I have just flipped the switch that has moved the CI system over to using Qt 6.7 for Linux \
> builds on our SUSE images.
> Should you see any issues with builds failing as a result of packages being missing in the \
> registry then please submit a merge request to sysadmin/ci-management to ensure that build \
> dependency is added to our seed jobs.
> I'll leave the Qt 6.6 package registry and container images in place for another week or so \
> then will schedule them for removal.
> As part of this I have also updated the list of projects with Qt 6 only master branches. Any \
> residual Qt 5 build artifacts the CI system was holding for those projects have now been \
> purged, which may impact downstream projects that depend on those projects that are still on \
> Qt 5.
> On an adjacent note, i'd also like to schedule removing CI support for release/23.08 and \
> Plasma/5.27 builds (by purging all their binaries we currently hold) for the Qt 5.15 series. \
> While checking however I note that several projects still have activity on those branches. \
> Can we please confirm whether any further releases are expected, as i'd prefer to remove \
> anything that isn't being properly maintained anymore.
> Thanks,
> Ben
[Attachment #5 (text/html)]
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<div style="font-family: sans-serif;">
<span dir="ltr" style="margin-top:0; margin-bottom:0;">kdiff3 will make one or two releases \
but needs only frameworks. This support will end in three months. master is qt6 only \
now.</span> <br>
</div>
<div>
<div dir="ltr" style="font-family: sans-serif">
<p>Apr 20, 2024 8:35:40 PM Ben Cooksley <bcooksley@kde.org>:</p>
</div>
<blockquote style="margin:0;border-left:3px solid #ccc; padding-left:10px;">
<div dir="ltr">
Hi all,
<div>
<br>
</div>
<div>
I have just flipped the switch that has moved the CI system over to using Qt 6.7 for \
Linux builds on our SUSE images. </div>
<div>
<br>
</div>
<div>
Should you see any issues with builds failing as a result of packages being missing in \
the registry then please submit a merge request to sysadmin/ci-management to ensure that \
build dependency is added to our seed jobs. </div>
<div>
<br>
</div>
<div>
I'll leave the Qt 6.6 package registry and container images in place for another week or \
so then will schedule them for removal. </div>
<div>
<br>
</div>
<div>
As part of this I have also updated the list of projects with Qt 6 only master branches. \
Any residual Qt 5 build artifacts the CI system was holding for those projects have now been \
purged, which may impact downstream projects that depend on those projects that are still on Qt \
5. </div>
<div>
<br>
</div>
<div>
On an adjacent note, i'd also like to schedule removing CI support for release/23.08 and \
Plasma/5.27 builds (by purging all their binaries we currently hold) for the Qt 5.15 \
series. </div>
<div>
<br>
</div>
<div>
While checking however I note that several projects still have activity on those \
branches. Can we please confirm whether any further releases are expected, as i'd prefer to \
remove anything that isn't being properly maintained anymore. </div>
<div>
<br>
</div>
<div>
Thanks,
</div>
<div>
Ben
</div>
</div>
</blockquote>
</div>
</body>
</html>
["signature.asc" (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic