-
Notifications
You must be signed in to change notification settings - Fork 978
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
Add a changelog #233
base: master
Are you sure you want to change the base?
Add a changelog #233
Conversation
Release notes for early releases have been taken from the GitHub releases. For the unreleased things on master I read the commit messages and picked the most significant ones.
@robryk Please take a look. |
CHANGELOG.md
Outdated
|
||
## v0.2 | ||
|
||
Released 2016-01-17. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wrong date.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
Initial release. | ||
|
||
<!-- Note that some of these are PRs, but GitHub will redirect anyway. --> | ||
[#1]: https://github.com/google/guetzli/issues/1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need this list of references? I thought #x just simply linked correctly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does in issues but not in standalone documents.
In preparation of the next release, I thought it would be nice to have a changelog in the repository itself.
Release notes for early releases have been taken from the GitHub releases. For the unreleased things on master I read the commit messages and picked the most significant ones.