KDE Frameworks 5: Rhythm

Kevin Ottens ervin at kde.org
Sat Jan 21 19:34:22 GMT 2012

On Saturday 21 January 2012 16:17:38 Stephen Kelly wrote:
> Kevin Ottens wrote:
> > There's three main reasons for this rhythm:
> >  * Qt 5.0 feature freeze is upon us now;
> >  * CMake 2.8.8 will be released in April;
> >  * it'd be nice to release KDE Frameworks 5.0 at Akademy[*].
> You mean 'some of the frameworks'? They won't all be done by then. More
> stuff will need to get into Qt before that's possible.

Yeah, I know a couple of them will need some merging scheduled for Qt 5.1 
already (like equivalent to KSaveFile for instance). But if I reintroduce the 
few words I forgot to type which were "a technology preview of" I think it's 
doable. It means it'd build against "qt master" likely earmarked to become 

> > To that effect we did some modifications to the active wiki pages:
> >  * Now we have one page per Qt version we want to target for pushing
> >  features
> > 
> > in Qt, the Qt 5.0 page contains the really critical stuff we want to see
> > achieved:
> > http://community.kde.org/Frameworks/Epics/Qt_5.0_Merging
> Some of the stuff on that page that isn't close to done is almost impossible
> at this point.

Come on, it's just *almost* impossible? So still deserves to be attempted. :-)

> * command line arguments - potential bikeshed. Discussion would have been
> needed weeks ago on the Qt5 list for it to be possible. Is anyone driving
> it? If it really can't wait until Qt 5.1 there needs to at least be a
> subtask for it here: https://bugreports.qt.nokia.com/browse/QTBUG-20885
> * KAction/QAction stuff - Don't know what's needed. If QAction needs new
> virtual method that would need to be determined soon. Is anyone driving
> that? Again, needs subtask here if it's going to happen:
> https://bugreports.qt.nokia.com/browse/QTBUG-20885
> * Ssl stuff - I don't know.
> * i18n - AFAIU nothing is going to happen in that area.

Yep, that one we can do without.

> * refcounted quit - might happen.

I actually wanted to talk to you about that one. Didn't you have a patch aeons 
ago? What happened to it.

> * locale stuff - Don't know. Depends on John.
> * timezone - I want to take ownership and 'do what python does'
> https://bugreports.qt.nokia.com/browse/QTBUG-23509, which David confirmed
> the sense in, but waiting on response from John.
> * Thiagos stuff - I don't know.
> If all of that stuff is going to move along, the actions need to happen on
> Qt lists and review trackers basically within 2 weeks or sooner.

Known open issues, and perfectly valid questions above. Those would have to be 
answered by David though who is coordinating the efforts for Qt merges, I've 
only a high level overview there (for the record I sent him an email along the 
same lines this morning).


[*] That said this mistake of mine in the previous email could have been a 
lapsus in the true sense. Now that we pointed it out (and no it definitely 
wasn't in my plans), it makes me wonder if around that time we wouldn't end up 
in a situation where we'd only miss a handful of class which aren't used in 
API... the list we have targetted for 5.1 seems to indicate that. So a small 
statically linked library with those class would allow us to release against 
Qt 5.0. Again, not making plans, but to keep in mind maybe once we get closer 
to a splitted kdelibs world.
Kévin Ottens, http://ervin.ipsquad.net

KDAB - proud patron of KDE, http://www.kdab.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20120121/f42e94e7/attachment.sig>

More information about the kde-core-devel mailing list