[Kde-pim] Releasing KHolidays as a Framework

[John Layt]

On 2 September 2015 at 08:57, Volker Krause <vkrause at kde.org> wrote:

> Just an idea: While the clean and minimally disruptive porting approach would
> indeed be branches, I think considering the special KDateTime case we could
> probably also live with temporary breakage. E.g. kcalcore is ported and we
> have clear and reasonably complete instructions on how to port its users, we
> could merge that at an agreed point in time and then for a few days all
> together focus on KDateTime porting. Certainly a lot more disruptive and
> risky, but then we would be done with this once and for all. IOW, quick and
> painful for everyone vs. long and painful for John.
>
> Anything in between those two extremes is of course also possible, like
> porting some of the particularly challenging KDateTime users in a branch, and
> do the rest together in master.

I had a quick look at the other pimlibs last night, and really the
only stuff using KDateTime is the KCalCore / KCalUtils / KAlarmCal
stack and whatever uses them, so the first task is to get that all
working together. Once that works then it's porting kdepim apps to use
them. In the interim though we could try port stuff that doesn't reply
on kcalcore, e.g. kmail and kaddressbook perhaps could be ported first
without worrying about waiting for kcalcore et al? That could greatly
reduce the size of the potential breakage? I'll have a poke at that
tonight.

John.
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/