Changes

Page history
Update Release Strategy authored by Mohammad Malekmakan's avatar Mohammad Malekmakan
Hide whitespace changes
Inline Side-by-side
Release-Strategy.md
View page @ 1764b65d
...@@ -27,6 +27,7 @@ Each release branch will contain tags, one for each patch released under that ve ...@@ -27,6 +27,7 @@ Each release branch will contain tags, one for each patch released under that ve
* [R3 Milestone 6](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-Notes#milestone-6-july-2-2021) * [R3 Milestone 6](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-Notes#milestone-6-july-2-2021)
* [R3 Milestone 7](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-Notes#milestone-7-august-20-2021) * [R3 Milestone 7](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-Notes#milestone-7-august-20-2021)
* [R3 Milestone 8 \[DRAFT\]](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-Notes#darft-milestone-8-september-24-2021-tentative)
## Development timeline for milestones ## Development timeline for milestones
...@@ -39,15 +40,14 @@ Below is the current planned date for upcoming OSDU milestone releases. Note tha ...@@ -39,15 +40,14 @@ Below is the current planned date for upcoming OSDU milestone releases. Note tha
* Code freeze date is for development teams to complete the new function development and integration in this release. * Code freeze date is for development teams to complete the new function development and integration in this release.
* Deployed to pre shipping date is target date for CSP teams to deploy the tagged milestone baseline into pre shipping env so that pre shipping team is ready to execute the tests. * Deployed to pre shipping date is target date for CSP teams to deploy the tagged milestone baseline into pre shipping env so that pre shipping team is ready to execute the tests.
* Public release date is after the validation from pre shipping team. The date may change depending on the validation results. * Public release date is after the validation from pre shipping team. The date may change depending on the validation results.
| Milestones | Code freeze date for Dev teams | Deployed to Pre Shipping | Public release date |
|Milestones|Code freeze date for Dev teams|Deployed to Pre Shipping|Public release date| |------------|--------------------------------|--------------------------|---------------------|
|----------|------------------------------|-------------------|-------------------| | M5 | Apr 9, 2021 | | May 2021 |
|M5 |Apr 9, 2021 | |May 2021 | | M6 | May 28, 2021 (end of May) | | Jul 2, 2021 |
|M6 |May 28, 2021 (end of May) | |Jul 2, 2021 | | M7 | Jul 16, 2021 (mid of Jul) | Jul 30, 2021 | Aug 20, 2021 |
|M7 |Jul 16, 2021 (mid of Jul) |Jul 30, 2021 |Aug 20, 2021 | | M8 | Aug 27, 2021 (end of Aug) | Sep 10, 2021 | Sep 24, 2021 |
|M8 |Aug 27, 2021 (end of Aug) |Sep 10, 2021 |Sep 24, 2021 | | M9 | Oct 22, 2021 (mid of Oct) | Nov 5, 2021 | Nov 19, 2021 |
|M9 |Oct 22, 2021 (mid of Oct) |Nov 5, 2021 |Nov 19, 2021 | | M10 | Jan 14, 2022 (mid of Jan) | Jan 28, 2022 | Feb 11, 2022 |
|M10 |Jan 14, 2022 (mid of Jan) |Jan 28, 2022 |Feb 11, 2022 |
* M10 cycle is longer with consideration of Christmas and new year holiday * M10 cycle is longer with consideration of Christmas and new year holiday
...@@ -65,4 +65,4 @@ After the release pipeline passes and/or you are satisfied with the results, cre ...@@ -65,4 +65,4 @@ After the release pipeline passes and/or you are satisfied with the results, cre
## Creating a new Patch ## Creating a new Patch
If a new patch is needed on a particular service, simply add the new commits to the release branch, either with cherry picks or merges. Then, wait for the new pipeline to succeed, and create a new tag on the branch incrementing the patch number (for example, "vX.Y.1"). If new CI-CD Pipelines are needed for the patch, don't forget to update the `.gitlab-ci.yml` file to reference the new version of the CI-CD includes. If a new patch is needed on a particular service, simply add the new commits to the release branch, either with cherry picks or merges. Then, wait for the new pipeline to succeed, and create a new tag on the branch incrementing the patch number (for example, "vX.Y.1"). If new CI-CD Pipelines are needed for the patch, don't forget to update the `.gitlab-ci.yml` file to reference the new version of the CI-CD includes.
\ No newline at end of file