Elaborate a little bit about the automatic release process.

luniehq · Nov 13, 2018 · 53e510d · 53e510d
1 parent cdef23b
commit 53e510d
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -20,6 +20,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 * [\#1472](https://github.com/cosmos/voyager/issues/1472) Added mock functionality for redelegation @fedekunze + @faboweb
 * [\#1501](https://github.com/cosmos/voyager/issues/1501) Vote on proposals through modal @fedekunze + @jbibla
 * [\1502](https://github.com/cosmos/voyager/issues/1502) A page for each proposal. @jbibla
+* [\1116](https://github.com/cosmos/voyager/issues/1116) Elaborate a bit about the release process. @NodeGuy
 
 ### Changed
 

diff --git a/docs/release.md b/docs/release.md
@@ -2,7 +2,10 @@
 
 ### Automatic Release
 
-There is an automatic release process setup. Just push to release and the CI will create a release candidate PR. If this is merged the CI will create and publish the release.
+When you're ready to publish a release, push code to the `release` branch.
+CircleCI will notice and automatically increment the patch level of the version
+number, create a tag, and generate a pull request. If the pull request is
+merged then CircleCI will use it to build applications for all three platforms and publish a release on GitHub.
 
 ### Manual Release