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.

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

Update CHANGELOG.md, follow keepachangelog format #709

Merged
merged 2 commits into from
Dec 24, 2021

Conversation

Art4
Copy link
Contributor

@Art4 Art4 commented Dec 20, 2021

I've noted that the CHANGELOG.md was not updated since 1.5.5, so I updated it. And I formated the file to follow the keepachangelog.com format.

I couldn't find a note if this project adheres to Semantic Versioning as I assumed in the CHANGELOG.md, so please correct me if I'm wrong.

CHANGELOG.md Show resolved Hide resolved
CHANGELOG.md Outdated
## [1.5.7](https://github.com/simplepie/simplepie/compare/1.5.6...1.5.7) - 2021-12-19

* Fix PHP8 crash due to insufficient isset test by @Alkarex in #670
* gitignore tests by @Alkarex in #671
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, the changelog should be curated and not contain inconsequential stuff like CI changes. Author names are probably too noisy for it.

Copy link
Contributor Author

@Art4 Art4 Dec 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The format stated that Changelogs should be written for humans. Since I copied the text from the release page, it means to me that the maintainers decided to keep this info in the Changelog, so did I. But removing or rewriting those changes could be done in this or an next PR. This is up to the maintainers.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I interpret being written for humans as reducing noise since humans do not deal with it very well. Similarly, reader probably does not care who contributed each feature so I would suggest moving acknowledgements into a paragraph at the end – there we can thank the contributors while keeping the list of changes clean. But yeah, this is largely up to maintainers and their preferences.

CHANGELOG.md Outdated Show resolved Hide resolved
@Art4
Copy link
Contributor Author

Art4 commented Dec 20, 2021

Some thoughts on backwards compatability.

A comment from 2017 by @skyzyx suggests that this project adheres to Semver and that "we should be responsible about messaging BC breaks". (But I don't see that confirmed or documented anywhere.)

The CHANGELOG.md and adhering Semver solve both of these problems. In the CHANGELOG.md deprecations can be documented. And breaking changes are only introduced via new major version and are documented in the CHANGELOG.md.

The first step would be for @mblaney to determine if SemVer is being adhering. The CHANGELOG.md file would be a good place to state that. Personally, I would be very happy to see this happen.

@mblaney mblaney merged commit d1d80f3 into simplepie:master Dec 24, 2021
@mblaney
Copy link
Member

mblaney commented Dec 24, 2021

thanks @Art4 happy for you to keep the changelog updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants