From f4b8d760e58c5d90e2d564f2c1e890e1fca44a19 Mon Sep 17 00:00:00 2001
From: Lorenzo Fontana <lo@linux.com>
Date: Mon, 16 Sep 2019 00:41:20 +0200
Subject: [PATCH] docs: describe the release process

Signed-off-by: Lorenzo Fontana <lo@linux.com>
---
 docs/release.md | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 docs/release.md

diff --git a/docs/release.md b/docs/release.md
new file mode 100644
index 00000000..a023a56d
--- /dev/null
+++ b/docs/release.md
@@ -0,0 +1,28 @@
+# kubectl-trace Release Process
+
+Our release process is automated using goreleaser.
+
+When we release we do the following process:
+
+- We decide together (usually in the #kubectl-trace channel in Kubernetes slack) what's the next version to tag
+- A person with repository rights does the tag
+- The same person runs goreleaser in their machine
+- The tag is live on Github with the artifacts
+- Travis will build the tag and push the related docker images
+
+## Release commands
+
+Tag the version
+
+```bash
+git tag -a v0.1.0-rc.0 -m "v0.1.0-rc.0"
+git push origin v0.1.0-rc.0
+```
+
+Run goreleaser, make sure to export your GitHub token first.
+
+```
+export GITHUB_TOKEN=`YOUR_GH_TOKEN`
+make cross
+```
+