diff --git a/HACKING.md b/HACKING.md
index f5cf0373db22..8f6693169703 100644
--- a/HACKING.md
+++ b/HACKING.md
@@ -26,12 +26,14 @@ Once a release has been created, it can be pushed:
 To cut an official tag release, we generally use the images built by [ci.openshift.redhat.com](https://ci.openshift.redhat.com)
 under the openshift3_ami job.
 
+1. Make sure the "openshift3_ami" job is passing
+1. Pause the merge queue by disabling the "process_pull_requests" job on [ci.openshift.redhat.com](https://ci.openshift.redhat.com)
 1. Create a new git tag `git tag v0.X.X -a -m "v0.X.X" HEAD`
-2. Push the tag to GitHub `git push origin --tags` where `origin` is `github.com/openshift/origin.git`
-3. Run the "openshift3_ami" job
-4. Once the images are pushed to the repository, run `OS_PUSH_TAG="v0.X.X" hack/push-release.sh`. Your tag must match the Git tag.
-5. Upload the binary artifacts generated by that build to GitHub release page
-6. Send an email to the dev list, including the important changes prior to the release.
+1. Tag the images that previously passed in the "openshift3_ami" build by running `OS_PUSH_TAG="v0.X.X" hack/push-release.sh`. Your tag must match the Git tag.
+1. Push the tag to GitHub `git push origin --tags` where `origin` is `github.com/openshift/origin.git`
+1. Select the last passing "openshift3_ami" job and click "Rebuild".  This is why it's important to pause the merge queue.  Otherwise another pull request could land.  This could lead to the git tag and the Docker image tags becoming out of sync.  However, if you push the tag before images exist with the corresponding tag in the Docker hub you will get test failures.
+1. Upload the binary artifacts generated by that build to GitHub release page
+1. Send an email to the dev list, including the important changes prior to the release.
 
 We generally cut a release before disruptive changes land.