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

Get a proper changelog #366

Closed
balupton opened this issue Feb 12, 2015 · 1 comment
Closed

Get a proper changelog #366

balupton opened this issue Feb 12, 2015 · 1 comment

Comments

@balupton
Copy link

A commit history isn't a changelog, a changelog tells the users of the module what we need to be aware of. For instance, Chai v2 is out - that means somewhere there is a breaking change. I have no idea where or why that is, and I have to go through the commits to figure out.

It should be something like:

## v2.0.0 date

- We've updated blah
- We've fixed blah
- There is this breaking changes to be aware of

Examples:

@keithamus
Copy link
Member

@balupton thanks for the issue.

Our History.md is a list of commits - what has changed since the last release. You're very right, this isn't a changelog. We don't intend it to be one either though.

We also have a ReleaseNotes.md file in the project. This gives you more human readable set of notes about the release. It summarises the changes and has a paragraph about the breaking change. These release notes are also reflected in our Releases page (the Releases tab in github). For your convenience I've put the notes below:


2.0.0 / 2015-02-09

Unfortunately with 1.10.0 - compatibility broke with older versions because of
the addChainableNoop. This change has been reverted.

Any plugins using addChainableNoop should cease to do so.

Any developers wishing for this behaviour can use dirty-chai
by @joshperry

Community Contributions

Code Features & Fixes

Documentation fixes

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

No branches or pull requests

2 participants