From 81718200a3e4bcb7daa25b580023082a9726623e Mon Sep 17 00:00:00 2001 From: Seth Vargo Date: Tue, 14 Jun 2016 20:33:19 +0200 Subject: [PATCH] Update RELEASE --- RELEASE.md | 45 ++++++++++++++++++-------- scripts/{bintray_upload.sh => sign.sh} | 0 2 files changed, 31 insertions(+), 14 deletions(-) rename scripts/{bintray_upload.sh => sign.sh} (100%) diff --git a/RELEASE.md b/RELEASE.md index ce63dd8cb..bb71c9556 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -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 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: - `git tag vX.Y.Z`. Push them. +1. Commit those changes and also tag the release with the version: - 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 - relative to the Vagrant repository. +1. Trigger an installer creation run within the HashiCorp Bamboo installation. + This will take around 45 minutes. - 1. Run the awkwardly-named `./scripts/bintray_upload.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. Download all the resulting artifacts into the `pkg/dist` folder relative to + the Vagrant repository on your local machine. - 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. diff --git a/scripts/bintray_upload.sh b/scripts/sign.sh similarity index 100% rename from scripts/bintray_upload.sh rename to scripts/sign.sh