|
Depot Version Definitions
| |
| | |
Depot Version defines some basic aspects of versioning. They are...
A version object represents an instance of a version, e.g. 1.1.
So long as two versions can be checked for compatibility, and can be compared (for order), there are no other requirements on a version.
A compound version is a version object that contains version data information such as:
| Part | Description |
| Major | Major Version Number |
| Minor | Minor Version Number |
| Point | Point Version Number |
| Release Level | Release Level (alpha, ...) |
| Release Number | Release Number (e.g. 4 in dev4) |
| Build Number | Incrementing Build Number |
| Date | Build Date |
A version identifier identifies that entity this version applies to.
A version marker contains information to uniquely version an entity. It contains:
| Part | Description |
| Version Identifier | What is being versioned |
| Version | The version objectd |
| Attributes | User defined (e.g. the build user, build host) |
| Annotations | User defined |
A version specification can be applied to a version.
A version specification defines the text format of the version.
A version format mask is a string syntax for creating a version format
A constraint is a version assertion, perhaps a range or a boolean expression.
by Adam R. B. Jack
