update release docs with new release branch instructions

Signed-off-by: ehearneredhat <ehearne@redhat.com>

RELEASE.md

@@ -2,26 +2,34 @@
 
 ## Process
 
-To release a version “v0.X.Y” of Authorino in GitHub and Quay.io, follow these steps:
+To release a version “vX.Y.Z” of Authorino in GitHub and Quay.io, follow these steps:
 
-1. Pick a `<git-ref>` (SHA-1) as source.
+1. Create a release branch as source.
 
 ```shell
-git checkout <git-ref>
+git checkout release-vX.Y.Z
 ```
 
-2. Create a new tag and named release `v0.X.Y`. Push the tag to GitHub.
+2. Change the `version` field in `build.yaml` to `vX.Y.Z` and save. 
+
+```yaml
+# This is where the build configuration is stored.
+build:
+  version: vX.Y.Z
+```
+
+3. Create a new tag and named release `vX.Y.Z`. Push the tag to GitHub.
 
 ```shell
-git tag -a v0.X.Y -m "v0.X.Y"
-git push origin v0.X.Y
+git tag -a vX.Y.Z -m "vX.Y.Z"
+git push origin vX.Y.Z
 ```
 
 Then at the GitHub repository, create a new release from the tag you just pushed. One could start autogenerating the
 release notes and then write the change notes highlighting all the new features, bug fixes, enhancements, etc.
 ([example](https://github.com/Kuadrant/authorino/releases/tag/v0.9.0)).
 
-3. Run the GHA ‘Build and push images’ for the `v0.X.Y` tag. This will cause a new image to be built and pushed to quay.io/kuadrant/authorino.
+4. Run the GHA ‘Build and push images’ for the `vX.Y.Z` tag. This will cause a new image to be built and pushed to quay.io/kuadrant/authorino.
 
 ## Notes on Authorino’s automated builds