Upgrade Documentation

I do not know if other users have encountered this or if I am the only one. However I find the instructions for upgrades to be generic and not always applicable to the upgrade itself.

For example when I upgraded from 2.2.3 to 2.3 I have a few issues with a database error relating to categories. It was not after spending time on the forums and reading a few when I thought that the issues may have been due an incompatible plug-in. I deactivated all of my plugins and the reactivated each one to see which one(s) were causing issues.

In the future it would be nice when upgrading to provide a such information as:

Release Log – stating what file(s) are being added or modified

Known Issues – Issues that are know at the time of the release and any work around that may resolve the issue. This may include plug-ins that are no longer compatible, listing of error messages that may be encountered in regard to the upgrade, how to solve the error messages, and issues with platforms, servers, and Operating systems.

Any testing – Including the results of the test.

Issue / Change log – I know there is a nightly build section and the forums. However it would be nice if there was an area for user to log an issue, see the status of the issue, and see what other users have encountered it instead of having to troll through the forums to find it. It could be as simple of putting it into an MS Excel workbook for download.

Hopefully 2.4 will be much smoother and more understandable on how to upgrade it.

All I am trying to ask for is more clarity in release documentation so that if a problem is encountered it is in one area, the user does not have to spend a lot of time trolling through the forums, and does not have to read all of the messages on their dashboard to locate the information to trouble shoot their problem.