Skip to content

Changes

Page history
Update Release Strategy authored by Chad Leong's avatar Chad Leong
Hide whitespace changes
Inline Side-by-side
Release-Strategy.md
View page @ 533e09f8
......@@ -16,9 +16,13 @@ Each release of OSDU libraries and services will have a major/minor version pair
These releases are created as branches with the prefix `release/` so that the release can be updated with additional patches later. Patches of this nature will not introduce new features but only apply bug fixes or minor updates.
## Version Tags
## Tags
Each release branch will contain tags, 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.
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.
All QA and pre-shipping deployments are made using the tags to ensure alignment and consistency.
## [Tagging Notes](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Tagging-Notes)
......