github.com/superfly/nomad@v0.10.5-fly/dev/guides/releasing.md (about)

     1  This guide provides step by step guidance for cutting a new release of Nomad.
     2  
     3  1. Bump the version in `version/version.go`
     4  2. Run `make prerelease`
     5  3. Commit any changed, generated files.
     6  4. On the Linux Vagrant run `make release`
     7  5. `mv pkg/ pkg2/`. We move the compiled packages such that when we run step 6,
     8     the binaries are deleted.
     9  6. On a Mac, run `make release`
    10  7. `mv pkg2/* pkg/`. This moves all the binaries into the same folder and thus
    11     we are ready for releasing.
    12  8. Ensure you have the hc-release environment variables set for being able to
    13     read/write to S3. This can be retrieved from 1password.
    14  9. `./scripts/dist.sh <version>`. Formating of <version> is 0.x.x(-|rcx|betaX)
    15  10. Bump the version to the new dev version.
    16  11. Remove the generated files and commit
    17  
    18  # Only on final releases
    19  
    20  1. Add the new version to checkpoint.
    21  
    22  # Modifying the website
    23  
    24  Assuming master is the branch you want the website to reflect
    25  
    26  1. On master, bump the version in `website/config.rb`
    27  2. Delete the remote stable-website branch (`git push -d origin stable-website`)
    28  3. Create the new stable website, `git checkout -b stable-website`
    29  4. `git push origin stable-website`
    30  5. In Slack run, `hashibot deploy nomad`