Frameworks / Plasma/ Gear Release Schedule Plan

in February Due to the delay of KDE Gear by an additional patch release of 23.08 will be made. David Edmundson

Re: Planning the final 6 release timeframes

As a reminder this meeting is tonight in 3 hours. David

Re: Planning the final 6 release timeframes

Video call at https://meet.kde.org/b/ada-mi8-aem

Re: Planning the final 6 release timeframes

A time has been chosen on the poll with a clear winner: 4th September 18:00 CEST See you all there David Edmundson

Planning the final 6 release timeframes

h multiple rounds of elimination. Open discussion ahead of time is available at: https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/55 David Edmundson

Re: Gamepad KCM

b) merge it into the gamepad-kcm repo itself I would suggest doing this. It'll be easiest for future gamepad-kcm devs to find than any other repo, and means it'll be obvious if it ever becomes obsoleted. David

Re: Suggestion to drop ktp from KDE Gear

I was the one most resistant last time it came up. I no longer hold that opinion. It's clearly dead. Kill it. David On Wed, 21 Jun 2023, 18:35 Jonathan Riddell, wrote: > I'd like to suggest dropping ktp packages from the next KDE Gear release. > Telepathy upstream is unmaintained, KTP is

Re: KDE Gear and KF6

>> > (2a) The migration happens in a separate kf6 branch: > I think 2a worked well on the kf5 migration and should serve us well here too. Just to clarify that's having a kf6 branch for development and testing but then when each individual project decides it's ready to ship then that repo

Re: releases driven through invent?

I like the tagging first, right now there's potential for things to get out of sync. >The primary complication here is that since invent releases are based on tags >we'd need to tag each respin. I don't think that's an issue. If there's 26 plasma-workspace 1.0.0.N respins what would we want to

Re: Copying po/docbook files to repositories nightly

>Opinions? Comments? So our releases will end up a 1:1 with a git tag? That would be super-duper amazing for many cleanup things, including the security aspect +1 What's the plan for stable branches? We'll either need to port all active stable branches at the same time or we will have to

Re: Gitlab CI - Inbound

Excellent news!! Thanks very much > Once the scripts have been proven successfully for Frameworks, we will look > at extending them to projects that depend only on Frameworks and repositories Does this mean we would like Plasma to wait a while before merging? Is it worth us creating the kde-cli

Re: Can we consider bumping up the Plasma 5.23 release by one week?

We discussed this some more, and we are not in favour of moving forwards for Fedora: Reasons given were: - It either cuts into our beta period, or causes us issues with framework releases. - Fedora has regular releases anyway - It collides with the promo plans above - .0 releases tend to not

Re: Proposal of release blocker (missing translations for some .desktop files)

On Sun, Jan 3, 2021 at 5:16 PM Luigi Toscano wrote: > > Hi, > > scripty recognizes a few extensions as "desktop files" and extract their > strings. Additional files can be added by adding an ExtraDesktop.sh file which > lists them. > > So far, .desktop.in is *not* a recognized pattern by default.

Re: Proposed reversion-in-the-tarball

I hate to have to do this. The merged code had a bug, we'll need 142097e6ca5129a835199d93aee7b304586a8039 David

Re: Proposed reversion-in-the-tarball

> > How about we give this a day of testing first, to make sure it's ok now? Should have made that 2 days. I got a new report: https://invent.kde.org/frameworks/kservice/-/merge_requests/27 David

Re: Proposed reversion-in-the-tarball

Reading the bug comments I'm fairly sure the bug is this ``` extraFiles.keys() != KBuildSycoca::factoryExtraFiles() ``` Putting keys into a map and back out can change the order, whereas factoryExtraFiles is fixed. This could always fire. I haven't tested it, but I'll prepare a

Re: 2 kirigami fixes for a point release

>> > Kirigami seems to be rather unstable, I wonder if anything can be done to >> > improve upon that [*]. > >> One important thing seems to have been getting sloppy in those repos; >> mandatory code reviews. >> That's an easy thing to enforce, and we know it makes a huge difference to >> code. >>

Re: 2 kirigami fixes for a point release

> > IMHO distributions using Plasma LTS, Plasma team & other stakeholders should > > team up here and maintain a matching LTS branch of Frameworks together at > > the > > central KDE repos together. Well, and a version also satisfying other > > clients > > of KF, like non-workspace applications

Re: 2 kirigami fixes for a point release

> Kirigami seems to be rather unstable, I wonder if anything can be done to > improve upon that [*]. > One important thing seems to have been getting sloppy in those repos; mandatory code reviews. That's an easy thing to enforce, and we know it makes a huge difference to code. Even if no-one

