@@ -18,9 +20,9 @@ These releases are created as branches with the prefix `release/` so that the re
## Tags
Each release branch will contain tag(s) once the release process is completed. The tags are immutable and they point to a specific commit in the release branch. In general, there is one for each patch released under that version. The tags will be named with a `v` prefix and will repeat the version number (such as "v1.0.0"). All release branches will have at least a ".0" patch but may gain additional tags if patches are applied after branch creation.
Each release branch will contain tag(s) once the release process is completed. The tags are immutable and they point to a specific commit in the release branch. In general, there is one for each patch released under that version. The tags will be named with a `v` prefix and will repeat the version number (such as "v1.0.0"). All release branches will have at least a ".0" patch but may gain additional tags if patches are applied after branch creation. The version number `0.X` refers to the version of the OSDU Data Platform and can be accessed via the `/info`[API endpoint in core services](https://community.opengroup.org/osdu/documentation/-/wikis/Core-Services-API-Docs).
For CSP-specific patches following the release, we will denote a CSP-specific tag, e.g. `v0.23.0-azure.1`. This contains similar common code as `v0.23.0` but with additional changes made on the CSP-specific SPI.
For CSP-specific patches following the release, we will denote a CSP-specific tag, e.g. `v0.23.0-azure.1`. This contains similar common code as `v0.23.0` but with additional changes made on the CSP-specific SPI layer.
All QA and pre-shipping deployments are made using the tags to ensure alignment and consistency.
...
...
@@ -69,7 +71,8 @@ They are mostly relevant to the developers while releases are being prepared.
