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

List:       kde-i18n-doc
Subject:    Re: Gear: how to handle the i18n branches/stable/l10n-kf5 branch? (23.08 or 24.02)
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2024-01-10 23:19:09
Message-ID: 14328339.3DqgzJOKfe () xps15
[Download RAW message or body]

El dimecres, 10 de gener de 2024, a les 22:13:34 (CET), Luigi Toscano va 
escriure:
> Hi all,
> 
> the last release of Gear 23.08 (23.08.5) is planned at the beginning of
> February. On the other hand, we need to create the stable branches for
> Gear, which means pointing the branches/stable/l10n-kf5 branch now and have
> it point to the bits of Gear which are still KF5-based.
> 
> I see 3 possible outcome:
> 
> - drop scripty tracking for those branches, release 23.08.5 with whatever we
> have now in branches/stable/l10n-kf5, and start using
> branches/stable/l10n-kf5 for the remaining of KF5 Gear modules. It is less
> than a month and I don't see us losing much;
> 
> - create a special branch to track 23.08.5;
> 
> - restrict 23.08.5 to just the modules which are ported to KF6 in 24.02.
> This way we could use branches/stable/l10n-kf5 to track all remaining KF5
> modules: the ones still in 24.04 and the other still at 23.08.

Personally I prefer "option 4":

* trunk-kf5 tracks KDE Gear 24.02 until 23.08.5 is released
* stable-kf5 tracks KDE Gear until 23.08.5 is released

After that we switch back trunk-kf5  to track KDE Gear master and stable-kf5  
to KDE Gear 24.02

The only downside I see in this option is that KDE Gear master is not tracked 
for a while, but that should not be a problem at all.

Cheers,
  Albert

> 
> Unfortunately we need to decide before tomorrow, January 11th...
> 
> Ciao




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