Open BenTheElder opened 4 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/lifecycle frozen
As discussed previously in https://github.com/kubernetes/test-infra/issues/31728#issuecomment-2025662460
Prow at minimum will have to go through https://github.com/kubernetes/k8s.io/issues/1343 but will be special because other affected projects (at least as far as we know) serve users through registry.k8s.io already so the migration is less pressing ...
Really, we should be promoting images, along with tagging releases, now that we have a repo dedicated to prow.
/kind bug /priority important-soon