Release Process As CI Job

[drewdaemon]

Background

I think some automation around the release-HubJS-and-wrap-it-back-into-monorepo process could really save time and make people more excited to build code in HubJS.

Problems with current process

The current release process is subject to various intermittent and consitent woes, many of which have to do with someone's local environment/Github perms. Among the possible scenarios.

• May not have permission to push to master which the release script tries to do
• May have enabled two-factor auth which seems to prevent a github tag from being created
• May not have NPM access rights
• May not be able to build a release because of some strange local issue
• Changelog only works for some, even when npm run c is used for every commit

Benefits of CI Job

I think that If we instead had a Travis job to release HubJS, it would ameliorate the situation.

• It could act as a single user with all the right privileges.
• It could be an isolated, clean environment, aleviating build woes
• Release could be cut without opening HubJS repo in a terminal or an editor

@tomwayson @dbouwman @ajturner