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

List:       kde-release-team
Subject:    Re: MegaRelease Freezes - Re: Release schedule proposal for the February MegaRelease
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2023-10-03 20:57:57
Message-ID: 1953550.9L78OJEMnJ () xps15
[Download RAW message or body]

El dimarts, 3 d'octubre de 2023, a les 7:13:52 (CEST), Justin Zobel va 
escriure:
> Plasma depends on kexiv in Gear so Gear would need to be before Plasma.

Why?

We just need that if someone changes API in kexiv they change the code in all 
places that use it.

Do you freeze parts of Plasma before other parts of Plasma just because they 
depend on each other? 

Probably not, then why do we need to do that procedure for kexiv?

Cheers,
  Albert

> 
> On 3/10/23 02:29, Aleix Pol wrote:
> > On Tue, Sep 26, 2023 at 12:29 AM Albert Astals Cid <aacid@kde.org> wrote:
> >> El dimarts, 26 de setembre de 2023, a les 0:28:15 (CEST), Albert Astals
> >> Cid va>> 
> >> escriure:
> >>> https://community.kde.org/Schedules/February_2024_MegaRelease
> >>> 
> >>> Beta 1 is during Qt World Summit that is not ideal but I guess doable?
> >>> 
> >>> I'll answer to this email with a few other emails things i thing we have
> >>> to
> >>> discuss to try to organize the discusion earlier.
> >> 
> >> Do we want common times for dependency/feature/string freezes for all the
> >> 3
> >> products or different for each of them?
> >> 
> >> I have no particular opinion.
> > 
> > I'd say that by nature KF needs to freeze before Plasma & Apps.
> > 
> > I don't think there's any difference between apps and Plasma.
> > 
> > I'll include the Plasma and Frameworks lists JIC.
> > 
> > Aleix




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