Removing Qt4 in Strech

[Scott Kitterman]

On April 16, 2015 6:29:17 PM EDT, "Lisandro Damián Nicanor Pérez Meyer" <perezmeyer at gmail.com> wrote:
>On Thursday 16 April 2015 22:37:52 Andreas Cord-Landwehr wrote:
>> On Thursday 16 April 2015 15:58:58 Scott Kitterman wrote:
>[snip] 
>> Hi, the porting progress of KDE Applications is currently working
>quite
>> nicely IMO. An overview on what currently is already ported is e.g.
>here:
>> 
>>   http://developer.kde.org/~cfeck/portingstatus.html
>> 
>> Yet some important applications (e.g. the whole of PIM, Okular,
>Calligra...)
>> have not seen any Qt5/KF5 based release yet. Trying to not make too
>bold
>> statements, my gut feeling is that the KDE Applications release after
>15.08
>> (probably around X-Mas) should provide ports for "most" of the
>> applications, making early 2016 sound a feasible date. If you add 4
>more
>> months for another Applications release cycle for safety, there
>should have
>> been two Qt5/KF5 based release cycles for most applications at spring
>2016.
>> 
>> Talking about the Workspace, it is already quite usable IMO (whereas
>I am
>> running master branches).
>
>Thanks you all for the feedback!
>
>Having KDE at that guesstimate of june/july 2016 is actually quite
>good, 
>although it would have been better sooner for other non-KDE stuff to
>follow. 
>Anyways good news :)
>
>Does any of you think of any way to gently push people to port their
>stuff to 
>Qt5 without calling it a "removal" at once? I do understand that we
>might not 
>be able to remove Qt4, but I *think* we should start pushing it
>somehow. I'm 
>open to other ideas :)

If you look at what paultag started regarding python3 migration (see dda), I think that's a good model for creating positive motivation to work on porting thing.

Scott K