Delete default release.scope and update doc
MODIFY
doc/RELEASE.md
doc/RELEASE.md
@@ -21,15 +21,10 @@ The release process is automated to some extent. The following steps describe th
1. Developer updates `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
-```
-`release` task will use the default value for `release.scope` parameter which is `patch`. It is defined in the [`gradle.properties`](gradle.properties) file. If necessary, developer can override it by executing 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.
-
+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.

DELETE
gradle.properties
-
-# Can take the form of either `major`, `minor`, or `patch`
-release.scope=patch
-
-# Defined here for documentation purposes. When ready
-# to do a release the user should pass this along on
-# the command line for a 1 time execution.
-#
-# release.stage=final
-

Delete default release.scope and update doc