From bcooksley at kde.org  Fri May  1 11:02:20 2026
From: bcooksley at kde.org (Ben Cooksley)
Date: Fri, 1 May 2026 22:02:20 +1200
Subject: CI Outages
Message-ID: <CA+XidOG-1ZoXuAboB54sPOffLakbksuqu1SbytbbMNy2PrAcbg@mail.gmail.com>

Hi all,

Over the past 48 hours or so we've had a series of two unfortunate
incidents that have significantly degraded the CI system.

The first part of this took place approximately 36 hours ago, when an
admin, in response to the announcement of the https://copy.fail/ Linux
kernel exploit, installed updates on one or more of our VM Runners. The
unfortunate side effect of this is that it also installed updates for
gitlab-runner and upgraded it to a newer version. As part of it's work,
Gitlab Runner requires the assistance of a helper binary within the VM, and
this helper should ideally be the same version as is deployed on the VM
runner hosts, or at the very least be a newer version.

In the case of this update, there were incompatible changes as part of
changes to how artifacts are captured, which is why we are seeing breakages
related to an unrecognised timeout parameter which is causing a complete
fatal failure of the CI jobs.

The images that support the majority of our CI builds (Linux - Qt 6.11, Qt
6.12 and Qt 5.15, Android, Flatpak, Snap and Appimages) have been rebuilt
to include the newer Gitlab Runner helper and those builds should now be
functional again.
Custom VM images utilised by Yocto, Buildstream, Neon and KDE Linux have
also been rebuilt and should also be functional again.

Windows builds require a replacement base image as the Gitlab Runner helper
is burned into the base image - and that is in the process of being
uploaded currently.
Once uploaded, i'll rebuild the image that supports both general Windows CI
and Craft builds which will restore those builds to working order as well.

For FreeBSD, we will need our custom package repository updated to include
the newer Gitlab Runner helper.
This has been requested and should be completed in the next few days so
those builds will remain broken for a bit longer i'm afraid.

The second incident involved a service outage of the builder that supports
Docker based jobs. This was caused by hoster maintenance related to the SAN
that supports those hosts, and also caused service disruptions to all
Notary Service operations, WebSVN and Sentry.
This outage impacted us for approximately 12 hours and has now been
corrected with all services fully returned to normal.

Apologies for the disruption caused by these incidents, it is most
regrettable - and in the case of the issue affecting VM builds - completely
avoidable.

Please let me know if you have any questions on the above.

Many thanks,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260501/b6097dea/attachment.htm>

From nicolas.fella at gmx.de  Fri May  1 21:43:08 2026
From: nicolas.fella at gmx.de (Nicolas Fella)
Date: Fri, 1 May 2026 22:43:08 +0200
Subject: Frameworks 6.26 tars available
Message-ID: <08fc3f8b-851c-47e8-8816-a34a71a62105@gmx.de>

Hi,

Frameworks 6.26 tars are now available for packagers.

Cheers

