## Current planned dates for upcoming OSDU milestone releases
_Note that the dates below might change depending on various reasons, announcement will be made in [PMC Slack channel](https://opensdu.slack.com/archives/C010VA9RD25) for further communication_
#### :snail: Updated Mercury Release Cadence starting M23 as announced in the 31-Jan-2024 Focal Point meeting
| Milestones | Code Dev Start | Feature Freeze | Code Tagging Start | Code Tagging Completed | Deployed to Pre Shipping | Public Release |
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".
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.
## 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. 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 layer.
All QA and pre-shipping deployments are made using the tags to ensure alignment and consistency.
Each OSDU milestone starts with about 1.5 months of development, followed by the checkpoints of `Feature Freeze`, `Code Tagging Start`, `Code Tagging Completed`, deployment into both QA and pre-shipping environment by CSP teams, and 3 weeks validation in pre-shipping environment.
-`Feature Freeze` is the target date for the completion of feature development on common code. No new feature should be planned and developed for this milestone release after this date.
- Between `Feature Freeze` and `Code Tagging Start`:
- No new features should be developed but existing merge requests (MRs) can still be merged if pending reviews and approvals
- Only bug fixes, CSP-specific changes, stabilizing pipeline
- On the day of `Code Tagging Start`, the release branch is forked from the default (main/master) branch. Any new feature/code development in the default branch now goes towards the next milestone release. Release coordinator completes the code tagging.
- As soon as code tagging is completed, the [tags](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-Strategy#tagging-notes) are deployed to the `QA/Testing Platform Validation` environment.
-`Deployed to Pre Shipping` date is the target date for CSP teams to complete deployment of the tagged milestone baseline into pre-shipping environment so that pre-shipping team is able to execute UAT.
-`Public Release` date is after the confirmation and validation from pre-shipping team. The date may change depending on the validation results.
You may find additional notes about "CSP deployment to QA/Testing (aka "Platform Validation") and Preship environments" in this document.
## Current planned dates for upcoming OSDU milestone releases
_Note that the dates below might change depending on various reasons, announcement will be made in [PMC Slack channel](https://opensdu.slack.com/archives/C010VA9RD25) for further communication_
#### :snail: Updated Mercury Release Cadence starting M23 as announced in the 31-Jan-2024 Focal Point meeting
| Milestones | Code Dev Start | Feature Freeze | Code Tagging Start | Code Tagging Completed | Deployed to Pre Shipping | Public Release |
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".
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.
## 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. 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 layer.
All QA and pre-shipping deployments are made using the tags to ensure alignment and consistency.
Each OSDU milestone starts with about 1.5 months of development, followed by the checkpoints of `Feature Freeze`, `Code Tagging Start`, `Code Tagging Completed`, deployment into both QA and pre-shipping environment by CSP teams, and 3 weeks validation in pre-shipping environment.
-`Feature Freeze` is the target date for the completion of feature development on common code. No new feature should be planned and developed for this milestone release after this date.
- Between `Feature Freeze` and `Code Tagging Start`:
- No new features should be developed but existing merge requests (MRs) can still be merged if pending reviews and approvals
- Only bug fixes, CSP-specific changes, stabilizing pipeline
- On the day of `Code Tagging Start`, the release branch is forked from the default (main/master) branch. Any new feature/code development in the default branch now goes towards the next milestone release. Release coordinator completes the code tagging.
- As soon as code tagging is completed, the [tags](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-Strategy#tagging-notes) are deployed to the `QA/Testing Platform Validation` environment.
-`Deployed to Pre Shipping` date is the target date for CSP teams to complete deployment of the tagged milestone baseline into pre-shipping environment so that pre-shipping team is able to execute UAT.
-`Public Release` date is after the confirmation and validation from pre-shipping team. The date may change depending on the validation results.
You may find additional notes about "CSP deployment to QA/Testing (aka "Platform Validation") and Preship environments" in this document.
