[NOTICE]: k8s-triage robot will not always be closing important triaged bugs

Skip to first unread message

Wojciech Tyczyński

Apr 22, 2022, 6:08:49 AMApr 22
to kubernetes-s...@googlegroups.com, le...@kubernetes.io, dev
  TL;DR; Issues marked with kind/bug, triage/accepted and priority/critical-*|important-* will no longer be closed by k8s-triage-robot. The lazy consensus deadline for it is Wed 27th 23:59 PST.

  As many of you have heard, we're trying to improve our quality bar by attacking it from different fronts. One of the important aspects of it is to ensure that important bugs will stop disappearing from our radars.
  As a result, we decided that issues that are labels by:
priority/critical-urgent, priority/important-soon, priority/important-longterm
 will not be closed by k8s-triage-robot. We will still be marking them as stale or rotten, but rotten issues will not be closed.
  This has been discussed on:
- during Community Meeting on Apr 21st (hopefully recording will appear soon)

 There are some follow ups we want to do including:
- ensuring that all SIGs are actually triaging their issues
- issues that aren't marked with any SIG label are also triaged
- provide some configurability for time-period to mark issues as stale/rotten/closed per repo
But those will not be blocking the change described above.

 We're targeting updating the robot on Apr 29th. Please respond to this email or comment on the issue of you have concerns about it.

Reply all
Reply to author
0 new messages