Fix release URL and release docs.

Author: kabalin

docs/CHANGELOG.md

@@ -281,6 +281,7 @@ No unreleased changes.
 - `moodle-plugin-ci csslint` command.  Lints the CSS files in the plugin.
 
 [Unreleased]: https://github.com/moodlehq/moodle-plugin-ci/compare/3.0.0...master
+[3.0.1]: https://github.com/moodlehq/moodle-plugin-ci/compare/3.0.0...3.0.1
 [3.0.0]: https://github.com/moodlehq/moodle-plugin-ci/compare/2.5.0...3.0.0
 [2.5.0]: https://github.com/moodlehq/moodle-plugin-ci/compare/2.4.0...2.5.0
 [2.4.0]: https://github.com/moodlehq/moodle-plugin-ci/compare/2.3.0...2.4.0

docs/ReleaseNewVersion.md

@@ -13,17 +13,23 @@ Prior to tagging a release, ensure the following have been updated:
 * If this is a new major version, then the `.travis.dist.yml` and `doc/TravisFileExplained.md` need to be updated
   to use the new major version.  Any other version will automatically be used.
 
-When all the changes above have been performed, push them straight upstream to `master` (or create a standard PR
-to get them reviewed and incorporated upstream, but **avoid merge commit**, use "Rebase and merge" instead).
+When all the changes above have been performed, push them straight upstream to
+`master` or create a standard PR to get them reviewed and incorporated
+upstream. In the latter case, use your repo clone for PR - this way Packagist
+will not capture new branch in the list of tags and you will not end up having
+double CI build on Travis, also when merging PR, please **avoid merge commit**
+(use "Rebase and merge" option).
 
-Once all code and commits are in place and verified, you need to tag a release.
+Once all code and commits are in place and verified, you need to tag a
+release.
 
 There are two options: you can tag `master` branch `HEAD` and push using commands:
 
 ```bash
 $ git tag -a 3.1.0 -m "Release version 3.1.0"
 $ git push origin 3.1.0
 ```
+
 Alternatively, you can use GitHub interface to tag: click "Draft a new release" and specify
 tag using the interface (you can leave title field empty, tag will be used as
 title in this case) and click "Publish release".
@@ -35,6 +41,10 @@ to the latest release "assets" on GitHub. Verify it has worked correctly by
 navigating at
 [Releases](https://github.com/moodlehq/moodle-plugin-ci/releases).
 
+__Note:__ Before triggering tag build, make sure that Travis is not running any
+builds, otherwise tag build might not get triggered. If this happenened, you
+need to remove tag and push it again when Travis is not busy.
+
 If there is any problem with that automatic deployment, the artifact will need to be created manually. First build PHAR file manually:
 
 ```bash