|
|
|
# Versioning Strategy
|
|
|
|
## Versioning Strategy
|
|
|
|
|
|
|
|
The overall versioning strategy for OSDU products is still in initial draft state. Members of The OSDU Forum can see and comment on the proposed governance.
|
|
|
|
The overall versioning strategy for OSDU products is still in its initial draft state. Members of The OSDU Forum can see and comment on the proposed governance.
|
|
|
|
|
|
|
|
[**Latest version of the strategy document**](http://osdu.projects.opengroup.org/pmc/work-products/versioning-strategy)
|
|
|
|
|
|
|
|
[**Common OSDU CI/CD Pipeline**](https://osdu.pages.opengroup.org/platform/ci-cd-pipelines/)
|
|
|
|
|
|
|
|
## Release Branches
|
|
|
|
|
|
|
|
Each release of OSDU libraries and services will have a major/minor version pair (such as "1.0") that represents the release. Release numbers that match across different services are meant to be considered a package -- that is, they were released at the same time. The specific numbers in the version are increased with each release (in the normal way), but importantly are not synchronized to any other milestone name, including monikers such as "R3" or "M1".
|
| ... | ... | |
