News for hackers. Stuff that matters.
Re:Keep a Changelog by ygra on Saturday July 28, 2018 @01:12AM (#17631660)
It's a bit annoying to document every single bugfix in a changelog too, though. At least I don't want to read dozens of lines like

- Fixed flickering lower-right pixel when hovering over close button with a stylus on devices with more than 300 % UI scaling applied.

- Fixed alignment issue in About dialog.

- Improved help text for Gizmo frobbing feature.

To me a changelog should prominently document changes in function and behaviour. I don't particularly care if an exception message got a typo fixed, but I do care about a new feature, if a login problem for a subset of users has been resolved or a crash under weird circumstances has been fixed.

Re:Keep a Changelog by craftyguy on Saturday July 28, 2018 @02:29AM (#17631885)
> At least I don't want to read dozens of lines like

I must be a crazy user, because I generally like reading through changelogs to see if an update is worth applying because it addresses a specific issue I am having, implements a new interesting feature I want to try, or fixes critical flaws.

Luckily, though, public bug trackers are generally a good way to find out at least the 'is my bug fixed' part without the changelog (your issue is closed as 'fixed in X.Y')

Re:Keep a Changelog by stared on Saturday July 28, 2018 @06:09AM (#17632465)
Yes, it is possible to mention such. It is not important for most users, but super important to ones affected by a given bug. Vide:

http://us.battle.net/sc2/en/game/patch-notes/3-9-0