Add release note block to cherry-pick script

[ehashman]

What type of PR is this?

/kind cleanup
/sig testing

What this PR does / why we need it:

Cherry-pick script always is missing a release-note block, this adds one to fill in.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

@ehashman: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[ehashman]

/priority backlog

[ialidzhikov]

I think this approach is not a correct one. The script should rather use the rel note of the PR that is being backoported. Have in mind that the script can backport n PRs at once. Also I think that there is already a machinery that can collect release notes from backports without rel notes - the changelog of the patch releases should be generated via automation. So I am wondering even why we need such change.

[fejta]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ehashman, fejta

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:

• hack/OWNERS [fejta]

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

[ehashman]

I think this approach is not a correct one. The script should rather use the rel note of the PR that is being backoported. Have in mind that the script can backport n PRs at once. Also I think that there is already a machinery that can collect release notes from backports without rel notes - the changelog of the patch releases should be generated via automation. So I am wondering even why we need such change.

Because currently if you don't specify a release note on backport PRs, the merge is blocked: #103977 (comment) #103977 (comment)

[ehashman]

flake #100788
/retest

[fejta]

/lgtm

[dims]

/ok-to-test

[k8s-triage-robot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.