On Sat, Nov 9, 2013 at 1:04 PM, Christoph Cullmann <cul= lmann@absint.com> wrote:

Hi,

KDE Frameworks 5 gets more traction in the last months and perhaps we shoul= d plan ahead how
we want to go the 5.x road.

We have a lot of "cleanups" and "fixups" listed for the= KTextEditor interfaces we want to do for
the 5.x release and until now I think we have no clear plan when to go for = this.

I think Kate/KatePart are at the moment in a relative good state for the 4.= x line and not that much stuff is missing
that we actually need to implement in 4.x (beside perhaps some plugin enhan= cements or bugfixes).

Perhaps we should draft some small timeline for the future when we want to = go to switch the main focus
on porting + cleaning for 5.0.

We should coordinate a bit with the KDevelop guys, not sure how their plans= for 5.x are, either.

I would propose for Kate, to create some "frameworks" branch in D= ecember, in which the idea is to

a) first get it compiling with KDE 5 Frameworks + Qt 5.2
b) then cleanup and fix the stuff in the interfaces

This "frameworks" branch would have no BC/SC requirements until w= e arrive in the 5.0 Beta phase I think.

"master" should stay KDE 4.x until the last 4.xx release is done = and then we can switch that over.

All stuff that goes into master after the frameworks branch is there must b= e synced to frameworks by
the people doing the change, there won't be an auto-merge by me or some= one else I think.

This is just a bit brainstorming to kick this topic off, comments / changes= are welcome :P

Greetings
Christoph

--
----------------------------- Dr.-Ing. Christoph Cullmann ---------
AbsInt Angewandte Informatik GmbH =C2=A0 =C2=A0 =C2=A0Email: cullmann@AbsIn= t.com
Science Park 1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 Tel: =C2=A0 +49-681-38360-22
66123 Saarbr=C3=BCcken =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0Fax: =C2=A0 +49-681-38360-20
GERMANY =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0WWW: =C2=A0 http://www.AbsInt.com
--------------------------------------------------------------------
Gesch=C3=A4ftsf=C3=BChrung: Dr.-Ing. Christian Ferdinand
Eingetragen im Handelsregister des Amtsgerichts Saarbr=C3=BCcken, HRB 11234=
_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@kde.org
https://mail.kde.org/mailman/listinfo/kdevelop-devel

Hi,

Good thing to see that you're interested in the portin= g. I would suggest to create a frameworks branch in kdelibs (just like kde-= workspaces and kdelibs did) and just start working on it.

As for KDev= elop, we're quite depending on Kate, so I guess more than coordinating,= we'll have to work on the Kate side if you guys don't start before= .

Regarding d= ependencies, I'd just go forward and whenever we see the result we end = up, we can decide to cut them up. Either way, Just depending on KIO and Xml= Gui makes us depend on many many many things.

Aleix