Mana OTP releases

[InoMurko]

• OTP releases need to be versioned.
  Release configuration has no limitations on where it can pickup the release version/name. I think it's good branding if major releases have names :).
  If a git tag is a release (-major.minor.patch) we could use that. Or if the name is a problem, then a git tag could update a priv/release file.
• Building for multiple platforms (@atoulme ?)
  That puts pressure on devops and QA and acceptance testing. Do we need Windows? :)
• Customer issues (how good is our logging?)
  We need to review that as part of QA.
• Release testing (acceptance testing in CI, QA?)
  Acceptance testing: I've had good experience with Robotframework. It's easy and it's implemented in Python.
  Could we get someone doing QA part time?
  Testing release upgrades is also important.
  Security testing!
• When do we start with changelogs and how?
  We could postpone this until we decide when to roll out Alpha or Pre Alpha. Current PR merges don't have structure that would allow us to parse git history and create the changelog.