Questions about KDE 4.14 and later + branches

Jeremy Whiting jpwhiting at
Mon Jul 14 19:49:02 UTC 2014

Hello Christoph,

I have the same question re kanagram. It already has a frameworks
branch which builds and runs, and a soc student is working on
fixes/improvements to master branch. but I wonder if I should ask him
to switch his work to be based on kf5 and Qt5 or let him complete his
project on master (which wont be released) since KDE SC 14.12 will be
what's currently in frameworks branch (I'll of course cherry-pick
what's in master at the end of his project into the frameworks branch
then frameworks will become master I guess at that point).


On Mon, Jul 14, 2014 at 1:03 PM, Christoph Cullmann <cullmann at> wrote:
> Hi,
> perhaps I am only a little confused, but I am not sure how
> Kate (kate.git) should progress now in respect of "what is KDELIBS 4.x base"
> and "what is KF 5.x" based.
> At the moment, all branches beside "frameworks" in kate.git are targeted to kdelibs 4.x.
> That means, Kate for 4.14 will still be a kdelibs 4.x application (same for KWrite).
> For later, I would like to switch that over (and main development) to KF 5.x (which has
> already a nice and working ktexteditor KatePart port).
> What would be the "normal" transition planned for that?
> Leaving KDE/4.14 the last kdelibs 4.x based branch and just killing "master" and switching it over
> to what is now in "frameworks"?
> Greetings
> Christoph
> --
> ----------------------------- Dr.-Ing. Christoph Cullmann ---------
> AbsInt Angewandte Informatik GmbH      Email: cullmann at
> Science Park 1                         Tel:   +49-681-38360-22
> 66123 Saarbrücken                      Fax:   +49-681-38360-20
> GERMANY                                WWW:
> --------------------------------------------------------------------
> Geschäftsführung: Dr.-Ing. Christian Ferdinand
> Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
> _______________________________________________
> release-team mailing list
> release-team at

More information about the release-team mailing list