16 Dec
2004
16 Dec
'04
2:04 p.m.
Am Donnerstag, 16. Dezember 2004 13:51 schrieb Casper Hornstrup:
The problem I'm trying to solve is that if you
generate the ChangeLog
before the release, you need to go through all commit messages to find the
important ones. When you commit a particular change you know if it is
important enough to include in the ChangeLog.
as a variation to this, add a file to
the tree, "ChangeLog" (or even
"ReleaseNotes", for something more highlevel) and add comments to this as you
go like you would in the commit message
less clutter in the commit logs and all information is in a single spot. with
each release, either clear the file or add some header to separate released
information from new one as part of release engineering.
eg.
= current =
* done this (gvg)
* done that (ekohl)
* completed something else (sedwards)
= 0.2.5 (released 2004-12-24) =
...
patrick mauritz
--
Besides a mathematical inclination, an exceptionally good mastery of
one's native tongue is the most vital asset of a competent programmer.