Clarify the release process doc
@@ -18,10 +18,11 @@ The release process is automated to some extent. The following steps describe th
1. Developer updates `README.md` and `RELEASE_NOTES.md` with new planned version.
2. Developer commits all changes in local working copy.
3. Developer triggers new version release using the following command: `$ ./gradlew release -Prelease.stage=final -Prelease.scope=[SCOPE]`, where `[SCOPE]` can be one of: `major`, `minor`, `patch` and determines which part of the version string `<major>.<minor>.<patch>` will be increased.
-4. Gradle builds new version string, creates new tag with it and pushes to the `origin`.
-5. Travis detects new tag and triggers a build.
-6. Travis [is instructed](.travis.yml#L23) to execute [release stage](https://docs.travis-ci.com/user/build-stages/) when on Git tag.
-7. In this stage [Gradle script](.travis.yml#L21) assembles plugin binaries (with new version) and uploads them to Bintray (credentials are stored as [secure variables](https://docs.travis-ci.com/user/environment-variables/#Defining-Variables-in-Repository-Settings) in Travis).
+4. Gradle executes a build on developer's machine which calculates new version string, creates new tag with it and pushes to the `origin`.
+5. When Gradle build is finished, developer's work is done and the rest of the release process is automated.
+6. After push to the `origin`, Travis detects new tag and triggers a build.
+7. Travis [is instructed](.travis.yml#L23) to execute [release stage](https://docs.travis-ci.com/user/build-stages/) when on Git tag.
+8. In this stage [Gradle script](.travis.yml#L21) assembles plugin binaries (with new version) and uploads them to Bintray (credentials are stored as [secure variables](https://docs.travis-ci.com/user/environment-variables/#Defining-Variables-in-Repository-Settings) in Travis). Also JavaDoc is published to `gh-pages` branch.
# Useful links
* [Semantic Versioning](http://semver.org/)
