- versions always increase
- versions are numbers
- versions are strings
- versions are semantic
- versions are decimals
- a major number of 1 or above means stable api
- versions with the same major number will have the same api
- versions have numbers, periods, and maybe a preceding v
- semantic is always the best way to go
- versions are consistent within a project
- semantic versions will never see double digits or triple digits within dots
- at least if you're using a semantic version people can compare it correctly
- versions will be consistent amongst projects in a given language or community
- semantic versioning cannot be represented as number or decimal
- as long as the versions increase the length of the version doesn't matter
- if versions have the same number they are equivalent
- in a given archive all code will have the same version
- semantic versions can only have 3 positions
- dates are bad for versions
- versions always increase by exactly one
- the least significant digit, character or group is the last one
- version numbers convey no runtime information
- over-the-wire and human-readable versions are fully convertible back and forth without any loss of information
- "10" is not a valid single digit
- Latest is always set to the latest semantic versioning