From 838246e9a919705f649d2d9ba3fd92f6a9a0c683 Mon Sep 17 00:00:00 2001
From: Dan Lorenc <lorenc.d@gmail.com>
Date: Fri, 10 Jun 2016 06:56:31 -0700
Subject: [PATCH] Add a releasing doc.

---
 RELEASING.md | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)
 create mode 100644 RELEASING.md

diff --git a/RELEASING.md b/RELEASING.md
new file mode 100644
index 0000000000..43e4977d01
--- /dev/null
+++ b/RELEASING.md
@@ -0,0 +1,51 @@
+# Steps to Release Minikube
+
+## Create a Release Notes PR
+
+Assemble all the meaningful changes since the last release into the CHANGELOG.md file.
+See [this PR](https://github.com/kubernetes/minikube/pull/164) for an example.
+
+## Build and Release a New ISO
+
+This step isn't always required. Check if there were changes in the deploy directory.
+If you do this, bump the ISO URL to point to the new ISO, and send a PR.
+
+## Bump the version in the Makefile
+
+See [this PR](https://github.com/kubernetes/minikube/pull/165) for an example.
+
+## Run integration tests
+
+Run this command:
+```shell
+make integration
+```
+Investigate and fix any failures.
+
+## Tag the Release
+
+Run a command like this to tag it locally: `git tag -a v0.2.0 -m "0.2.0 Release"`.
+
+And run a command like this to push the tag: `git push upstream v0.2.0`.
+
+## Build the Release
+
+Run these commands:
+
+```shell
+GOOS=linux GOARCH=amd64 make out/minikube-linux-amd64
+GOOS=darwin GOARCH=amd64 make out/minikube-darwin-amd64
+```
+
+## Upload to GCS:
+
+```shell
+gsutil cp out/minikube-linux-amd64  gs://minikube/releases/$RELEASE/
+gsutil cp out/minikube-darwin-amd64  gs://minikube/releases/$RELEASE/
+```
+
+## Create a Release in Github
+
+Create a new release based on your tag, like [this one](https://github.com/kubernetes/minikube/releases/tag/v0.2.0).
+
+Upload the files, and calculate checksums.