Request backport of 4a9820a6df15a55a7d36d343ce70a25ba7d56b79 in kirigami

Hi all, I'm getting ~2 bug reports a day in systemsettings over a fixed Kirigami issue. Can I recommend that we release a patchfix cherry-picking 4a9820a6df15a55a7d36d343ce70a25ba7d56b79. Thanks David

Re: Plasma 2020 release schedules

Seems there's some consensus from two of our big distros I will bring this up at Akademy, 14:30 today to help move this discussion forward. David

Re: KDE Frameworks 5.58.0

>Python bindings for kcoreaddons don't build: Urgh, I clicked ship it on https://phabricator.kde.org/D20007 because it was Monday and I assumed tagging had just happened. (I should have checked, sorry) The windows side of that code was written blindly, and I did some last minute fixes to make it

Re: Issue with Discover on the Plasma/5.14 branch

My previous email missed the release team. Fowarding: Presumably also requires 4b6420596ca6a557591c24184a57b7985c77984e and more importantly e8e3160cd20c11090572bd66337b41d9567bf461 from KNS which is a whole new error reporting API with the error codes which you'd need As it's new API any

Re: do you need www.kde.org write access?

I'm trying to get things going again. >I would be so happy if someone would figure out all this and provide me with a command-line solution for adding KF5 release info pages and inserting text into the main page... I didn't sign up for figuring out webby stuff ;-) I've been having a play with a

Re: Plasma 5.13.1

plasma-desktop 5.13.1.1 tarball is now up. Should have both issues resolved sha256 c5f51c34a8549c879b691ea5de054100884c00bea32f559fc537ce338870a1bf plasma-desktop-5.13.1.1.tar.xz c1edded6db86fa77d8078f08ba9858f94e82dca336b7da871cbd611093e8a70e plasma-desktop-5.13.1.1.tar.xz.sig Note it's signed

Re: Plasma 5.13.1

Two issues were: * Complete crash on startup. Seems to be with Qt < 5.11 so Arch is fine * Some relatively minor issue with the touchpad KCM not loading We'll have a 5.13.1.1 of plasma-desktop coming today which addresses both. David

Re: Plasma 5.13.1

​Distros, We're getting numerous reports of two major problems with 5.13.1 Please hold off on any roll outs. Will update when I have more info/fixes. Sorry David

Re: KDE Frameworks 5.45.0

It's not in the v5.45.0-rc1 tag. It was committed today. Thanks for taking care of it. David

Re: RFC: Dropping (for real) KTP from Applications 17.12

> > > Does someone remember why telepathy-logger-qt is no longer part of the KDE > Applications releases? It got stuck at 15.04. > At the time we forked it from fd-o because they were didn't make a release (due to some Nokia related reason) We always assumed it would move back, it's really more

Re: RFC: Dropping (for real) KTP from Applications 17.12

Heiko, Thanks for fixing that. Can you make sure a release happens? Ping me if I can help. David

Re: RFC: Dropping (for real) KTP from Applications 17.12

I can't see a report on the telepathy Qt bug tracker. Do you have a link? On 23 Aug 2017 4:47 p.m., "Luca Beltrame" wrote: > NOTE: this mail comes from a downstream (distributor / integrator) point of > view. Feel free to correct possible errors. Also please try to keep both

Plasma 5.10.5

Plasma 5.10.5 is out at the usual location on http://download.kde.org https://www.kde.org/announcements/plasma-5.10.5 David

Re: KDE Telepathy as part of KDE Applications

Valorie spent some time at Akademy telling me about some other person she knows who uses the project. It might not be active, but it isn't all doom and gloom either. We do have two semi-active developers; Alexandr(Kaffiene) and James. You've been actively blocking anything from James for over a

Re: Plasma 5.9 Beta

That's 5.10 beta. David

Re: critical bugfix in KCoreAddons 5.30

Cuurent released plasma compiled with this release, without this patch will fail to load any new panel. It's "just a bug" but it's new and quite major. On 14 Jan 2017 3:50 p.m., "David Faure" wrote: On mercredi 11 janvier 2017 16:21:08 CET Marco Martin wrote: > hi all, > due to

Plasma 5.7.4 is out

https://www.kde.org/announcements/plasma-5.7.4.php Regards David

Re: Plasma 5.7.0 tars

On Mon, Jul 4, 2016 at 1:45 PM, Sebastian Kügler <se...@kde.org> wrote: > On Monday, July 4, 2016 1:29:55 PM CEST David Edmundson wrote: > > ... and if not, I need to know, because that means that > > > > - nobody tested the changes in libkscreen's master in the beta &g

