Update release doc with current process
-## Steps to release octant via TravisCI (Deprecated)
+## Release Process
-`GITHUB_TOKEN` needs to be set with the "repo" scope to have access to private repositories. This token should be regenerated once the project is public. See [TravisCI docs](https://docs.travis-ci.com/user/travis-ci-for-private/#how-can-i-make-a-private-repository-public) for changing from a private to public project.
+Drone Cloud is used along with goreleaser for releases. This document is used to track the manual processes that occur during a release process.
-1. The version is tracked in the Makefile. Update and merge the new version prior to release.
+### Update version
-2. Pull the change then run `make release`
+The version is tracked by a Makefile though `make version`. Update this to the next version then commit the changes.
-3. A new build will be triggered then a draft of the artifacts will be available for review in GitHub Releases.
+### Generate Changelogs
-### Encrypt a token
+Each pull request should have a changelog entry in `/changelogs/unreleased`. Run `make changelogs` to condense each change into a single console output. Update for formatting and editing as needed.
-1. Download the Travis CLI ruby gem: `gem install travis`
+Follow the console output and remove old changelog entries. Then create the new changlog file in the format `CHANGELOG-X.Y.md`.
-2. Login with your GitHub account: `travis login --pro`.
+Finally, add the new changelog file under `CHANGELOG.md`.
-3. Generate the token through the heptibot GitHub account. Navigate to the project root and encrypt the token: `travis encrypt GITHUB_TOKEN="..." --add`. The token can only be decrypted by Travis CI, not the encrypter or owners of the repository.
+### Trigger a Release
-4. Commit the changes to `.travis.yml` and push.
+Once the above steps are completed, a user with write access to the repository will need to tag a commit then push the tag.
-## Steps to release octant manually
+```
+$ VERSION=$(make version)
+$ git tag -a $VERSION -m "$VERSION release"
+$ git push origin $VERSION
+```
-What you'll need:
+The release pipeline will trigger. If there are no errors, goreleaser will draft a release.
- - a GitHub token with repo scope enabled
- - an installation of rpmbuild
- - an installation of [goreleaser](https://goreleaser.com)
+### Publish Release
-Start the release process with the commands:
+Navigate to the releases page on Github. There should be a release in draft.
-```
-VERSION=v0.0.1
-git tag -a $VERSION -m "$VERSION release"
-git push origin $VERSION
-goreleaser --rm-dist
-```
+Remove the autogenerated commit log and replace with the one generated by the Makefile.
+
+After the release notes are updated, click `Publish release`.
-This will
- - create a [semver](http://semver.org) git tag
- - tag the latest commit
- - push the tag to the repo
- - build and push the release
