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

Should we add a CHANGELOG? #15

Open
davidhewitt opened this issue Oct 25, 2024 · 2 comments
Open

Should we add a CHANGELOG? #15

davidhewitt opened this issue Oct 25, 2024 · 2 comments

Comments

@davidhewitt
Copy link
Member

As per title. I think these can be nice user-friendly documents :)
@cjdsellers
Copy link
Collaborator

This is a good idea, we could just use the same format as the PyO3 CHANGELOG.md.

Should we start from this release though (or add some previous history as well)?

@davidhewitt
Copy link
Member Author

Agreed; I like the PyO3 format 😉

I am happy if we just start from the current version, I think it might be a ton of work to extract history, with diminishing returns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@davidhewitt @cjdsellers