Prepare for 1.0.0 release

.promu.yml

@@ -2,6 +2,8 @@ go:
     cgo: true
 repository:
     path: github.com/mesosphere/mesos_exporter
+build:
+    flags: -a
 tarball:
     files:
         - LICENSE

CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
 and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
-## [1.0.0-rc3] - 2017-09-02
+## [1.0.0] - 2017-09-02
 ### Changed
 - Build releases with cgo enabled. This allows the exporter to use the system cert store
   which can simplify deployments significantly.

README.md

@@ -34,7 +34,7 @@ When using HTTP authentication, the following values are read from the environme
 Usually you would run one exporter with `-master` for each master and one
 exporter for each slave with `-slave`. Monitoring each master individually
 ensures that the cluster can be monitored even if the underlying Mesos cluster
-is in an degraded state.
+is in a degraded state.
 
 - Master: `mesos_exporter -master http://localhost:5050`
 - Agent: `mesos_exporter -slave http://localhost:5051`
@@ -48,8 +48,8 @@ The necessary Prometheus configuration could look like this:
   static_configs:
   - targets:
     - master1.mesos.example.org:9105
-    - master1.mesos.example.org:9105
-    - master1.mesos.example.org:9105
+    - master2.mesos.example.org:9105
+    - master3.mesos.example.org:9105
 
 - job_name: mesos-slave
   scrape_interval: 15s

VERSION

@@ -1 +1 @@
-1.0.0-rc2
+1.0.0