Consider Continous Delivery

[averagehat]

No description provided.

[necrolyte2]

I think that we should definitely do this.
Should do it for all our major projects as well.

[necrolyte2]

So just to get an idea of what we are looking at doing here.

Workflow:

1. Checkout new feature/bugfix branch
2. code and other goodies
3. push new branch + Pull Request
4. Tests pass
5. Peer review
6. Merge PR into master
7. Tests pass
8. new release is auto generated from Travis with name such as current.version-commit-sha-beta or something similar(is this step needed? seems like this would be the staging portion of the release process?)
9. at some point a manual tag/release would be made where changelog and actual version created and pushed

So then we would probably want to somehow work in a version checker into the pipeline that could pull all release names from github(non-dev unless they somehow opt into beta releases) and then compare to current release and prompt user "New version X.Y.Z is available" and somehow make it easy for user to upgrade

[necrolyte2]

The hardest thing with this will be dealing with upgrading the config.yaml file