From kde-devel  Sun Nov 26 08:39:57 2023
From: laurent Montel <montel () kde ! org>
Date: Sun, 26 Nov 2023 08:39:57 +0000
To: kde-devel
Subject: Re: KDE Gear 24.02 feature freeze and branching
Message-Id: <73965057.1APyNdZLXW () localhost ! localdomain>
X-MARC-Message: https://marc.info/?l=kde-devel&m=170098803103841

Le samedi 25 novembre 2023, 21:05:10 CET Ingo Kl=C3=B6cker a =C3=A9crit :
> On Samstag, 25. November 2023 00:30:05 CET Albert Astals Cid wrote:
> > According to https://community.kde.org/Schedules/February_2024_MegaRele=
ase
> > feature freeze is 29 November (i.e. next week).
> >=20
> > Due to this release being a bit special we will create the branches a b=
it
> > later, a few days before RC1 (10 January 2024).
> >=20
> > This means that between 29 November and branching time, master in KDE G=
ear
> > repositories is bugfix only (Qt6 porting is allowed).
>=20
> I'm wondering how to deal with merges to master from kf5-based branches=20
where=20
> feature development will continue. Specifically, I'm talking about libkle=
o,=20
> kleopatra, mimetreeparser and probably a few other (PIM) projects. Featur=
e=20
> development (and bug fixing) continues in the kf5 branches for Gpg4Win an=
d=20
> related releases done by g10Code.
>=20
> I suppose the easiest solution would be to postpone any merges from kf5 t=
o=20
> master until KDE Gear is branched.

Ok I postpone it until kde grear is created
Regards.

>=20
> Regards,
> Ingo