Please reconsider planned build breakage on new KF deprecations

[Ahmad Samir]

[...]

Hello. My meagre 2p's :) :

How about staggering it by one KF release? i.e. latest stable KF release is 5.85, build with no
deprecations from 5.84, this way code will still build and you have a longer period to port the code
(and you let other PIM contributors help you carry the burden of porting away from deprecated
methods in KF, IMHO, this is more beneficial in the long run, because we get more contributors).

It's the same logic used in KF, IIUC; right now the version is 5.86 in master, but the min. required
version is still 5.85, so that contributors can still build from source and keep working on their
patches/changes/feature, without having to immediately update all KF packages once a release happens.

Have a good day.

-- 
Ahmad Samir