Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add expandable auto-generated release notes for beta and RC (non-GA) releases #9319

Closed
nprokopic opened this issue Aug 27, 2023 · 7 comments · Fixed by #10091
Closed

Add expandable auto-generated release notes for beta and RC (non-GA) releases #9319

nprokopic opened this issue Aug 27, 2023 · 7 comments · Fixed by #10091
Assignees
Labels
area/release Issues or PRs related to releasing help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@nprokopic
Copy link

What would you like to be added (User Story)?

(Coming from #9104)

As a Cluster API release team member, I would like to be create auto-generated release notes for beta and RC (non-GA) releases the same like release notes are generated for GA releases.

Detailed Description

When running make release-notes for a pre-release, instead of outputting a static text defined in the Makefile, run go run ./hack/tools/release/notes.go to generate release notes for a beta/RC release.

This requires adding support for beta and RC releases to go run ./hack/tools/release/notes.go so that (expandable) release notes are generated automatically.

Release notes for a beta/RC release must have a clear signal on top that the release is a beta/RC.

Anything else you would like to add?

This issue could be considered obsolete if Cluster API project decides to switch to Kubernetes release-notes tool. For more details see #8292.

Label(s) to be applied

/kind feature
/area release

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. area/release Issues or PRs related to releasing needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 27, 2023
@nprokopic
Copy link
Author

/assign

@furkatgofurov7
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 28, 2023
@furkatgofurov7
Copy link
Member

/priority backlog

@k8s-ci-robot k8s-ci-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Aug 28, 2023
@furkatgofurov7
Copy link
Member

@nprokopic hey, just checking in the status here: is there any progress on this issue or do you need help with anything?

@furkatgofurov7
Copy link
Member

/unassign @nprokopic
/help

@k8s-ci-robot
Copy link
Contributor

@furkatgofurov7:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/unassign @nprokopic
/help

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 k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Nov 1, 2023
@chandankumar4
Copy link
Contributor

I'll work on this issue.
/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release Issues or PRs related to releasing help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Development

Successfully merging a pull request may close this issue.

4 participants