Getting ready for the v0.4.0 release

CHANGELOG.md

@@ -1,5 +1,26 @@
-## [0.4.0](https://github.com/fgrehm/devstep/compare/v0.3.1...next) (unreleased)
+## [0.4.0](https://github.com/fgrehm/devstep/compare/v0.3.1...v0.4.0) (2015-07-06)
 
+BREAKING CHANGES:
+
+  - Switched to `heroku/cedar:14` [image](https://registry.hub.docker.com/u/heroku/cedar/)
+    since it [has been brought up to speed](https://github.com/heroku/stack-images/pull/15)
+    with `progrium/cedarish`.
+  - Inline buildpack uses an array of string commands instead of an array with the command to run....
+
+IMPROVEMENTS:
+
+  - buildpacks/golang: Download test dependencies by default
+  - buildpacks/golang: Backport recent Golang buildpack updates
+  - buildpacks/golang: Bump default Go to 1.4.2
+  - buildpacks/php: Backport recent oficial Heroku buildpack updates
+  - buildpacks/php: Enable support for HHVM
+  - buildpacks/php: Composer's `vendor` dir is now kept inside images instead of the host machine when using the CLI
+  - buildpacks/python: Backport recent oficial Heroku buildpack updates
+  - buildpacks/python: Bump default Python to 2.7.10
+  - buildpacks/nodejs: Backport recent oficial Heroku buildpack updates (including support for iojs)
+  - buildpacks/nodejs: `node_modules` are now kept inside images instead of the host machine when using the CLI
+  - buildpacks/ruby: Bump default Ruby to 2.2.2
+  - buildpacks/ruby: Bump default Bundler to 1.10.5
 
 ## [0.3.1](https://github.com/fgrehm/devstep/compare/v0.3.0...v0.3.1) (2015-03-04)
 

docs/buildpacks/golang.md

@@ -29,5 +29,5 @@ This buildpack will also fix `$GOPATH/src` ownership so that you can safely
 mount a local checkout of a project dependency into the container without
 running into permission issues.
 
-To install a specific Go version, please use the `GO_VERSION` environmental
+To install a specific Go version, please use the `GOVERSION` environmental
 variable.

docs/buildpacks/python.md

@@ -14,7 +14,7 @@ You can also provide arbitrary releases Python with a `runtime.txt` file.
 
 Runtime options include:
 
-- python-2.7.8 (default)
+- python-2.7.10 (default)
 - python-3.4.1
 - pypy-1.9 (experimental)
 

docs/buildpacks/ruby.md

@@ -6,8 +6,8 @@ use [Bundler](http://bundler.io/) for dependency management. It will be used if
 a `Gemfile` is found.
 
 The installed Ruby will be the same one that gets installed on Heroku's Cedar 14
-stack with a fallback to a Ruby from the Cedar stack. By default Ruby 2.1.4 and
-Bundler 1.7.4 will be installed.
+stack with a fallback to a Ruby from the Cedar stack. By default Ruby 2.2.2 and
+Bundler 1.10.5 will be installed.
 
 To specify a Ruby version, use the [`ruby` directive](http://bundler.io/v1.6/gemfile_ruby.html)
 of your project's `Gemfile`, the `DEVSTEP_RUBY_VERSION` environmental variable or

docs/cli/installation.md

@@ -10,7 +10,7 @@ This one liner can handle it for you assuming that `$HOME/bin` is available
 on your `PATH`:
 
 ```sh
-L=$HOME/bin/devstep && curl -sL https://github.com/fgrehm/devstep-cli/releases/download/v0.3.1/linux_amd64 > $L && chmod +x $L
+L=$HOME/bin/devstep && curl -sL https://github.com/fgrehm/devstep-cli/releases/download/v0.4.0/linux_amd64 > $L && chmod +x $L
 ```
 
 Please note that the CLI is currently limited to connecting to a local `/var/run/docker.sock`
@@ -24,9 +24,7 @@ process will be aborted. This is to guarantee that files created within Docker
 containers have the appropriate permissions so that you can manipulate them
 on the host without the need to use `sudo`. This is currently a Devstep limitation
 that will be worked around in case there is enough demand or will be fixed once
-Docker adds support for user namespaces ([#6600](https://github.com/dotcloud/docker/pull/6600)
-/ [#6602](https://github.com/dotcloud/docker/pull/6602) / [#6603](https://github.com/dotcloud/docker/pull/6603)
-/ [#4572](https://github.com/dotcloud/docker/pull/4572)).
+Docker adds support for user namespaces.
 
 > The `1000` id was chosen because it is the default uid / gid of Ubuntu Desktop users
 that are created during the installation process. To work around this limitation

docs/getting-started.md

@@ -28,9 +28,7 @@ process will be aborted. This is to guarantee that files created within Docker
 containers have the appropriate permissions so that you can manipulate them
 on the host without the need to use `sudo`. This is currently a Devstep limitation
 that will be worked around in case there is enough demand or will be fixed once
-Docker adds support for user namespaces ([#6600](https://github.com/dotcloud/docker/pull/6600)
-/ [#6602](https://github.com/dotcloud/docker/pull/6602) / [#6603](https://github.com/dotcloud/docker/pull/6603)
-/ [#4572](https://github.com/dotcloud/docker/pull/4572)).
+Docker adds support for user namespaces.
 
 > The `1000` id was chosen because it is the default uid / gid of Ubuntu Desktop users
 that are created during the installation process. To work around this limitation
@@ -176,7 +174,7 @@ safely clean things up or disable the caching behavior at will.
 --------------------------------------
 
 In case your project require additional dependencies to work you can use the provided
-`fgrehm/devstep` or `fgrehm/devstep-ab` images as a starting point for your `Dockerfile`s.
+`fgrehm/devstep` image as a starting point for your `Dockerfile`s.
 
 The `fgrehm/devstep` image is the base image used for Devstep environments and
 requires you to manually trigger the build:
@@ -190,14 +188,6 @@ WORKDIR /workspace
 RUN CLEANUP=1 /opt/devstep/bin/build-project /workspace
 ```
 
-To make things easier, there's also a `fgrehm/devstep-ab:v0.3.1` image that
-does the same steps as outlined above automatically for you by leveraging `ONBUILD`
-instructions, trimming down your `Dockerfile` to a single line:
-
-```Dockerfile
-FROM fgrehm/devstep-ab:v0.3.1
-```
-
 By using a `Dockerfile` to build your images (instead of using `devstep build`)
 you'll be able to skip mounting project's sources on the container when running
 it and a simple `docker run -it <IMAGE-NAME>` should do the trick. **_Keep in mind

docs/introduction.md

@@ -37,7 +37,7 @@ extracted inside the container.
 
 Devstep can be used to build development environments in at least two different
 ways: from the provided Golang CLI or from `Dockerfile`s. To run the images built,
-you can use the provided `devstep hack` command, use other tools (like [Fig](http://orchardup.github.io/fig/))
+you can use the provided `devstep hack` command, use other tools (like [docker-compose](http://docs.docker.com/compose/))
 or just `docker run` them by hand.