[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDE Gear 24.02 feature freeze and branching
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2023-11-27 4:53:10
Message-ID: 1840354.SL8RjpZkrB () xps15
[Download RAW message or body]

El dissabte, 25 de novembre de 2023, a les 21:05:10 (CET), Ingo Klöcker va 
escriure:
> On Samstag, 25. November 2023 00:30:05 CET Albert Astals Cid wrote:
> > According to https://community.kde.org/Schedules/February_2024_MegaRelease
> > feature freeze is 29 November (i.e. next week).
> > 
> > Due to this release being a bit special we will create the branches a bit
> > later, a few days before RC1 (10 January 2024).
> > 
> > This means that between 29 November and branching time, master in KDE Gear
> > repositories is bugfix only (Qt6 porting is allowed).
> 
> I'm wondering how to deal with merges to master from kf5-based branches
> where feature development will continue. Specifically, I'm talking about
> libkleo, kleopatra, mimetreeparser and probably a few other (PIM) projects.
> Feature development (and bug fixing) continues in the kf5 branches for
> Gpg4Win and related releases done by g10Code.
> 
> I suppose the easiest solution would be to postpone any merges from kf5 to
> master until KDE Gear is branched.

either that or have a branch work/newfeatures or something similar where you 
can all put commits to and then it can be deleted.

Cheers,
  Albert

> 
> Regards,
> Ingo




[prev in list] [next in list] [prev in thread] [next in thread]