Re: Frameworks / Plasma/ Gear Release Schedule Plan
El dilluns, 4 de setembre de 2023, a les 18:50:45 (CEST), David Edmundson va escriure: > Following on from the last Akademy we checked where we were with our > development progress in a meeting and settled on the following plan > for all 3 major parts: > > - In KDE Gear master will be open for Qt6 code to land for those > ready to move. Not all apps need to port. For the trigger happy among us... This is a plan/proposal, let's give people at least one week to comment/ disagree on it before making master Qt6-only for Gear apps. > > - The KDE Gear release will move by 2 months to allow for the extra > time needed for testing initial Qt6 changes > > - An Alpha will be made in November (a soft freeze in Plasma terms) > > - Betas/RCs will be made throughout December and January (3 releases, > 3 weeks apart) > > - Final release of all 3 major parts in sync in February > > Due to the delay of KDE Gear by an additional patch release of 23.08 > will be made. Or maybe even two if there's bugfixes flowing. Cheers, Albert > > David Edmundson
Re: Frameworks / Plasma/ Gear Release Schedule Plan
El dilluns, 4 de setembre de 2023, a les 18:50:45 (CEST), David Edmundson va escriure: > Following on from the last Akademy we checked where we were with our > development progress in a meeting and settled on the following plan > for all 3 major parts: > > - In KDE Gear master will be open for Qt6 code to land for those > ready to move. Not all apps need to port. For the trigger happy among us... This is a plan/proposal, let's give people at least one week to comment/ disagree on it before making master Qt6-only for Gear apps. > > - The KDE Gear release will move by 2 months to allow for the extra > time needed for testing initial Qt6 changes > > - An Alpha will be made in November (a soft freeze in Plasma terms) > > - Betas/RCs will be made throughout December and January (3 releases, > 3 weeks apart) > > - Final release of all 3 major parts in sync in February > > Due to the delay of KDE Gear by an additional patch release of 23.08 > will be made. Or maybe even two if there's bugfixes flowing. Cheers, Albert > > David Edmundson
Re: Do you use votes on Bugzilla tickets to help you make decisions?
El diumenge, 3 de setembre de 2023, a les 23:45:50 (CEST), Elvis Stansvik va escriure: > I noticed today that my votes on some bugs had been removed. Visiting > the bugs I see there's no longer any way to vote. > > So I guess as a result of this discussion, voting was disabled on some > products? > > No problem with me, but would have been nice with some sort of > announcement (sorry if I missed it!) I'm with Elvis. Why were votes removed? Or was this a mistake? The discussion here was IMO not conclusive. And even if it was, it needs to be announced before it happens. Otherwise we have 0 knowledge of what's going on and have no way to answer our users when they start complaining of why the votes are gone. Albert > > Elvis > > Den fre 4 aug. 2023 kl 23:55 skrev Harald Sitter : > > Never looked at them. Never seen the benefit. > > > > On Fri, Aug 4, 2023 at 3:53 PM Nate Graham wrote: > > > Hello folks! > > > > > > I often find myself explaining to users that votes on Bugzilla tickets > > > are generally meaningless and not used by most developers to help > > > prioritize work. After I explain this, they generally express surprise, > > > as it's not obvious. > > > > > > I find myself wondering whether it would make sense to disable the > > > voting feature by default to avoid giving our users this false > > > impression. > > > > > > So if you *do* take user votes into consideration when determining what > > > tickets to prioritize, I'd like to hear from you! > > > > > > > > > Nate
Re: drkonqi's many debuggers
El dijous, 31 d’agost de 2023, a les 12:42:59 (CEST), Halla Rempt va escriure: > On dinsdag 29 augustus 2023 05:22:56 CEST Thiago Macieira wrote: > > True, but the majority of our user base is still Linux, so if we had to > > choose only one, it would have to be gdb. > > Um, no? The majority is on Windows. Do you have actual numbers for this? Albert > > Halla
[ANNOUNCE] GammaRay 3.0.0
Announcing GammaRay 3.0.0 (not quite 2 years since the last release) Highlights of this Release: = * Port to Qt6. * Network operations now optionally allow capturing HTTP response body. * Objects can now be favorited via context menu. A favorited object appears in a separate item view above the main itemview * Add support for modifying QMargins in properties * Allow zooming with mouse wheel in Signals view * Filtering for an object now automatically expands the tree and selects the object * Fix a crash when an object is re-parented * Improved performance of signals view * Improved performance when target application triggers massive object destructions/constructions * Remove the KDAB commercial license. * Remove the 3D Widget Inspector View. * Remove the experimental VTK-based Object Visualizer. * Update 3rdparty/backward-cpp to version 1.6. * Update 3rdparty/lz4 to version 1.9.4. * Update 3rdparty/StackWalker. * Increase CMake requirement to version 3.16.0. The source code can be found on GitHub at: https://github.com/KDAB/GammaRay Tarballs and zipballs for v3.0.0 are available from: https://github.com/KDAB/GammaRay/releases Since this release, we are no longer providing pre-built packages for some popular Linux distros via the OpenSUSE Build Service, nor are we providing homebrew recipes for Mac users. =>Build from source or ask your favorite distro/homebrew/chocolatey/etc to provide packages. GammaRay is a tool to poke around in a Qt-application and also to manipulate the application to some extent. GammaRay uses various DLL injection techniques to hook into an application at runtime and provide access to a lot of interesting information. For more information about GammaRay, please see: * the KDAB GammaRay home page at http://www.kdab.com/gammaray * the GammaRay wiki at https://github.com/KDAB/GammaRay/wiki * the GammaRay User Manual at https://docs.kdab.com/gammaray-manual/latest/ * the GammaRay API doc at https://docs.kdab.com/gammaray/latest/ -- Allen Winter | allen.win...@kdab.com | Senior Software Engineer & Teamlead KDAB (USA) LLC, a KDAB Group company Tel. USA +1-866-777-KDAB(5322) ext3 KDAB - The Qt, C++ and OpenGL Experts signature.asc Description: This is a digitally signed message part.
Frameworks / Plasma/ Gear Release Schedule Plan
Following on from the last Akademy we checked where we were with our development progress in a meeting and settled on the following plan for all 3 major parts: - In KDE Gear master will be open for Qt6 code to land for those ready to move. Not all apps need to port. - The KDE Gear release will move by 2 months to allow for the extra time needed for testing initial Qt6 changes - An Alpha will be made in November (a soft freeze in Plasma terms) - Betas/RCs will be made throughout December and January (3 releases, 3 weeks apart) - Final release of all 3 major parts in sync in February Due to the delay of KDE Gear by an additional patch release of 23.08 will be made. David Edmundson
Frameworks / Plasma/ Gear Release Schedule Plan
Following on from the last Akademy we checked where we were with our development progress in a meeting and settled on the following plan for all 3 major parts: - In KDE Gear master will be open for Qt6 code to land for those ready to move. Not all apps need to port. - The KDE Gear release will move by 2 months to allow for the extra time needed for testing initial Qt6 changes - An Alpha will be made in November (a soft freeze in Plasma terms) - Betas/RCs will be made throughout December and January (3 releases, 3 weeks apart) - Final release of all 3 major parts in sync in February Due to the delay of KDE Gear by an additional patch release of 23.08 will be made. David Edmundson
Reminder: KF6 Meeting
Hello everyone, please remember the KF6 meeting tomorrow, Tuesday 17:00 CEST: https://meet.kde.org/b/ada-mi8-aem Topics and notes are collected here: https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/57 Thank you, Volker signature.asc Description: This is a digitally signed message part.
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
As a reminder this meeting is tonight in 3 hours. David
