Re: Stable branches, including frameworks for Kubuntu LTS

2Albert Astals Cid <[email protected]> Tue, 12 May 2026 22:45:10 +0200
Newsgroups gmane.comp.kde.devel.core,gmane.comp.kde.devel.frameworks
Message-ID <[email protected]>
El dimarts, 12 de maig del 2026, a les 20:13:01 (Hora d=E2=80=99estiu d=E2=
=80=99Europa=20
central), Marco Martin va escriure:
> On Tue, May 12, 2026, 18:15 Marco Martin <[email protected]> wrote:
> > We (as in Techpaladin) pledge to take up the maintenance of such branch=
 as
> > long as it's supported, managing backports, testing and releases, as we=
ll
> > as keeping the new CI nodes green
>=20
> What do you think about it? Is something that looks sensible on the
> upstream/community point of view?

Apologies if the next question sounds a bit blunt I didn't figure out how w=
ord=20
it in a somewhat better way.

Is this something we want to pretend the community is doing?

That is, do we want to try to make this "a KDE thing" or is it clearly=20
structured as a Techpaladin/Kubuntu Focus thing?

=46or me the second option makes it "simpler".

Then my suggestion would be to just create "vendor" branches like the ones=
=20
that we have for example in kleopatra/mimetreeparser/friends

  gpg4win/23.10
  gpg4win/24.05
  gpg4win/gpd-5.0
  gpg4win/gpd-5.1

So create something like kubuntufocus/26.04

Maybe it would even make sense to create such branches for KDE Plasma 6.6=20
(after final 6.6.6 is released) and KDE Gear 25.12?

Cheers,
  Albert

>=20
> --
> Marco Martin