Hi,
Just for my curiousity: what has happened to updating ChangeLog? It's been more that 200 commits to SVN since 0.44 and only several changes are reflected, no changes in ReleaseNotes as well. Maybe it's just my schizophrenia of course :)
Alexandre
Just for my curiousity: what has happened to updating ChangeLog? It's been more that 200 commits to SVN since 0.44 and only several changes are reflected, no changes in ReleaseNotes as well. Maybe it's just my schizophrenia of course :)
New features are notoriously forgotten to be added to the Release Notes, that's well-known. If the authors think other people can do a better job to describe their changes, they will be surprised, negatively. So their changes get bad reflection, pah, what do I care?
You forgot to look into the 0.44 Release Notes which is still updated with stable changes (at the top).
Finally, on Changelog, I'm personally against repetition of things that can be easily got from 'svn log'. But that's
my 2 cents, ralf
On 12/07/06, Ralf Stephan <ralf@...748...> wrote:
[ snip ]
Finally, on Changelog, I'm personally against repetition of things that can be easily got from 'svn log'. But that's my 2 cents, ralf
+1
I KEEP six honest serving-men; (They taught me all I knew) Their names are What and Where and When And How and Where and Who.
There is a ragged but detailed note about maintaining a Changelog at http://wiki.inkscape.org/wiki/index.php/ChangeLog , which IIRC correctly, predates the switch to svn . Can you suggest any changes to this which would be widely accepted and be useful to new committers?
FWIW, I feel that repetition is always, always to be avoided (see DRY, exempli grati http://c2.com/cgi/wiki?DontRepeatYourself ), and my first suggestion is that the svn log should answer the What? question: What was changed; and the Changelog, the Why?: Why was this done.
I think that it is more important to get something relevant and accurate into the Changelog, preferably as short as is reasonably possible, rather than spend much time and divert unnecessary effort into getting that log just right
Ben
$ svn log -r 12400:head -v --xml | svn2log.py
What else do you need? Those people not adding Why's to svn-logs won't do it in Changelog, either. Short log messages are an art, and it is definitely fun to try to fit What+Why into one line.
ralf
participants (3)
-
Alexandre Prokoudine -
Ben Fowler -
Ralf Stephan