| ... | ... | @@ -23,6 +23,18 @@ All release branches will have at least a ".0" patch, but may gain additional ta |
|
|
|
- [R3 Milestone 4 deliverables - 0.7.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.7-Tagging-Notes)
|
|
|
|
- [R3 Milestone 5 deliverables - 0.8.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.8-Tagging-Notes)
|
|
|
|
|
|
|
|
## Development timeline for milestones
|
|
|
|
Each OSDU milestone starts with about 1.5 months of development, following the code tagging process, deployment into pre shipping environment by CSP teams, and validation in pre shipping environment.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The code freeze date is important milestone for development teams. Below is the current planned date for code freeze for upcoming milestones:
|
|
|
|
|
|
|
|
- M5:
|
|
|
|
- M6: end of May - May 28, 2021
|
|
|
|
- M7: mid of Jul - Jul 16, 2021
|
|
|
|
- M8: end of Aug - Aug 27, 2021
|
|
|
|
|
|
|
|
# Creation Process
|
|
|
|
|
|
|
|
## Creating a new Release
|
| ... | ... | @@ -44,4 +56,4 @@ Once created, the tag will run a full protected pipeline as well. |
|
|
|
|
|
|
|
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 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 |
