Release Stage

[carlosthe19916]

We need to think about the release process of Xavier repositories. Here is a draft we can use in order to have our release workflow completed.
What this PR does:

• When a new tag is identified, Travis will create a new Release for us. However, we need to create and add a GITHUB_OAUTH_TOKEN into Travis settings using Travis` webpage.
• When a new tag is identified, Travis will create docker images and push them to Docker Hub. We need to create and add DOCKER_USERNAME and DOCKER_PASSWORD (can be a generated token) to Travis.

Suggestions:

• We can build the docker images and push them to Quay.io as well, it is just a matter of adding additional commands

[codecov-io]

Codecov Report

Merging #66 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #66   +/-   ##
=========================================
  Coverage     57.55%   57.55%           
  Complexity      438      438           
=========================================
  Files            69       69           
  Lines          1998     1998           
  Branches         90       90           
=========================================
  Hits           1150     1150           
  Misses          790      790           
  Partials         58       58

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 292c249...92730a3. Read the comment docs.

[jonathanvila]

Should we rethink this release process trying to align it with what's defined in document for MA going GA ? @mrizzi