Re: Frameworks master is Qt6 now
Am 23.01.23 um 17:23 schrieb Nicolas Fella: Am 19.01.23 um 13:44 schrieb Nicolas Fella: Am 18.01.23 um 23:58 schrieb Nicolas Fella: Hi, the master branch of frameworks repositories now required Qt6 to build. Maintenance of KF5 continues in the "kf5" branch. Those using kdesrc-build make sure your kdesrc-builrc contains "branch-group kf5-qt5", then it will switch to the correct branch automatically. Those building manually please adjust your workflow accordingly. Any merge requests for frameworks should target Qt6/master (unless they are not applicable there). If the change should be backported to KF5 cherry-pick it to the kf5 branch after merging. Note that for the time being the kf5 branch has to stay compatible with Qt6. This is required to keep the currently existing Qt6 builds working. This does *not* mean that master is now open for any kind of breaking change. We will announce more on this soon. Assuming no major issues with our tooling crop up soon we will proceed with the following changes: - Bump the KF_VERSION in master to 5.240.0. At some point we will release one or more beta versions, which will have 5.250.0 etc as version number. This is to follow the practice of .80/.90 version numbers, but slightly adjusted to account for 255 being the technical upper limit. - Drop build system code to build with Qt5 - Rename library/target names to KF6 - Drop deprecated API. To ensure compatibility with existing Qt6 builds this will initially be done only for API that was deprecated before 5.100 since that is what the current Qt6 CI enforces. Eventually we of course want to drop everything deprecated, but that requires porting consumers of it first. I expect this to happen over the next few days. I will announce once this is done and master is open for more invasive changes. Hi, as an update to this: We are currently progressing nicely with this, but are not done yet. Some amount of instability/breakage is expected, so *I do not recommend* to try and use frameworks master until things have settled down a bit. Doing so prematurely would only cause extra work for everyone involved. I will announce once things have settled enough to start working on more things. Hi, the items mentioned are now done. We are now mostly in the process of ironing out some edges and wrapping up some loose ends. There's a list of "TODO after branching" tasks in https://phabricator.kde.org/tag/kf6/ as well as a lot of "TODO KF6" comments all across our codebase. Help with going through them and addressing them is appreciated. master is open for regular development as well as breaking changes. Cheers Nico
Re: Frameworks master is Qt6 now
Am 23.01.23 um 17:23 schrieb Nicolas Fella: Am 19.01.23 um 13:44 schrieb Nicolas Fella: Am 18.01.23 um 23:58 schrieb Nicolas Fella: Hi, the master branch of frameworks repositories now required Qt6 to build. Maintenance of KF5 continues in the "kf5" branch. Those using kdesrc-build make sure your kdesrc-builrc contains "branch-group kf5-qt5", then it will switch to the correct branch automatically. Those building manually please adjust your workflow accordingly. Any merge requests for frameworks should target Qt6/master (unless they are not applicable there). If the change should be backported to KF5 cherry-pick it to the kf5 branch after merging. Note that for the time being the kf5 branch has to stay compatible with Qt6. This is required to keep the currently existing Qt6 builds working. This does *not* mean that master is now open for any kind of breaking change. We will announce more on this soon. Assuming no major issues with our tooling crop up soon we will proceed with the following changes: - Bump the KF_VERSION in master to 5.240.0. At some point we will release one or more beta versions, which will have 5.250.0 etc as version number. This is to follow the practice of .80/.90 version numbers, but slightly adjusted to account for 255 being the technical upper limit. - Drop build system code to build with Qt5 - Rename library/target names to KF6 - Drop deprecated API. To ensure compatibility with existing Qt6 builds this will initially be done only for API that was deprecated before 5.100 since that is what the current Qt6 CI enforces. Eventually we of course want to drop everything deprecated, but that requires porting consumers of it first. I expect this to happen over the next few days. I will announce once this is done and master is open for more invasive changes. Hi, as an update to this: We are currently progressing nicely with this, but are not done yet. Some amount of instability/breakage is expected, so *I do not recommend* to try and use frameworks master until things have settled down a bit. Doing so prematurely would only cause extra work for everyone involved. I will announce once things have settled enough to start working on more things. Hi, the items mentioned are now done. We are now mostly in the process of ironing out some edges and wrapping up some loose ends. There's a list of "TODO after branching" tasks in https://phabricator.kde.org/tag/kf6/ as well as a lot of "TODO KF6" comments all across our codebase. Help with going through them and addressing them is appreciated. master is open for regular development as well as breaking changes. Cheers Nico
Re: Frameworks master is Qt6 now
Am 23.01.23 um 17:23 schrieb Nicolas Fella: Am 19.01.23 um 13:44 schrieb Nicolas Fella: Am 18.01.23 um 23:58 schrieb Nicolas Fella: Hi, the master branch of frameworks repositories now required Qt6 to build. Maintenance of KF5 continues in the "kf5" branch. Those using kdesrc-build make sure your kdesrc-builrc contains "branch-group kf5-qt5", then it will switch to the correct branch automatically. Those building manually please adjust your workflow accordingly. Any merge requests for frameworks should target Qt6/master (unless they are not applicable there). If the change should be backported to KF5 cherry-pick it to the kf5 branch after merging. Note that for the time being the kf5 branch has to stay compatible with Qt6. This is required to keep the currently existing Qt6 builds working. This does *not* mean that master is now open for any kind of breaking change. We will announce more on this soon. Assuming no major issues with our tooling crop up soon we will proceed with the following changes: - Bump the KF_VERSION in master to 5.240.0. At some point we will release one or more beta versions, which will have 5.250.0 etc as version number. This is to follow the practice of .80/.90 version numbers, but slightly adjusted to account for 255 being the technical upper limit. - Drop build system code to build with Qt5 - Rename library/target names to KF6 - Drop deprecated API. To ensure compatibility with existing Qt6 builds this will initially be done only for API that was deprecated before 5.100 since that is what the current Qt6 CI enforces. Eventually we of course want to drop everything deprecated, but that requires porting consumers of it first. I expect this to happen over the next few days. I will announce once this is done and master is open for more invasive changes. Hi, as an update to this: We are currently progressing nicely with this, but are not done yet. Some amount of instability/breakage is expected, so *I do not recommend* to try and use frameworks master until things have settled down a bit. Doing so prematurely would only cause extra work for everyone involved. I will announce once things have settled enough to start working on more things. Hi, the items mentioned are now done. We are now mostly in the process of ironing out some edges and wrapping up some loose ends. There's a list of "TODO after branching" tasks in https://phabricator.kde.org/tag/kf6/ as well as a lot of "TODO KF6" comments all across our codebase. Help with going through them and addressing them is appreciated. master is open for regular development as well as breaking changes. Cheers Nico
Re: Downtime Notice: Bugzilla - bugs.kde.org
On Tue, Feb 7, 2023 at 3:20 AM Halla Rempt wrote: > On zondag 5 februari 2023 19:44:12 CET Ben Cooksley wrote: > > > There hasn't been much in the way of substantive changes to how Bugzilla > > sends emails - my guess would be your filters detected it being a > Bugzilla > > email based on the old server hostname of komaci.kde.org. > > If so you will need to update your filters. > > Actually, I filtered on from:bugzilla_nore...@kde.org. It seems to have > fixed itself, though... > Interesting, that shouldn't have changed at all. No idea why a small handful of mails went out that didn't match that signature > > Halla > > > Thanks, Ben
Reminder: KF6 Meeting
Hello everyone, please remember the KF6 meeting tomorrow, Tuesday 17:00 CET: https://meet.kde.org/b/ada-mi8-aem Note as discussed last time we are back to a weekly interval now due to the increased amount of things to discussed after branching. Topics and notes are collected here: https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/27 Thank you, Volker signature.asc Description: This is a digitally signed message part.
Splitting Plasma-frameworks
Hi all, I've resurrected a project i started a long time ago. Since Plasma Dataengines are now deprecated, but being able to port away everything for Plasma 6.0 is not a given, I've started a split as a standalone dataengines library called Plasma5Support, so far in my personal area https://invent.kde.org/mart/plasma5support Even in the unlikely event if we can port all the things in time and end up not releasing this, It will allow to having what we don't want removed from libplasma to not have big unwanted thing there for the 6 lifetime. as soon as workspace goes kf6, i would then port plsmoids to use that, and then remove dataengines from p-f I would like after ironing out the obvious big rough edges to make it a module in workspace (after workspace is kf6 of course) Opinions? comments? -- Marco Martin
Re: Downtime Notice: Bugzilla - bugs.kde.org
On zondag 5 februari 2023 19:44:12 CET Ben Cooksley wrote: > There hasn't been much in the way of substantive changes to how Bugzilla > sends emails - my guess would be your filters detected it being a Bugzilla > email based on the old server hostname of komaci.kde.org. > If so you will need to update your filters. Actually, I filtered on from:bugzilla_nore...@kde.org. It seems to have fixed itself, though... Halla