Changes

Page history
Adding M6 / 0.9 release link authored by David Diederich's avatar David Diederich
Hide whitespace changes
Inline Side-by-side
Release-Strategy.md
View page @ 23a818ec
...@@ -22,6 +22,7 @@ All release branches will have at least a ".0" patch, but may gain additional ta ...@@ -22,6 +22,7 @@ All release branches will have at least a ".0" patch, but may gain additional ta
- [R3 Milestone 3 deliverables - 0.5.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.5-Tagging-Notes) - [R3 Milestone 3 deliverables - 0.5.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.5-Tagging-Notes)
- [R3 Milestone 4 deliverables - 0.7.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.7-Tagging-Notes) - [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) - [R3 Milestone 5 deliverables - 0.8.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.8-Tagging-Notes)
- [R3 Milestone 6 deliverables - 0.9.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.9-Tagging-Notes)
## Development timeline for milestones ## Development timeline for milestones
Each OSDU milestone starts with about 1.5 months of development, followed by the 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 code tagging process, deployment into pre shipping environment by CSP teams, and validation in pre shipping environment.
...@@ -60,4 +61,4 @@ Once created, the tag will run a full protected pipeline as well. ...@@ -60,4 +61,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. 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"). 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