When you have to update your project's dependencies, you (presumably) look at the changelogs for each package to see if you can safely update. This experience varies wildly based on how well changes are tracked and documented (if at all). I'm looking to suss out what separates a great changelog from a mediocre one.<p><pre><code> - What bits of a changelog are most helpful / important?
- What's not helpful, but usually included?
- How should the document balance skimmability / comprehensiveness / readability?
- What projects have the most helpful changelogs?
</code></pre>
Thank you!
Overall I like the format and advice from <a href="https://keepachangelog.com/" rel="nofollow">https://keepachangelog.com/</a><p>We’ve adopted it at work and it’s nice to have a consistent format that is relatively noise free.