Aligning KF releases with Gear & Plasma dep freezes? (Re: KDE Gear 26.12 proposed schedule)

[Albert Astals Cid]

El diumenge, 20 de setembre del 2026, a les 17:46:56 (Hora d’estiu d’Europa 
central), Friedrich W. H. Kossebau va escriure:
> Am Donnerstag, 13. August 2026, 23:23:18 Mitteleuropäische Sommerzeit
> 
> schrieb Albert Astals Cid:
> > https://community.kde.org/Schedules/KDE_Gear_26.12_Schedule
> > 
> > Opinions?
> 
> One thing I just noticed while thinking about changes which affect both KIO
> /& KIO-Extra:
> the dependency freeze is one day before (assumed, not yet stated in docs) KF
> 6.32 tagging, the beta tarballing again one day before the (assumed) KF
> 3.32 release.
> 
> Which means one can only rely on KF 6.31 API released at begin of October in
> Gear software to be released in December. 2 months separation of library &
> app development synchronisation, is there any advantage here?
> 
> Did not track, has this issue of KF release dates been considered in the
> past? Could it be considered a bit in the future?
> 
> Perhaps KF tagging/releases could be shifted one week backwards in general,
> like tagging done at last Friday of month instead of first of month. to
> match Gear release date patterns?
> 
> What release date pattern does Plasma have here, to align dependency freeze
> & beta tagging with the targetted min KF dependency?

KDE Frameworks is released once a month, how much more aligning can we do?

I understand that this time there is some "bad luck" that makes it a bit 
"sad".

I would prefer not to introduce extra synchronization, the whole point of 
different products is that they are independent.

If you need an explicit exception for some feature I guess we can always 
discuss it?

Cheers,
  Albert

> 
> Cheers
> Friedrich