The Problem

Changelogs decay more and more towards short messages — without full sentences, without punctuation, and with a lot of ambiguous abbreviations, et cetera which leads to misunderstanding and the necessity to ask for details or how the message should be interpreted.

The Solution

Take the time and mention all changes you consider potentially relevant; keep an eye on style, language and grammar; do not forget punctuation or salutation; avoid ambiguous abbreviations; and proof-read the message at least once before sending or publishing. is a personal policy that all Changelogs regardless of reader or subject will be as long and detailed as necessary and not castrated by arbitrary and artifical limits which just needlessly cripple what a user of your product may want to know about an update. It's that simple.

See also:,,,,,, and

Valid HTML · Valid CSS · WCAG 2.0, Section 508, and BITV conforming · Viewable with any browser · 100% hand-coded with GNU Emacs
About this site · FAQ · Blog · Idea: Martin Ebnöther and Axel Beckert · Thanks to: Christian Herzog and Erik Meltzer
Powered by: Debian GNU/Linux, Apache, and Embperl · Last modified: Sat Sep 29 18:15:01 2018 by Axel Beckert.