Remove periodic-enhancements-unfreeze job

[mrbobbytables]

Enhancement tracking issues should not rot out, they should be closed when their feature has graduated or removed for another reason.

/cc @BenTheElder @kikisdeliveryservice

[kikisdeliveryservice]

Agree on this. Closed issues need to have specific meaning/state, auto-closing reduces visibility and can cause loss of kep status clarity. Allowing authors to freeze would be useful.

/lgtm

[justaugustus]

Agreed with the current state assessment from @kikisdeliveryservice + @mrbobbytables, but linking #8637 for historical context:

Based on the current parameters for fejta-bot checks, issues will be closed after 90 days, after moving through various lifecycle/* phases.

The lifecycle/frozen label was introduced to ensure critical issues remain open. However, because Features issues should be reviewed and updated every release cycle (~90 days), I'd like to discourage / disable the use of the lifecycle/frozen label via automation.

This PR prevents issues in k/features from being marked as lifecycle/frozen

Slack convo: https://kubernetes.slack.com/archives/C09QZ4DQB/p1531154081000419

It's wonderful that enhancements are flowing in a way that this is no longer required!

xref current Slack convo: https://kubernetes.slack.com/archives/C1L57L91V/p1623189852047200
cc: @sftim @kubernetes/enhancements

/assign @BenTheElder @dims @fejta
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, justaugustus, kikisdeliveryservice, mrbobbytables

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/OWNERS [BenTheElder]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@mrbobbytables: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key fejta-bot-periodics.yaml using file config/jobs/kubernetes/test-infra/fejta-bot-periodics.yaml

In response to this:

Enhancement tracking issues should not rot out, they should be closed when their feature has graduated or removed for another reason.

/cc @BenTheElder @kikisdeliveryservice

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.