haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update RELEASE

This commit is contained in:
Seth Vargo 2016-06-14 20:33:19 +02:00
parent 3ba53f2c06
commit 81718200a3
No known key found for this signature in database
GPG Key ID: 905A90C2949E8787
2 changed files with 31 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
RELEASE.md
View File

@ -4,25 +4,42 @@ This documents how to release Vagrant. Various steps in this document will
require privileged access to private systems, so this document is only require privileged access to private systems, so this document is only
targetted at Vagrant core members who have the ability to cut a release. targetted at Vagrant core members who have the ability to cut a release.
1. Update `version.txt` to the version you want to release. 1. Update `version.txt` to the version you want to release.
1. Update `CHANGELOG.md` to have a header with the release version and date. 1. Update `CHANGELOG.md` to have a header with the release version and date.
1. Commit those changes and also tag the release with the version: 1. Commit those changes and also tag the release with the version:
`git tag vX.Y.Z`. Push them.
1. Trigger an installer creation run within the HashiCorp Bamboo ```
installation. This will take around 45 minutes. $ git tag vX.Y.Z
$ git push --tags
```
1. Download all the resulting artifacts into the `pkg/dist` folder 1. Trigger an installer creation run within the HashiCorp Bamboo installation.
relative to the Vagrant repository. This will take around 45 minutes.
1. Run the awkwardly-named `./scripts/bintray_upload.sh` with the version 1. Download all the resulting artifacts into the `pkg/dist` folder relative to
that is being created. This must be run from the Vagrant repo root. the Vagrant repository on your local machine.
This will GPG sign and checksum the files.
1. Run `hc-releases -upload pkg/dist` to upload the releases to S3. 1. Run `./scripts/sign.sh` with the version that is being created. This must be
run from the Vagrant repo root. This will GPG sign and checksum the files.
1. Update `website/config.rb` to point to the latest version. Commit and push. 1. Run the following command to upload to the releases site:
1. Use Atlas `hashicorp/vagrant-www` to deploy the site by queueing a build. ```
$ hc-releases -upload pkg/dist -publish -purge
```
1. Update `website/config.rb` to point to the latest version, commit, and push.
1. Tell HashiBot to deploy in ``#deploys`
```
hashibot deploy vagrant
```
1. Update `version.txt` to append `.dev` and add a new blank entry in the
CHANGELOG, commit, and push.
1. Update [Checkpoint](https://checkpoint.hashicorp.com/control) with the new
version.

0
scripts/bintray_upload.sh → scripts/sign.sh
View File