-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Change CHANGELOG to 'Keep a changelog' format #824
Comments
Thanks for the info and a PR is welcome. I guess that the second level bullets can be kept as I'm not sure what you meant about the newline usage. Where, exactly, does it deviate from the spec as of now? |
Btw, I just noticed a bug in the current version of the Music app, and I assume that I need to release 1.0.2 soon (although I haven't yet investigated the issue throughoutly). But if the PR doesn't make it in time for 1.0.2, then there's of course new releases coming later. |
Great! The changes are in PR #827. Regarding the newlines, there were some unnecessary newlines in early releases. Not a big deal :). |
The PR has been merged, case closed! |
Music v1.0.2 is now out, and the changelog now shows up in the Nextcloud app management as intended. |
Awesome, thanks! |
It would be awesome if the current changelog format is changed to the 'Keep a changelog' format. Nextcloud recommends this for its apps. A benefit is that the entry of the most recent version is shown in the 'Apps' section of a Nextcloud installation. This makes it easy for admins to see what's new :)!
I'd be happy to create a PR to change the format. Some instructions about what to change would be nice. Some notions/questions:
CHANGELOG
toCHANGELOG.md
v1.0.1 2021-02-13
to## 1.0.1 - 2021-02-13
0.2
and0.1-alpha
the same*
to-
, but what to do with the indented lines? I'm not sure if this follows the format, but I guess it doesn't matter muchThe text was updated successfully, but these errors were encountered: