Heads-up: Frameworks branch merged, master now KF5-based
mail at milianw.de
Wed Aug 27 23:11:31 UTC 2014
On Thursday 28 August 2014 00:33:58 Kevin Funk wrote:
> I've now finally merged the frameworks branch of both kdevplatform and
> kdevelop into their respective master branches. In other words:
> Both kdevplatform.git and kdevelop.git master are now KF5-based.
> *What does that mean for you as a user*
> - If you still want the KDE4 version:
> Checkout branch '1.7' for kdevplatform.git and branch '4.7' for
> kdevelop.git - If you want to get started with KDevelop/Frameworks:
> https://community.kde.org/Frameworks/Building (use kdesrc-build!)
For those relying on an unported external plugin that depends on what was kde4
master, I've now created kde4-legacy branches in KDevelop and KDevplatform.
These branches are *dead* and no development should happen there. If you do,
you are on your own.
> *Further tasks for us developers*
> - Please, everyone, have a look at the failing unit tests and try to fix
> them It's important to have reliable tests before working further on the
> code. - There are still lot's of KDE4->KF5 porting tasks open:
> Dāvis Mosāns seems to take care of kdevplatform.git right now,
> but kdevelop.git still needs some love here.
> (@Dāvis, could you comment on the current state?)
> - Removal of deprecated API would be good now, too
Please, before changing more API let's get the existing plugins ported. Imo,
it's much simpler to update a given API in multiple places in one go, compared
to trying to get some piece of code working and having to adapt tons of random
places. At least these important plugins are currently missing a frameworks
Then there are these plugins which many people use, even though we never did a
proper stable release:
In general, I'd welcome if we could ensure most of the plugins, even the semi-
unmaintained ones, compile in KF5.
> *Most apparent issues in KDevelop on KF5 right now*
> - KTextEditor now provides their own status bar, but we'd like to be able
> to show/hide it on request because it wastes vertical space.
> The most clean approach would be a patch in KTE, also see 
> - CMake manager blocking the UI on project import
> (when parsing compile_commands.json)
> - Anything else?
> *Overall state of KDevelop on KF5*
> Seems to be good for daily use already, we've fixed the most annoying issues
> during the Randa sprint. Windows support is coming along nicely and we want
> to improve that.
> That's it from my side!
Nice. Many many thanks to all those involved. I'll see whether I can finally
submit my first KF5 patches this week :)
mail at milianw.de
More information about the KDevelop-devel