Document versions of used infrastructure components

[Christian Berendt]

We use a lot of infrastructure components in specific version (e.g. MariaDB 10.0 or 2.x). Does requirements should be documented in our docs. This way it is easier to track them.

[Steven Dake (sdake)]

Agreed. Our docs are published based upon master, and I think this work can wait until after master is open as a result. Pushing to o1.

[Jeffrey Zhang (jeffrey4l)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA