Re: Moving KMime to Frameworks

--nextPartVpLQzbPBQ3Wmh8sPQtzV7A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Volker Krause <[email protected]>
To: [email protected], [email protected], [email protected]
Subject: Re: Moving KMime to Frameworks
Date: Wed, 15 Apr 2026 18:01:07 +0200
Message-ID: <[email protected]>
Organization: KDE
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0

With no objections here and based on discussions during the sprint in Graz=
=20
last week this will now go ahead after Gear 26.04 and for KF 6.27 (ie. earl=
y=20
May).

https://invent.kde.org/pim/kmime/-/merge_requests/209 contains the necessar=
y=20
changes for KMime, https://invent.kde.org/pim/akonadi-mime/-/merge_requests=
/36=20
shows forward-compatibility changes that we'll apply to consumer modules=20
beforehand for a smooth transition.

Regards,
Volker

On Samstag, 27. Dezember 2025 09:49:05 Mitteleurop=C3=A4ische Sommerzeit Vo=
lker=20
Krause wrote:
> Hi,
>=20
> 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 P=
IM
> libraries with uses outside of the PIM Gear modules to Frameworks.
>=20
> 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.
>=20
> As we haven't done such a move in the 6 era yet, here's a possible proces=
s/
> 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=
=2Ex
> 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.
>=20
> If we cannot keep that schedule, shift everything back by 3-4 months, so
> that the switch occurs after the 26.04 Gear branching.
>=20
> Would that work?
>=20
> Best regards,
> Volker


--nextPartVpLQzbPBQ3Wmh8sPQtzV7A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iHkEABECADkWIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCad+2QxsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMSwyLDIACgkQf5bM1k0S0ke8ogCfTx6ZyW38KZQBnIrj0wcD
ndSjZxkAoIpH0rWLuK1O08QyeyYDX1PbuB4s
=cjRe
-----END PGP SIGNATURE-----

--nextPartVpLQzbPBQ3Wmh8sPQtzV7A--