--nextPart1787711.VLH7GnMWUR
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"; protected-headers="v1"
From: Ingo =?ISO-8859-1?Q?Kl=F6cker?= <kloecker@kde.org>
To: kde-windows@kde.org
Date: Wed, 07 Feb 2024 21:58:56 +0100
Message-ID: <5915127.MhkbZ0Pkbq@daneel>
In-Reply-To: <2390005.cojqenx9y0@klux>
MIME-Version: 1.0

Hi Friedrich,

TL;DR: You are confusing the Flatpak jobs with our CI/CD jobs in general.

On Mittwoch, 7. Februar 2024 19:48:27 CET Friedrich W. H. Kossebau wrote:
> So effectively this means:
> * KF - no CI on new API with non-KF repos, only KF-internal CI

Not true. The CI uses whatever you specify in the project's .kde-ci.yml. If 
you specify @same for the dependencies in your project's master branch (or an 
MR targeting master) then CI will use the master branch of those dependencies.

Currently, @latest-kf6 also means master for frameworks. See
https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/branch-rules.yml

> * KF - no CD, only released versions

Also not true. You can use master of everything (built with Craft). In fact, 
we have done this for many of the Craft builds during the transition period. 
But, as Ben wrote, it's discouraged to waste energy to rebuild master of all 
dependencies for each build.

I haven't read the rest of your rant because it's based on wrong assumptions.

Regards,
Ingo
--nextPart1787711.VLH7GnMWUR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCZcPvEAAKCRCxb1mVFkdK
umEzAQDUr8Pb7zF1a6w+J/WCA+hMt6l008efAqBt64/eGPDdXAD+JCut+3tx+fEX
3+PGXViRX29GxoMAnkfuAhIpSyuM0g4=
=RCt5
-----END PGP SIGNATURE-----

--nextPart1787711.VLH7GnMWUR--