Nico
-------------- next part --------------
A non-text attachment was scrubbed...
Name: changelog.txt
Type: text/markdown
Size: 10313 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260501/58d3edd9/attachment-0001.md>
-------------- next part --------------
attica;master;aef3c6951afb0c5a850957bcfdafdc129f442b5b;attica-6.26.0.tar.xz;eb2d3d2d8b12c2ab4d192c4ae6f07b0188a40aa002b3056db6369b47b2f9df96
baloo;master;b7a557afe4f6b37c19c9179394a5f1d92c44e3d3;baloo-6.26.0.tar.xz;702f5b868aaef48153c6c3828111b3b335403079491a8f37043ebd89c6995b30
bluez-qt;master;42c6c45f2018716d45e4d189854b5d7cd884eb7e;bluez-qt-6.26.0.tar.xz;ebeb301eaeb6ec6729b27969556839165ba582ebe242b42cde71c8faa80d63df
breeze-icons;master;872cc3cc073f857e2160105216488585e340d314;breeze-icons-6.26.0.tar.xz;4e123fac511dfab2b7c505857849a5cecfac2ce6194e3230c51ceec31676b06e
extra-cmake-modules;master;a1dac86d6c848473d840b748b82694ef6916a3ca;extra-cmake-modules-6.26.0.tar.xz;f4e10d9d45aafb5273e996196040f4e420f0bc4071c208282aae94d9ad8e1743
frameworkintegration;master;a732ffb3859c1214c1d90385231dc48ae51183e4;frameworkintegration-6.26.0.tar.xz;84ebbad39b559e271bcec4817eba9124903ca660ad4f5c3f73f21a5f4a32062d
kapidox;master;b1c65f846d3263e529fcd8c1a82fea4068628ead;kapidox-6.26.0.tar.xz;6def21600efa777aedd8eac97664e0e3d55fb2dc0898559e6c7bbafda87e16ef
karchive;master;14a16c7568277389d211b9ded6025e0f400e3dc8;karchive-6.26.0.tar.xz;a7fdf6d0b8db88d60aa52bcc87d8e00d95391a1ad39a4b2a8e9f3027b8ff4035
kauth;master;e29d60d4f37872b1c73c36dd0a86c250f8150805;kauth-6.26.0.tar.xz;e6b6562114c2cb71db6ca48fdf0ebed2df70e164c48295b35433a80b03385847
kbookmarks;master;93a31eb7c67ed8ba70b00a5263b77283a2c2202e;kbookmarks-6.26.0.tar.xz;82e8794281870686da9e7e7b5ddc0839f50b15d919357490d508faccb2635030
kcalendarcore;master;9143b9e64c787b8f22430c11bab9c1b29dd2019b;kcalendarcore-6.26.0.tar.xz;386be0eee392d8432b6b7fafd3dead95dd1fc74f81790928c580f81e6222a17c
kcmutils;master;1ffa3b5e5f9de44bb49c8c6a17664c43ee46431d;kcmutils-6.26.0.tar.xz;6d0810649b71528124cdf9dbdeb8b3c6c6d31d787325ca3e4a20c536ecbdf2d9
kcodecs;master;90bc6c5db860fa715fd4cf2f3b35fb49986fac39;kcodecs-6.26.0.tar.xz;ee1fe3bd8bcd93a84d44186a5fc50395b6bf43dd2bf8972338a7aad72aa0bcb4
kcolorscheme;master;df727793a1673f04f69d51dbbaff0c7915d3896c;kcolorscheme-6.26.0.tar.xz;74149a0379bd8bf6590d3c1f7f8c503665e0f3adafc2adbd44fc6bb764c969f1
kcompletion;master;3bcc8d95c960c71cea26737088b4aae8332547f6;kcompletion-6.26.0.tar.xz;95f71eb807e4de40ecdfe7234c9c3d844423171ac52588aecca642f78d904e48
kconfig;master;320c75b97892aeef45b947f78f46a461fe42a38d;kconfig-6.26.0.tar.xz;8bb5aa918d8e60ec140a33db3c329414d2319dc97a1644b368da5576125c92b5
kconfigwidgets;master;0307ea844f9933a9a29cb8e34e777b3ae24a07ae;kconfigwidgets-6.26.0.tar.xz;3babcef22aea293fad0db65fcdbf76eb4ac9077bc758ee8daec108090242ea3c
kcontacts;master;08b02bd326cf151f918b768a407be5f5b8d57523;kcontacts-6.26.0.tar.xz;dce9af34050fcf09c8b4ece6df5a0abedbaf02fe85039fc371c5e11e91443cf0
kcoreaddons;master;799c32965cc502ca72815b23e2642f5ba277736d;kcoreaddons-6.26.0.tar.xz;92fdbfab68e52d9eacf44a992f01cb364d6395c24441e2fd47dd48a23b3281f6
kcrash;master;411aa2ed63a881d5ade82331fbf90f301f3386ce;kcrash-6.26.0.tar.xz;d05d93863a745ce0d4ab8ccff684a84a813ee4cbcc68c9c7a5175107b107e931
kdav;master;30632fbec822b82ad6127df59b0d82b16c7a6523;kdav-6.26.0.tar.xz;7535b2b9a6eb35e5b539de780f2d2b84668eb97eec3b7a6cf14d91fbe6bedfec
kdbusaddons;master;076bb542e5dbe36c26aaaf6b57c88574ef5bfe3d;kdbusaddons-6.26.0.tar.xz;894bb2e032c6f6d9b4a58b8b24678692a9f4e70e953ff4dabda2ed4e9b5431e2
kdeclarative;master;23ab14a1e34671956172361ae68fd9d92df90e5f;kdeclarative-6.26.0.tar.xz;9a464e560e436cd3a626ca6aab894f414c6212d2de8b9c5a8eda33be213e00d8
kded;master;0a508287490b6e6f3062e2624678463090de202f;kded-6.26.0.tar.xz;4265d1162cbd7febf16d103bf1bd9fab858fa3f54f52797ed0938436bee347af
kdesu;master;463b015e5adf4d667dd975cfbdf6d8364cb3fd26;kdesu-6.26.0.tar.xz;37df33a1236850b6bebd773a1aeab56ca597e347432924ca5855369337d4be24
kdnssd;master;c35cedb33d03c3073212b5ddb1dacd13a97d6c4c;kdnssd-6.26.0.tar.xz;8439daed9c4b942a74393daf23c8d97fdaabd81b93dc347f91bbb45a2bf85248
kdoctools;master;6645649958326fac6d879626ff5729604ef25342;kdoctools-6.26.0.tar.xz;3fbea5de215076130007f3c18e16b870774ffa4fc85ddace201ac020d0245fb6
kfilemetadata;master;18349cefb4afcff2714f093408dfdd845e974267;kfilemetadata-6.26.0.tar.xz;f75942b9a3d1be0b0910cd50a22c3c432ededdc506858c8d5511ddf5498051f2
kglobalaccel;master;3ee8470c3ac2e060f53fe4c6d7d14fa7ab0304e0;kglobalaccel-6.26.0.tar.xz;3f19d22d143577e5ddcc883170fe19a56f8f65766e41c4f9c011c4dfbde17a61
kguiaddons;master;19d657c78f869258b445f3af74983e470dff46ba;kguiaddons-6.26.0.tar.xz;8375342f852104f36fd72a6870eb9795183af4516592cd6fa73445ea6b813172
kholidays;master;b0f6aaeccbaf9e49aa586463cbf1ecfb88a6b6c9;kholidays-6.26.0.tar.xz;fc4f46cb5bb8e4766f550fe1a8b401731d797fcf6afa7cb53679048c215a60be
ki18n;master;be6d61539b251ae8f70b64a6528098426dba2af6;ki18n-6.26.0.tar.xz;484aad486bfafef6c86d8d5b26529258e67c74c96250c1ac212ddf568448c7c0
kiconthemes;master;668d7a3d3b088bbf1073ccfcbf7ca3e6b40ece32;kiconthemes-6.26.0.tar.xz;ed6c0c0bfed517dd5b6462d9b1c84ebe7bc99c7a75214921b5978f086df8653d
kidletime;master;45ec0921cfe558b686c14c804555f2515b0503ff;kidletime-6.26.0.tar.xz;f0efd67ee0e5b5eb9200e924e9478c1ecb179b4a38e0cf125b377e7fa373ef07
kimageformats;master;84f28e8bc9faecbae29e7c32c91c6f8902f2276b;kimageformats-6.26.0.tar.xz;c192552ee1831fd5e09af4e3633bb24726dfb4031170c4285024683bedaf9972
kio;master;caf323e0f314ee28b8a9cc1a6cc9fa18a6eeef16;kio-6.26.0.tar.xz;567f64db9766986b5535d884a5db30203685c33e67f56892bceff30e1bd5cc8a
kirigami;master;dada4e888b216b297e5c65e44f7a18a95183cbbc;kirigami-6.26.0.tar.xz;b268785b271198acec7fe4b6177eafdee890e180245c7168916da3ccff1425ff
kitemmodels;master;1a580ef218d8b71f7432c591880371b0b197680a;kitemmodels-6.26.0.tar.xz;a996201062ff7d21f9db972debc2d9615762ddb0fd9da069a42b7fd7bba1e61d
kitemviews;master;e423e89d213c5cc0a4ab1eb910f2f2d923f2adb2;kitemviews-6.26.0.tar.xz;e76cc9d7561d0aae22b07a77552fbcddf61c8066bac5cfac9958ac065b617e74
kjobwidgets;master;90db0d70c33a918ae580ab6ffe502c6683d6f570;kjobwidgets-6.26.0.tar.xz;8057b7bd132cc2b469ac406f95ba22bc3cfc240c1031485f19fa072ab942f71e
knewstuff;master;3b47aebf3df8e60324921f994bee10f7ff891560;knewstuff-6.26.0.tar.xz;94ef39077ba53a72f4e555b6f94a2762cba79730619cb80a31c5435642ebe1aa
knotifications;master;9c3cb2911c88006f844780efda67f5507128491d;knotifications-6.26.0.tar.xz;2033a798856a9d2776e6e4cef6f3eb3bc24b938c0d00b06b2f6e71be44e1446a
knotifyconfig;master;3e15f6ffb17232d85d05198e13443325462c7755;knotifyconfig-6.26.0.tar.xz;062e22f48a1da485d42ef56b37db1fc502f5f9305871483627d218f357560a28
kpackage;master;3f0f9d09c22154c741198add3ca04b487c761e8b;kpackage-6.26.0.tar.xz;313cda4a335ecdb67bb8e2fcc15bdeb5970db17d5597282ca655bf97a98abab5
kparts;master;a534217afb47501a3e5918cccd66bab12e1f84c5;kparts-6.26.0.tar.xz;049c2cf048b4cbbffe0bea9357bd9ab53b8be672ba509b2bb058f764d21b3f5b
kpeople;master;fe446b709192cada84e967c6d43d0b26fd58e27c;kpeople-6.26.0.tar.xz;bd1092cd9900d0ee3b3d08d0971e669a82d1a11c9bec6e2322d713b59191b873
kplotting;master;bedbbe055323bf89094519679dff1c346bb8418d;kplotting-6.26.0.tar.xz;bb120f446e6bfc376129e03663e4b3b9e7146abc948ccc68da19187840f9f181
kpty;master;a88ed97bede73ed6dd7239a29d6f9a23b5f1fd9d;kpty-6.26.0.tar.xz;7613c26cfaa7465a2fe28a22762ceb38266414e7f4a94a127c09dc0628625553
kquickcharts;master;339e5f19dfbfe89cf69b5ea85f162a657eec7468;kquickcharts-6.26.0.tar.xz;ae3e0784a2a2d1396cb751cc61f43a567e066d6434971246b1a18365481a1b52
krunner;master;40908a96309a57299367d2b3b9834c2392f6f4d2;krunner-6.26.0.tar.xz;3519c7fe170be1359a4c38dd5269de64c0208ccfeb950661002ddfa4e92f2bf0
kservice;master;e422dcdb85b369c04fac849f58e15d788d403eb4;kservice-6.26.0.tar.xz;f8528524ccafb6a495962dd3260c442377920169f1c444f11657ea42558a53b6
kstatusnotifieritem;master;fb56832ebcff866cd817728e86a2f831745ac9f3;kstatusnotifieritem-6.26.0.tar.xz;898914c94820f99889d879f33cabbb5fbe7b9f4e24a6a1d9a9b4439489bc3266
ksvg;master;fac8d2fc6753e0690ca415a32f0429e44d6a4695;ksvg-6.26.0.tar.xz;f3a7412e227d13b1cafec91c1b58dd3f86980abefc08b2535b46bef362b4c07e
ktexteditor;master;163ad01d31c7a7e5190bd9dc7187d91e08bf55c3;ktexteditor-6.26.0.tar.xz;ec7bc094f93d514b5f675ae95c274dd24acc47769d971606d8708cc88f811341
ktexttemplate;master;7eabf503d7a206d672425c49e84a0f92c3ed31d6;ktexttemplate-6.26.0.tar.xz;8b84643c32caf58812fec5a910a1fb98865bc7f91e778af860fa98b79d0ff038
ktextwidgets;master;2d8f56b0749328924d56a953f8c7717f14bb264a;ktextwidgets-6.26.0.tar.xz;6511f9909f90fac951e2873a44dd451b8ac71d38085a62c65a6fb5028e62d84d
kunitconversion;master;3d30c3a00260fe0fa70ce1d1889ff41657cc05f5;kunitconversion-6.26.0.tar.xz;94404453011eec373f858ef4a58091d24fbadbb90f96bbbf470c098646d9675e
kuserfeedback;master;a822eff06d7c95b5502e9f6f21c39139294ccd63;kuserfeedback-6.26.0.tar.xz;6cc18dca65a24af2ac262cb9c8761991701c8081a7133487b4ec936003f3f864
kwallet;master;5c19119682c3f88f5fc31c33648c5e3bd2228f5b;kwallet-6.26.0.tar.xz;2321f8591f1f225d3d7253fae9ee61d0789db231b3eeae6a5f8a14c013531389
kwidgetsaddons;master;372bd8fa11769909d5edfd2797ff8059aedf06ab;kwidgetsaddons-6.26.0.tar.xz;65044882e30b305fe9fb20331a354cd811ca9d80b5c7f9fa722639f3334fe630
kwindowsystem;master;d701fedb310eacfd17a81e0813580750e0042b93;kwindowsystem-6.26.0.tar.xz;5f7962b7c986e77c5d25fa4f7d09cd89144b8781e57ebc37fd45eaec1961bb02
kxmlgui;master;565fe2af48a57370acd8e5260e1cb63b9ad5ca79;kxmlgui-6.26.0.tar.xz;4383855cea5a7f9a269c72dda15490b8d70c1d23d17950963937332fc5d6b7a0
modemmanager-qt;master;9cada7952c158c5571619cc709475a3bdbe52c98;modemmanager-qt-6.26.0.tar.xz;bef456ac0a5983bcc14a1580cb0d32a001241f380d901cb503613855380af3a5
networkmanager-qt;master;03cb7b0ef1ae8cb24b3e418b6ca8938dfe47be92;networkmanager-qt-6.26.0.tar.xz;a5cfed06af6156161f7fee56efe1521a6e9e26119327069f1799986f90b432e5
prison;master;5f8346bd9dd244a6dc2541cf906d129be4dbc2c5;prison-6.26.0.tar.xz;0414ddc310bca5eecfc1a6f9d4463b8a6d81894db4128ac43b4f8c1e14b73b5b
purpose;master;2976526a14272a45409d7562465f00f58a215d89;purpose-6.26.0.tar.xz;cc7b7599d1ac7ce7ed07351a35d742fac1b7e554b208a7b1c92e859b3b4add30
qqc2-desktop-style;master;a63714aa1b59d8c1b0639bab3da5063eabcfcaf8;qqc2-desktop-style-6.26.0.tar.xz;1805fa31355ff86c02158fd2b8d396fd88835d01db97d8700314c48ee3360986
solid;master;f4ee22958f3a6feee71eda3f8d63347c74c886c0;solid-6.26.0.tar.xz;85cfab9b0787f59478661140997c485fadab62cec535ffcef2953d312f736c4a
sonnet;master;331e7290fa41e116ffa2e3afdf797fe9173aea39;sonnet-6.26.0.tar.xz;3ac4e165c0b3c79eda416b754bb837292f354188a1220f2065f57f686489af25
syndication;master;d945b4198a551d99a088b1ed28a86a5d219ac1b1;syndication-6.26.0.tar.xz;6130b8bc976cb078eda34b833ecd558a156b4e6bc4cb55e57ac362cb2998ba47
syntax-highlighting;master;8a8789ca55c1209109f97a34b18e633c4240bee0;syntax-highlighting-6.26.0.tar.xz;a4e86d167cd5f3c4318584119451f891551c24cd4a0ff1f7ef95e2476a39c5ac
threadweaver;master;fd547264b6986b114cdd303352c3d946f78bc5ed;threadweaver-6.26.0.tar.xz;ad32daeafac62077590885f3abc4bcac1abbc6faeb34c20b32f6040648f7de1b

