Correct outdated information in releasing doc
Remove outdated information and update it to be current.
6. Edit the release notes and make sure the binaries uploaded return the correct version
7. Perform the [image promotion process](https://github.com/kubernetes/k8s.io/tree/master/k8s.gcr.io#image-promoter)
8. Publish draft
-9. If it's a major release, notify `kubernetes-dev@googlegroups.com`
+9. Email `kubernetes-sig-cluster-lifecycle@googlegroups.com` to announce the release
## Manual
1. Make sure your repo is clean by git's standards
2. If this is a new minor release, create a new release branch and push to github, for example `release-0.2`
-3. Tag the repository and push the tag `git tag -s $VERSION`
+3. Tag the repository and push the tag `git tag -s -m $VERSION $VERSION`
4. Create a draft release in github and associate it with the tag that was just created
5. Checkout the tag you've just created and make sure git is in a clean state
-6. Run `make release-artifacts REGISTRY=us.gcr.io/k8s-artifacts-prod/cluster-api-aws MANAGER_IMAGE_TAG=${VERSION}`
-7. Attach the tarball to the drafted release
-8. Attach `clusterawsadm` and `clusterctl` to the drafted release (for darwin and linux architectures)
-9. Run `make docker-build docker-push REGISTRY=gcr.io/k8s-staging-cluster-api-aws MANAGER_IMAGE_TAG=${VERSION}`
-10. Perform the [image promotion process](https://github.com/kubernetes/k8s.io/tree/master/k8s.gcr.io#image-promoter)
-11. Write the release notes (see note below on release notes)
-12. Publish release
-13. Email `kubernetes-dev@googlegroups.com` to announce the release
-
-## Expected artifacts
-
-1. A container image containing the aws-provider manager binary
-2. A release tarball containing the manifest-templates and a script to generate
- the actual manifests
-3. `clusterctl`
-4. `clusterawsadm`
-5. Release notes
-6. Email to `kubernetes-dev@googlegroups.com` announcing the release
-
-## Output locations
-
-### Container image
-
-The container image will live in the registry `gcr.io/k8s-staging-cluster-api-aws`
-under the image name `cluster-api-aws-controller:<tag>` where `<tag>` is
-replaced by the version being released.
-
-### Manifests
-
-Manifests must be generated by hand.
-
-Running `make release-artifacts` will create a tarball that you can attach to
-the drafted release.
-
-### Binaries
-
-The two binaries produced by a release are the `clusterctl` binary and the
-`clusterawsadm` binary. There should be support for both darwin and linux architectures.
+6. Run `make release`
+7. Attach the files in the `out` directory to the drafted release:
+ 1. `clusterawsadm-darwin-amd64`
+ 2. `clusterawsadm-linux-amd64`
+ 3. `infrastructure-components.yaml`
+8. Perform the [image promotion process](https://github.com/kubernetes/k8s.io/tree/master/k8s.gcr.io#image-promoter)
+9. Write the release notes (see note below on release notes)
+10. Publish release
+11. Email `kubernetes-sig-cluster-lifecycle@googlegroups.com` to announce the release
### Release Notes
