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.

Sign up for GitHub

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

Jump to bottom

Replace conventional-commit with reno #1080

Open
mnaser opened this issue Apr 10, 2024 · 2 comments
Open

Replace conventional-commit with reno #1080

mnaser opened this issue Apr 10, 2024 · 2 comments
Assignees
@mnaser
Labels
releng

Comments

@mnaser
Copy link
Member

mnaser commented Apr 10, 2024 •
edited by gtirloni
Loading

We're better off with following the same structure that exists within OpenStack such as reno.
@mnaser mnaser added the releng label Apr 10, 2024
@mnaser mnaser self-assigned this Apr 10, 2024
@gtirloni
Copy link
Contributor

@mnaser is the plan to continue to use release-please for release PRs and other automation and reno for changelog generation?

@mnaser
Copy link
Member Author

mnaser commented May 29, 2024

@mnaser is the plan to continue to use release-please for release PRs and other automation and reno for changelog generation?

I don't think so, I'd like us to get in the habit of using reno for release notes and we can add those to our docs on every release.

@okozachenko1203 okozachenko1203 mentioned this issue Sep 26, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mnaser mnaser

Labels
releng
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mnaser @gtirloni