## 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_
_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 to Venus Releases Cadence starting M23 as announced in the 31-Jan-2024 Focal Point meeting
_**PLEASE BARE IN MIND THE FOLLOWING TABLE WILL BE SOON DEPRECATED IN FAVOR OF THE ONE CENTRALISED IN PMC PORTAL - [HERE](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/home)**_
**_PLEASE BARE IN MIND THE FOLLOWING TABLE WILL BE SOON DEPRECATED IN FAVOR OF THE ONE CENTRALISED IN PMC PORTAL - _**[**_HERE_**](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/home)
| 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".
...
...
@@ -81,8 +77,7 @@ All QA and pre-shipping deployments are made using the tags to ensure alignment
These pages are generated by scripts to report the status of the tagging process.
They are mostly relevant to the developers while releases are being prepared.
These pages are generated by scripts to report the status of the tagging process. They are mostly relevant to the developers while releases are being prepared.
-`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.
You may find additional notes about "CSP deployment to QA/Testing (aka "Platform Validation") and Preship environments" in this document. https://gitlab.opengroup.org/osdu/pmc/docs/-/blob/master/Planning/OSDU_Community_Milestone_Release_Process.docx