release icon indicating copy to clipboard operation
release copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Detect and prevent incorrect categorizations for deprecations

Open msau42 opened this issue 2 years ago • 8 comments

What would you like to be added:

In 1.25, we deprecated glusterfs, but did not categorize the PR correctly as a deprecation, so the release note got buried and easily missed by users.

In 1.26 when we removed glusterfs, we again did not categorize the release note correctly, so the release note got buried again.

It would be great if we had some tooling or bot that could search for certain keywords in the release notes like "deprecate", and then flag/warn if they're not tagged properly.

Why is this needed:

This was a breaking change that was not elevated enough to users, and can catch people by surprise now as they're upgrading to 1.26.

msau42 avatar May 02 '23 21:05 msau42

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 19 '24 13:01 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jan 19 '24 18: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 18 '24 19:04 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Apr 19 '24 08: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 18 '24 09:07 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jul 22 '24 16:07 xmudrii