## Current planned dates for upcoming OSDU milestone releases
## 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
#### :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 |
| Milestones | Code Dev Start | Feature Freeze | Code Tagging Start | Code Tagging Completed | Deployed to Pre Shipping | Public Release |
These pages are generated by scripts to report the status of the tagging process.
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.
They are mostly relevant to the developers while releases are being prepared.
@@ -144,14 +139,13 @@ Each OSDU milestone starts with about 1.5 months of development, followed by the
...
@@ -144,14 +139,13 @@ Each OSDU milestone starts with about 1.5 months of development, followed by the
Please note that:
Please note that:
-`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.
-`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`:
- 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
- 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
- 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.
- 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.
- 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.
-`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.
-`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
