ci-utilities files to update when branching KDE Gear

[Ben Cooksley]

On Mon, Apr 21, 2025 at 9:11 PM Albert Astals Cid <aacid at kde.org> wrote:

> My notes for branching KDE Gear say
>
>  - Update the "*signer-projects.yaml" and "macappnotarizer-projects.yaml"
> files in ci-utilities/signing
>
>
> Should I also be doing that for the *publisher-projects.yaml files?
>
> Or maybe that should wait for the publishing day?
>

We can add multiple branches so my recommendation would be to add the new
branch on branching, removing the previous discontinued branch when doing
so.
(ie. when adding release/25.04 you would remove release/24.08, leaving a
list of release/24.12 and release/25.04)

The buildpublisher-projects.yaml list should be updated in addition to
*signer-projets.yaml yes.


> Or do we expect people doing the actual releases on
> fdroid/googleplay/microsoftstore to do that on their own?
>

For fdroidpublisher-projects.yaml that is just to our nightly repository so
you can update that one as well if you want.

The Google Play and Microsoft Store ones require taking action on the Store
front side, so not automatically updating them will allow us to better spot
unmaintained builds and unpublish them.


>
> Cheers,
>   Albert
>
>
>
Cheers,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/release-team/attachments/20250422/1846e02e/attachment.htm>