From bcooksley at kde.org  Sat May  2 19:56:10 2026
From: bcooksley at kde.org (Ben Cooksley)
Date: Sun, 3 May 2026 06:56:10 +1200
Subject: CI Outages
In-Reply-To: <CA+XidOG-1ZoXuAboB54sPOffLakbksuqu1SbytbbMNy2PrAcbg@mail.gmail.com>
References: <CA+XidOG-1ZoXuAboB54sPOffLakbksuqu1SbytbbMNy2PrAcbg@mail.gmail.com>
Message-ID: <CA+XidOEpgcCs4fPagnS5WBf768RCd2N_Yn0rY77viFgY4_8Wag@mail.gmail.com>

Hi all,

I'm happy to announce that final repairs on both Windows and FreeBSD were
completed yesterday and those builds are now fully functional again which
completes the restoration of normal CI service.

Please let us know if you see any unusual failures.

Many thanks,
Ben

On Fri, May 1, 2026 at 10:02 PM Ben Cooksley <bcooksley at kde.org> wrote:

> Hi all,
>
> Over the past 48 hours or so we've had a series of two unfortunate
> incidents that have significantly degraded the CI system.
>
> The first part of this took place approximately 36 hours ago, when an
> admin, in response to the announcement of the https://copy.fail/ Linux
> kernel exploit, installed updates on one or more of our VM Runners. The
> unfortunate side effect of this is that it also installed updates for
> gitlab-runner and upgraded it to a newer version. As part of it's work,
> Gitlab Runner requires the assistance of a helper binary within the VM, and
> this helper should ideally be the same version as is deployed on the VM
> runner hosts, or at the very least be a newer version.
>
> In the case of this update, there were incompatible changes as part of
> changes to how artifacts are captured, which is why we are seeing breakages
> related to an unrecognised timeout parameter which is causing a complete
> fatal failure of the CI jobs.
>
> The images that support the majority of our CI builds (Linux - Qt 6.11, Qt
> 6.12 and Qt 5.15, Android, Flatpak, Snap and Appimages) have been rebuilt
> to include the newer Gitlab Runner helper and those builds should now be
> functional again.
> Custom VM images utilised by Yocto, Buildstream, Neon and KDE Linux have
> also been rebuilt and should also be functional again.
>
> Windows builds require a replacement base image as the Gitlab Runner
> helper is burned into the base image - and that is in the process of being
> uploaded currently.
> Once uploaded, i'll rebuild the image that supports both general Windows
> CI and Craft builds which will restore those builds to working order as
> well.
>
> For FreeBSD, we will need our custom package repository updated to include
> the newer Gitlab Runner helper.
> This has been requested and should be completed in the next few days so
> those builds will remain broken for a bit longer i'm afraid.
>
> The second incident involved a service outage of the builder that supports
> Docker based jobs. This was caused by hoster maintenance related to the SAN
> that supports those hosts, and also caused service disruptions to all
> Notary Service operations, WebSVN and Sentry.
> This outage impacted us for approximately 12 hours and has now been
> corrected with all services fully returned to normal.
>
> Apologies for the disruption caused by these incidents, it is most
> regrettable - and in the case of the issue affecting VM builds - completely
> avoidable.
>
> Please let me know if you have any questions on the above.
>
> Many thanks,
> Ben
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260503/97c7d708/attachment.htm>

