[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Proposing 2025 workflow changes for Go team



Hi,

On 08/12/24 2:16 am, Otto Kekäläinen wrote:
Hi!

On Sat, 7 Dec 2024 at 05:45, Nilesh Patra <nilesh@riseup.net> wrote:
On 07/12/24 5:37 pm, Simon Josefsson wrote:
I think we exagerate the salsa CI load concerns. My perception is that
while the Go package system is substantial, the churn is actually fairly
low and building Go packages is much faster than most Debian packages.
   Remember that the CI only runs after a manual human commit and push.
It usually takes more time for a human to think about and commit a
change than CI consumes to run a pipeline for it.

While I agree with this, I'd still prefer to err on the side of caution
and let the salsa CI admins know about this first.

There are 1000+ packages in the team. This may cause a sudden spike.

By proposing to merge
https://salsa.debian.org/go-team/infra/pkg-go-tools/-/merge_requests/2
I am erring on side on caution. After that is merged, it will be a
very slow rollout as no package updates automatically, and even after
a package has been updated to include this, a human needs to trigger
the CI.

ACK.

The https://salsa.debian.org/go-team/infra/pkg-go-tools/-/merge_requests/2
has now two thumbs up. Who are the decision makers in the Go team, is
there a specific person who should share ther opinion before we
proceed? How long do you suggest I wait before merging it?

zigo, creekorful and faustin have been managing the CI thus far. I am not sure if any of them except zigo are still active.

I am also waiting for Shengjing's opinion. I suppose if there are no
objections in a month it maybe sane to step ahead.

-n


Reply to: