Release-Strategy.md

@@ -16,7 +16,8 @@ The tags will be named with a `v` prefix and will repeat the version number (suc
 All release branches will have at least a ".0" patch, but may gain additional tags if patches are applied after branch creation.
 
 -  [R2 Gitlab milestone - 0.3.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.3-Tagging-Notes)
--  [R3 Milestone 1 deliverables - 0.4.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.4-Tagging-Notes) 
+-  [R3 Milestone 1/2 deliverables - 0.4.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.4-Tagging-Notes)
+-  [R3 Milestone 3 deliverables - 0.5.0](https://community.opengroup.org/osdu/governance/project-management-committee/-/wikis/Release-0.5-Tagging-Notes)
 
 # Creation Process
 
@@ -39,4 +40,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.
\ No newline at end of file
+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.