Sascha Grunert

icon indicating a website link http://saschagrunert.de icon indicating an email [email protected]

icon company Red Hat icon location I’m on earth right now. icon location The difference between fine and great software is listening to people.

Results 1324 comments of Sascha Grunert

RUSTSEC-2024-0370: proc-macro-error is unmaintained

Related to https://github.com/containers/oci-spec-rs/issues/209

Integrate `krel obs` into the release process

The automation will happen in this repository, we can also consider moving the specfile here.

Integrate `krel obs` into the release process

@kubernetes-sigs/release-engineering how about: 1. Creating a bot account similar to CRI-O to be able to publish packages for cri-tools 2. Move the specfile into this repository 3. Create an publish...

Integrate `krel obs` into the release process

@xmudrii I'd like to try a full automation here, means we would require a service account being able to push to https://console.cloud.google.com/storage/browser/k8s-artifacts-cri-tools. Can we create on in [kubernetes/k8s.io](https://github.com/kubernetes/k8s.io)?

Integrate `krel obs` into the release process

@xmudrii closing the loop: https://github.com/kubernetes/k8s.io/issues/5957

Integrate `krel obs` into the release process

/remove-lifecycle stale

Integrate `krel obs` into the release process

We still need this, and could also think about proposing an automated vendor PR for the RC of a new Kubernetes version. This could include a hint that we may...

Integrate `krel obs` into the release process

@xmudrii do you plan to work in this before v1.31 get's released?

Integrate `krel obs` into the release process

Let me know if you need anything, would be awesome to deliver it this cycle.

Integrate `krel obs` into the release process

@xmudrii I'm planning to release cri-tools v1.31 this week. Do we still want to invest in automation or plan that for 1.32?