In reply to Matt.

Oh sure, we can absolutely do things like auto-trimming and cutting down sizes and purging stuff. That will fix internal issues with size, certainly. Already working on that. :)

But nothing really beats writing your documentation with the end-user in mind. Even if we did something like purging old useless info and cutting down these things, that's still an automated process. My point is that changelogs, along with everything else in the readme.txt, should really be written to be useful to the end-user. Developers can go look at the SVN or Git history for details, or you can detail those in a separate document like changelog.txt.