Re: Stable branches, including frameworks for Kubuntu LTS

Hi,

from the discussion it appears that the intention is to provide a=20
generic stable branch that isn't inherently specific to Kubtuntu,=20
Kubuntu Focus, or Techpaladin. This matches the development for Plasma=20
and Gear.

With this in mind I have no objections, and would suggest to use=20
Frameworks/6.24 as branch name.

There's one question that needs figuring out though: Should the branch=20
be enabled for translations? Technically that shouldn't be much of a=20
problem, but it's worth discussing whether this is a good use of=20
translators time and energy.

Cheers

Nico

On 5/18/26 5:44 PM, Nate Graham wrote:
> To help move this forward, are there any formal objections to=20
> Techpaladin people (Marco, me, possibly others) creating stable=20
> branches for frameworks that we would maintain by backporting=20
> bug-fixes already on master to, and making releases from those=20
> branches as needed?
>
> Nate
>
>
>
> On 5/14/26 10:44 AM, Nate Graham wrote:
>> On 5/14/26 10:38 AM, Allen Winter wrote:
>>> not sure if this is clear:=C2=A0 you'll fix the bugs in the master=20
>>> branches and backport those fixes to the current release branch and=20
>>> to the LTS branch?
>>> and you won't add new features as this is only about fixing bugs?
>>
>> That's correct. This effort is about backporting public bug fixes=20
>> already on master, not doing private feature development.
>>
>> Plasma and Gear already have stable branches that can be used for=20
>> this; the discussion here is really mostly about creating such a=20
>> thing for a specific Frameworks release so the same thing can be done=
=20
>> for it.
>>
>> Nate
>