Updated README.md

Author: gh-andre

README.md

@@ -1,12 +1,21 @@
 # Test C++ Build Actions
 
 This is a test project that builds a small C++ program in a
-Debian container on an Ubuntu GitHub runner, and directly on
-a GitHub runner VM on Windows.
-
-A GitHub run number, which is the only variable that can be used
-for build numbers, is restarted from `1` when the workflow file
-is renamed. In addition to this, GitHub requires a workflow file
-to exist in `main` in order to run a workflow on any branch.
-This requires very careful workflow maintenance to match typical
-pipelines in other CI environments, such as Azure DevOps.
+Debian container on an Ubuntu GitHub runner, and on a GitHub
+runner VM on Windows.
+
+Each workflow YAML file represents the app version of the upcoming
+release, which in this demo case are `3.2.0` and `2.8.1` versions.
+
+The `3.2.0` workflow file  builds a candidate for the next dot-zero
+release, which would be branched into `3.2.x` for patch releases.
+
+The `2.8.1` workflow on the `main` branch is necessary because
+GitHub will not run a workflow file on a branch unless there is
+one on the `main` branch, so it's a dummy file that exists only
+for the purpose of surfacing the real workflow file on the `2.8.x`
+branch.
+
+Every time a release has been done, each respective workflow file
+must be renamed, so the build numbers would be restarted from `1`
+for the next target release.