Fix formatting in RELEASE.md
@@ -25,6 +25,7 @@ The release process is automated to some extent. The following steps describe th
./gradlew release -Prelease.stage=final -Prelease.scope=[SCOPE]
```
where `[SCOPE]` can be one of: `major`, `minor` or `patch`, and determines which part of the version string `<major>.<minor>.<patch>` will be increased.
+
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.
