Re: Proposal for using gitlab for kdereview process

https://community.kde.org/Goals/All_about_the_Apps On Wed, Feb 7, 2024 at 11:16 PM Friedrich W. H. Kossebau wrote: > > Long time ago, but perhaps there are still memories... > > Am Dienstag, 4. Juli 2023, 14:32:59 CET schrieb Jonathan Riddell: > > I've gone ahead an updated the Sanity checklist

Re: KDE Review: Skladnik (t.g.f.k.a. KSokoban), returning a KDE1-KDE3 age dino

Am Samstag, 27. Januar 2024, 18:22:35 CET schrieb Friedrich W. H. Kossebau: > moving slowly, but moving :) > > Would there be any objections to declare the kde(re)review phase to be > successfully completed now? See below for comments on the checklist. So 10 days passed and no actual objection,

Re: Proposal for using gitlab for kdereview process

Long time ago, but perhaps there are still memories... Am Dienstag, 4. Juli 2023, 14:32:59 CET schrieb Jonathan Riddell: > I've gone ahead an updated the Sanity checklist Having come across the checklist items * Passing KDE neon build * App packages in Flatpak, Snap, AppImages and Windows etc

Re: Flatpak jobs on KDE CI vs. continuous integration on main/master/devel branches

Am Sonntag, 4. Februar 2024, 19:22:28 CET schrieb Ben Cooksley: > On Mon, Feb 5, 2024 at 4:28 AM Friedrich W. H. Kossebau > > wrote: > > Hi, > > > > ((cc:kde-frameworks-devel for heads-up, replies please only to > > kde-core-deve)) > > > > I hit the problem that when working on a repo which

Re: Flatpak jobs on KDE CI vs. continuous integration on main/master/devel branches

Am Montag, 5. Februar 2024, 00:15:00 CET schrieb Julius Künzel: > > Besides all the resource costs to create flatpaks on master builds by > > default > every time, when those are usually not used by anyone anyway. > > It is important to mention that the pipelines on master usually publish to >

Re: Flatpak jobs on KDE CI vs. continuous integration on main/master/devel branches

Am Montag, 5. Februar 2024, 10:58:07 CET schrieb Ben Cooksley: > On Mon, Feb 5, 2024 at 4:28 AM Friedrich W. H. Kossebau > > wrote: > > So, how to solve those problems? Did I miss something? > > Could flatpak builds on master branches be made on-demand rather? > > For the record, my rebuild of

Re: KDE Gear projects with failing CI (release/24.02) (6 February 2024)

Am Mittwoch, 7. Februar 2024, 11:48:57 CET schrieb Ben Cooksley: > All of the Games Flatpak failures are caused by > https://invent.kde.org/games/libkdegames/-/commit/023d1a7b173f9d28453a0268e9 > 1ad1ccb47054b9 I intend to revert that commit in 24 hours unless a suitable > explaination can be

Re: KDE Gear projects with failing CI (release/24.02) (6 February 2024)

On Dienstag, 6. Februar 2024 22:24:22 CET Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for multiple > reasons. > > Good News: 7 failing repositories from previous report got

Re: KDE Gear projects with failing CI (release/24.02) (6 February 2024)

On Wed, Feb 7, 2024 at 10:24 AM Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for > multiple > reasons. > > Good News: 7 failing repositories from previous report got fixed >

Re: KDE Gear projects with failing CI (release/23.08) (6 February 2024)

On Mittwoch, 7. Februar 2024 09:50:12 CET Ingo Klöcker wrote: > On Dienstag, 6. Februar 2024 23:58:09 CET Albert Astals Cid wrote: > > Please work on fixing them, otherwise i will remove the failing CI jobs on > > their 4th failing week, it is very important that CI is passing for > > multiple

Re: KDE Gear projects with failing CI (release/23.08) (6 February 2024)

On Dienstag, 6. Februar 2024 23:58:09 CET Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for multiple > reasons. > > Good news: 3 repositories that were failing are fixed :) >