release icon indicating copy to clipboard operation
release copied to clipboard

Package specs generator: split specs per minor release

Open xmudrii opened this issue 2 years ago • 11 comments

We should make sure that krel obs can support different package specs for each minor Kubernetes release. This is to ensure we can bump various dependencies (such as cri-tools) without affecting existing minor releases. For example, we might want to bump cri-tools to v1.26.0 only for Kubernetes 1.27+

/assign /sig release /area release-eng /priority important-soon

xmudrii avatar May 15 '23 18:05 xmudrii

/assign /sig release /area release-eng /priority important-soon

xmudrii avatar May 15 '23 18:05 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jan 20 '24 11:01 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jan 22 '24 10:01 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Apr 21 '24 11:04 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Apr 22 '24 09:04 xmudrii

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jul 21 '24 10:07 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jul 22 '24 16:07 xmudrii