| ... | ... | @@ -63,19 +63,19 @@ They are mostly relevant to the developers while releases are being prepared. |
|
|
|
|
|
|
|
## Development timeline for milestones
|
|
|
|
|
|
|
|
Each OSDU milestone starts with about 1.5 months of development, followed by the checkpoints of: feature freeze, code freeze, code tagging process, deployment into pre shipping environment by CSP teams, and validation in pre shipping environment.
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Please note that:
|
|
|
|
* `Feature Freeze` is for the completion of features development on common code. No new features should be developed for this milestone 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`:
|
|
|
|
* No new features should be developed but 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
|
|
|
|
* On the day of `Code Tagging Start`, the release branch is forked from the default (main/master) branch. Release coordinator completes the code tagging.
|
|
|
|
* As soon as code tagging is completed, the tags are deployed to the `QA/Testing Platform Validation` environment.
|
|
|
|
* `Deployed to Pre Shipping` date is the target date for CSP teams to deploy the tagged milestone baseline into pre-shipping env so that preshipping 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.
|
|
|
|
* 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.
|
|
|
|
https://gitlab.opengroup.org/osdu/pmc/docs/-/blob/master/Planning/OSDU_Community_Milestone_Release_Process.docx
|
| ... | ... | |
