Versioning Style Guide

We need a versioning style guide that specifies:

• how version labels look like (so they are consistent throughout the system);
• how version labels are implemented (so tools can read them from compiled binaries);
• how version labels tell you all you need to know about maturity, build target, and patch level.

We start with a {major}.{minor} scheme (no dates, no serial build numbers, no x.y.z or even longer constructs), and build from there. The end product should be a formal document fit for public release, since the Installer will enforce any shared ressources to carry compliant version labels - so any application designer must read, understand, and adopt this document.