[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: Re: KDE Frameworks 5 Switch, When, how, what?
From: Aleix Pol <aleixpol () kde ! org>
Date: 2013-11-11 0:13:27
Message-ID: CACcA1RqM4rR5fS0WYnwX1aci6jUsOF6yPhp18wU1fSRf_M-8Hw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Sat, Nov 9, 2013 at 1:04 PM, Christoph Cullmann <cullmann@absint.com>wro=
te:
> Hi,
>
> KDE Frameworks 5 gets more traction in the last months and perhaps we
> should 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 fo=
r
> 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
> enhancements or bugfixes).
>
> Perhaps we should draft some small timeline for the future when we want t=
o
> 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 December,
> 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 we 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
> be synced to frameworks by
> the people doing the change, there won't be an auto-merge by me or someon=
e
> 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 Email: cullmann@AbsInt.com
> Science Park 1 Tel: +49-681-38360-22
> 66123 Saarbr=C3=BCcken Fax: +49-681-38360-20
> GERMANY WWW: http://www.AbsInt.com
> --------------------------------------------------------------------
> Gesch=C3=A4ftsf=C3=BChrung: Dr.-Ing. Christian Ferdinand
> Eingetragen im Handelsregister des Amtsgerichts Saarbr=C3=BCcken, HRB 112=
34
> _______________________________________________
> 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 porting. 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 KDevelop, 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 dependencies, 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 XmlGui makes us depend on many many many things.
Aleix
[Attachment #5 (text/html)]
<div dir="ltr">On Sat, Nov 9, 2013 at 1:04 PM, Christoph Cullmann <span dir="ltr"><<a \
href="mailto:cullmann@absint.com" target="_blank">cullmann@absint.com</a>></span> wrote:<br><div \
class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi,<br> <br>
KDE Frameworks 5 gets more traction in the last months and perhaps we should plan ahead how<br>
we want to go the 5.x road.<br>
<br>
We have a lot of "cleanups" and "fixups" listed for the KTextEditor interfaces we \
want to do for<br> the 5.x release and until now I think we have no clear plan when to go for this.<br>
<br>
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<br> that we actually need to implement in 4.x (beside perhaps some plugin enhancements or \
bugfixes).<br> <br>
Perhaps we should draft some small timeline for the future when we want to go to switch the main \
focus<br> on porting + cleaning for 5.0.<br>
<br>
We should coordinate a bit with the KDevelop guys, not sure how their plans for 5.x are, either.<br>
<br>
I would propose for Kate, to create some "frameworks" branch in December, in which the idea is \
to<br> <br>
a) first get it compiling with KDE 5 Frameworks + Qt 5.2<br>
b) then cleanup and fix the stuff in the interfaces<br>
<br>
This "frameworks" branch would have no BC/SC requirements until we arrive in the 5.0 Beta phase \
I think.<br> <br>
"master" should stay KDE 4.x until the last 4.xx release is done and then we can switch that \
over.<br> <br>
All stuff that goes into master after the frameworks branch is there must be synced to frameworks by<br>
the people doing the change, there won't be an auto-merge by me or someone else I think.<br>
<br>
This is just a bit brainstorming to kick this topic off, comments / changes are welcome :P<br>
<br>
Greetings<br>
Christoph<br>
<br>
--<br>
----------------------------- Dr.-Ing. Christoph Cullmann ---------<br>
AbsInt Angewandte Informatik GmbH Email: cullmann@AbsInt.com<br>
Science Park 1 Tel: <a href="tel:%2B49-681-38360-22" \
value="+496813836022">+49-681-38360-22</a><br> 66123 Saarbrücken Fax: \
<a href="tel:%2B49-681-38360-20" value="+496813836020">+49-681-38360-20</a><br> GERMANY \
WWW: <a href="http://www.AbsInt.com" target="_blank">http://www.AbsInt.com</a><br>
--------------------------------------------------------------------<br>
Geschäftsführung: Dr.-Ing. Christian Ferdinand<br>
Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234<br>
_______________________________________________<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kde.org">KDevelop-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kdevelop-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kdevelop-devel</a><br> \
</blockquote></div><br></div><div class="gmail_extra">Hi,</div><div class="gmail_extra">Good thing to see \
that you're interested in the porting. I would suggest to create a frameworks branch in kdelibs (just \
like kde-workspaces and kdelibs did) and just start working on it.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">As for KDevelop, 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.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Regarding dependencies, 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 XmlGui makes us depend on many many many things.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Aleix</div></div>
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic