Sun-setting QCA
QCA has served us well for quite some time, but it's time to sunset it. The architecture is quite complex, its plugin based functionality means that you can never be sure if a given feature your app needs will be available or not and the features we use from it are small compared to the huge amount of features QCA actually has meaning the maintainance effort is bigger than it needs to be. I've started https://invent.kde.org/libraries/qca/-/issues/18 to collect the uses of QCA and plan for replacing it with appropriate crypto code/library directly. Best Regards, Albert
Re: Proposal unify back our release schedules
On Friday, 19 April 2024 17.50.44 CEST Neal Gompa wrote: > > > * "KDE Framework" will still exists as an entity and its ABI and API > > > > > > compatibility requirement. Only change is the release frequency and > > > the > > > > > > introduction of a stable branch in sync with the other components. > > > > That part I'm against for the above mentioned reasons, KF's release > > frequency is a major feature of it. > > As a distribution, I found it tremendously helpful to integrate and > qualify the MegaRelease. That doesn't mean that we need *every* > release of KF and Gear to be MegaReleases. One thing I would like to hear from the distribution standpoint, is that in the past i also heard our release schedule being part of the reasons some enterprise distros dropped our stuff completely from the official release (suse and red hat). In part it sounded kinda an excuse to me, but if there is any part of truth is worth exploring. is changing frequency or dates something that would help significantly distros? is there something about our current schedules that is a significant hindrance for distributions to the point "we don't feel we can adequately support it"? a part of this discussion should have the point of a good relatioship with downstream in consideration (also because is part of the broader "getting to more users") -- Marco Martin
KDE Gear projects with failing CI (master) (23 April 2024)
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 got fixed Bad news: 5 new repositories failing this week kimap - NEW * https://invent.kde.org/pim/kimap/-/pipelines/671573 * testsession fails on freebsd14_qt66 tokodon - NEW * https://invent.kde.org/network/tokodon/-/pipelines/671582 * suse_tumbleweed_qt67 fails cantor - NEW * https://invent.kde.org/education/cantor/-/pipelines/671568 * suse_tumbleweed_qt515 and windows_qt515 fail kturtle - NEW * https://invent.kde.org/education/kturtle/-/pipelines/671569 * craft_windows_qt6_x86_64 fails neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/671651 * craft_appimage_qt6_x86_64 and craft_windows_qt6_x86_64 fail Cheers, Albert
KDE Gear projects with failing CI (release/24.05) (23 April 2024)
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. Bad news: 4 repositories have started failing cantor - NEW * https://invent.kde.org/education/cantor/-/pipelines/671601 * suse_tumbleweed_qt515 and windows_qt515 tests fail libkleo - NEW * https://invent.kde.org/pim/libkleo/-/pipelines/671605 * suse_tumbleweed_qt67 tests fail tokodon - NEW * https://invent.kde.org/network/tokodon/-/pipelines/671608 suse_tumbleweed_qt67 tests fail neochat - NEW * https://invent.kde.org/network/neochat/-/pipelines/671682 * craft_appimage_qt6_x86_64 and flatpak fail Cheers, Albert
Re: KDE Gear projects with failing CI (release/24.05) (23 April 2024)
On Dienstag, 23. April 2024 18:38:35 CEST Albert Astals Cid wrote: > libkleo - NEW > * https://invent.kde.org/pim/libkleo/-/pipelines/671605 > * suse_tumbleweed_qt67 tests fail Caused by a regression in Qt 6.7.0: https://bugreports.qt.io/browse/QTBUG-124653 Regards, Ingo signature.asc Description: This is a digitally signed message part.
Re: KDE Gear projects with failing CI (release/24.05) (23 April 2024)
On Dienstag, 23. April 2024 22:29:53 CEST Ingo Klöcker wrote: > On Dienstag, 23. April 2024 18:38:35 CEST Albert Astals Cid wrote: > > libkleo - NEW > > > > * https://invent.kde.org/pim/libkleo/-/pipelines/671605 > > > > * suse_tumbleweed_qt67 tests fail > > Caused by a regression in Qt 6.7.0: > https://bugreports.qt.io/browse/QTBUG-124653 Apparently, it's an intentional behavior change. *sigh* Adjust libkleo's unit test to the behavior change: https://invent.kde.org/pim/libkleo/-/merge_requests/98 Regards, Ingo signature.asc Description: This is a digitally signed message part.
Re: KDE Gear projects with failing CI (release/24.05) (23 April 2024)
On Dienstag, 23. April 2024 18:38:35 CEST Albert Astals Cid wrote: > neochat - NEW > * https://invent.kde.org/network/neochat/-/pipelines/671682 > * craft_appimage_qt6_x86_64 and flatpak fail Apparently, https://gitlab.matrix.org/ was temporarily unavailable. Same for master. Regards, Ingo signature.asc Description: This is a digitally signed message part.
