Tether is harder to update due to a missing changelog

[EamonNerbonne]

I started using tether (which works brilliantly btw - thanks!) at version 0.5.2, and will update to 0.6.4 today.

However, that's hard to do because it's unclear what has changed since then (the commit history shows this is mostly documentation a few bugfixes).

A short changelog would be really helpful to clarify what aspects of an upgrade might need attention (which if I understand correctly is likely to be not much for 0.5.2 -> 0.6.4).

[davidosomething]

+1

[NicBright]

+1

[AsaAyers]

@geekjuice I don't know who owns the project but you tagged the last release. This issue is over a year old. Can we either get a changelog or close it with a clear "No, we're not going to provide a changelog"?

For anyone adventerous enough to try to look through the code you can use /compare/ to look through changes: v0.6.5...v0.7.2

Also, do you follow semver? Does v0.7 introduce some breaking change I should know about before I try this upgrade?

[geekjuice]

@AsaAyers I've actually been working on all tether related projects with tether being the final one. If you check projects like tooltip, drop, select, & shepherd, I've started to add changelogs.

In regards to semver, out contributing doc tried to highlight how we will start dealing with versioning. The basic gist is:

• None: Documentation updates
• Patch: Bug fixes
• Minor: Non-breaking feature added
• Major: Anything not backwards compatible from the current version

As far as v0.7, it doesn't seem like there is anything breaking and rather a few features were added. However, I wouldn't consider this project to follow semver quite yet, but hopefully in the upcoming update, it should.

Hope that helps and let me know if you have any other questions 👍

[AsaAyers]

👍 Thanks for the quick update.

[RobbieTheWagner]

We will be generating changelogs going forward.