-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Comments
/assign |
/triage accepted |
/priority backlog |
@nprokopic hey, just checking in the status here: is there any progress on this issue or do you need help with anything? |
/unassign @nprokopic |
@furkatgofurov7: GuidelinesPlease ensure that the issue body includes answers to the following questions:
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 In response to this:
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. |
I'll work on this issue. |
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 theMakefile
, rungo 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
The text was updated successfully, but these errors were encountered: