Moving KMime to Frameworks

[Volker Krause]

Hi,

I'd like to propose moving the KMime library (https://invent.kde.org/pim/
kmime/) to Frameworks. That's part of the long ongoing effort of moving PIM 
libraries with uses outside of the PIM Gear modules to Frameworks.

KMime basically implements the data format of email. It has been under KF-like 
stability guarantees in the 4 era already but ended up in Gear after the KF 
split in 5. Most recent API changes were the result of a review during Akademy 
in preparation of the KF move, ie. I'd not take this an indication on the 
ability to keep API/ABI stability.

As we haven't done such a move in the 6 era yet, here's a possible process/
timeline we discussed during the PIM sprint:
* Review/approve this until mid January (latest).
* Apply the build system and naming changes to comply with KF standards in 
KMime master
* Release KMime with KF 6.23 in February, continue to release KMime 25.12.x 
from the release branch as part of Gear.
* Depend on KMime KF 6.23 in PIM in time for 26.04, stop releasing KMime with 
Gear 26.04.

If we cannot keep that schedule, shift everything back by 3-4 months, so that 
the switch occurs after the 26.04 Gear branching.

Would that work?

Best regards,
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 232 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20251227/3d68c981/attachment.sig>