docs/make-release: Added workflow for release build outcomes. Also corrected release branching info to show branches with 3 version components.

Author: NightOwl888

docs/images/release-build-outcomes.md

@@ -0,0 +1,16 @@
+This markup can be edited and converted to .svg or .png here:
+https://www.mermaidchart.com/app/projects/95759d78-db93-499c-ad66-0e3f698ba88c/diagrams/31dbd6bc-7ec8-4583-a456-55e3fe3f6cfc/version/v0.1/edit
+
+```mermaid
+flowchart TD
+    A[Tag + Push release branch] --> B{Draft Release generated?}
+    B -- Yes --> C[Review release notes]
+    C --> D[Check release artifacts]
+    D --> E[Publish Release to NuGet.org]
+
+    B -- No --> F[Check GitHub Actions logs]
+    F --> G[Fix problems]
+    G --> H[Delete failed tag]
+    H --> I["Reset AnalyzerReleases.Shipped.md<br/>header to {{vnext}} if needed"]
+    I --> A
+```

docs/images/release-build-outcomes.svg

@@ -0,0 +1,16 @@
+This markup can be edited and converted to .svg or .png here:
+https://www.mermaidchart.com/app/projects/95759d78-db93-499c-ad66-0e3f698ba88c/diagrams/35faa26e-5ccf-4433-962e-32f20496471c/version/v0.1/edit
+
+```mermaid
+flowchart LR
+    main[Main Branch]
+    release[Release Branch]
+    tag[Git Tag]
+    draft[Draft Release]
+    publish[Publish Release]
+
+    main -->|Prepare Release| release
+    release -->|Tag Version| tag
+    tag --> draft
+    draft -->|Manual Review| publish
+```

docs/images/release-workflow.md

@@ -101,11 +101,11 @@ nbgv prepare-release --nextVersion 2.0.1
 The command should respond with:
 
 ```console
-release/v2.0 branch now tracks v2.0.0 stabilization and release.
+release/v2.0.0 branch now tracks v2.0.0 stabilization and release.
 main branch now tracks v2.0.1-alpha.{height} development.
 ```
 
-The tool created a release branch named `release/v2.0`. Every build from this branch will be versioned 2.0.x, but the patch version may be incremented depending on the number of additional commits that will be added.
+The tool created a release branch named `release/v2.0.0`. Every build from this branch will be versioned 2.0.0, regardless of how many commits are added.
 
 ### Requires Stabilization
 
@@ -118,11 +118,11 @@ nbgv prepare-release beta --nextVersion 2.0.1
 The command should respond with:
 
 ```console
-release/v2.0 branch now tracks v2.0.0-beta.{height} stabilization and release.
+release/v2.0.0 branch now tracks v2.0.0-beta.{height} stabilization and release.
 main branch now tracks v2.0.1-alpha.{height} development.
 ```
 
-The tool created a release branch named `release/v2.0`. Every build from this branch will be given a unique pre-release version starting with 2.0.0-beta and ending in a dot followed by one or more digits.
+The tool created a release branch named `release/v2.0.0`. Every build from this branch will be given a unique pre-release version starting with 2.0.0-beta and ending in a dot followed by one or more digits.
 
 ---------------------------------------------
 
@@ -235,6 +235,10 @@ The release process is mostly automated. However, a manual review is required on
 4. Abort the release to try again
 5. Publish the release to deploy the packages to NuGet.org
 
+<p align="center">
+  <img src="images/release-build-outcomes.svg" alt="Release Build Outcomes" width="40%" align="center" />
+</p>
+
 ### Create a Draft Release
 
 Tagging the commit and pushing it to the GitHub repository will start the automated draft release. The progress of the release can be viewed in the [GitHub Actions UI](https://github.com/apache/lucenenet-codeanalysis-dev/actions). Select the run corresponding to the version tag that is pushed upstream to view the progress.