Re: Moving KMime to Frameworks
Neal Gompa <[email protected]> Fri, 2 Jan 2026 04:04:36 -0500
| Newsgroups | gmane.comp.kde.releases,gmane.comp.kde.devel.frameworks,gmane.comp.kde.devel.pim |
|---|---|
| Message-ID | <CAEg-Je9N=bqF+YtFayOYuO6ztAja=DF9DLBM1w7N-5BcfFHSwQ@mail.gmail.com> |
On Sat, Dec 27, 2025 at 3:50=E2=80=AFAM Volker Krause <[email protected]> wro= te: > > 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 P= IM > 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 Ak= ademy > 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 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 i= n > 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? > It seems reasonable to me. --=20 =E7=9C=9F=E5=AE=9F=E3=81=AF=E3=81=84=E3=81=A4=E3=82=82=E4=B8=80=E3=81=A4=EF= =BC=81/ Always, there's only one truth!