Re: Plasma 5.7.0 tars

On Mon, Jul 4, 2016 at 1:20 PM, Sebastian Kügler <se...@kde.org> wrote: > On Thursday, June 30, 2016 11:06:46 PM CEST Harald Sitter wrote: > > On Thu, Jun 30, 2016 at 4:45 PM, David Edmundson > > > > <da...@davidedmundson.co.uk> wrote: > > > *sigh* seems

Re: Plasma 5.7.0 tars

On Thu, Jun 30, 2016 at 6:55 PM, Eric Hameleers <al...@slackware.com> wrote: > On Thu, 30 Jun 2016, David Edmundson wrote: > > Fixed - and checked a bit more thorougly this time. >> Thanks again. >> >> David >> > > I have two compile errors in plasm

Re: Plasma 5.7.0 tars

Fixed - and checked a bit more thorougly this time. Thanks again. David ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team

Re: Plasma 5.7.0 tars

*sigh* seems so. Yet plasma-workspace is from the right branch and it's done by an automated script(!) Thanks for spotting David ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team

Plasma 5.7.0 tars

Plasma 5.7 tars are up on depot for packagers Release is due on Tuesday. David ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team

Re: Review Request 125986: Enable gwenview to build against the new versions of libkipi (as well as older ones)

tps://git.reviewboard.kde.org/r/125986/#comment60471> why not return new KIPI::FileReadWriteLock(url); - David Edmundson On Nov. 8, 2015, 9:58 p.m., Shlomi Fish wrote: > > --- > This is an automatically generated e

Re: Review Request 125986: Enable gwenview to build against the new versions of libkipi (as well as older ones)

> On Nov. 9, 2015, 9:56 p.m., David Edmundson wrote: > > app/kipiinterface.cpp, line 463 > > <https://git.reviewboard.kde.org/r/125986/diff/1/?file=415688#file415688line463> > > > > why not > > > > return new KIPI::FileReadWriteLock(url)

Re: Plasma 5.4.3 tars are up

On Fri, Nov 6, 2015 at 10:40 AM, Jonathan Riddell wrote: > breeze 5.4.3 is updated to remove the breeze icons and icons-dark > themes, these are now separated into breeze-icons which is due to be > released with frameworks 5.16 tomorrow > Where was that discussed? That brings

Re: Gwenview ui file in 15.08

On Wed, Oct 7, 2015 at 10:13 PM, Luigi Toscano wrote: > Hi Ivan, > the change you committed few months ago to Gwenview: > > https://quickgit.kde.org/?p=gwenview.git=commit=78e4e57af3a5476dd949797c559a3d25d8ce50a1 > > broke the loading of the menu, as the ui file still

Re: minified javascript in telepathy-qt

It's not an issue. That file is not part of the source code for Telepathy-qt. David ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team

Re: KDE Workspaces 4.11 End of Life this August

On Sun, Aug 9, 2015 at 6:25 PM, Albert Astals Cid aa...@kde.org wrote: Back in August 2013 we promised to do Long Term Support for kde-workspace for 2 years. This means this August is the last release for kde-workspace. With that can I request we also stop releasing: kde-base-artwork

Re: What's up with dolphin?

On Sun, Jul 19, 2015 at 7:29 PM, Albert Astals Cid aa...@kde.org wrote: You guys have removed dolphin from kde-baseapps. There seems to be a dolphin.git repository but noone has asked for it to be released. kde-build metadata shows it should be released from the repo. Where should it have

Re: Review Request 123907: Make log viewer usable in multiple instances + fix the KDEInit couldn't launch log viewer error and Plasma being blocked

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/123907/#review80846 --- Ship it! Ship It! - David Edmundson On May 26, 2015, 1:30

Re: about-distro now part of kinfocentre

On Fri, Apr 3, 2015 at 9:35 PM, Burkhard Lück lu...@hube-lueck.de wrote: Am Freitag, 3. April 2015, 16:56:14 schrieb Jonathan Riddell: I've moved about-distro to kinfocentre to replace the summary page there. It uses /etc/os-release so distros will need to support the os-release spec.

Re: KF 5.6.0 release

On Sat, Jan 3, 2015 at 2:57 PM, David Faure fa...@kde.org wrote: On Saturday 03 January 2015 14:38:14 David Faure wrote: On Saturday 03 January 2015 14:17:12 David Edmundson wrote: ​What happened with Baloo? I don't know. What was supposed to happen? It was meant as a genuine question

