...
Each ONAP component (microservice) will have a SemVer version number that follows the SemVer specification: MARKETING/MAJOR.MARKETING.MINOR.PATCH.
ONAP will use a marketing version number (e.g. "London") as the MARKETING version number in the SemVer version number of each component.
The MARKETING/MAJOR
will represent the usual ONAP update cycle, e.g. 11 (Kohn), 12 (London), 13 (Montreal), marketing releases version number
the MINOR will be used to represent incompatible API changes ,
the
PATCH version number will represent
new functionality in a backward-compatible manner
& number will represent backward-compatible bug fixes
.
This will allow the marketing version to be directly incorporated into the version number while still following the SemVer specification.
And basically everything is shifted one component to the "right" and from a traditional SemVer-Point-of-View.
An example of versions:
- for Kohn (Marketing version 11, and therefore all MAJOR numbers are 11 as well)
- AAI: 11.4.5
- SDC: 11.1.1
- CDS: 11.69.0
- Component without PTL: 11.69.1
- Kafka: 7.1.2
- Keycloak: 9.1.2
- for London (Marketing version 12, and therefore all MAJOR numbers are 12 as well)
- AAI: 12.4.6
- SDC: 12.2.1
- CDS: 12.69.0
- Component without PTL: 12.69.1
- Kafka: 7.1.3
- Keycloak: 9.1.3
- for Montreal (Marketing version 13, and therefore all MAJOR numbers are 13 as well)
- AAI: 13.4.6
- SDC: 13.2.1
- CDS: 13.69.0
- Component without PTL: 13.69.1
- Kafka: 7.1.4
- Keycloak: 9.1.4
...