Also add goreleaser install script (see #418).

README will be updated once the script is verified as working widely.

.goreleaser.yml

@@ -185,7 +185,7 @@ archive:
   name_template: '{{ .Binary }}-{{ .Version }}-{{ .Os }}-{{ .Arch }}{{ if .Arm }}v{{ .Arm }}{{ end }}'
   files:
     - COPYING
-    - README*
+    - README.md
 
 snapshot:
   name_template: SNAPSHOT-{{ .Commit }}

.travis.yml

@@ -4,7 +4,6 @@ install:
 - go get -t -v . ./regressiontests
 - gometalinter --install
 go:
-- 1.8.x
 - 1.9.x
 - 1.10.x
 script: go test -v . ./regressiontests

README.md

@@ -17,6 +17,7 @@
   - [What's the best way to use `gometalinter` in CI?](#whats-the-best-way-to-use-gometalinter-in-ci)
   - [How do I make `gometalinter` work with Go 1.5 vendoring?](#how-do-i-make-gometalinter-work-with-go-15-vendoring)
   - [Why does `gometalinter --install` install a fork of gocyclo?](#why-does-gometalinter---install-install-a-fork-of-gocyclo)
+  - [Many unexpected errors are being reported](#many-unexpected-errors-are-being-reported)
   - [Gometalinter is not working](#gometalinter-is-not-working)
     - [1. Update to the latest build of gometalinter and all linters](#1-update-to-the-latest-build-of-gometalinter-and-all-linters)
     - [2. Analyse the debug output](#2-analyse-the-debug-output)
@@ -315,6 +316,13 @@ unusably slow when vendoring. The recursive behaviour can be achieved with
 gometalinter by explicitly specifying `<path>/...`. There is a
 [pull request](https://github.com/fzipp/gocyclo/pull/1) open.
 
+### Many unexpected errors are being reported
+
+If you see a whole bunch of errors being reported that you wouldn't expect,
+such as compile errors, this typically means that something is wrong with your
+Go environment. Try `go install` and fix any issues with your go installation,
+then try gometalinter again.
+
 ### Gometalinter is not working
 
 That's more of a statement than a question, but okay.