I wasn't quite sure where to put this topic, moderators please move if you feel like it.
I'm still finding the upgrade process a little chaotic. It's that small things that sneak in unintended (As in the law of unintended consequences again). An new version can pass all the tests and still with a minor change break a specific server or break the accustomed workflow of users.
What about a little running list somewhere in docs of minor changes that have come with a .X (or even a .X.X) version like the loss of editing inline with assignments, changes in role hierachies, changes in flowplayer version and behaviour, changes in course formats . . . sort of a one stop shop focused on just the version upgrade to ask "is this what I see a feature or a bug or an unintended consequence".
Such a hypothetical list could have links to the tracker or a discussion. A first point of call with considering the upgrade to a new version. Some sort of focus on the Current upgrade path, which is what most will be looking at at any given time.
We actually all (as a community) are doing some wheel spinning doing lots of testing for ourselves and there are lost of duplicate posts on critical issues. See just as one example this blog post by Mark: http://www.markdrechsler.com/?p=878
And as a PS. Plugins remain a huge problem with version changes. I'm personally finding it hard to keep up with GIT, Google docs, Blogs, Messaging, Forums, Plugins database, Tracker, Dev and Docs as inputs. I am conscious I do not want to sent more stuff in the direction of developers if I have not done my homework.
Good news: https://tracker.moodle.org/browse/MDLSITE-2092 we may have notifications from the comments sections on the tracker to non-maintainers (ie regular users) soon. (Tx Aparup!!) I think this will help with keeping track of plugins.