Nuke 'triage' labels / replace them with 'lifecycle' or other

[nikopen]

Triage labels are a bit old and unused. Following discussions on https://groups.google.com/forum/#!topic/kubernetes-sig-contribex/BvGmOQ0v5f0 , the proposal is to instantiate a new workflow roughly defined at the discussion above and here kubernetes/test-infra#11818 (comment) - introduce a new label that allows SIGs to sort new issues and filter valid ones / label them / organize upcoming work in an approximately scheduled way.

As a first step, the proposal is to nuke and reclaim 'triage' labels so they are not confusing anyone.

Further idea for a replacement is to use the 'lifecycle' labels, which can be reworked and actively used more.

Roughly:

1. Auto-label 'lifecycle/active' (which means 'in progress') when someone is assigned into an issue.
2. 'lifecycle/stale' automatically kicks in in 90 days currently - might be useful to have something milder for 30 days, only when 'lifecycle/active' is already there
3. 'lifecycle/active' gets removed when issue is closed.
4. Perhaps rename 'lifecycle/active' to 'lifecycle/inprogress' to be more clear
5. Absorb any 'triage' labels that can be useful into 'lifecycle'.
   Current triage labels from the (outdated) https://github.com/kubernetes/community/blob/master/contributors/guide/issue-triage.md#closing-issues:

    triage/support: Indicates an issues is not a bug but a support request.
    triage/duplicate: Indicates an issue is a duplicate of other open issue.
    triage/not-reproducible: Indicates an issue can not be reproduced as described.
    triage/needs-information: Indicates an issue needs more information in order to work on it.
    triage/unresolved: Indicates an issue that can not be resolved.

/sig release pm contribex
/milestone v1.15

[nikhita]

/milestone May

[nikhita]

I think this still needs discussion + communicating with lazy consensus after any changes have been made. We definitely won't get this in for the current milestone with KubeCon around the corner.

/milestone Next

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nikopen]

/remove-lifecycle rotten
/reopen

[k8s-ci-robot]

@nikopen: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[justaugustus]

/remove-sig pm
/assign

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[mrbobbytables]

/remove-lifecycle stale

[nikhita]

PR to add the needs-triage workflow - kubernetes/test-infra#19272

[nikhita]

Closing since we have the needs-triage and triage/accepted workflow now. Please reopen if needed.

/close

[k8s-ci-robot]

@nikhita: Closing this issue.

In response to this:

Closing since we have the needs-triage and triage/accepted workflow now. Please reopen if needed.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.