Why do so many CPAN developers get their Changes files so wrong?
Please update the change log! An ignored change log doesn't tell me if I need to upgrade your module.
The change date is important, but not as important as the version number. The date in the Changes file has an excellent chance of not being the date in the version dropdown on CPAN, so we can't correlate the two. Put your version number in there.
Put your most recent changes at the top. When people click on changes, they usually want to see the most recent ones and scrolling down is annoying.
For each change set, put the most important changes at the top. If you have a long change set (shorter is better), it's easy to miss the "incompatible API change" buried halfway through.
If your bug fix has an RT number, please put it in there. Many times the ticket will have important information we don't want to lose.
If someone contributed a patch please list them in the changes file. Sometimes if an author doesn't have the time to respond, it's nice to talk to the person who's familiar with the code you're struggling with.
"Fixed regression" is not an appropriate change message because I need to know if the regression impacted me. "POD tweaks" is probably OK because it doesn't affect me.