Detail the release process

Signed-off-by: Juraci Paixão Kröhling <[email protected]>

RELEASE.md

@@ -4,11 +4,20 @@ This project uses [Shipkit](http://shipkit.org) for most of the release manageme
 
 ## Automated
 
-1. Update the `CHANGELOG.md` with the changes for the last release. Most of the changes should have been added there already, but at least the release date has to be set.
+Assuming we have a `version.properties` with `0.31.1` as the next version, this is what's to be done:
+
+1. Update the `CHANGELOG.md` with the changes for `0.31.1`. Most of the changes should have been added there already, but at least the release date has to be set
 1. Get the change above merged
-1. Tag the release, like, `git tag release/v0.31.1` and push the tag to the main repository (`git push upstream v0.31.0`, if your `jaegertracing/jaeger-client-java` remote is called `upstream`)
+1. Tag the release build, like, `git tag release/v0.31.1` and push the tag to the main repository (`git push upstream release/v0.31.1`, if your `jaegertracing/jaeger-client-java` remote is called `upstream`)
+
+Once these steps are done, here's what happens:
+* Travis will trigger a `make release`
+* Our `travis/release.sh` is called, possibly updating the `version.properties` to match the release tag `0.31.1`
+* The Shipkit Gradle task `ciPerformRelease` is called, which builds, tags the version as `v0.31.1` and uploads the release `0.31.1` to Bintray
+* Bintray publishes the artifacts to Maven Central in a few minutes
 
-Once these steps are done, Travis will trigger a `make release`, our `travis/release.sh` will update the `version.properties` used by Shipkit, which then builds and uploads the release to Bintray. The artifacts then end up in Maven Central in a few minutes.
+Not automated yet:
+* [GitHub release](https://github.com/jaegertracing/jaeger-client-java/releases)
 
 ## Manual