As a GUI maintainer, now that the UI has moved towards the container based build the prior build tooling needs to be disabled and removed.

Disable, remove, archive...

• Travis configuration, related custom release scripting, and README badge
• Update CONTRIBUTING documentation related to release process
• Archive the Curiosity-Build repository

Assumptions and questions

• Curiosity build repo, https://github.com/RedHatInsights/curiosity-frontend-build
• Consider displaying a Quay.io badge "container ready" on the README instead of the Travis build badge This was a nice to have but it appears disabled for the cloudservices Quay org... would have helped provide a status without needing to actively open the site
  • https://quay.io/repository/cloudservices/curiosity-frontend/status
• Confirm that CodeCov coverage is still coming through. There's an old facet that was being submitted through the Travis build
• Appears we may need a GitHub org admin to remove the Travis app from Github, apparently maintainers are no longer allowed to remove certain apps?!?  We disabled the "build on push" under Travis' settings
  • https://github.com/RedHatInsights/curiosity-frontend/settings/installations