On Fri, Jul 25, 2025 at 11:03:35AM +0200, Andreas Enge wrote: > > I know how to create branch evaluations, and have just done so for the > > audio-team branch, with builds on x86_64 and i686. Thank you!
> And now I see that you called the branch "audio". I would suggest to > keep with the "audio-team" name to be consistent with other teams, > and so have pushed the audio branch under this second name as well. Sorry, I didn't realize this was a policy (since many branches are not directly named `foo-team'). > (I had created such a branch before you became committer, and it > existed with just an old master commit at the top.) I know, I renamed it since I liked "audio" for branch name better. > I would suggest to delete the audio branch. (However, the name of the > evaluation on CI is audio, sorry.) > https://ci.guix.gnu.org/jobset/audio Now I am confused. Why is the CI jobset not called audio-team? I do not have strong opinions on the names but would prefer consistency. Scrolling through the branch names and thinking of it, i guess `audio-updates` fit best, since not all team-audio changes will end up in that branch, only the ones causing significant package rebuilds. WDYT? Also: what exactly does this jobset evaluate/build? Could we restrain it to just build some essential audio/multimedia tools and/or leaf packages (audacity, ffmpeg, mpv, mixxx) and not (what seems now to be the case) /everything/ even when not touched by any audio changes?
