Hello, Andreas Enge <andr...@enge.fr> writes:
> Hello Chris, > > Am Fri, Mar 28, 2025 at 10:31:26PM +0300 schrieb Christopher Baines: >> On tooling, as I say, QA used to attempt to build the first 2 or 3 >> branches. With the data service and build coordination being a bit >> faster now, I think building the first two branches might be >> feasible. That might compliment my previous point about optimising the >> order in which branches are merged, since we'll have more information on >> a number of branches, not just the one at the top of the queue. > > I noticed that you have enabled building of the second branch, > elogind-updates, on QA; so I have taken the liberty to rebase it on a > recent master commit that has been treated by the data service, so that > we get a comparison for the changes. AKAICT, the elogind-updates branch already provides sufficient feedback to chew on. Maybe we could juggle a bit more with branches and let QA build the next branch now, i.e., node-team? More generally, I think at first quick iterations, even if incomplete, are more useful than complete builds, which become necessary only when the branch is ready. Regards, -- Nicolas Goaziou
