About project itself suggestion: add `CHANGELOG.md` file

[Zeroto521]

There are already have release notes on the release page.
Why add a changelog (or history) file?

Obviously, this is the result we could finally see.
But the path is hard to collect information.

Base on thinking, it should add a file to record change before a PR is merged.
And another benefit, all things could be traced in one file.

Use #623 to make an example.

# ChangeLog

## Version 1.9.0 (2021-??-??)

### New Features

- Add Add Glyph Icon Support (#623)

### Fixed Bugs

...

[JohnTheGr8]

Use the Releases page, instead of the tags page, and you can view more releases and their release notes in one place...

That said, I do agree that we should link the issues/PRs of each change.

[jjw24]

Don't think changelog file is necessary, it's just extra maintenance when you can get the same result by going to the releases page or go to the pr section and filter by releases tag and see all the release pr and details of the change. You can also now filter by 'milestones' and see what prs each of the release contains.

I do agree that we should link the issues/PRs of each change.

I am ok to implement this, i didnt do it because thought the average user would not need to look at prs and if you are a dev you can always go to the release prs to get the same info plus the associated prs.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[jjw24]

I also agree GitHub Releases page is sufficient for end users, and release PRs have been containing pr links for a while now, so will close as won't implement.

Feel free to re-open if further discussion is required.