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

Create a CHANGELOG #243

Open
ianthetechie opened this issue Sep 13, 2024 · 1 comment
Open

Create a CHANGELOG #243

ianthetechie opened this issue Sep 13, 2024 · 1 comment
Assignees
@ianthetechie

Comments

@ianthetechie
Copy link
Contributor

We state in our contributing policy that we have a CHANGELOG, but we don't! h/t to @michaelkirk for pointing this out.
@ianthetechie ianthetechie self-assigned this Sep 13, 2024
@ianthetechie ianthetechie mentioned this issue Sep 13, 2024
Merged
@ianthetechie
Copy link
Contributor Author

To keep the releases from getting silly at the moment where (nearly every merge is useful to turn into a release), I think we can defer this until we hit 1.0. I do publish notes for each release including call-outs for breaking changes, so the practical necessities are there. After we hit 1.0 (a reasonable measure of API stability with ~a dozen production apps using it), a changelog will be much more useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ianthetechie ianthetechie

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ianthetechie