@Elpie - I'll buy your argument of not upgrading because of accessibility issues but not for anything else.

Clients who do not want their sites worked on every few weeks obviously don't understand the nature of the web or web based software. Better education up front would solve this problem.

Sites that use custom plugins or code really should have taken it upon themselves to check with the developer to make sure it was coded in such a way to not interfere with the core of WordPress or provide deep integration without an easy way to upgrade the parent software. Again, this is what I consider to be a short sighted stance of using WordPress. Make a decision today, it haunts you tomorrow.

I see nothing wrong with that release cycle. It tells me that the folks behind WordPress are true to their 'Word' in that when their is a security issue that has been addressed, it will be pushed out asap for us to take advantage of. Let's flip the coin here and say that 2.8.4, 2.8.3, and 2.8.2, were not released because of the fear of too many releases in too short of time. Meanwhile, a security bulletin goes out to the public saying their is a major vulnerability in the software along with a proof of concept of the code. Now all the hackers get to exploit all the blogs they like. I prefer the former versus the latter.

As for a list of the files revised, generally, a page is created on the Codex for that specific version of WordPress. For example, WordPress 2.8.3 http://codex.wordpress.org/Version_2.8.3 however, you usually have to go to the WordPress Trac to download the changed files for the version changeset. I suppose it would be nice to have that information upfront as part of the release post.

The only patch the patch that occurred was I believe 2.8.3 which missed some things in 2.8.1. That was a blunder. The other things addressed separate issues.

If it weren't for the damn hackers and worms, we wouldn't have to worry about all of this lol.