From jr at jriddell.org Fri Apr 5 12:31:32 2024 From: jr at jriddell.org (Jonathan Riddell) Date: Fri, 5 Apr 2024 12:31:32 +0100 Subject: Frameworks 6.1 tars available Message-ID: Tars for KDE Frameworks 6.1 are available for pre-release packaging, release is due next Friday 12 April http://embra.edinburghlinux.co.uk/~jr/tmp/frameworks-6.1.0-release-data Jonathan From arojas at archlinux.org Mon Apr 8 12:08:09 2024 From: arojas at archlinux.org (Antonio Rojas) Date: Mon, 08 Apr 2024 13:08:09 +0200 Subject: Frameworks 6.1 tars available In-Reply-To: References: Message-ID: <3475888.QJadu78ljV@arl> El viernes, 5 de abril de 2024 13:31:32 (CEST), Jonathan Riddell escribió: > Tars for KDE Frameworks 6.1 are available for pre-release packaging, > release is due next Friday 12 April Hello, Please consider a respin of extra-cmake-modules to include 7e68938f075a0423e3744358be9c4e77c6922104 It fixes the default CMAKE_INSTALL_PREFIX value with cmake>=3.29.1. -------------- next part -------------- An HTML attachment was scrubbed... URL: From heiko.becker at kde.org Tue Apr 9 12:49:35 2024 From: heiko.becker at kde.org (Heiko Becker) Date: Tue, 09 Apr 2024 13:49:35 +0200 Subject: KDE Gear 24.02.2 packages available for packagers Message-ID: Hello packagers, tarballs are available at the usual place under "stable/release-service/24.02.2". Please report any issues, release is planned next Thursday. Revisions and hashes can be found at https://invent.kde.org/-/snippets/3073 and a preliminary changelog from 24.02.1 at https://invent.kde.org/-/snippets/3074 The tars are signed with my public key with the follow fingerprint D81C0CB38EB725EF6691C385BB463350D6EF31EF. Thanks for packaging, Heiko From jr at jriddell.org Tue Apr 9 14:39:28 2024 From: jr at jriddell.org (Jonathan Riddell) Date: Tue, 9 Apr 2024 14:39:28 +0100 Subject: Frameworks 6.1 tars available In-Reply-To: <3475888.QJadu78ljV@arl> References: <3475888.QJadu78ljV@arl> Message-ID: extra-cmake-modules 6.1.0 tar has been updated ahead of release on Friday extra-cmake-modules;master;7e68938f075a0423e3744358be9c4e77c6922104;extra-cmake-modules-6.1.0.tar.xz;76c9edf00807e6cf8d4ae35f5195b4bc3fe94648d976fef532bf7f97d86388bd extra-cmake-modules-6.1.0 333kB - a51fb26baea9f6828884bfe6671d1cda840bd7f8c8bba904b7abb2160c2fedd2 + 76c9edf00807e6cf8d4ae35f5195b4bc3fe94648d976fef532bf7f97d86388bd http://embra.edinburghlinux.co.uk/~jr/tmp/frameworks-6.1.0-release-data http://embra.edinburghlinux.co.uk/~jr/tmp/extra-cmake-modules-6.1.0-changes_report.html On Mon, 8 Apr 2024 at 12:09, Antonio Rojas wrote: > > El viernes, 5 de abril de 2024 13:31:32 (CEST), Jonathan Riddell escribió: > > > Tars for KDE Frameworks 6.1 are available for pre-release packaging, > > > release is due next Friday 12 April > > > Hello, > > Please consider a respin of extra-cmake-modules to include 7e68938f075a0423e3744358be9c4e77c6922104 > > > It fixes the default CMAKE_INSTALL_PREFIX value with cmake>=3.29.1. > > > > From nate at kde.org Tue Apr 9 17:53:24 2024 From: nate at kde.org (Nate Graham) Date: Tue, 9 Apr 2024 10:53:24 -0600 Subject: KDE Gear 24.02.2 packages available for packagers In-Reply-To: References: Message-ID: <76551f09-4275-4485-b669-c5aae4603426@kde.org> Hello folks! I have a late breaking change for Gwenview: https://invent.kde.org/graphics/gwenview/-/commit/1592fa119db3370cf963cf627c37955f65eebc59 Could I ask for a re-spin of Gwenview to pick this up? Thanks a lot! Nate On 4/9/24 05:49, Heiko Becker wrote: > Hello packagers, > > tarballs are available at the usual place under > "stable/release-service/24.02.2". > > Please report any issues, release is planned next Thursday. > > Revisions and hashes can be found at https://invent.kde.org/-/snippets/3073 > and a preliminary changelog from 24.02.1 at > https://invent.kde.org/-/snippets/3074 > > The tars are signed with my public key with the follow fingerprint > D81C0CB38EB725EF6691C385BB463350D6EF31EF. > > Thanks for packaging, > Heiko > From arojas at archlinux.org Tue Apr 9 21:42:10 2024 From: arojas at archlinux.org (Antonio Rojas) Date: Tue, 09 Apr 2024 22:42:10 +0200 Subject: KDE Gear 24.02.2 packages available for packagers In-Reply-To: References: Message-ID: <5621224.ElGaqSPkdT@archlinux-arl> El martes, 9 de abril de 2024 a las 13:49 Heiko Becker escribió: > Hello packagers, > > tarballs are available at the usual place under > "stable/release-service/24.02.2". > > Please report any issues, release is planned next Thursday. Hi, The kio-extras-kf5 signature is bad. From christophe at krop.fr Tue Apr 9 22:51:15 2024 From: christophe at krop.fr (Christophe Marin) Date: Tue, 09 Apr 2024 23:51:15 +0200 Subject: KDE Gear 24.02.2 packages available for packagers In-Reply-To: References: Message-ID: <2177621.ra90peggMo@yuuko> Hello, On mardi 9 avril 2024 13:49:35 UTC+2 Heiko Becker wrote: > Hello packagers, > > tarballs are available at the usual place under > "stable/release-service/24.02.2". > > Please report any issues, release is planned next Thursday. > Not a new issue but worth mentioning: https://bugs.kde.org/483425 kdenlive fails to build since 24.02.0 if qtbase is built with gles rather than opengl (that's the case for our arm builds) Christophe From heiko.becker at kde.org Wed Apr 10 08:06:27 2024 From: heiko.becker at kde.org (Heiko Becker) Date: Wed, 10 Apr 2024 09:06:27 +0200 Subject: KDE Gear 24.02.2 packages available for packagers [gwenview =?iso-8859-1?Q?respin]?= In-Reply-To: <76551f09-4275-4485-b669-c5aae4603426@kde.org> References: <76551f09-4275-4485-b669-c5aae4603426@kde.org> Message-ID: <147760cf-8b3d-421d-b1e4-7d2185613c2a@kde.org> On Tuesday, 9 April 2024 18:53:24 CEST, Nate Graham wrote: > Hello folks! I have a late breaking change for Gwenview: > https://invent.kde.org/graphics/gwenview/-/commit/1592fa119db3370cf963cf627c37955f65eebc59 > > Could I ask for a re-spin of Gwenview to pick this up? Thanks a lot! Sure: gwenview-24.02.2.tar.xz gwenview release/24.02 4306b77be65d901e5ee59844e057be980e58f309 5f18604076fee297e722eb5dd4f45969f0e00c65ece939e7b12463f57df78b9e gwenview-24.02.2.tar.xz Regards, Heiko From heiko.becker at kde.org Wed Apr 10 08:07:00 2024 From: heiko.becker at kde.org (Heiko Becker) Date: Wed, 10 Apr 2024 09:07:00 +0200 Subject: KDE Gear 24.02.2 packages available for packagers In-Reply-To: <5621224.ElGaqSPkdT@archlinux-arl> References: <5621224.ElGaqSPkdT@archlinux-arl> Message-ID: <3a1a824a-3d70-4904-bcd2-996abe54718c@kde.org> On Tuesday, 9 April 2024 22:42:10 CEST, Antonio Rojas wrote: > El martes, 9 de abril de 2024 a las 13:49 Heiko Becker escribió: > >> Hello packagers, >> >> tarballs are available at the usual place under >> "stable/release-service/24.02.2". >> >> Please report any issues, release is planned next Thursday. > > The kio-extras-kf5 signature is bad. Sorry. This should be fixed now. Regards, Heiko From nate at kde.org Wed Apr 10 14:40:26 2024 From: nate at kde.org (Nate Graham) Date: Wed, 10 Apr 2024 07:40:26 -0600 Subject: KDE Gear 24.02.2 packages available for packagers [gwenview respin] In-Reply-To: <147760cf-8b3d-421d-b1e4-7d2185613c2a@kde.org> References: <76551f09-4275-4485-b669-c5aae4603426@kde.org> <147760cf-8b3d-421d-b1e4-7d2185613c2a@kde.org> Message-ID: <96a72c80-875f-4dd6-a371-754e89daba31@kde.org> On 4/10/24 01:06, Heiko Becker wrote: > On Tuesday, 9 April 2024 18:53:24 CEST, Nate Graham wrote: >> Hello folks! I have a late breaking change for Gwenview: >> https://invent.kde.org/graphics/gwenview/-/commit/1592fa119db3370cf963cf627c37955f65eebc59 >> >> Could I ask for a re-spin of Gwenview to pick this up? Thanks a lot! > > Sure: > > gwenview-24.02.2.tar.xz > gwenview release/24.02 > 4306b77be65d901e5ee59844e057be980e58f309 > 5f18604076fee297e722eb5dd4f45969f0e00c65ece939e7b12463f57df78b9e > gwenview-24.02.2.tar.xz Thanks a lot, Heiko! Nate From heiko.becker at kde.org Thu Apr 11 16:51:58 2024 From: heiko.becker at kde.org (Heiko Becker) Date: Thu, 11 Apr 2024 17:51:58 +0200 Subject: KDE Gear 24.02.2 released Message-ID: Thursday, 11 April 2024. 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: * kcachegrind: Fix crash when opening history menu (fixes bug #483973) * gwenview: No longer inhibit suspend when viewing an image (fixes bug #481481) * elisa: Fix broken volume slider with Qt Multimedia backend (fixes bug #392501) The full changelog can be found at https://kde.org/announcements/changelogs/gear/24.02.2/ and checksums at https://kde.org/info/releases-24.02.2/ The released code has been GPG-signed using the following key: https://keys.openpgp.org/search?q=D81C0CB38EB725EF6691C385BB463350D6EF31EF From jr at jriddell.org Fri Apr 12 16:05:13 2024 From: jr at jriddell.org (Jonathan Riddell) Date: Fri, 12 Apr 2024 16:05:13 +0100 Subject: Frameworks 6.1 Released Message-ID: KDE Frameworks 6.1 is released for distros and packagers https://kde.org/announcements/frameworks/6/6.1.0/ From aacid at kde.org Sun Apr 14 22:48:37 2024 From: aacid at kde.org (Albert Astals Cid) Date: Sun, 14 Apr 2024 23:48:37 +0200 Subject: KDE Gear: add Kalm In-Reply-To: References: <15282434.nJyUdutbpF@xps15> Message-ID: <57105614.LnF1eQmvNf@xps15> El dimecres, 27 de març del 2024, a les 9:23:54 (CEST), Plata va escriure: > Thanks for the feedback! > > > Generally, I think the reasoning makes sense. However, in the case of > Kalm, I don't think it's required. If you look at the app, it's pretty > simplistic (intentionally, due to its purpose). > > Therefore, I would prefer to just get it out to the public to eventually > get some feedback. I think it's pretty unlikely that anybody will notice > it if I just create a release myself. The dependency freeze for KDE Gear 24.05 is this thursday, it would be good if we get some tie breaking comment here so far we have two votes (the person proposing it for yes "obvious, so only gets 0.5 value for yes") and (me voting 0.5 against). Cheers, Albert > > > El dilluns, 25 de març de 2024, a les 8:10:43 (CET), Plata va escriure: > >> Dear Release Team, > >> > >> > >> Kalm has spent some time in KDE Review (see > >> https://invent.kde.org/utilities/kalm/-/issues/2). Can we add it > >> to/release it in KDE Gear? > > > > As far as I understand Kalm has never been released, right? > > > > For new apps *personally* I always suggest to do a few releases on your > > own > > because it allows for much faster feature turn-around than KDE Gear that > > has a very strict 3 months for new features schedule, that is usually > > fine for "established" apps but for something new you may very well find > > that there's that obvious feature missing that everyone needs and now you > > can't add it until 3 months in the future. > > > > Cheers, > > > > Albert > >> > >> Best regards > >> > >> Plata > >> > >> P.S.: CC me on the answers, I'm not subscribed From vkrause at kde.org Mon Apr 15 17:06:30 2024 From: vkrause at kde.org (Volker Krause) Date: Mon, 15 Apr 2024 18:06:30 +0200 Subject: Moving KUnifiedPush to KDE Gear Message-ID: <12424162.O9o76ZdvQC@vkpc5> Hi, I'd like to propose the KUnifiedPush library (https://invent.kde.org/libraries/ kunifiedpush) for inclusion in KDE Gear. This was stalled for some time but we finally have a default server installation thanks to Carl, so this is now actually useful for people not running their own infrastructure as well. There's two users of this already, Neochat and Tokodon, both have it as an optional dependency at the moment. Thanks, Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part. URL: From carl at carlschwan.eu Mon Apr 15 17:47:26 2024 From: carl at carlschwan.eu (Carl Schwan) Date: Mon, 15 Apr 2024 18:47:26 +0200 Subject: Moving KUnifiedPush to KDE Gear In-Reply-To: <12424162.O9o76ZdvQC@vkpc5> References: <12424162.O9o76ZdvQC@vkpc5> Message-ID: <1886573.FoFGESigpz@fedora> On Monday, April 15, 2024 6:06:30 PM GMT+2 Volker Krause wrote: > Hi, > > I'd like to propose the KUnifiedPush library > (https://invent.kde.org/libraries/ kunifiedpush) for inclusion in KDE Gear. > > This was stalled for some time but we finally have a default server > installation thanks to Carl, so this is now actually useful for people not > running their own infrastructure as well. > > There's two users of this already, Neochat and Tokodon, both have it as an > optional dependency at the moment. +1 Having KUnifiedPush released at the same time as NeoChat and Tokodon would be very helpful. Cheers, Carl > > Thanks, > Volker -------------- 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: From aacid at kde.org Mon Apr 15 22:22:00 2024 From: aacid at kde.org (Albert Astals Cid) Date: Mon, 15 Apr 2024 23:22:00 +0200 Subject: Moving KUnifiedPush to KDE Gear In-Reply-To: <12424162.O9o76ZdvQC@vkpc5> References: <12424162.O9o76ZdvQC@vkpc5> Message-ID: <4294955.Uxg6lR804x@xps15> El dilluns, 15 d’abril del 2024, a les 18:06:30 (CEST), Volker Krause va escriure: > Hi, > > I'd like to propose the KUnifiedPush library > (https://invent.kde.org/libraries/ kunifiedpush) for inclusion in KDE Gear. My answer when someone else asked the same question for other apps on Matrix this morning. I'd say feels a bit late with dependency freeze in 3 days and freeze freeze in 10. I'd prefer 2 weeks before dependency freeze, could live with 2 weeks before freeze freeze. [1] Can we wait for 24.08 for this? Cheers, Albert [1] This is to give people enough time to say yes/no/question things. > > This was stalled for some time but we finally have a default server > installation thanks to Carl, so this is now actually useful for people not > running their own infrastructure as well. > > There's two users of this already, Neochat and Tokodon, both have it as an > optional dependency at the moment. > > Thanks, > Volker From kossebau at kde.org Mon Apr 15 23:46:55 2024 From: kossebau at kde.org (Friedrich W. H. Kossebau) Date: Tue, 16 Apr 2024 00:46:55 +0200 Subject: Moving KGraphViewer & Massif Visualizer to KDE Gear Message-ID: <1927898.7Z3S40VBb9@klux> Hi, I would like to propose moving both KGraphViewer (invent.kde.org/graphics/ kgraphviewer) & Massif Visualizer (invent.kde.org/sdk/massif-visualizer) to the KDE Gear release bundle on next occasion. Both are rather stable in their feature-set and "community-maintained". As such community maintenance, they just got finally their Qt6 port completed and turned Qt6-only in the master branches. Ideally the "next occasion" would already be KDE 24.05, if that would be still acceptable given the history of the repos. While adding more work onto the Gear release managers already now, it would save individuals (like myself) from trying to do custom releases work, where otherwise the Gear release automation could free some time to e.g. do any needed regression finding & fixing. Cheers Friedrich From heiko.becker at kde.org Mon Apr 15 23:56:57 2024 From: heiko.becker at kde.org (Heiko Becker) Date: Tue, 16 Apr 2024 00:56:57 +0200 Subject: KDE Gear: add Kalm In-Reply-To: <57105614.LnF1eQmvNf@xps15> References: <15282434.nJyUdutbpF@xps15> <57105614.LnF1eQmvNf@xps15> Message-ID: <62716bd8-ce8f-49df-9ced-67263d47cb72@kde.org> On Sunday, 14 April 2024 23:48:37 CEST, Albert Astals Cid wrote: > El dimecres, 27 de març del 2024, a les 9:23:54 (CEST), Plata va escriure: >> Generally, I think the reasoning makes sense. However, in the case of >> Kalm, I don't think it's required. If you look at the app, it's pretty >> simplistic (intentionally, due to its purpose). >> >> Therefore, I would prefer to just get it out to the public to >> eventually ... > > The dependency freeze for KDE Gear 24.05 is this thursday, it > would be good if > we get some tie breaking comment here so far we have two votes (the person > proposing it for yes "obvious, so only gets 0.5 value for yes") > and (me voting > 0.5 against). To be honest, I don't feel very decisive about this one. For me it seems even a tad too simple for monthly releases. On the other hand, it doesn't have any insane dependencies and is well behaved, so in absence of other rules I'll add my +0.1. Regards, Heiko From heiko.becker at kde.org Tue Apr 16 00:02:09 2024 From: heiko.becker at kde.org (Heiko Becker) Date: Tue, 16 Apr 2024 01:02:09 +0200 Subject: Moving KGraphViewer & Massif Visualizer to KDE Gear In-Reply-To: <1927898.7Z3S40VBb9@klux> References: <1927898.7Z3S40VBb9@klux> Message-ID: <01e23f9c-756d-4353-98cc-be1c935bfd8b@kde.org> On Tuesday, 16 April 2024 00:46:55 CEST, Friedrich W. H. Kossebau wrote: > I would like to propose moving both KGraphViewer (invent.kde.org/graphics/ > kgraphviewer) & Massif Visualizer (invent.kde.org/sdk/massif-visualizer) to > the KDE Gear release bundle on next occasion. > > Both are rather stable in their feature-set and "community-maintained". > As such community maintenance, they just got finally their Qt6 > port completed > and turned Qt6-only in the master branches. > > Ideally the "next occasion" would already be KDE 24.05, if that > would be still > acceptable given the history of the repos. > > While adding more work onto the Gear release managers already now, it would > save individuals (like myself) from trying to do custom > releases work, where > otherwise the Gear release automation could free some time to e.g. do any > needed regression finding & fixing. How about a compromise: I'll do stand-alone releases for both and we have enough time for feedback before Gear 24.08? Regards, Heiko From jr at jriddell.org Tue Apr 16 13:40:45 2024 From: jr at jriddell.org (Jonathan Riddell) Date: Tue, 16 Apr 2024 13:40:45 +0100 Subject: Plasma 6.0.4 Message-ID: Plasma 6.0.4 is now released https://kde.org/announcements/plasma/6/6.0.4 From kossebau at kde.org Tue Apr 16 15:32:21 2024 From: kossebau at kde.org (Friedrich W. H. Kossebau) Date: Tue, 16 Apr 2024 16:32:21 +0200 Subject: Moving KGraphViewer & Massif Visualizer to KDE Gear In-Reply-To: <01e23f9c-756d-4353-98cc-be1c935bfd8b@kde.org> References: <1927898.7Z3S40VBb9@klux> <01e23f9c-756d-4353-98cc-be1c935bfd8b@kde.org> Message-ID: <2160711.yiUUSuA9gR@klux> Am Dienstag, 16. April 2024, 01:02:09 MESZ schrieb Heiko Becker: > On Tuesday, 16 April 2024 00:46:55 CEST, Friedrich W. H. Kossebau wrote: > > I would like to propose moving both KGraphViewer (invent.kde.org/graphics/ > > kgraphviewer) & Massif Visualizer (invent.kde.org/sdk/massif-visualizer) > > to > > the KDE Gear release bundle on next occasion. > > > > Both are rather stable in their feature-set and "community-maintained". > > As such community maintenance, they just got finally their Qt6 > > port completed > > and turned Qt6-only in the master branches. > > > > Ideally the "next occasion" would already be KDE 24.05, if that > > would be still > > acceptable given the history of the repos. > > > > While adding more work onto the Gear release managers already now, it > > would > > save individuals (like myself) from trying to do custom > > releases work, where > > otherwise the Gear release automation could free some time to e.g. do any > > needed regression finding & fixing. > > How about a compromise: I'll do stand-alone releases for both and we have > enough time for feedback before Gear 24.08? Thanks for the offer, Heiko. "Works for me" when it comes to trying to avoid release work :P so would happily pick up that. >From a pragmatic world approach I would still think that... anyway, main motive is to get the Qt6 ports of both out next and have releases "automated"/"schedule-forced" as ensured perspective :) Even more with the bad fonts finally fixed while at it, which annoyed me for years. So in case the last-minute door to 24.05 will not open here after any more discussion, would then approach you about further steps directly, thanks again. Guess I would get serious here around end of April, for some rough planning from my side. New version numbers had already been set in the code (and also registered at bugs.kde.org), just letting current code changes sink in a bit (and be processed by the good bloody-edge consumers) before moving on :) Cheers Friedrich From vkrause at kde.org Tue Apr 16 19:52:14 2024 From: vkrause at kde.org (Volker Krause) Date: Tue, 16 Apr 2024 20:52:14 +0200 Subject: Moving KUnifiedPush to KDE Gear In-Reply-To: <4294955.Uxg6lR804x@xps15> References: <12424162.O9o76ZdvQC@vkpc5> <4294955.Uxg6lR804x@xps15> Message-ID: <2725647.mvXUDI8C0e@vkpc5> On Montag, 15. April 2024 23:22:00 CEST Albert Astals Cid wrote: > El dilluns, 15 d’abril del 2024, a les 18:06:30 (CEST), Volker Krause va > > escriure: > > Hi, > > > > I'd like to propose the KUnifiedPush library > > (https://invent.kde.org/libraries/ kunifiedpush) for inclusion in KDE > > Gear. > > My answer when someone else asked the same question for other apps on Matrix > this morning. > > I'd say feels a bit late with dependency freeze in 3 days and freeze freeze > in 10. > > I'd prefer 2 weeks before dependency freeze, could live with 2 weeks before > freeze freeze. [1] > > Can we wait for 24.08 for this? Fair enough, we can fill the gap with manual releases if needed. Regards, Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part. URL: From nate at kde.org Fri Apr 19 13:18:36 2024 From: nate at kde.org (Nate Graham) Date: Fri, 19 Apr 2024 14:18:36 +0200 Subject: Solid backport opportunity In-Reply-To: <4a9-66224d00-3-4d476e80@201554663> References: <4a9-66224d00-3-4d476e80@201554663> Message-ID: Thanks Bernhard. Release team, could we consider a Solid 6.1.1 release for this given the severity of the issue and the fact that it doesn't backport cleanly? Nate On 4/19/24 12:53, Bernhard Rosenkränzer wrote: > On Friday, April 19, 2024 08:33 CEST, Nate Graham wrote: > >> https://invent.kde.org/frameworks/solid/-/commit/9ecaf388ccd41d2831ab3833c26627f72ab78f40 >> fixed a nasty regression whereby LUKS-encrypted disks wouldn't decrypt. >> It missed Frameworks 6.1 but 6.2 is three weeks away, so you may want to >> consider backporting it sooner. > > Thanks for the pointer. FWIW the fix doesn't apply on 6.1, so here's a backport: > https://github.com/OpenMandrivaAssociation/kf6-solid/blob/master/backport-9ecaf388ccd41d2831ab3833c26627f72ab78f40.patch > > ttyl > bero > From nicolas.fella at gmx.de Fri Apr 19 14:01:25 2024 From: nicolas.fella at gmx.de (Nicolas Fella) Date: Fri, 19 Apr 2024 15:01:25 +0200 Subject: Solid 6.1.1 In-Reply-To: References: <4a9-66224d00-3-4d476e80@201554663> Message-ID: <48936cf7-66c9-454d-9a16-c8796178e268@gmx.de> Hi, due to an important issue Solid 6.1.1 is available at https://download.kde.org/stable/frameworks/6.1/solid-6.1.1.tar.xz The release is signed with 90A968ACA84537CC27B99EAF2C8DF587A6D4AAC1 Cheers Nico From halla at valdyas.org Sat Apr 20 10:24:03 2024 From: halla at valdyas.org (Halla Rempt) Date: Sat, 20 Apr 2024 11:24:03 +0200 Subject: Fwd: 1 release-team moderator request(s) waiting Message-ID: <1890654.CQOukoFCf9@thinkstation> I notice that spam messages remain this list's moderator queue for a long time, mostly until I am fit enough to get out of bed and dispose of them, while genuine messages get moderated pretty quickly. Fellow moderators, can you please also dispose of the spam? Halla ---------- Forwarded Message ---------- Subject: 1 release-team moderator request(s) waiting Date: vrijdag 19 april 2024, 09:00:04 CEST From: release-team-bounces at kde.org To: release-team-owner at kde.org The release-team at kde.org mailing list has 1 request(s) waiting for your consideration at: https://mail.kde.org/mailman/admindb/release-team Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. Pending posts: From: juny at news.suvsyselects.com on Wed Apr 17 06:08:47 2024 Subject: Re:SMAJ90CA Cause: Message is suspected to be spam ----------------------------------------- From aacid at kde.org Sat Apr 20 13:00:56 2024 From: aacid at kde.org (Albert Astals Cid) Date: Sat, 20 Apr 2024 14:00:56 +0200 Subject: KDE Gear: add Kalm In-Reply-To: <62716bd8-ce8f-49df-9ced-67263d47cb72@kde.org> References: <57105614.LnF1eQmvNf@xps15> <62716bd8-ce8f-49df-9ced-67263d47cb72@kde.org> Message-ID: <10644680.gENAm5DLRW@xps15> El dimarts, 16 d’abril del 2024, a les 0:56:57 (CEST), Heiko Becker va escriure: > On Sunday, 14 April 2024 23:48:37 CEST, Albert Astals Cid wrote: > > El dimecres, 27 de març del 2024, a les 9:23:54 (CEST), Plata va escriure: > >> Generally, I think the reasoning makes sense. However, in the case of > >> Kalm, I don't think it's required. If you look at the app, it's pretty > >> simplistic (intentionally, due to its purpose). > >> > >> Therefore, I would prefer to just get it out to the public to > >> eventually ... > > > > The dependency freeze for KDE Gear 24.05 is this thursday, it > > would be good if > > we get some tie breaking comment here so far we have two votes (the person > > proposing it for yes "obvious, so only gets 0.5 value for yes") > > and (me voting > > 0.5 against). > > To be honest, I don't feel very decisive about this one. For me it seems > even a tad too simple for monthly releases. On the other hand, it doesn't > have any insane dependencies and is well behaved, so in absence of other > rules I'll add my +0.1. Ok, so with your 0.1 the answer, this is a "yes" and I've added it to the release. Cheers, Albert > > Regards, > Heiko From bcooksley at kde.org Sun Apr 21 01:34:29 2024 From: bcooksley at kde.org (Ben Cooksley) Date: Sun, 21 Apr 2024 12:34:29 +1200 Subject: CI moved to Qt 6.7 for Linux builds Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From aacid at kde.org Sun Apr 21 09:44:14 2024 From: aacid at kde.org (Albert Astals Cid) Date: Sun, 21 Apr 2024 10:44:14 +0200 Subject: AppStream Metadata with our releases In-Reply-To: <21a707f0965ab8ffb1de4bdc26ff20f656b24ef3@smartlab.uber.space> References: <21a707f0965ab8ffb1de4bdc26ff20f656b24ef3@smartlab.uber.space> Message-ID: <3222326.bebeVtv7W4@xps15> El divendres, 22 de març del 2024, a les 0:37:00 (CEST), Julius Künzel va escriure: > Hi! > > (This mail goes to multiple lists, please reply to kde-devel) > > With Flathub beeing more strict on its AppStream metadata guidlines [1] > there is yet another spotlight on AppStream metadata. > > AppStream metadata are consumed by app stores like Flathub, Snapcraft, > Discover, our scripts to submit apps to the Microsoft Store and last but > not least by apps.kde.org [2]. > > For release info in particular the quality guidelines say: "Make sure all > your releases have release notes, even minor ones." [3] As I think this > makes perfectly sense, I like to propose two things that seem straight > forward to me: > > - We should not remove older releases from the AppStream data as already > suggested by Carl in a merge request [4]. I'd go for https://invent.kde.org/sysadmin/release-tools/-/merge_requests/48/diffs instead. Cheers, Albert > > - Also it would be convenient to add noteworthy changes to the metadata > together with the related code change. However at the moment for KDE Gear > the release is usually only added to the metadata a few days before > tagging. Would it be possible to add the next minor release to the release > branch right after the current one has been released and the next major > release to master ones the upcoming version has been branched? > > I belive this makes it easier for developers to contribute to the release > meta info and I hope it hence raises motivation to do so. > > I am happy to hear your opionions, thoughts and concerns! > > Cheers, > Julius > > [1] https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines > [2] https://apps.kde.org/ > [3] > https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/quality-g > uidelines/#release-notes [4] > https://invent.kde.org/sysadmin/appstream-metainfo-release-update/-/merge_r > equests/6 > > Julius Künzel > Volunteer KDE Developer, mainly hacking Kdenlive > KDE GitLab: www.invent.kde.org/jlskuz https://invent.kde.org/jlskuz > Matrix: @jlskuz:kde.org https://go.kde.org/matrix/#/@jlskuz:kde.org From reeves.87 at gmail.com Sun Apr 21 17:23:38 2024 From: reeves.87 at gmail.com (Michael Reeves) Date: Sun, 21 Apr 2024 12:23:38 -0400 (EDT) Subject: CI moved to Qt 6.7 for Linux builds In-Reply-To: References: Message-ID: <4dc8dd5f-df79-4fbc-93d4-0ab66c09460e@gmail.com> 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 : > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 854 bytes Desc: not available URL: From kossebau at kde.org Sun Apr 21 18:55:36 2024 From: kossebau at kde.org (Friedrich W. H. Kossebau) Date: Sun, 21 Apr 2024 19:55:36 +0200 Subject: Moving KGraphViewer & Massif Visualizer to KDE Gear (-> 24.08) In-Reply-To: <1927898.7Z3S40VBb9@klux> References: <1927898.7Z3S40VBb9@klux> Message-ID: <2062622.YKUYFuaPT4@klux> Am Dienstag, 16. April 2024, 00:46:55 MESZ schrieb Friedrich W. H. Kossebau: > Hi, > > I would like to propose moving both KGraphViewer (invent.kde.org/graphics/ > kgraphviewer) & Massif Visualizer (invent.kde.org/sdk/massif-visualizer) to > the KDE Gear release bundle on next occasion. > > Both are rather stable in their feature-set and "community-maintained". > As such community maintenance, they just got finally their Qt6 port > completed and turned Qt6-only in the master branches. So after discussion the "next occasion" would be 24.08, and until then some stand-alone releases will happen (currently prepared). In case of positive decision on the proposal for Gear inclusion, prepared already some respective MRs: https://invent.kde.org/sysadmin/release-tools/-/merge_requests/49 https://invent.kde.org/sysadmin/release-tools/-/merge_requests/50 Cheers Friedrich From jr at jriddell.org Mon Apr 22 12:41:26 2024 From: jr at jriddell.org (Jonathan Riddell) Date: Mon, 22 Apr 2024 12:41:26 +0100 Subject: Plasma KWin 6.0.4.1 Message-ID: An updated tar for KWin fixes some performance regressions - kwin-6.0.4 + kwin-6.0.4.1 8.4MB - f5552f8c5b179e272fee33a19249686573eabffddd5541bc31f8fd7069baa82b + 56ffb37fa36e10f058ec5499c6858f6b21105b56ac7d70407921f063bc4bcb36 http://embra.edinburghlinux.co.uk/~jr/tmp/kwin-6.0.4.1-changes_report.html From aacid at kde.org Fri Apr 26 15:49:10 2024 From: aacid at kde.org (Albert Astals Cid) Date: Fri, 26 Apr 2024 16:49:10 +0200 Subject: KDE Gear 24.05 Beta release Message-ID: <9081277.kg8Xsf6nZK@xps15> Packages are available at the usual locations. krfb does not compile at this point (needs an unreleased kpipewire). I've contacted the people that should fix it and we're hoping to get it fixed ASAP. Cheers, Albert From aacid at kde.org Sun Apr 28 11:43:05 2024 From: aacid at kde.org (Albert Astals Cid) Date: Sun, 28 Apr 2024 12:43:05 +0200 Subject: KF5 kio-extras and future releases Message-ID: <6374130.JxFpSNCNT5@xps15> I have not included a package of the kf5 branch of kio-extras in the KDE Gear 24.05 release. At least two people have asked me about whether it should be included or not. I honestly don't know what to say :D In my mind it's a no and i'll explain the reasons below, feel free to disagree or prove my points nonsense. As far as I understand kio-extras-kf5 was created because: A) We needed a KF6 kio-extras so that KF6 apps can use extra-kio stuff B) We needed a KF5 kio-extras that could be coinstalled with the above KF6 kio-extras so that KF5 apps can use extra-kio stuff Now, question is should we keep releasing kio-extras-kf5 or not? Given KF5 kio is in a relatively deep freeze, no new changes in kio-extras-kf5 are going to be needed to adapt to changes in kio. kio-extras-kf5 is extracted from a branch named "kf5" that I guess not many developers are really paying attention to because it's neither master nor the usual release/xx.yy branch. It could happen that we need a very important bugfix to kio-extras-kf5 and it would be commited to that branch and we would need to do a release. But given how that doesn't seem super likely and how much of a pain it is to our release process to release it (we need to release two tarballs from the same repo but from different branches) I would really really say, no, we don't release it with every single KDE Gear release (until we drop KF5 support), if there's any eventual bugfix we'll just release a new tarball (in the 24.02.x naming?). Cheers, Albert From aacid at kde.org Tue Apr 30 23:01:29 2024 From: aacid at kde.org (Albert Astals Cid) Date: Wed, 01 May 2024 00:01:29 +0200 Subject: Moving KGraphViewer & Massif Visualizer to KDE Gear In-Reply-To: <1927898.7Z3S40VBb9@klux> References: <1927898.7Z3S40VBb9@klux> Message-ID: <3118541.PV7fZc78Hv@xps15> El dimarts, 16 d’abril del 2024, a les 0:46:55 (CEST), Friedrich W. H. Kossebau va escriure: > Hi, > > I would like to propose moving both KGraphViewer (invent.kde.org/graphics/ > kgraphviewer) & Massif Visualizer (invent.kde.org/sdk/massif-visualizer) to > the KDE Gear release bundle on next occasion. > > Both are rather stable in their feature-set and "community-maintained". > As such community maintenance, they just got finally their Qt6 port > completed and turned Qt6-only in the master branches. > > Ideally the "next occasion" would already be KDE 24.05, if that would be > still acceptable given the history of the repos. Added for 24.08 since noone complained in 2 weeks. Cheers, Albert > > While adding more work onto the Gear release managers already now, it would > save individuals (like myself) from trying to do custom releases work, where > otherwise the Gear release automation could free some time to e.g. do any > needed regression finding & fixing. > > Cheers > Friedrich