Clarify release steps

microsoft · Nov 14, 2023 · a4d76fa · a4d76fa
1 parent e7aff8d
commit a4d76fa
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 10 deletions.
diff --git a/doc/release_process.md b/doc/release_process.md
@@ -2,7 +2,7 @@
 
 1. Rev versions as appropriate following semver.
     - Repo-wide versions can be found in `eng/targets/Release.props`
-    - Individual packages can version independently by adding the `<VersionPrefix>` and `<VersionSuffix>` properties directly in their `.csproj`
+    - Individual packages can version independently by adding the `<VersionPrefix>` and `<VersionSuffix>` properties directly in their `.csproj`.
     - We follow an approach of just releasing everything, even if the package has no changes. _Unless_ we intentionally do not want to release a package.
 2. Ensure appropriate `RELEASENOTES.md` are updated in the repository.
     - These are per-package and contain only that packages changes.
@@ -11,12 +11,12 @@
 3. Ensure `CHANGELOG.md` in repo root is updated.
 4. Tag the release.
     - `git tag v<version>`, `git push <remote> -u <tag>`
-5. Draft github release for new tag
-6. Kick off ADO release build (use the tag as the build target, enter `refs/tags/<tag>`)
-7. Validate signing, package contents (if build changes were made)
-8. Create ADO release
-9. Release to ADO feed
-10. Internal validation
-11. Release to nuget once validated (and dependencies are also released to nuget)
-12. Publish github draft release
-13. Delete contents of all `RELEASENOTES.md` files.
+5. Draft github release for new tag.
+6. Kick off [ADO release build](https://dev.azure.com/durabletaskframework/Durable%20Task%20Framework%20CI/_build?definitionId=29) (use the tag as the build target, enter `refs/tags/<tag>`)
+7. Validate signing, package contents (if build changes were made.)
+8. Create ADO release.
+    - From successful ADO release build, click 3 dots in top right -> 'Release'.
+9. Release to ADO feed.
+10. Release to nuget once validated (and dependencies are also released to nuget.)
+11. Publish github draft release.
+12. Delete contents of all `RELEASENOTES.md` files.
diff --git a/misc/misc.csproj b/misc/misc.csproj
@@ -22,6 +22,7 @@
     <None Include="$(RepoRoot)nuget.config" />
     <None Include="$(EngRoot)**" LinkBase="eng" />
     <None Include="$(RepoRoot).github/**" LinkBase="github" />
+    <None Include="$(RepoRoot)doc/**" LinkBase="doc" />
   </ItemGroup>
 
 </Project>