From 902f0fed8a8323db20606adff66dd84d65bc29b4 Mon Sep 17 00:00:00 2001
From: Seth Vargo <sethvargo@gmail.com>
Date: Mon, 18 Jul 2016 22:42:20 -0400
Subject: [PATCH] Update RELEASE docs

---
 RELEASE.md | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/RELEASE.md b/RELEASE.md
index bb71c9556..0cb033e5c 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -24,10 +24,16 @@ targetted at Vagrant core members who have the ability to cut a release.
 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. Run the following command to upload to the releases site:
+1. Run the following command to upload the binaries to the releases site:
 
     ```
-    $ hc-releases -upload pkg/dist -publish -purge
+    $ hc-releases upload pkg/dist
+    ```
+
+1. Publish the new index files to the releases site:
+
+    ```
+    $ hc-releases publish
     ```
 
 1. Update `website/config.rb` to point to the latest version, commit, and push.