Marking release/v0.15

Signed-off-by: Eric Myhre <[email protected]>

CHANGELOG.md

@@ -1,7 +1,13 @@
-recent /// not yet released
+v0.15 -- tip -- 2017 Apr 25
 ---------------------------
 
-- *your changes here!*
+Portability and internal systems updates galore: v0.15 should quietly make things better.  No major shakeups to formulas or APIs.
+
+Have you seen the new projects in the ecosystem?
+[Reppl](https://github.com/polydawn/reppl/) brings pipelining tools to the table, so you can now compose complex build processes with multiple formulas easily.
+[r2k8s](https://github.com/polydawn/r2k8s) demonstrates integrating Repeatr and Kubernetes, making it possible to run services in k8s, as well as use k8s clusters as resources for running builds.
+Repeatr might not be changing much in this release, but there's a lot of other stuff to play with!
+
 - Change: `runc` executor updated!  Repeatr now references a runc release from the 1.0rc3+ region (build specified in a formula, and reproducible).
 - Change: the working directory will now always be ensured to be owned and writable by the container process UID.  (This is followup to the "cradle" system introduced back in v0.11, and if necessary can be disabled the same way as before.)
   - This makes it much easier to have inputs that are placed inside the working directory!  Previously that would cause directories to be implicitly created as necessary, potentially resulting in a CWD that was unwritable to UID>0.  Now, such input configuration may still result in such implicit directory creation, but the CWD itself will consistently be writable, which is usually what the user expects.

cmd/repeatr/main.go

@@ -42,7 +42,7 @@ func Main(
 		Name:      "repeatr",
 		Usage:     "Run it. Run it again.",
 		UsageText: "Repeatr runs processes in containers, provisioning their inputs and saving their outputs using reliable, immutable, content-addressable goodness.",
-		Version:   "v0.14+dev",
+		Version:   "v0.15",
 		Writer:    stderr,
 		Commands: []cli.Command{
 			{