[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:       Joseph Wenninger <jowenn () kde ! org>
Date:       2013-11-10 10:53:58
Message-ID: 0EF50A6D-BFD9-4215-A937-0C1BE3A092EE () kde ! org
[Download RAW message or body]

Hi!

The sooner we start porting, the more time we have for bug fixing and stabilizing again. Are all things \
we need in KF5 (at least somehow) by now?

Coordination with KDevelop/Kile is important.

KF is a big switch, so I guess there will be along beta phase. Of course at that point we should not \
break API BC/SC just for fun, but I think it a soft freeze should start and a hard API freeze should \
start with KF5 RCs. Reasoning, I think some users of the API will start porting quite late (e.g. Kile), \
therefor if we overlooked something we should be able to fix the problems and not start with workarounds \
and hacks on 5.0.1.

Best regards, 
Joseph

> Am 09.11.2013 um 13:04 schrieb Christoph Cullmann <cullmann@absint.com>:
> 
> 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 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 enhancements 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 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 someone 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ücken                      Fax:   +49-681-38360-20
> GERMANY                                WWW:   http://www.AbsInt.com
> --------------------------------------------------------------------
> Geschäftsführung: Dr.-Ing. Christian Ferdinand
> Eingetragen im Handelsregister des Amtsgerichts Saarbrücken, HRB 11234
> _______________________________________________
> KWrite-Devel mailing list
> KWrite-Devel@kde.org
> https://mail.kde.org/mailman/listinfo/kwrite-devel
_______________________________________________
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]