[En-Nut-Discussion] Changelog for releases

Harald Kipp harald.kipp at egnite.de
Tue Aug 21 19:49:09 CEST 2012

Hi Ole,

On 21.08.2012 18:46, Ole Reinhardt wrote:

> My first intention was something like the kernel changelog:
> http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.5.2

Log entries of this quality can be achieved only by publishing patches in a mailing list first, get them reviewed (criticized, bashed) over and over again until an authority finally commits it or until the contributor gives up.

IMHO, our project is too small and the time of our developers is too limited. Our main goal is to get something running on the target, everything else has low priority.

> Ideally something like 
> http://git.videolan.org/?p=vlc.git;a=blob_plain;f=NEWS;hb=HEAD
> How can we achieve that every developer will cultivate it like this?

By giving a good example? ;-)

It's actually like that. For example, I never got the headers in compiler.h right. Now everyone just adds more stuff and it becomes more and more difficult to read and maintain this pile of sh*t. If you present a NEWS file like it is now, developers will simply add their SVN log entries. How should they know better?

But I fully agree, the VLC NEWS file is the way to go. So my initial


wasn't that bad, it was just too long.



More information about the En-Nut-Discussion mailing list