On Fri, 1 Feb 2002, Stephen Adkins wrote:
> Unless there is a clear consensus on how to do this, I will
> probably modify my "cvshistory" script to create the
> "CHANGES" file. ("cvshistory" is the script which creates the
> CVS Activity page and is located in the P5EEx/Blue/sbin directory.)
>
> http://www.officevision.com/pub/p5ee/activity.html
I really hate seeing changelogs that are collections of CVS comments. You
end up with lots of stuff like:
Rewrote algorithm to detect smells
Tweaked some variable names
...
They tend to be way too low level to be of interest to non-core
developers, people who just use the stuff. When I look at a changelog for
a Perl module, I want to to see what will affect me. Faster, more
features, API changes, etc. And that's it. Take the time to write a
changelog by hand based on the CVS changes or something.
-dave
/*==================
www.urth.org
we await the New Sun
==================*/
