No Changelog so unable to asess changes between 2.0 and 3.0 without reading the code

matthewwithanm / pilkit

Utilities and processors built for, and on top of PIL

BSD 3-Clause "New" or "Revised" License

196 stars 54 forks source link

No Changelog so unable to asess changes between 2.0 and 3.0 without reading the code #73

Open jberends opened 8 months ago

jberends commented 8 months ago

Please describe a changelog in each release as people rely on it in production. When makeing a major version bump we always do a check what has been changed.

either commit a CHANGELOG.md
either put a changelog in the release message
either put a changelog in the README.md

vstoykov commented 7 months ago

Yep it is a good idea to have one. If you have the time to do it, I'll be happy to merge it. For guidance you can use the git history: https://github.com/matthewwithanm/pilkit/compare/2.0...3.0