Release-Strategy.md

@@ -21,6 +21,7 @@ Each release branch will contain tags, one for each patch released under that ve
 * [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)
 * [R3 Milestone 7 deliverables - 0.10.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.10-Tagging-Notes)
+* [R3 Milestone 8 deliverables - 0.11.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.11-Tagging-Notes)
 
 ## Release Notes
 
@@ -64,4 +65,4 @@ After the release pipeline passes and/or you are satisfied with the results, cre
 
 ## 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.
\ No newline at end of file
+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.