Release v2.0.0

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>

Bump version to v1.0.9

Signed-off-by: Marek Kochanowski <mkochanowski@redhat.com>

bump version for release

Bump version to v1.0.7

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>

version bump to v1.0.6

ssssss-off-by: Ryan Goulding <rgouldin@redhat.com>

Version bump for release

Signed-off-by: Charlie Wheeler-Robinson <cwheeler@redhat.com>

Release containerized solution

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>

Version bump for release

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>

Version bump for release

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>

Add in better descriptions of the existing test specs

Currently, we have very well documented reel.Handler instances.  In
fact, documentation could be guaranteed via API in the near future.

However, reel.Handlers are really just the building blocks for
composing larger test cases.  As such, we need to be more pedantic
about documenting our Ginkgo test specs.

Since Ginkgo does not appear to utilize or enforce any interface, this
is currently nearly impossible to do programmatically.  This change is
a low cost addition to README.md which explains in plain english what
each Ginkgo test spec actually tests.  It also provides hints for
well-aligned future work, but makes no commitment to delivering such
tests.

Signed-off-by: Ryan Goulding <rgouldin@redhat.com>