Skip to content

Commit

Permalink
docs: ordered steps to release
Browse files Browse the repository at this point in the history
  • Loading branch information
leodido committed Sep 15, 2019
1 parent 1034689 commit 64577fa
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions docs/release.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,11 @@ Our release process is automated using [goreleaser](https://github.com/gorelease

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
1. We decide together (usually in the #kubectl-trace channel in Kubernetes slack) what's the next version to tag
2. A person with repository rights does the tag
3. The same person runs goreleaser in their machine
4. The tag is live on Github with the artifacts
5. Travis builds the tag and push the related docker images

## Release commands

Expand All @@ -22,7 +22,7 @@ git push origin v0.1.0-rc.0
Run goreleaser, make sure to export your GitHub token first.

```
export GITHUB_TOKEN=`YOUR_GH_TOKEN`
export GITHUB_TOKEN=<YOUR_GH_TOKEN>
make cross
```

0 comments on commit 64577fa

Please sign in to comment.