Re: KF 5.6.0 release

​What happened with Baloo? ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team

Re: Fwd: Plasma Framework problems

On Thu, Oct 23, 2014 at 9:33 AM, David Faure fa...@kde.org wrote: On Monday 20 October 2014 02:52:58 David Edmundson wrote: Give me the sha1 to cherry-pick and I'll make a 5.3.1 with it. a3932843386a29faa3c62bf2934a173a3781d56c ​ That doesn't make sense, that commit is from September 15

Re: Fwd: Plasma Framework problems

Give me the sha1 to cherry-pick and I'll make a 5.3.1 with it. a3932843386a29faa3c62bf2934a173a3781d56c ​ ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team

Re: Fwd: Plasma Framework problems

I'll report back when I've confirmed this and then we can work out how we proceed. Reverting a3932843386a29faa3c62bf2934a173a3781d56c does indeed make everything work. Assuming we don't have a time machine our options are: - revert this commit and release plasma-framework 5.3.1 really

Re: Fwd: Plasma Framework problems

On 12 Oct 2014 18:04, šumski hrvoje.sen...@gmail.com wrote: On Sunday 12 of October 2014 11:58:44 David Edmundson wrote: I'll report back when I've confirmed this and then we can work out how we proceed. Reverting a3932843386a29faa3c62bf2934a173a3781d56c does indeed make

Fwd: Plasma Framework problems

Packagers, It seems Plasma 5.0 does NOT run smoothly against Plasma Framework 5.3. It would be easiest if distros hold off shipping frameworks 5.3 until Plasma 5.1 when Plasma5.1 is released. Clearly this is a screw-up and we need to come up with some better policies when we plan Plasma 5.2

SDDM-KCM

Hey, I've just tagged the SDDM KCM for releasing. It's not /technically/ part of KDE, but given SDDM is the recommended login manager for Plasma 5, so having the KCM will be useful for most Plasma 5 distros. Tarballs are at: https://github.com/sddm/sddm-kcm/releases Translations currently are

Re: KF 5.2.0

How are you generating that changelog? Plasma Framework has quite a few changes, which aren't listed. I assume we're forgetting to do something? David ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team

Re: bugzilla verion numbers

There's an email from Frank Reinginghaus in a thread on this list a while back titled Automatic creation of version information on bugs.kde.org: Jekyll Wu has the script that creates new versions automatically (just one of the many things he does to make bugs.kde.org a better place - thanks for

Re: 4.11.2 is released

s/September/October/ On Tue, Oct 1, 2013 at 5:42 PM, Albert Astals Cid aa...@kde.org wrote: http://kde.org/announcements/announce-4.11.2.php Cheers, Albert ___ release-team mailing list release-team@kde.org

Re: Review Request 111963: Turn off Battery fully charged notification by default

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/111963/#review37411 --- Ship it! Looks ok to me. - David Edmundson On Aug. 9, 2013

Re: Review Request 111949: Backup ResourceListGenerator: Do not only count files with tags

On Aug. 8, 2013, 9:06 p.m., Albert Astals Cid wrote: I can confirm that the new test fails without the patch and works with it. I can't assess the correctness of the code itself since my nepomuk-foo ? 0 It'd be cool if someone else from nepomuk-land can try to review. If not I'll

Re: KDE SC 4.11 Release Schedule (bis)

On Thu, Mar 7, 2013 at 10:58 AM, Albert Astals Cid aa...@kde.org wrote: El Dijous, 7 de març de 2013, a les 01:48:30, David Edmundson va escriure: On Wed, Mar 6, 2013 at 11:49 PM, Albert Astals Cid aa...@kde.org wrote: El Dimecres, 6 de març de 2013, a les 14:52:07, Vishesh Handa va

Re: KDE SC 4.11 Release Schedule (bis)

On Wed, Mar 6, 2013 at 11:49 PM, Albert Astals Cid aa...@kde.org wrote: El Dimecres, 6 de març de 2013, a les 14:52:07, Vishesh Handa va escriure: On Tue, Mar 5, 2013 at 5:13 AM, Albert Astals Cid aa...@kde.org wrote: A few months ago we were discussing changes regarding 4.11

Re: Re: Re: KDE SC 4.11 Release Schedule

On Sun, Jan 20, 2013 at 9:58 AM, Martin Gräßlin mgraess...@kde.org wrote: On Saturday 19 January 2013 19:21:27 Martin Gräßlin wrote: I think that the 4.11 cycle was not optimal, but I think it is because it overlapps with Christmas and New Year. Why was that suboptimal? We've been