0.7.0

Use standard "images" target vs "dapper-image"

As a part of simplifying our building/testing experience, all projects
are moving to using a standard `make images` command to build whatever
container images they are responsible for.

This also reduces the need for Shipyard-specific docs.

Signed-off-by: Daniel Farrell <[email protected]>

0.6.1

This release includes subctl 0.6.0-rc0 and git commit linting support.

Framework fixes around connector pods

Release by default to 'devel' image tag

Since `latest` is commonly used to point to the latest *stable* release
of an image, we better use `devel` to point to the latest image unless
we specify the `latest` tag explicitly when releasing.

Also changed the release script to be able to accept multiple tags.

Signed-off-by: Mike Kolesnik <[email protected]>

Better version script handling

Use `git describe` to get a coherent version

Instead of the tag, or a `dev` value which dont give much information,
use `git describe` to generate a version that gives more information
such as the last tag, how far away is the commit from that tag, and also
a short commit hash and a dirty mark in case the working tree is dirty.

This can then be used to generate binaries with this version which
would be very useful in debugging.

As part of this change, the version is applied to released image tags to
get better information on the image.

Signed-off-by: Mike Kolesnik <[email protected]>

0.4.0 shipyard release

remove default reporter and file path since ginkgo creates them

Signed-off-by: pinikomarov <[email protected]>