Adjusting PR boilerplate and labels to improve Release Notes UX

[onyiny-ang]

There was some discussion during this release cycle and in slack about collecting more information from each PR in order to improve the user experience for release notes and ease curation for the release notes team.
This boils down to 3 main improvements:

1. Collecting KEP numbers associated with any PRs that work towards implementing a KEP.
2. Collecting the Primary-sig or sponsoring SIG associated with each PR to eliminate guess work for the release notes team.
3. Labeling the PR as a deprecation if it is a deprecation to a dependency.

I would like to propose a subform--or in any case, more detailed release note section of the k/k PR boilerplate that ensures a contributor fills out the Primary SIG section and has a space to associate a KEP # if it is appropriate. A label to indicate deprecations would be great.

[onyiny-ang]

/cc @tpepper @justaugustus @jeefy @saschagrunert @lachie83 @jberkus
/sig release

Ideally we would like to have some (or all) of these things available starting in the 1.16 release

[justaugustus]

/area release-team
/kind design documentation
/milestone v1.16
/priority important-soon
/help

[jeefy]

/assign @saschagrunert

[saschagrunert]

I think the only related PR is kubernetes/kubernetes#81278, which we either have to finish or postpone to the next release.

[saschagrunert]

Please take a look at the two linked PRs, we decided to split up the work a bit more.

[alejandrox1]

/milestone v1.17

[guineveresaenger]

We are waiting on some automation and decisions around proposed labels here.

This won't make the 1.17 milestone.

/milestone v1.18

[justaugustus]

I think we can close the loop on this before 1.17 is out.
/milestone v1.17

[saschagrunert]

I propose that we close this issue now. If we're going to sort the notes by kind then we would not need a primary SIG at all, WDYT?

[justaugustus]

This needs to stay open until we have a community decision on kind vs SIG.
See here: kubernetes/release#923 (comment)

I'll send a note out next week since US folks are on holiday now.
/remove-help
/unassign
/area release-eng

[saschagrunert]

@justaugustus I think we can close this issue, what do you think?

[alejandrox1]

Just confirmed with @justaugustus that it is cool to close this one
/close

[k8s-ci-robot]

@alejandrox1: Closing this issue.

In response to this:

Just confirmed with @justaugustus that it is cool to close this one
/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.