On Sun, Sep 1, 2019 at 12:40:50PM +0200, Bastian Blank wrote: > As mentioned during the last meeting, I would like to move the daily > builds out of the main debian-cloud-images project. The new project > reponsible for them would exist in a different group, so we don't longer > need to guard access to the main cloud-team group that strict. > > Disadvantages of this move: > - Visibility of daily builds is reduced as they are in a new group. > - Code and config updates for now need explicit changes in the -daily > (and the same in the already existing -release) repo to become active.
The second disadvantage recently came up in [1]. I proposed a possible fix for discussion at [2]. Bastian thought the discussion needed to happen on the ML, not salsa. So here we are! Context for others: currently, the daily builds don't use the latest tools/config from debian-cloud-images. Instead, a git submodule has to be occasionally updated. The change at [2] pulls the latest submodule before doing anything with the debian-cloud-image tools/config. That change assumes that we continue with a single common code base for the tools. If we break it into different branches/packages for different releases, [2] doesn't make sense. I'm not invested in the change - it's short enough that I found it easier to write a patch than to describe it. Ross [1] - https://salsa.debian.org/cloud-admin-team/debian-cloud-images-daily/-/issues/2 [2] - https://salsa.debian.org/cloud-admin-team/debian-cloud-images-daily/-/merge_requests/34