2017-10-26 17:08:19 +00:00
|
|
|
This guide provides step by step guidance for cutting a new release of Nomad.
|
|
|
|
|
|
|
|
1. Bump the version in `version/version.go`
|
|
|
|
2. Run `make prerelease`
|
|
|
|
3. Commit any changed, generated files.
|
|
|
|
4. On the Linux Vagrant run `make release`
|
|
|
|
5. `mv pkg/ pkg2/`
|
|
|
|
6. On a Mac, run `make release`
|
|
|
|
7. `mv pkg2/* pkg/`
|
|
|
|
8. `./scripts/dist.sh <version>`. Formating of <version> is 0.x.x(-|rcx|betax)
|
|
|
|
|
|
|
|
# Only on final releases
|
|
|
|
|
|
|
|
1. Add the new version to checkpoint.
|
|
|
|
|
|
|
|
# Modifying the webiste
|
|
|
|
|
|
|
|
Assuming master is the branch you want the website to reflect
|
|
|
|
|
|
|
|
1. On master, bump the version in `website/config.rb`
|
|
|
|
2. Delete the remote stable-website branch (`git push -d origin stable-website`)
|
|
|
|
3. Create the new stable webiste, `git checkout -b stable-webiste`
|
2017-10-26 17:10:17 +00:00
|
|
|
4. `git push origin stable-website`
|
2017-10-26 17:08:19 +00:00
|
|
|
5. In Slack run, `hashibot deploy nomad`
|