Uselessnes of Changelogs

I just saw that a new Mail::SpamAssassin release has hit the CPAN. Unfortunately I am unable to conclude from the changelog whether I should upgrade or not. Can anyone but the developpers themselves learn anything from this?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

You write a manual, you write POD, you write code, you write tests, you write a piece of software with audience in mind, then when it comes to the CHANGES file - all this changes and things get very simplified and incomprehensible (at least in your example).

I will go over my changes file to see whether I make the same mistake.

More precisely, provide a CHANGE file for users and a ChangeLog for developers.

Perl is doing this wonderfully, I think. The various Changes* files are useful for the porters while the end-user gets a polished perldelta that is articulate, pleasant to read and always contains some additional bits of interest. The perldeltas are one of the things I always keep looking forward to when it comes to new Perl releases (I wonder whether there'll be a perldelta6).