Update readme (#498)

The main purpose of this PR is to test and investigate build triggers

Author: recrwplay

README.adoc

@@ -70,4 +70,4 @@ There are a few edge cases where we might want to work only on the current branc
 ** Open a draft PR against `dev`, with a label for the specific version it is targeting - this can be shared & reviewed in draft mode, but will not be mergeable until it is pointed at the next release.
 ** Create a feature branch from `dev`, to be merged into `dev` when appropriate.
 * When a new version is ready to published, the `5.x` branch will get a git tag, named with the exact version (for example, **5.1.0**), signifying that this point-in-time marks the completion of the work for that minor release.
-* The `dev` branch, with all merged content for the next release, will then be merged
+* Updates merged into the `dev` branch for the next release are cherry-picked into the `5.x` branch.