Karp project - Review request
Hi there, With the hope that the Karp project reached state "worthy-to-release" I have just opened an issue for the review: https://invent.kde.org/graphics/karp/-/issues/9 So please, help us with that to make it part of April KDE Gear. Kind regards Tomasz
Re: End of life policy
On Tuesday, January 21, 2025 05:16:25 PM Albert Astals Cid wrote: > Is it not a consequence from the fact that there's no more releases > planned? > > It's weird to say "for things that we don't plan releases there will no be > releases" > > What would you write? From the peanut gallery: How about: No more releases planned for this project. and perhaps, in parenthesis after that, something like (end of project)
Threaded Sonnet ISpell plugin on Windows
Hello. Does anybody know if ISpell plugin from Sonnet on Windows can be used in thread? I noticed when using Sonnet::Speller in non main thread it stops working, isValid() returns false. Is it a known issue? Can it be workarounded somehow? Thank you.
Re: End of life policy
El dimarts, 21 de gener del 2025, a les 1:19:47 (Hora estàndard del Centre d’Europa), Justin Zobel va escriure: > On 21/1/25 10:41, Neal Gompa wrote: > > On Mon, Jan 20, 2025 at 7:03 PM Justin Zobel wrote: > >> Hey Everyone, > >> > >> I've only been a part of KDE for a few years now but I've seen it > >> mentioned multiple times and I'm guessing it's been discussed before but > >> I think KDE needs clearly defined end-of-life policies for it's > >> software. These are common practice and let users and developers know > >> what they should be using. > >> > >> KDE being a mostly volunteer-driven organization would be well within > >> expectations to only support the latest version of it's software. > >> > >> I'm sending this email in a hope of starting a productive discussion > >> around this. > > > > My understanding is that we currently only support the latest version. > > That is, as soon as a new version arrives, the previous version is no > > longer supported or maintained. > > > > Is there a different rule in place? > > If this is a rule it is not stated on https://community.kde.org from > what I can see. Is it not a consequence from the fact that there's no more releases planned? It's weird to say "for things that we don't plan releases there will no be releases" What would you write? Cheers, Albert
KDE Gear projects with failing CI (master) (21 January 2025)
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: 4 repositories were fixed Bad news: 2 repositories started failing kalarm - NEW * https://invent.kde.org/pim/kalarm/-/pipelines/869910 * kaeventtest fails in freebsd * insterestingly says that 2010/05/13 03:45:00.000[UTC+00:00:01] and 2010/05/13 03:45:00.000[UTC+00:00:01] are different neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/869365 * flatpak build fails Cheers, Albert
KDE Gear projects with failing CI (release/24.12) (21 January 2025)
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 projects were fixed Bad news: 3 new projects have started failing kalarm - NEW * https://invent.kde.org/pim/kalarm/-/pipelines/870508 * kaeventtest fails in freebsd * insterestingly says that 2010/05/13 03:45:00.000[UTC+00:00:01] and 2010/05/13 03:45:00.000[UTC+00:00:01] are different neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/868564 * flatpak build fails kmail - NEW * https://invent.kde.org/pim/kmail/-/pipelines/865902 * Fails to compile, wrong backport? Cheers, Albert
Re: Review Requests
On 22/1/25 17:03, Justin Zobel wrote: Hey everyone, Where does the template come from e.g. https://invent.kde.org/graphics/karp/-/issues/9? I think each distribution method e.g. Flatpak, Snap, etc should be a different checkbox. I also think it should more specifically refer to GitLab builds in CI/CD. As often these checklists are used for new apps that aren't released yet so won't be published to Flathub or the Snap store, etc. Once the project is approved, then we can look at publishing to stores as the author wants. Justin Further this I'd like to add: - Passing JSON, XML and YAML CI checks where files exist in the repository.
Review Requests
Hey everyone, Where does the template come from e.g. https://invent.kde.org/graphics/karp/-/issues/9? I think each distribution method e.g. Flatpak, Snap, etc should be a different checkbox. I also think it should more specifically refer to GitLab builds in CI/CD. As often these checklists are used for new apps that aren't released yet so won't be published to Flathub or the Snap store, etc. Once the project is approved, then we can look at publishing to stores as the author wants. Justin
Re: Review Requests
Hi, I would say https://develop.kde.org/docs/getting-started/add-project/#kde-review. Cheers, Johnny Le mer. 22 janv. 2025 à 07:38, Justin Zobel a écrit : > > On 22/1/25 17:03, Justin Zobel wrote: > > Hey everyone, > > > > Where does the template come from e.g. > > https://invent.kde.org/graphics/karp/-/issues/9? I think each > > distribution method e.g. Flatpak, Snap, etc should be a different > > checkbox. > > > > I also think it should more specifically refer to GitLab builds in > > CI/CD. As often these checklists are used for new apps that aren't > > released yet so won't be published to Flathub or the Snap store, etc. > > > > Once the project is approved, then we can look at publishing to stores > > as the author wants. > > > > Justin > > > Further this I'd like to add: > > - Passing JSON, XML and YAML CI checks where files exist in the repository. >
