Skip to content

Commit

Permalink
Adding cherry-pick to release note docs
Browse files Browse the repository at this point in the history
  • Loading branch information
willdavsmith committed Sep 11, 2023
1 parent e085341 commit d9e8344
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/contributing/contributing-releases/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,8 @@ If sample validation passes, we can start the process of creating the final rele

1. After creating the pull request, there should be an automatically-generated release notes comment. Create a new release note document in the [release-notes](../../release-notes/) directory. Follow the directory's README.md for instructions on how to create a new release note document. Include this file in the release version pull request. [Example](https://github.com/project-radius/radius/pull/6092/files)

1. Cherry-pick the release notes into the release branch (see the "Patching" section for details). This will ensure that the release notes are included in the release branch. [Example](https://github.com/radius-project/radius/pull/6114/files)

1. Purge the [CDN cache](https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/66d1209e-1382-45d3-99bb-650e6bf63fc0/resourcegroups/assets/providers/Microsoft.Cdn/profiles/Radius/endpoints/radius/overview).
```bash
$ az login
Expand Down

0 comments on commit d9e8344

Please sign in to comment.