🌱 update the release doc with missing steps and workarrounds

Co-authored-by: Bryce Palmer <[email protected]>

Author: camilamacedo86

RELEASE.md

@@ -31,7 +31,12 @@ the process was done to ensure that we have an aligned process under the org (si
 1. Create a new tag with the correct version from the new `release-<MAJOR.MINOR>` branch
 2. Add the changelog on it and publish. Now, the code source is released !
 
-### Announce the new release:
+### Update the website docs (https://book.kubebuilder.io/quick-start.html)
+
+1. Push a PR to update the `book-v3` branch with the changes of the latest release branch created (`release-<MAJOR.MINOR>`)
+2. Ping in the [Kubebuilder Slack channel](https://kubernetes.slack.com/archives/CAR30FCJZ) and ask for reviews.
+
+### When the release be done and the website update: Announce the new release:
 
 1. Publish the new release on the Slack channel, i.e:
 
@@ -44,6 +49,27 @@ For more info, see the release page: https://github.com/kubernetes-sigs/kubebuil
 
 2. An announcement email is sent to `[email protected]` with the subject `[ANNOUNCE] Kubebuilder $VERSION is released`
 
+## What to do if things goes wrong? How to release from my local env as a workaround?
+
+As a workaround we can release from locally by:
+
+1. Download google container builder: https://github.com/GoogleCloudPlatform/cloud-build-local
+2. Verify that you can use the cloud-build-local CLI tool
+3. Ensure that you are locally in the branch created for the release (`release-<MAJOR.MINOR>`)
+4. Ensure that it has no changes in the code source ( `git status`)
+5. Create the directory `cloudbuild` (`mkdir cloudbuild`)
+6. Then, update the file `build/cloudbuild_local.yaml` with:
+
+The following change is required for Goreleaser be able to add the binaries in the release page.
+
+```sh
+env: ["SNAPSHOT=1","GITHUB_TOKEN=your github token with access in the repo"]
+```
+**NOTE** You can create a token [here](https://github.com/settings/tokens/new).
+
+7. Then, update the file `build/build_kubebuilder.sh` to remove the flag `--snapshot` (Otherwise, the binaries will be built with snapshot git commit hash instead of the tag version)
+8. Run the command to trigger the release `$ cloud-build-local --config=build/cloudbuild_local.yaml --dryrun=false --write-workspace=./cloudbuild .`
+
 ## HEAD releases
 
 The binaries releases for HEAD are available here: