[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-frameworks-devel
Subject: Re: KF5 branches
From: Volker Krause <vkrause () kde ! org>
Date: 2023-01-08 10:08:13
Message-ID: 5644571.DvuYhMxLoT () vkpc5
[Download RAW message or body]
On Sonntag, 8. Januar 2023 01:37:33 CET Luigi Toscano wrote:
> David Edmundson ha scritto:
> > There is now a "kf5" branch in all frameworks repos as discussed last
> > frameworks meeting.
> >
> > Starting now any commits that are also wanted in the next KF5 should
> > be cherry-picked after landing.
> >
> > This does *not* mean master is fully open for going into KF6 dev mode.
> > Now the kf5 branches exist, we'll set up tooling and infrastructure
> > and make sure that is all stable. Only after that is all sorted should
> > master start getting any Qt6-exclusive dev work and version bumps.
>
> Can't we quickly merge this repo-metadata branch:
> https://invent.kde.org/sysadmin/repo-metadata/-/tree/work/vkrause/kf5-branch
> ing-changes
>
> and namely this change, at least the changes to the i18n.json files?
>
> https://invent.kde.org/sysadmin/repo-metadata/-/commit/426669ff0f30d9839e5f8
> 9fbfb51eeffb69487bf
>
> I had to temporarily workaround it in scripty in order to only fetch kf5,
> but repo-metadata should be the source of truth.
> (we will have to create the infrastructure to handle the new kf6 i18n
> branches, but it can wait a bit I guess).
The corresponding merge requests are:
- https://invent.kde.org/sysadmin/repo-metadata/-/merge_requests/135
- https://invent.kde.org/sysadmin/ci-management/-/merge_requests/38
Integrating those would be the next step to switch infrastructure and tooling
to the new branches I think, only once that is confirmed to be working we can
start making changes in master again.
Regards,
Volker
["signature.asc" (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic