Create tooling to generate / manage KEPs

[justaugustus]

Create tooling to:

• generate KEP directories and associated metadata
• graduate KEPs through approval phases
• convert existing KEPs from flat-files to directory structure (Perform survey of KEPs and identify those needing update to directory format community#2725)

Work item for #617

/kind feature
/sig pm
/milestone v1.13
/assign @calebamiles

[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

[nikhita]

/remove-lifecycle stale

[spiffxp]

/milestone clear
ref #617 (comment)

[bgrant0607]

There were tooling comments here: #617 (comment)

@jdumars @calebamiles Is there a description of the tool you were working on somewhere?

[justaugustus]

/remove-milestone v1.14
/milestone keps-beta

[bgrant0607]

How about tracking KEPs?

Something like this could be useful, to populate a review backlog:
kubernetes/test-infra#9925

SIG Arch was doing this manually:
https://github.com/kubernetes-sigs/architecture-tracking/projects/2

[bgrant0607]

Note that tracking is made trickier since some may have PRs open and some may be merged in a provisional state.

[bgrant0607]

Regarding real experience with merging KEPs early/often:

It is possible to review KEP PRs after they've merged, but is harder to track responses to those review comments.

Example: Windows KEP updates: #676, #685, #729, #732, #739

[liggitt]

It is possible to review KEP PRs after they've merged, but is harder to track responses to those review comments.

Agree. In a flurry of merge early activity, there's also often no other place for comment than an already merged PR (c.f. #716 (review))

[liggitt]

it would also be extremely useful to have safeguards in place informing the merge bot so that KEPs don't accidentally transition to implementable state with no approvers listed, or without the listed approvers actually approving

[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

[nikhita]

/remove-lifecycle rotten

[justaugustus]

/unassign @calebamiles
/assign @dims @mrbobbytables @saschagrunert @jeefy

[jeremyrickard]

Would also be interested in helping with this when 1.18 is done.

[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

[palnabarun]

/remove-lifecycle rotten

[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.