From aleixpol at kde.org  Sun May  3 16:25:19 2026
From: aleixpol at kde.org (Aleix Pol)
Date: Sun, 3 May 2026 17:25:19 +0200
Subject: CI Outages
In-Reply-To: <CA+XidOG-1ZoXuAboB54sPOffLakbksuqu1SbytbbMNy2PrAcbg@mail.gmail.com>
References: <CA+XidOG-1ZoXuAboB54sPOffLakbksuqu1SbytbbMNy2PrAcbg@mail.gmail.com>
Message-ID: <CACcA1RpnHVmmYX6ju=RLg5tGHtrXydjKmpA58XH=JCeHFg526A@mail.gmail.com>

Thanks a lot for the quick response! 👏

Aleix

On Fri, May 1, 2026 at 12:02 PM Ben Cooksley <bcooksley at kde.org> wrote:
>
> Hi all,
>
> Over the past 48 hours or so we've had a series of two unfortunate incidents that have significantly degraded the CI system.
>
> The first part of this took place approximately 36 hours ago, when an admin, in response to the announcement of the https://copy.fail/ Linux kernel exploit, installed updates on one or more of our VM Runners. The unfortunate side effect of this is that it also installed updates for gitlab-runner and upgraded it to a newer version. As part of it's work, Gitlab Runner requires the assistance of a helper binary within the VM, and this helper should ideally be the same version as is deployed on the VM runner hosts, or at the very least be a newer version.
>
> In the case of this update, there were incompatible changes as part of changes to how artifacts are captured, which is why we are seeing breakages related to an unrecognised timeout parameter which is causing a complete fatal failure of the CI jobs.
>
> The images that support the majority of our CI builds (Linux - Qt 6.11, Qt 6.12 and Qt 5.15, Android, Flatpak, Snap and Appimages) have been rebuilt to include the newer Gitlab Runner helper and those builds should now be functional again.
> Custom VM images utilised by Yocto, Buildstream, Neon and KDE Linux have also been rebuilt and should also be functional again.
>
> Windows builds require a replacement base image as the Gitlab Runner helper is burned into the base image - and that is in the process of being uploaded currently.
> Once uploaded, i'll rebuild the image that supports both general Windows CI and Craft builds which will restore those builds to working order as well.
>
> For FreeBSD, we will need our custom package repository updated to include the newer Gitlab Runner helper.
> This has been requested and should be completed in the next few days so those builds will remain broken for a bit longer i'm afraid.
>
> The second incident involved a service outage of the builder that supports Docker based jobs. This was caused by hoster maintenance related to the SAN that supports those hosts, and also caused service disruptions to all Notary Service operations, WebSVN and Sentry.
> This outage impacted us for approximately 12 hours and has now been corrected with all services fully returned to normal.
>
> Apologies for the disruption caused by these incidents, it is most regrettable - and in the case of the issue affecting VM builds - completely avoidable.
>
> Please let me know if you have any questions on the above.
>
> Many thanks,
> Ben

From prayagjain2 at gmail.com  Sun May  3 14:06:01 2026
From: prayagjain2 at gmail.com (Prayag Jain)
Date: Sun, 3 May 2026 18:36:01 +0530
Subject: Drawy 1.0.0 Release | Request for Support
Message-ID: <CAFYV=d5d6JvxN63W2ZnP7U00xKb721T6=5nQy_-D4nZ0ectBcg@mail.gmail.com>

Hi Team,

Drawy is a new KDE whiteboard application that has approached its first
release 1.0.0. I'm writing this email because of an oversight from my end
during the release process.

