Change the release process to use GitHub Release Notes

[meghanajangi]

Signed-off-by: Meghana Jangi mjangi@vmware.com

What type of PR is this?
/kind feature

What this PR does / why we need it:
To change the release process to use GitHub Release Notes instead of the release-notes cli.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #3170
Fixes #2835

Special notes for your reviewer:
I have made the changes mentioned in the issue description except the following:

• Add any post generation header or footer text to generated markdown file.

Checklist:

• squashed commits
• includes documentation
• adds unit tests
• adds or updates e2e tests

Release note:

Change the release process to use GitHub Release Notes

[k8s-ci-robot]

@meghanajangi: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[k8s-ci-robot]

@meghanajangi: This issue is currently awaiting triage.

If CAPA/CAPI contributors 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.

[k8s-ci-robot]

Welcome @meghanajangi!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-aws 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-aws has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @meghanajangi. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[sedefsavas]

Also, we could have a section for Dependencies.

There is no specific kind used for those but /area release is used.

[meghanajangi]

Also, we could have a section for Dependencies.

There is no specific kind used for those but /area release is used.

Sure, I can add that.
Also had a few questions about some of the remaining labels:

• Would kind/proposal be under Documentation section?
• Should there be a separate section for kind/deprecation and kind/design?

[sedefsavas]

/ok-to-test

[Ankitasw]

/lgtm
@meghanajangi can you push a blank commit so that netlify error goes off

[richardcase]

@meghanajangi - just a couple of small comments on this one.

[richardcase]

@sedefsavas - i can't see anything else needed with this so from my side:

/lgtm

[sedefsavas]

We probably need to remove release-note plugin from Prow to remove release-note needed label:

  kubernetes-sigs/cluster-api-provider-aws:
    plugins:
    - golint
    - mergecommitblocker
    - milestone
    - milestonestatus
    - override
    - release-note
    - require-matching-label

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sedefsavas

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:

• OWNERS [sedefsavas]

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

[sedefsavas]

Created a PR for removing the release-note-needed label.
https://github.com/kubernetes/test-infra/pull/25762/files