update release guides

Even though it makes sense to only bump the quickstart guides after we
have cut a bootkube release, the conformance scripts use the quickstart
guide by overwriting the bootkube container image to use but not the
kubelet version. Lets make this change and accept that the quickstart
guides will have a temporary version skew between updating hyperkube and
releasing the image, but the the person doing the release via the
conformance scripts will at least run the correct host hyperkube.

Author: Patrick Baxter

RELEASING.md

@@ -11,6 +11,8 @@
 - Update on-host kubelet versions (`KUBELET_VERSION`)
     - hack/multi-node/user-data.sample
     - hack/single-node/user-data.sample
+    - hack/quickstart/kubelet.master
+    - hack/quickstart/kubelet.worker
 
 ### Update conformance test k8s version
 
@@ -59,11 +61,6 @@ PUSH_IMAGE=true ./build/build-image.sh
 
 Note: the quickstart guides use the release images, so we should not update them until after building/pushing new release.
 
-Update on-host kubelet version (`KUBELET_VERSION`)
-
-- hack/quickstart/kubelet.master
-- hack/quickstart/kubelet.worker
-
 Update the bootkube image version (to latest release)
 
 - hack/quickstart/init-master.sh (`BOOTKUBE_VERSION`)