Skip to content

Commit 80da6a6

Browse files
authored
Update release process docs (#8068)
1 parent e40de65 commit 80da6a6

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

documentation/release-process.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -97,11 +97,11 @@ The nightly image is `mcr.microsoft.com/dotnet/nightly/monitor`. The tag list is
9797
## Release to nuget.org and Add GitHub Release
9898

9999
1. Run the [Generate release notes](https://github.com/dotnet/dotnet-monitor/actions/workflows/generate-release-notes.yml) workflow, setting `Use workflow from` to the release branch. Review and merge in the PR created by this workflow.
100-
1. Start [release pipeline](https://dev.azure.com/dnceng/internal/_release?_a=releases&view=mine&definitionId=105). Allow the stages to trigger automatically (do not check the boxes in the associated dropdown). During creation of the release you must select the dotnet-monitor build to release from the list of available builds. This must be a build with the tag `MonitorRelease` and the associated `MonitorRelease` artifact (set `dotnet-monitor_build` to the pipeline run of `dotnet monitor` that is being released; set `dotnet-monitor_source` to the latest commit from `main`).
100+
1. **The day of the release** run the [dotnet-dotnet-monitor-publish](https://dev.azure.com/dnceng/internal/_build?definitionId=1444) pipeline. During creation of the release you must select the dotnet-monitor build to release from the list of available builds. This must be a build with the tag `MonitorRelease` and the associated `MonitorRelease` artifact. Set `DraftRelease` to false when ready to publish.
101101
1. The release will start the stage "Pre-Release Verification"; this will check that the above steps were done as expected. The name of the release will be updated automatically.
102-
1. Approve the sign-off step the day before the release after 8:15 AM PT, when ready to publish.
102+
1. Have the release approved by another team member.
103103
> [!NOTE]
104-
> After sign-off of the "Pre-Release Verification" environment the NuGet and GitHub release steps will automatically wait until 8:15 AM PT the next day.
104+
> Please note that approval will immediately start the next phase of the workflow; there is no delay until the next day.
105105
106106
The remainder of the release will automatically push NuGet packages to nuget.org, [tag](https://github.com/dotnet/dotnet-monitor/tags) the commit from the build with the release version, and add a new [GitHub release](https://github.com/dotnet/dotnet-monitor/releases).
107107

0 commit comments

Comments
 (0)