Modify release cycle via publish
Modify release cycle via publish

With this change we take up a release cycle similar to many Github
projects:
- Development is done in a single master branch
- Stable releases are tagged with current point release

Development versions are published to S3 as MAJ.MIN-dev, and
release versions are published as MAJ.MIN - thus even though the
point version (MAJ.MIN.POINT) is updated, the version deployed
only references the minor release. This supports a fast
development cycle where devel and release versions can happen
several times a day without having to update deployment
definitions.

uva-its/ruby-awstools,uva-its/ruby-awstools,uva-its/ruby-awstools