During the release process, I used releaseme
<https://invent.kde.org/sdk/releaseme> to create a tag in the git
repository on invent <https://invent.kde.org/graphics/drawy> and a tarball
which was just uploaded to download.kde.org a few hours ago (
https://phabricator.kde.org/T18625). I realised that I missed an important
part of the release process, which was updating the appstream metainfo
file. As a result, the uploaded tarball uses an outdated version of the
file which contains outdated description, no screenshots, no keywords, and
no release information which are required by software repositories like
FlatHub.

I deeply regret this oversight and would like to understand how I can
proceed from here. Should I create a new tag *1.0.1* and upload a new
tarball with the updated files or would it be better to request for the
removal of the currently uploaded tarball, delete the tag, and proceed
again? The first option seems like the way to go but I'm still not sure
because *1.0.0* has not been announced yet.

I deeply apologize for the inconvenience caused and will appreciate your
support as I'm still figuring some things out.

Thanks and Regards,
Prayag Jain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260503/e86bdd93/attachment.htm>

From julius.kuenzel at kde.org  Mon May  4 11:17:08 2026
From: julius.kuenzel at kde.org (=?UTF-8?Q?Julius_K=C3=BCnzel?=)
Date: Mon, 4 May 2026 12:17:08 +0200
Subject: Drawy 1.0.0 Release | Request for Support
In-Reply-To: <CAFYV=d5d6JvxN63W2ZnP7U00xKb721T6=5nQy_-D4nZ0ectBcg@mail.gmail.com>
References: <CAFYV=d5d6JvxN63W2ZnP7U00xKb721T6=5nQy_-D4nZ0ectBcg@mail.gmail.com>
Message-ID: <f2f0c6f7-32c2-4ec3-bc7c-d959bbf41cc2@kde.org>

Hi Prayag,

it is not a big deal, others did the some mistake before. Best would be to do a 1.0.1 release. The metainfo file is not only relevant for Flathub, but other consumers too. As soon as files are uploaded to download.k.o they should not be replaced anymore.

Regards,
Julius Künzel
KDE Developer
Matrix: @jlskuz:kde.org
KDE GitLab: https://invent.kde.org/jlskuz

04.05.2026 00:29:35 Prayag Jain <prayagjain2 at gmail.com>:

> Hi Team,
> 
> Drawy is a new KDE whiteboard application that has approached its first release 1.0.0. I'm writing this email because of an oversight from my end during the release process.
> 
> During the release process, I used releaseme[https://invent.kde.org/sdk/releaseme] to create a tag in the git repository on invent[https://invent.kde.org/graphics/drawy] and a tarball which was just uploaded to download.kde.org[http://download.kde.org] a few hours ago (https://phabricator.kde.org/T18625). I realised that I missed an important part of the release process, which was updating the appstream metainfo file. As a result, the uploaded tarball uses an outdated version of the file which contains outdated description, no screenshots, no keywords, and no release information which are required by software repositories like FlatHub.
> 
> I deeply regret this oversight and would like to understand how I can proceed from here. Should I create a new tag *1.0.1* and upload a new tarball with the updated files or would it be better to request for the removal of the currently uploaded tarball, delete the tag, and proceed again? The first option seems like the way to go but I'm still not sure because *1.0.0* has not been announced yet.
> 
> I deeply apologize for the inconvenience caused and will appreciate your support as I'm still figuring some things out.
> 
> Thanks and Regards,
> Prayag Jain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260504/02e41bff/attachment.htm>

From thb at net-bembel.de  Mon May  4 12:03:00 2026
From: thb at net-bembel.de (Thomas Baumgart)
Date: Mon, 04 May 2026 13:03:00 +0200
Subject: Drawy 1.0.0 Release | Request for Support
In-Reply-To: <f2f0c6f7-32c2-4ec3-bc7c-d959bbf41cc2@kde.org>
References: <CAFYV=d5d6JvxN63W2ZnP7U00xKb721T6=5nQy_-D4nZ0ectBcg@mail.gmail.com>
 <f2f0c6f7-32c2-4ec3-bc7c-d959bbf41cc2@kde.org>
Message-ID: <2286226.Icojqenx9y@sy-346-nb>

All,

is it still the case that the information for apps.kde.org is
drawn from the master branch only? In that case, don't forget
to update the master branch of the metainfo file as well.

Thomas

On Montag, 4. Mai 2026 12:17:08 Mitteleuropäische Sommerzeit Julius Künzel wrote:

> Hi Prayag,
> 
> it is not a big deal, others did the some mistake before. Best would be to do a 1.0.1 release. The metainfo file is not only relevant for Flathub, but other consumers too. As soon as files are uploaded to download.k.o they should not be replaced anymore.
> 
> Regards,
> Julius Künzel
> KDE Developer
> Matrix: @jlskuz:kde.org
> KDE GitLab: https://invent.kde.org/jlskuz
> 
> 04.05.2026 00:29:35 Prayag Jain <prayagjain2 at gmail.com>:
> 
> > Hi Team,
> > 
> > Drawy is a new KDE whiteboard application that has approached its first release 1.0.0. I'm writing this email because of an oversight from my end during the release process.
> > 
> > During the release process, I used releaseme[https://invent.kde.org/sdk/releaseme] to create a tag in the git repository on invent[https://invent.kde.org/graphics/drawy] and a tarball which was just uploaded to download.kde.org[http://download.kde.org] a few hours ago (https://phabricator.kde.org/T18625). I realised that I missed an important part of the release process, which was updating the appstream metainfo file. As a result, the uploaded tarball uses an outdated version of the file which contains outdated description, no screenshots, no keywords, and no release information which are required by software repositories like FlatHub.
> > 
> > I deeply regret this oversight and would like to understand how I can proceed from here. Should I create a new tag *1.0.1* and upload a new tarball with the updated files or would it be better to request for the removal of the currently uploaded tarball, delete the tag, and proceed again? The first option seems like the way to go but I'm still not sure because *1.0.0* has not been announced yet.
> > 
> > I deeply apologize for the inconvenience caused and will appreciate your support as I'm still figuring some things out.
> > 
> > Thanks and Regards,
> > Prayag Jain
> 

-- 

Regards

Thomas Baumgart

-------------------------------------------------------------
The Unix Guru's View of Sex:
============================
# unzip; strip; touch; finger; mount; fsck; more; yes; umount; sleep
-------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 868 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260504/9b633d3f/attachment.sig>

From aacid at kde.org  Mon May  4 14:18:41 2026
From: aacid at kde.org (Albert Astals Cid)
Date: Mon, 04 May 2026 15:18:41 +0200
Subject: Drawy 1.0.0 Release | Request for Support
In-Reply-To: <2286226.Icojqenx9y@sy-346-nb>
References: <CAFYV=d5d6JvxN63W2ZnP7U00xKb721T6=5nQy_-D4nZ0ectBcg@mail.gmail.com>
 <f2f0c6f7-32c2-4ec3-bc7c-d959bbf41cc2@kde.org> <2286226.Icojqenx9y@sy-346-nb>
Message-ID: <71F0t9ZjT7OVWKLEbNjVQA@kde.org>

El dilluns, 4 de maig del 2026, a les 13:03:00 (Hora d’estiu d’Europa 
central), Thomas Baumgart va escriure:
> All,
> 
> is it still the case that the information for apps.kde.org is
> drawn from the master branch only? 

It is.

Cheers,
  Albert

> In that case, don't forget
> to update the master branch of the metainfo file as well.
> 
> Thomas
> 
> On Montag, 4. Mai 2026 12:17:08 Mitteleuropäische Sommerzeit Julius Künzel 
wrote:
> > Hi Prayag,
> > 
> > it is not a big deal, others did the some mistake before. Best would be to
> > do a 1.0.1 release. The metainfo file is not only relevant for Flathub,
> > but other consumers too. As soon as files are uploaded to download.k.o
> > they should not be replaced anymore.
> > 
> > Regards,
> > Julius Künzel
> > KDE Developer
> > Matrix: @jlskuz:kde.org
> > KDE GitLab: https://invent.kde.org/jlskuz
> > 
> > 04.05.2026 00:29:35 Prayag Jain <prayagjain2 at gmail.com>:
> > > Hi Team,
> > > 
> > > Drawy is a new KDE whiteboard application that has approached its first
> > > release 1.0.0. I'm writing this email because of an oversight from my
> > > end during the release process.
> > > 
> > > During the release process, I used
> > > releaseme[https://invent.kde.org/sdk/releaseme] to create a tag in the
> > > git repository on invent[https://invent.kde.org/graphics/drawy] and a
> > > tarball which was just uploaded to
> > > download.kde.org[http://download.kde.org] a few hours ago
> > > (https://phabricator.kde.org/T18625). I realised that I missed an
> > > important part of the release process, which was updating the appstream
> > > metainfo file. As a result, the uploaded tarball uses an outdated
> > > version of the file which contains outdated description, no
> > > screenshots, no keywords, and no release information which are required
> > > by software repositories like FlatHub.
> > > 
> > > I deeply regret this oversight and would like to understand how I can
> > > proceed from here. Should I create a new tag *1.0.1* and upload a new
> > > tarball with the updated files or would it be better to request for the
> > > removal of the currently uploaded tarball, delete the tag, and proceed
> > > again? The first option seems like the way to go but I'm still not sure
> > > because *1.0.0* has not been announced yet.
> > > 
> > > I deeply apologize for the inconvenience caused and will appreciate your
> > > support as I'm still figuring some things out.
> > > 
> > > Thanks and Regards,
> > > Prayag Jain





From aacid at kde.org  Mon May  4 22:28:21 2026
From: aacid at kde.org (Albert Astals Cid)
Date: Mon, 04 May 2026 23:28:21 +0200
Subject: KDE Gear 26.08 proposed schedule
In-Reply-To: <cfc2f7c0-3ff8-4c2f-88fc-bca7029d6d1c@kde.org>
References: <5091145.31r3eYUQgx@xps15> <QmI9OsjtRKOobWir4VB-WQ@kde.org>
 <cfc2f7c0-3ff8-4c2f-88fc-bca7029d6d1c@kde.org>
Message-ID: <Z6eGPmsHR-6Gt8ORvgIusA@kde.org>

El dijous, 23 d’abril del 2026, a les 13:30:12 (Hora d’estiu d’Europa 
central), Heiko Becker va escriure:
> On Thursday, 23 April 2026 00:17:53 CEST, Albert Astals Cid wrote:
> >> On Monday, 20 April 2026 23:47:28 CEST, Albert Astals Cid wrote: ...
> > 
> > I think I got a bit confused with the dates :D
> > 
> > Can you propose the dates that would work for you?
> 
> Sure :) If we keep the weekdays:
> 
> August 13, 2026, 23:59 UTC: 26.08 tarball creation
> August 14, 2026: 26.08 packages released to packagers
> August 20, 2026: 26.08 Release
> 
> In this case we would have three weeks between RC and final tarball
> creation, which seems a bit long. So I would propose to move beta and RC a
> week later too, if that works for you.

It actually works a bit better.

> 
> The one week less between .0 and .1 seems like a nice thing, to get fixes a
> tad faster to users, so I'd keep that as it is.

Ok, updated the wiki with what i think we said, please check :D

Cheers,
  Albert

> 
> Regards,
> Heiko





From heiko.becker at kde.org  Tue May  5 14:20:48 2026
From: heiko.becker at kde.org (Heiko Becker)
Date: Tue, 05 May 2026 15:20:48 +0200
Subject: KDE Gear 26.04.1 packages available for packagers
Message-ID: <e2812677-2063-4300-9c88-5952dacf7b37@kde.org>

Hello packagers,

tarballs are available at the usual place under 
"stable/release-service/26.04.1".

Please report any issues, release is planned for Thursday, the 7th of May.

The checksums and included commits can be found at 
https://invent.kde.org/-/snippets/3786

The tars are signed with my public key with the follow fingerprint 
D81C0CB38EB725EF6691C385BB463350D6EF31EF.

Thanks for packaging,
Heiko



From arojas at archlinux.org  Wed May  6 07:29:10 2026
From: arojas at archlinux.org (Antonio Rojas)
Date: Wed, 06 May 2026 08:29:10 +0200
Subject: KDE Gear 26.04.1 packages available for packagers
In-Reply-To: <e2812677-2063-4300-9c88-5952dacf7b37@kde.org>
References: <e2812677-2063-4300-9c88-5952dacf7b37@kde.org>
Message-ID: <pb6XZVZcSzyqdlG3gpE1Bg@archlinux.org>

El martes, 5 de mayo de 2026 a las 15:20 Heiko Becker escribió:

> Hello packagers,
> 
> tarballs are available at the usual place under 
> "stable/release-service/26.04.1".
> 
> Please report any issues, release is planned for Thursday, the 7th of May.

Hi,
 Could you respin cantor to include https://invent.kde.org/education/cantor/-/commit/61d08d4d3b32301272e72e8009c1f5f0d0d903e3 ?

Thanks



From heiko.becker at kde.org  Wed May  6 22:50:34 2026
From: heiko.becker at kde.org (Heiko Becker)
Date: Wed, 06 May 2026 23:50:34 +0200
Subject: KDE Gear 26.04.1 packages available for packagers
In-Reply-To: <pb6XZVZcSzyqdlG3gpE1Bg@archlinux.org>
References: <e2812677-2063-4300-9c88-5952dacf7b37@kde.org>
 <pb6XZVZcSzyqdlG3gpE1Bg@archlinux.org>
Message-ID: <35ae6d4f-028f-485f-a398-0afc7e8608ee@kde.org>

On Wednesday, 6 May 2026 08:29:10 CEST, Antonio Rojas wrote:
> El martes, 5 de mayo de 2026 a las 15:20 Heiko Becker escribió:
>
>  Could you respin cantor to include 
> https://invent.kde.org/education/cantor/-/commit/61d08d4d3b32301272e72e8009c1f5f0d0d903e3 
> ?

Yes!

cantor release/26.04
61d08d4d3b32301272e72e8009c1f5f0d0d903e3
ce835577baaad9acf438fefd69ffd8da406d9c3f148abee467270f6d8cf96670  
sources/cantor-26.04.1.tar.xz



From heiko.becker at kde.org  Thu May  7 13:12:20 2026
From: heiko.becker at kde.org (Heiko Becker)
Date: Thu, 07 May 2026 14:12:20 +0200
Subject: KDE Gear 26.04.1 released
Message-ID: <9c1aa766-7af5-4743-b974-dcc69f428efc@kde.org>

Thursday, 7 May 2026. Over 180 individual programs plus dozens of 
programmer libraries and feature plugins are released simultaneously as 
part of KDE Gear.

Today they all get new bugfix source releases with updated translations, 
including:

* akonadi: Fix crash in EntityTreeView when selecting multiple items
* kcachegrind: Don't read out of bounds (fixes bug #519280)
* konsole: Prevent QTabBar from closing tabs on middle mouse clicks (fixes 
bug #515014)

The full changelog can be found at 
https://kde.org/announcements/changelogs/gear/26.04.1/ and checksums at 
https://kde.org/info/releases-26.04.1/

The released code has been GPG-signed using the following key: 
https://keys.openpgp.org/search?q=D81C0CB38EB725EF6691C385BB463350D6EF31EF


From nicolas.fella at gmx.de  Fri May  8 19:15:06 2026
From: nicolas.fella at gmx.de (Nicolas Fella)
Date: Fri, 8 May 2026 20:15:06 +0200
Subject: KDE Frameworks 6.26
Message-ID: <dc20107f-e2a4-4166-929e-b620d18a7698@gmx.de>

Hi,

KDE Frameworks 6.26 is now available: 
https://kde.org/announcements/frameworks/6/6.26.0/

Cheers

Nico


From aacid at kde.org  Sat May  9 00:09:09 2026
From: aacid at kde.org (Albert Astals Cid)
Date: Sat, 09 May 2026 01:09:09 +0200
Subject: Adding KDominate to KDE Gear
In-Reply-To: <CAAQViEtQSZ9xMwEd7_KK00SiXM629zAFzTUZSykOE3JidZsLJg@mail.gmail.com>
References: <CAAQViEtQSZ9xMwEd7_KK00SiXM629zAFzTUZSykOE3JidZsLJg@mail.gmail.com>
Message-ID: <mPG3767cSP-SFpsJCjKMnw@kde.org>

El dijous, 9 d’abril del 2026, a les 9:33:41 (Hora d’estiu d’Europa central), 
Albert Vaca Cintora va escriure:
> Hello release team,
> 
> I would like KDominate [1] to be released as part of future KDE Gear
> releases.
> 
> [1] https://invent.kde.org/games/kdominate
> 
> Albert

No one disagreed in a month.

Please create a MR for release-tools like

https://invent.kde.org/sysadmin/release-tools/-/merge_requests/60

Cheers,
  Albert




From albertvaka at gmail.com  Mon May 11 21:46:31 2026
From: albertvaka at gmail.com (Albert Vaca Cintora)
Date: Mon, 11 May 2026 22:46:31 +0200
Subject: Adding KDominate to KDE Gear
In-Reply-To: <CAAQViEtQSZ9xMwEd7_KK00SiXM629zAFzTUZSykOE3JidZsLJg@mail.gmail.com>
References: <CAAQViEtQSZ9xMwEd7_KK00SiXM629zAFzTUZSykOE3JidZsLJg@mail.gmail.com>
Message-ID: <CAAQViEsPgD6-1knAMYUzdNx5xV7iY0LfcE=wmSqF8KTCc2Ubzg@mail.gmail.com>

I've opened a merge request here:
https://invent.kde.org/sysadmin/release-tools/-/merge_requests/72
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260511/27e161e6/attachment.htm>

From bshah at kde.org  Tue May 12 12:49:54 2026
From: bshah at kde.org (Bhushan Shah)
Date: Tue, 12 May 2026 17:19:54 +0530
Subject: KDE Plasma 6.6.5 is now released
Message-ID: <KvCqqIIQQp2SPcyOz0wp5g@kde.org>

Hello,

KDE Plasma 6.6.5 is now released

https://kde.org/announcements/changelogs/plasma/6/6.6.4-6.6.5/

This is bugfix release in 6.6 series.

Best Regards,
Bhushan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260512/0f7b7543/attachment.sig>

From bshah at kde.org  Thu May 14 07:39:45 2026
From: bshah at kde.org (Bhushan Shah)
Date: Thu, 14 May 2026 12:09:45 +0530
Subject: cxx-rust-cssparser v1.0.0 released
Message-ID: <cWa7-HOKRaO9_9mSjjV9FQ@kde.org>

Hello,

Please find v1.0.0 release of the cxx-rust-csparser.

https://download.kde.org/stable/cxx-rust-cssparser/cxx-rust-cssparser-1.0.0.tar.xz.mirrorlist

This is required dependency for KDE Plasma 6.7.

Best Regards,
Bhushan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260514/62dd244e/attachment.sig>

From bshah at kde.org  Thu May 14 08:32:33 2026
From: bshah at kde.org (Bhushan Shah)
Date: Thu, 14 May 2026 13:02:33 +0530
Subject: plasma-wayland-protocols 1.21.0 released
Message-ID: <Hf4sJaMgQtOa7-8z13Qz-A@kde.org>

Hello,

plasma-wayland-protocols 1.21.0 is now released.

https://download.kde.org/stable/plasma-wayland-protocols/plasma-wayland-protocols-1.21.0.tar.xz.mirrorlist

Best Regards,
Bhushan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260514/7667d7a8/attachment.sig>

From bshah at kde.org  Thu May 14 11:42:34 2026
From: bshah at kde.org (Bhushan Shah)
Date: Thu, 14 May 2026 16:12:34 +0530
Subject: Plasma 6.7 beta is now released
Message-ID: <VDZrM8giSXGW3JGPIMW-tw@kde.org>

Hello all,

Please find release announcement for KDE Plasma 6.7 beta,

https://kde.org/announcements/plasma/6/6.6.90/

This release includes two new repositories,

- plasma-bigscreen
- union

Please test this release out and report bugs or issues on bugzilla.

Best Regards,
Bhushan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260514/5d2d2465/attachment.sig>

From lbeltrame at kde.org  Thu May 14 17:01:17 2026
From: lbeltrame at kde.org (Luca Beltrame)
Date: Thu, 14 May 2026 18:01:17 +0200
Subject: cxx-rust-cssparser v1.0.0 released
In-Reply-To: <cWa7-HOKRaO9_9mSjjV9FQ@kde.org>
References: <cWa7-HOKRaO9_9mSjjV9FQ@kde.org>
Message-ID: <lBQtHN13Sw6Z6IxGRYoggg@kde.org>

In data giovedì 14 maggio 2026 08:39:45 Ora legale dell’Europa centrale, 
Bhushan Shah ha scritto:

Hello Bhushan,

> Please find v1.0.0 release of the cxx-rust-csparser.

Currently (in openSUSE) this fails to build because it requires network access 
(it tries to access crates.io), and the build hosts have none. 

-- 
Luca Beltrame
GPG key ID: A29D259B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 525 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260514/cdd707ad/attachment.sig>

From aacid at kde.org  Thu May 14 17:19:13 2026
From: aacid at kde.org (Albert Astals Cid)
Date: Thu, 14 May 2026 18:19:13 +0200
Subject: KDE Gear 26.08 proposed schedule
In-Reply-To: <5091145.31r3eYUQgx@xps15>
References: <5091145.31r3eYUQgx@xps15>
Message-ID: <4d5-UAU3RmC3a9E4ClUbIg@kde.org>

El dilluns, 13 d’abril del 2026, a les 23:29:01 (Hora d’estiu d’Europa 
central), Albert Astals Cid va escriure:
> https://community.kde.org/Schedules/KDE_Gear_26.08_Schedule

It's official now :)

Cheers,
  Albert

> 
> Opinions?
> 
> Cheers,
>   Albert





From rikmills at kubuntu.org  Fri May 15 07:25:17 2026
From: rikmills at kubuntu.org (Rik Mills)
Date: Fri, 15 May 2026 07:25:17 +0100
Subject: cxx-rust-cssparser v1.0.0 released
In-Reply-To: <53kR1epmQIi2FhmYmiIpuw@kde.org>
References: <cWa7-HOKRaO9_9mSjjV9FQ@kde.org> <lBQtHN13Sw6Z6IxGRYoggg@kde.org>
 <0a062d19-e04b-42d4-bfc3-e11ee09dc627@1707.io>
 <53kR1epmQIi2FhmYmiIpuw@kde.org>
Message-ID: <54dde085-646c-477c-b8c4-7681ffb81329@kubuntu.org>

On 15/05/2026 07:06, Luca Beltrame wrote:
> In data venerdì 15 maggio 2026 03:06:41 Ora legale dell’Europa centrale, 
> Justin Zobel ha scritto:
>> Then you'll need to vendor the Rust crates like Angelfish does:
>> https://build.opensuse.org/package/show/KDE:Applications/angelfish
> 
> It's not enough even after vendoring: https://invent.kde.org/libraries/cxx-rust-cssparser/-/merge_requests/18 is also needed, and tests still try to 
> access the network (and if network acces disabled, they complain about a crate 
> missing, although it is vendored).

This is also going to be a breaking issue with K/Ubuntu and Debian,
where buildds are very strictly not allowed to access the internet.
This is essential for security and archive integrity, and it is always
highly concerning when KDE developers think it is ok to download
dependencies on the fly or access servers from what could, given the
nature of the public internet, turn out to be compromised sources.

Rik.

From christophe at krop.fr  Fri May 15 20:59:08 2026
From: christophe at krop.fr (Christophe Marin)
Date: Fri, 15 May 2026 21:59:08 +0200
Subject: Plasma 6.7 beta is now released
In-Reply-To: <VDZrM8giSXGW3JGPIMW-tw@kde.org>
References: <VDZrM8giSXGW3JGPIMW-tw@kde.org>
Message-ID: <tZWU5bCNQ8SV-jEQWlBU2Q@krop.fr>

On jeudi 14 mai 2026 12:42:34 heure d’été d’Europe centrale Bhushan Shah 
wrote:
> Hello all,
> 
> Please find release announcement for KDE Plasma 6.7 beta,
> 
> https://kde.org/announcements/plasma/6/6.6.90/
> 
> This release includes two new repositories,
> 
> - plasma-bigscreen

It has a couple license issues:
- In settingsapp/ and uvcviewer/, a couple files are just 'LicenseRef-KDE-
Accepted-GPL'

- kded/CMakeLists.txt, kcms/webapps/ui/*, components/bigscreenplugin/qml/
controls/{Dialog,DialogButtonBox}.qml are GPL-2.0-or-later OR LicenseRef-KDE-
Accepted-GPL, which doesn't make sense

- the sound files license is in sounds/plasma-bigscreen rather than in the 
LICENSE folder




From aleixpol at kde.org  Thu May 21 13:46:06 2026
From: aleixpol at kde.org (Aleix Pol)
Date: Thu, 21 May 2026 14:46:06 +0200
Subject: cxx-rust-cssparser v1.0.0 released
In-Reply-To: <54dde085-646c-477c-b8c4-7681ffb81329@kubuntu.org>
References: <cWa7-HOKRaO9_9mSjjV9FQ@kde.org> <lBQtHN13Sw6Z6IxGRYoggg@kde.org>
 <0a062d19-e04b-42d4-bfc3-e11ee09dc627@1707.io>
 <53kR1epmQIi2FhmYmiIpuw@kde.org>
 <54dde085-646c-477c-b8c4-7681ffb81329@kubuntu.org>
Message-ID: <CACcA1Ro80TK6vT60qpsWtMizjzQVgh7h434O4o+05nobu=tBFw@mail.gmail.com>

I'm a bit confused, on the flatpak runtime we also don't have internet
access when building and it has been building fine. What we do there
is to download the crates assets on the source fetching step.

This week I saw that this workflow has also been adopted on
kdeplasma-addons for Plasma 6.7, so it's better to be ready.

Best,
Aleix


On Fri, May 15, 2026 at 8:25 AM Rik Mills <rikmills at kubuntu.org> wrote:
>
> On 15/05/2026 07:06, Luca Beltrame wrote:
> > In data venerdì 15 maggio 2026 03:06:41 Ora legale dell’Europa centrale,
> > Justin Zobel ha scritto:
> >> Then you'll need to vendor the Rust crates like Angelfish does:
> >> https://build.opensuse.org/package/show/KDE:Applications/angelfish
> >
> > It's not enough even after vendoring: https://invent.kde.org/libraries/cxx-rust-cssparser/-/merge_requests/18 is also needed, and tests still try to
> > access the network (and if network acces disabled, they complain about a crate
> > missing, although it is vendored).
>
> This is also going to be a breaking issue with K/Ubuntu and Debian,
> where buildds are very strictly not allowed to access the internet.
> This is essential for security and archive integrity, and it is always
> highly concerning when KDE developers think it is ok to download
> dependencies on the fly or access servers from what could, given the
> nature of the public internet, turn out to be compromised sources.
>
> Rik.

From lbeltrame at kde.org  Thu May 21 14:16:09 2026
From: lbeltrame at kde.org (Luca Beltrame)
Date: Thu, 21 May 2026 15:16:09 +0200
Subject: cxx-rust-cssparser v1.0.0 released
In-Reply-To: <CACcA1Ro80TK6vT60qpsWtMizjzQVgh7h434O4o+05nobu=tBFw@mail.gmail.com>
References: <cWa7-HOKRaO9_9mSjjV9FQ@kde.org>
 <54dde085-646c-477c-b8c4-7681ffb81329@kubuntu.org>
 <CACcA1Ro80TK6vT60qpsWtMizjzQVgh7h434O4o+05nobu=tBFw@mail.gmail.com>
Message-ID: <8siTkp52Rm6iAr4ZCQhtGA@kde.org>

In data giovedì 21 maggio 2026 14:46:06 Ora legale dell’Europa centrale, Aleix 
Pol ha scritto:

Hello Aleix,

> access when building and it has been building fine. What we do there
> is to download the crates assets on the source fetching step.

It does, but if you use corrosion, it still tries to download crates off the 
net for some reason (as if they weren't found).




From bshah at kde.org  Thu May 28 13:58:39 2026
From: bshah at kde.org (Bhushan Shah)
Date: Thu, 28 May 2026 18:28:39 +0530
Subject: Plasma 6.6.91 - Second Plasma 6.7 Beta
Message-ID: <PPsAbmdlTdWGAjw8eMQfwA@kde.org>

Hello

Plasma 6.7 beta 2 is now released

https://kde.org/announcements/plasma/6/6.6.91/

Best Regards,
Bhushan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/release-team/attachments/20260528/540d822d/attachment.sig>

From aacid at kde.org  Sun May 31 10:14:32 2026
From: aacid at kde.org (Albert Astals Cid)
Date: Sun, 31 May 2026 11:14:32 +0200
Subject: please set a new release of oxygen icons for the next framework
 6.27
In-Reply-To: <iAVJdiK_E4oqqCCGYmbbQEcoTNf5GJjW6In6jeWNJ88P0d8SBi7061BV4FdbReS8WdZq2Li1jaw2LvsiCpaz-8tOjhsWoPh4MU8DWJKo4_o=@cullmann.io>
References: <inE9J_k-R86l-r6ktRQ6pw@nuno-icons.com>
 <q3SfyAKWS9y01gc60fDCCA@kdab.com>
 <iAVJdiK_E4oqqCCGYmbbQEcoTNf5GJjW6In6jeWNJ88P0d8SBi7061BV4FdbReS8WdZq2Li1jaw2LvsiCpaz-8tOjhsWoPh4MU8DWJKo4_o=@cullmann.io>
Message-ID: <2ELYQ_feQDOtAlRtIKMcsA@kde.org>

El dilluns, 11 de maig del 2026, a les 16:43:35 (Hora d’estiu d’Europa 
central), Christoph Cullmann va escriure:
> Hi,
> 
> > A segunda-feira, 4 de maio de 2026 21:12:07 Hora de verão da Europa
> > Ocidental> 
> > David Redondo escreveu:
> > > Am Montag, 4. Mai 2026, 21:42 schrieb nuno:
> > > > in plasma  6.7 we are making oxygen work again and we dis a ton of
> > > > work on
> > > 
> > > the
> > > 
> > > > icons to match the entire thing...
> > > > 
> > > > can we please release a new tarbal with oxygen icon with the 6.27?
> > > 
> > > Oxygen icons is not part of frameworks (KF6) anymore as far as I know.
> > > Last release as a standalone project was by Jonathan in preparation for
> > > plasma 6 because of that so people would still have oxygen icons even
> > > when
> > > they don't have KF5 anymore.
> > > 
> > > If you think oxygen is due another release it can have another release
> > > as a
> > > standalone project. Either by you or someone else that knows how to make
> > > releases.
> > > 
> > > > cheers
> > > 
> > > Cheers,
> > > David
> > 
> > If  Jonathan was around he would sort this out, he was my go to guy to
> > make
> > this sort of things. We had it on slow burner for some years and would
> > publish new versions to fix bugs every now and then. in 6 series I'm
> > pretty sure we made 2 releases at
> > Given the current momentum on the project, i believe reinstating it as a
> > normal part of frameworks is the best action, lots  more work coming up in
> > the next year or so.
> > 
> > 
> > If you guys believe something different is required please let me know, I
> > just do the icons have no idea how any of this works. Any help is more
> > than welcome, in fact I'm asking for it....
> 
> given it still lives in the frameworks group and is even marked as still
> release, ...
> 
> https://invent.kde.org/frameworks/oxygen-icons/-/blob/master/metainfo.yaml?r
> ef_type=heads
> 
> could we not just add it to the packages we release with normal frameworks?

Sounds reasonable to me.

Nico?

Cheers,
  Albert

> 
> Greetings
> Christoph
> 
> > HELP
> > 
> > 
> > --
> > Nuno Pinheiro | nuno.pinheiro at kdab.com | Senior UI/UX Designer
> > KDAB Group, Klarälvdalens Datakonsult AB
> > Sweden (HQ) +46-563-540090, Direct Phone (+351 92 7326055)
> > KDAB - Trusted Software Excellence





From nicolas.fella at gmx.de  Sun May 31 22:50:51 2026
From: nicolas.fella at gmx.de (Nicolas Fella)
Date: Sun, 31 May 2026 23:50:51 +0200
Subject: please set a new release of oxygen icons for the next framework
 6.27
In-Reply-To: <2ELYQ_feQDOtAlRtIKMcsA@kde.org>
References: <inE9J_k-R86l-r6ktRQ6pw@nuno-icons.com>
 <q3SfyAKWS9y01gc60fDCCA@kdab.com>
 <iAVJdiK_E4oqqCCGYmbbQEcoTNf5GJjW6In6jeWNJ88P0d8SBi7061BV4FdbReS8WdZq2Li1jaw2LvsiCpaz-8tOjhsWoPh4MU8DWJKo4_o=@cullmann.io>
 <2ELYQ_feQDOtAlRtIKMcsA@kde.org>
Message-ID: <bf7cd6fd-4272-4418-8862-094864662203@gmx.de>

Am 31.05.26 um 11:14 schrieb Albert Astals Cid:
> El dilluns, 11 de maig del 2026, a les 16:43:35 (Hora d’estiu d’Europa
> central), Christoph Cullmann va escriure:
>> Hi,
>>
>>> A segunda-feira, 4 de maio de 2026 21:12:07 Hora de verão da Europa
>>> Ocidental>
>>> David Redondo escreveu:
>>>> Am Montag, 4. Mai 2026, 21:42 schrieb nuno:
>>>>> in plasma  6.7 we are making oxygen work again and we dis a ton of
>>>>> work on
>>>> the
>>>>
>>>>> icons to match the entire thing...
>>>>>
>>>>> can we please release a new tarbal with oxygen icon with the 6.27?
>>>> Oxygen icons is not part of frameworks (KF6) anymore as far as I know.
>>>> Last release as a standalone project was by Jonathan in preparation for
>>>> plasma 6 because of that so people would still have oxygen icons even
>>>> when
>>>> they don't have KF5 anymore.
>>>>
>>>> If you think oxygen is due another release it can have another release
>>>> as a
>>>> standalone project. Either by you or someone else that knows how to make
>>>> releases.
>>>>
>>>>> cheers
>>>> Cheers,
>>>> David
>>> If  Jonathan was around he would sort this out, he was my go to guy to
>>> make
>>> this sort of things. We had it on slow burner for some years and would
>>> publish new versions to fix bugs every now and then. in 6 series I'm
>>> pretty sure we made 2 releases at
>>> Given the current momentum on the project, i believe reinstating it as a
>>> normal part of frameworks is the best action, lots  more work coming up in
>>> the next year or so.
>>>
>>>
>>> If you guys believe something different is required please let me know, I
>>> just do the icons have no idea how any of this works. Any help is more
>>> than welcome, in fact I'm asking for it....
>> given it still lives in the frameworks group and is even marked as still
>> release, ...
>>
>> https://invent.kde.org/frameworks/oxygen-icons/-/blob/master/metainfo.yaml?r
>> ef_type=heads
>>
>> could we not just add it to the packages we release with normal frameworks?
> Sounds reasonable to me.
>
> Nico?
I'm okay with it.

Unless someone objects until next week I'll add it to 6.27

Cheers

Nico


